From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: pidge@toganlabs.com, yocto@yoctoproject.org
Cc: joshua.g.lock@intel.com,
Monserrat Sedeno <monserratx.sedeno.bustos@intel.com>
Subject: Re: [[PATCHv5][yocto-autobuilder]] buildset.controller: Add build set to test new OS distribution in autobuilder
Date: Wed, 12 Oct 2016 14:46:10 -0500 [thread overview]
Message-ID: <57FE9302.1080600@linux.intel.com> (raw)
In-Reply-To: <1476269488.7502.5.camel@toganlabs.com>
[-- Attachment #1: Type: text/plain, Size: 4820 bytes --]
On 10/12/2016 05:51 AM, Beth 'pidge' Flanagan wrote:
> On Mon, 2016-10-10 at 09:54 -0500, Aníbal Limón 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]
>>
>
> Is this something that should be on the production servers? If so, I'll
> pull it later.
This patch is for the QA team for be able to test a new distribution to
be supported.
So isn't a common use to trigger this buildset in production servers,
that's the reason for the previous commit adding the buildset into
buildset-config.autobuilder-qa, i don't want to make hard copy of the
dependent buildsets because there implies more work for keep updated the
buildsets.
I understand the idea of make symlinks, if only buildsets aim to run in
production are in buildset-config.controller what will be the best
folder for put this nigthly-qa trigger buildset?.
Cheers,
alimon
>
> If not, please re-read my prior email. If this is going to be on it's
> own ab with a specific purpose then it should exist in it's own
> directory and have full access to all the buildsets it needs.
>
> Which means symlinks to those buildsets in buildset.controller.
>
> If it's the former, I'll pull tonight. If it's the latter, please
> resubmit this patch.
>
> -b
>
>
>> 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>
>> ---
>> buildset-config.controller/nightly-qa-distro.conf | 55
>> +++++++++++++++++++++++
>> 1 file changed, 55 insertions(+)
>> create mode 100644 buildset-config.controller/nightly-qa-distro.conf
>>
>> diff --git a/buildset-config.controller/nightly-qa-distro.conf
>> b/buildset-config.controller/nightly-qa-distro.conf
>> new file mode 100644
>> index 0000000..def4118
>> --- /dev/null
>> +++ b/buildset-config.controller/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': {}}},]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2016-10-12 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 14:54 [[PATCHv5][yocto-autobuilder]] buildset.controller: Add build set to test new OS distribution in autobuilder Aníbal Limón
2016-10-12 10:51 ` Beth 'pidge' Flanagan
2016-10-12 19:46 ` 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=57FE9302.1080600@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=joshua.g.lock@intel.com \
--cc=monserratx.sedeno.bustos@intel.com \
--cc=pidge@toganlabs.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.