[Toaster] [RFC] - What's a build artifact?

[Paul Eggleton]

Hi Belen,

On Wednesday 16 April 2014 10:25:21 Barros Pena, Belen wrote:
> Our first go at Toaster was very much thinking of a local use case. From
> 1.7 we'll start focusing on the remote use case (this is a web application
> after all, right?).
> 
> One of the things we need to add is the ability to download build
> artifacts that have been produced (and are stored) on a remote build
> server. This brings up the question: what is a build artifact? I mean:
> what do you want to be able to download after a build?
> 
> Is it just rootfs files? Or is it also:
> 
> * cooker log
> * task logs
> * [your suggestion here]

Well, I would confine build artifacts as far as the user is concerned to 
deployed files; the interface for viewing logs would be separate even though 
they might be collected in the same manner. However deployed files still covers 
a number of different types of files:

* Rootfs / other filesystem images
* Kernel images
* Module tarballs
* Bootloader images (grub, u-boot, etc.)
* SDK installers
* Package files
* Firmware binaries?

People's own custom recipes may deploy other types of files as well (although 
they are likely to be along similar lines).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre