All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: Bill Randle <bill.randle@gmail.com>
Cc: joshua.g.lock@intel.com, yocto@yoctoproject.org,
	Monserrat Sedeno <monserratx.sedeno.bustos@intel.com>
Subject: Re: [[yocto-autobuilder][PATCHv4]] ] Build sets to test new OS distribution in autobuilder
Date: Mon, 10 Oct 2016 09:51:15 -0500	[thread overview]
Message-ID: <57FBAAE3.5020609@linux.intel.com> (raw)
In-Reply-To: <CA+n--H_8Bc6ogKjxUDHUy+ec4=0_XvgUS1M-C6LDGAa-h-aD7g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4352 bytes --]



On 10/07/2016 07:04 PM, Bill Randle wrote:
> This version appears to ignore Beth's comments from yesterday where
> she said buildset-config.autobuilder-qa wasn't really the appropriate
> directory and suggested a different name, plus she said all buildable
> configs should be present or links to them. If the later is true, then
> not only should the patch use a different directory, but it should
> also populate that new directory with links to the other build config
> files referenced in this file.

Yes Bill, sorry i forget to move the buildset to buildset-config.controller.

I'll send another patch.

	alimon


> 
>     -Bill
> 
> On Fri, Oct 7, 2016 at 1:50 PM, Aníbal Limón
> <anibal.limon@linux.intel.com> wrote:
>> From: Monserrat Sedeno <monserratx.sedeno.bustos@intel.com>
>>
>> As part of the process to set new OS distribution as supported on Yoctoc Project
>> a new patch was created with the list of build sets that should be executed.
>>
>> Detailed information:
>> https://wiki.yoctoproject.org/wiki/Distro_Testing_Plan#Execute_Build_Sets
>>
>> Fixes [YOCTO #9905]
>>
>> Note:In order to add a new distro as supported all the build sets should be PASS
>>
>> Signed-off-by: Monserrat Sedeno <monserratx.sedeno.bustos@intel.com>
>> Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
>> ---
>>  .../nightly-qa-distro.conf                         | 55 ++++++++++++++++++++++
>>  1 file changed, 55 insertions(+)
>>  create mode 100644 buildset-config.autobuilder-qa/nightly-qa-distro.conf
>>
>> diff --git a/buildset-config.autobuilder-qa/nightly-qa-distro.conf b/buildset-config.autobuilder-qa/nightly-qa-distro.conf
>> new file mode 100644
>> index 0000000..def4118
>> --- /dev/null
>> +++ b/buildset-config.autobuilder-qa/nightly-qa-distro.conf
>> @@ -0,0 +1,55 @@
>> +[nightly-qa-distro]
>> +builders: 'example-worker'
>> +repos: [{'poky':
>> +            {'repourl':'git://git.yoctoproject.org/poky',
>> +             'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp', 'yocto':'meta-yocto', 'poky':'meta-poky'},
>> +             'branch':'master'}},
>> +        {'oecore':
>> +            {'repourl':'git://git.openembedded.org/openembedded-core',
>> +             'layerversion':'core',
>> +             'checkout':False,
>> +             'branch':'master'}},
>> +        {'bitbake':
>> +            {'repourl':'git://git.openembedded.org/bitbake',
>> +             'checkout':False,
>> +             'branch':'master'}},
>> +        {'eclipse-poky-neon':
>> +            {'repourl':'git://git.yoctoproject.org/eclipse-poky',
>> +             'checkout':False,
>> +             'branch':'neon-master'}},
>> +        {'meta-qt4':
>> +            {'repourl':'git://git.yoctoproject.org/meta-qt4',
>> +             'branch':'master'}},
>> +        {'meta-qt3':
>> +            {'repourl':'git://git.yoctoproject.org/meta-qt3',
>> +             'branch':'master'}}]
>> +props: [{'fp_date':{'prop_type':'StringParameter',
>> +                       'size': 20,
>> +                       'name': 'fp_date',
>> +                       'label':'Full Pass date:'}}]
>> +steps: [{'SetDest':{}},
>> +        {'CheckOutLayers': {}},
>> +        {'RunPreamble': {}},
>> +        {'TriggerBuilds': {'schedulerName': 'dist-build',
>> +             'waitForFinish': 'True',
>> +             'schedulerNames': {
>> +                 'nightly-oe-selftest': {},
>> +                 'nightly-oecore': {},
>> +                 'nightly-deb': {},
>> +                 'nightly-ipk': {},
>> +                 'nightly-world': {},
>> +                 'nightly-arm': {},
>> +                 'nightly-multilib': {},
>> +                 'nightly-x86-64-lsb': {},
>> +                 'nightly-x86': {},
>> +                 'nightly-x32': {},
>> +                 'poky-tiny': {},
>> +                 'nightly-qa-systemd': {},
>> +                 'nightly-qa-extras': {},
>> +                 'nightly-qa-targetbuilds': {},
>> +                 'nightly-qa-skeleton': {},
>> +                 'nightly-qa-logrotate': {},
>> +                 'nightly-qa-pam': {},
>> +                 'buildtools': {}},
>> +                 'eclipse-plugin-neon': {},
>> +             'schedulerNames_nowait': {}}},]
>> --
>> 2.1.4
>>


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2016-10-10 14:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 20:50 [[yocto-autobuilder][PATCHv4]] ] Build sets to test new OS distribution in autobuilder Aníbal Limón
2016-10-08  0:04 ` Bill Randle
2016-10-10 14:51   ` Aníbal Limón [this message]

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=57FBAAE3.5020609@linux.intel.com \
    --to=anibal.limon@linux.intel.com \
    --cc=bill.randle@gmail.com \
    --cc=joshua.g.lock@intel.com \
    --cc=monserratx.sedeno.bustos@intel.com \
    --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.