From: msbarth <msbarth@linux.vnet.ibm.com>
To: Patrick Williams <patrick@stwcx.xyz>,
Andrew Geissler <geissonator@gmail.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Jenkins job for per-repository CI
Date: Fri, 18 Nov 2016 17:50:01 -0600 [thread overview]
Message-ID: <3c5a3bbe-6fa6-fa14-2e70-7f734de1769b@linux.vnet.ibm.com> (raw)
In-Reply-To: <20161118225429.6mytshalgitazutd@asimov>
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
Yes, that is the plan. This was just a step in getting the initial
scripts working correctly with Jenkins as the openpower.xyz Jenkins
server is different than the test Jenkins Andrew setup for me to
prototype in.
On 11/18/2016 04:54 PM, Patrick Williams wrote:
> On Fri, Nov 18, 2016 at 03:39:24PM -0600, Andrew Geissler wrote:
>> For initial prototype work, we created a jenkins job to trigger on
>> phosphor-event gerrit changes. That job is here -
>> https://openpower.xyz/job/phosphor-event-gerrit-trigger/
> Are you going to convert that over to a template job so that we do not
> need to create (and manage) a new Jenkins job for each repository?
>
>
>
> _______________________________________________
> openbmc mailing list
> openbmc@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc
[-- Attachment #2: Type: text/html, Size: 1651 bytes --]
next prev parent reply other threads:[~2016-11-18 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 21:39 Jenkins job for per-repository CI Andrew Geissler
2016-11-18 22:54 ` Patrick Williams
2016-11-18 23:50 ` msbarth [this message]
2016-11-21 0:47 ` Joel Stanley
2016-11-21 15:39 ` Matt Barth
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=3c5a3bbe-6fa6-fa14-2e70-7f734de1769b@linux.vnet.ibm.com \
--to=msbarth@linux.vnet.ibm.com \
--cc=geissonator@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
/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.