[RFC] - What's a build artifact?

[RFC] - What's a build artifact?

[Barros Pena, Belen]

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]

Thanks!

Belén

Re: [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

Re: [RFC] - What's a build artifact?

[Ravi Chintakunta]

I agree with Paul that logs can be separated from the build artifacts. I believe that logs would be of interest for a failed build and artifacts would be of interest for a successful build.

Build artifacts for download should include everything that is required for board bring up, application development and debugging, using the Eclipse ADT etc.

Thanks,
Ravi


>  -----Original Message-----
>  From: toaster-bounces@yoctoproject.org [mailto:toaster-
>  bounces@yoctoproject.org] On Behalf Of Paul Eggleton
>  Sent: Wednesday, April 16, 2014 9:54 AM
>  To: Barros Pena, Belen
>  Cc: toaster@yoctoproject.org
>  Subject: Re: [Toaster] [RFC] - What's a build artifact?
>  
>  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
>  --
>  _______________________________________________
>  toaster mailing list
>  toaster@yoctoproject.org
>  https://lists.yoctoproject.org/listinfo/toaster

Re: [RFC] - What's a build artifact?

[Reyna, David]

I would have added the projects "conf" files to allow a user to understand the project's configuration and/or clone it, but Belén's design has an import/export feature and that would appear to cover my use case.

As long as the build artifact class is extendible, then we can decide the fundamental list and still allow other adopters to extend as they see fit for their own purposes.

- David

> -----Original Message-----
> From: toaster-bounces@yoctoproject.org [mailto:toaster-
> bounces@yoctoproject.org] On Behalf Of Ravi Chintakunta
> Sent: Wednesday, April 16, 2014 10:39 AM
> To: 'Paul Eggleton'; BARROS PENA, BELEN
> Cc: 'toaster@yoctoproject.org'
> Subject: Re: [Toaster] [RFC] - What's a build artifact?
> 
> I agree with Paul that logs can be separated from the build artifacts. I
> believe that logs would be of interest for a failed build and artifacts would
> be of interest for a successful build.
> 
> Build artifacts for download should include everything that is required for
> board bring up, application development and debugging, using the Eclipse ADT
> etc.
> 
> Thanks,
> Ravi
> 
> 
> >  -----Original Message-----
> >  From: toaster-bounces@yoctoproject.org [mailto:toaster-
> >  bounces@yoctoproject.org] On Behalf Of Paul Eggleton
> >  Sent: Wednesday, April 16, 2014 9:54 AM
> >  To: Barros Pena, Belen
> >  Cc: toaster@yoctoproject.org
> >  Subject: Re: [Toaster] [RFC] - What's a build artifact?
> >
> >  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
> >  --
> >  _______________________________________________
> >  toaster mailing list
> >  toaster@yoctoproject.org
> >  https://lists.yoctoproject.org/listinfo/toaster
> --
> _______________________________________________
> toaster mailing list
> toaster@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/toaster