From: Chris Smart <chris@distroguy.com>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: Andrew Geissler <geissonator@gmail.com>,
Patrick Williams <patrick@stwcx.xyz>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Joel Stanley <joel@jms.id.au>
Subject: Re: openpower.xyz updates
Date: Tue, 11 Oct 2016 12:36:03 +1100 [thread overview]
Message-ID: <20161011013601.GA19444@distroguy.com> (raw)
In-Reply-To: <1476143058.16733.10.camel@aj.id.au>
[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]
On Tue, Oct 11, 2016 at 10:14:18AM +1030, Andrew Jeffery wrote:
>On Mon, 2016-10-10 at 11:09 -0500, Andrew Geissler wrote:
>> I noticed our gerrit trigger job to verify userid's was broken again
>> this morning. Looks like the trouble plugin (Git Client Plugin) was
>> upgraded again to the latest version. Anyone out there know why/who
>> did it? I'm going to put us back to 1.19.7 per my earlier comments.
>
>Joel and Chris Smart were looking at this yesterday. A job broke:
>
>https://openpower.xyz/job/openpower-op-build/184/console
>
>According to Chris it broke because of:
>
>https://bugs.eclipse.org/bugs/show_bug.cgi?id=428039
>
> 15:58 < csmart> joel, basically release() was replaced with close()
> and so any plugin that uses git needs to be updated
>
>Looks like we're stuck between a rock and a hard place.
>
Yep, I updated the git client plugin because openpower build couldn't
perform any git operations.
I didn't expect that to affect any comms with other Jenkins instances
though, that is strange. Why does the gerrit userid plugin rely on on
git client? Do you have a log or backtrace? Might help to try and track
it down.
-c
>Cheers,
>
>Andrew
>
>>
>> There's no fix per-se for this, jenkins is always a bit hit or miss
>> with it's latest LTS version working with the latest plugins. Best
>> thing we can do is when we schedule our next jenkins LTS upgrade, to
>> try all the latest plugins again.
>>
>> Andrew
>>
>> On Fri, Sep 30, 2016 at 8:12 AM, Patrick Williams <patrick@stwcx.xyz> wrote:
>> >
>> > On Fri, Sep 30, 2016 at 11:16:08AM +0930, Joel Stanley wrote:
>> > >
>> > > Okay. Do we plan to test the individual projects as part of an
>> > > openbmc/openbmc build in the future?
>> > >
>> > Yes. https://github.com/openbmc/openbmc/issues/382
>> >
>> > --
>> > Patrick Williams
>> _______________________________________________
>> openbmc mailing list
>> openbmc@lists.ozlabs.org
>> https://lists.ozlabs.org/listinfo/openbmc
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-10-11 1:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 11:07 openpower.xyz updates Joel Stanley
[not found] ` <CALLMt=rbR1usfKPt9G8kdUa2RaqRaaVEG3rV62wSBjaM59qi6Q@mail.gmail.com>
2016-09-30 1:07 ` Joel Stanley
2016-09-30 1:38 ` Patrick Williams
2016-09-30 1:46 ` Joel Stanley
2016-09-30 13:12 ` Patrick Williams
2016-10-10 16:09 ` Andrew Geissler
2016-10-10 23:44 ` Andrew Jeffery
2016-10-10 23:49 ` Joel Stanley
2016-10-11 1:36 ` Chris Smart [this message]
2016-10-11 1:43 ` Andrew Geissler
2016-10-11 2:00 ` Chris Smart
2016-10-11 2:05 ` Chris Smart
2016-10-11 2:06 ` Andrew Geissler
2016-10-11 2:12 ` Joel Stanley
2016-10-11 6:23 ` Joel Stanley
2016-10-12 5:36 ` Joel Stanley
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=20161011013601.GA19444@distroguy.com \
--to=chris@distroguy.com \
--cc=andrew@aj.id.au \
--cc=geissonator@gmail.com \
--cc=joel@jms.id.au \
--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.