All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yi Zhao <yi.zhao@windriver.com>
To: "Flanagan, Elizabeth" <elizabeth.flanagan@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: Reducing nightly/release build artifacts.
Date: Fri, 28 Mar 2014 10:23:30 +0800	[thread overview]
Message-ID: <5334DD22.5070806@windriver.com> (raw)
In-Reply-To: <CAPhnLPDwbCTBNg4aPHqYpakMwEz-wCyBYD-fr_ap97JC1fDWfg@mail.gmail.com>

Hi Beth,


于 2014年03月27日 05:30, Flanagan, Elizabeth 写道:
> A list of exactly what files you use for QA would be grand.
>
> We can use http://autobuilder.yoctoproject.org/pub/nightly/20140326-1/
> as our base.

We don't use all qemu-lsb , beagleboard-lsb, routerstationpro-lsb, and 
p1022ds-lsb artifacts.
For the image type, we don't need minimal-dev and sato-dev.

Thanks,
Yi


>
> -b
>
> On Wed, Mar 26, 2014 at 2:22 PM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>> Hello Beth,
>>
>> On Wed, Mar 26, 2014 at 6:14 PM, Flanagan, Elizabeth
>> <elizabeth.flanagan@intel.com> wrote:
>>> I'd like to start looking at reducing the number of artifacts we're
>>> releasing both for our nightly builds (which is at 250,000 artifacts
>>> and .25 TB!) and releases.
>>>
>>> What I'm thinking is this:
>>>
>>> Reduce nightly:
>>> - Reduce ADT-REPO to just qemu* arches for all builds
>>> - If every QA team could provide me a list of what files they actually
>>> need I could reduce the published artifacts to *just* what is needed.
>>>
>>> Reduce releases:
>>> - Reduce ADT-REPO to just qemu
>>> - Don't release ipk/rpm/debs. Continue to release ipks through ADT
>>> - Don't release machines outside of BSP tarball /binary directory
>>>
>>> If folks who do QA could get me a list of all the files they use, we
>>> can start removing excess artifacts. I know this is a balance, but I'd
>>> really like us to start targeting our release artifacts to just the
>>> things we need.
>> I fully agree on that.
>>
>> Is there anything you need specifically from me?
>>
>> --
>> Otavio Salvador                             O.S. Systems
>> http://www.ossystems.com.br        http://code.ossystems.com.br
>> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>
>



  reply	other threads:[~2014-03-28  2:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26 21:14 Reducing nightly/release build artifacts Flanagan, Elizabeth
2014-03-26 21:22 ` Otavio Salvador
2014-03-26 21:30   ` Flanagan, Elizabeth
2014-03-28  2:23     ` Yi Zhao [this message]
2014-03-28  8:20       ` Georgescu, Alexandru C
2014-03-28 13:02   ` Otavio Salvador
2014-03-31 18:38     ` Flanagan, Elizabeth
2014-03-31 18:39       ` Otavio Salvador
2014-04-01  5:33       ` Yi Zhao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5334DD22.5070806@windriver.com \
    --to=yi.zhao@windriver.com \
    --cc=elizabeth.flanagan@intel.com \
    --cc=otavio@ossystems.com.br \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.