From: "Lock, Joshua G" <joshua.g.lock@intel.com>
To: "anibal.limon@linux.intel.com" <anibal.limon@linux.intel.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [[PATCH][yocto-autobuilder]] bin/forcebuild.py: Add a script to support force a build
Date: Wed, 15 Feb 2017 13:57:04 +0000 [thread overview]
Message-ID: <1487167023.4342.3.camel@intel.com> (raw)
In-Reply-To: <589B34ED.7060100@linux.intel.com>
On Wed, 2017-02-08 at 09:10 -0600, Aníbal Limón wrote:
>
> On 02/08/2017 08:12 AM, Lock, Joshua G wrote:
> > On Wed, 2017-02-01 at 14:14 -0600, Aníbal Limón wrote:
> > > I know we have the remote_kick.py [1] script but i don't know if
> > > is
> > > currently on use also this new script support list the options in
> > > builders and specify custom ones via cmdline.
> >
> > I don't use remote_kick.py, I'm loathe to carry two scripts with a
> > similar purpose. Any idea how they differ?
>
> The remote_kick script has a fixed set of parameters like builder
> (nigthly), buildbot url (localhost:8010) and forces the same build.
>
> The new forcebuild script you can specify buildbot server url, user,
> password, builder and options (WEB inputs).
Thank you. I've queued up this patch for inclusion with a follow-on
patch that removes remote_kick with the above as reasoning.
Joshua
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
prev parent reply other threads:[~2017-02-15 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 20:12 [[PATCH][yocto-autobuilder]] bin/forcebuild.py: Add a script to support force a build Aníbal Limón
2017-02-01 20:14 ` Aníbal Limón
2017-02-08 14:12 ` Lock, Joshua G
2017-02-08 15:10 ` Aníbal Limón
2017-02-15 13:57 ` Lock, Joshua G [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=1487167023.4342.3.camel@intel.com \
--to=joshua.g.lock@intel.com \
--cc=anibal.limon@linux.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.