[kontinuity-dev-public] k8s Namespace autoset, but build stalls indefinitely

[Andrew Lee Rubinger]

On Mon, Jun 27, 2016 at 10:50 AM, Tomas Nozicka <tnozicka at redhat.com> wrote:

> On Ne, 2016-06-26 at 13:20 -0700, Andrew Lee Rubinger wrote:
> >
> >
> > On Sun, Jun 26, 2016 at 1:17 PM, Tomas Nozicka <tnozicka at redhat.com>
> > wrote:
> > > On Ne, 2016-06-26 at 13:13 -0700, Andrew Lee Rubinger wrote:
> > > >
> > > >
> > > > On Sun, Jun 26, 2016 at 11:32 AM, Tomas Nozicka <tnozicka at redhat.
> > > com>
> > > > wrote:
> > > > > On So, 2016-06-25 at 09:25 -0400, Ben Parees wrote:
> > > > > > You could remove that trigger and just manually start the
> > > build
> > > > > from
> > > > > >
> > > > >
> > > > > > On Jun 25, 2016 4:19 AM, "Andrew Lee Rubinger" <alr at redhat.co
> > > m>
> > > > > > wrote:
> > > > > > >
> > > > > > > Played around a bunch and I think it's this: The build is
> > > > > triggered
> > > > > > before Jenkins is up and running.
> > > > > > The sync plugin ought not care, when it comes up it should
> > > see
> > > > > the
> > > > > > build in the new state and process it. Please open an issue
> > > > > against
> > > > > > the sync plugin repo and tag Jimmi. (but we probably won't be
> > > > > > rebuilding the image during summit week even if we get a
> > > fix)
> > > > > > >
> > > > > > > Is there a more appropriate event we can use as a trigger
> > > like
> > > > > > "Jenkins probe succeeds"?
> > > > > > So your template is, upon instantiation, kicking off your
> > > > > pipeline
> > > > > > build? (presumably because you have a ConfigChangeTrigger on
> > > your
> > > > > > pipeline buildconfig definition)openshift once you know
> > > jenkins
> > > > > is
> > > > > > up, as a workaround.
> > > > > Andy, I have disabled the automatic trigger for the first build
> > > as
> > > > > Ben
> > > > > suggested. Better to run it manually then having to cancel it
> > > and
> > > > > do
> > > > > the same.
> > > > > https://github.com/redhat-kontinuity/jboss-eap-
> > > > > quickstarts/commit/09eb555f515dc38844a012b18ade5efa319986d8
> > > > OK, I agree; thank you!  Mind doing the same for the kitchensink
> > > > example (and the upcoming Node one from Rupali)?
> > > Sure, I will update those tomorrow with the fix for delayed
> > > deployment.
> > Thank you!
> >
> > BTW just ran through this demo with MartijnV (leader of the London
> > JUG; CEO of jClarity) to really positive reviews, which I'm hoping is
> > reflective of the type of response we can see to the features we've
> > been building. :)
> That's awesome!
>
> > Applying the two fixes you mention will basically eliminate the user
> > experience hiccups from the demo and really keep the message on-
> > point.
> It is all fixed now. + I put PR for Node.js app in place.
>

Tested and working and fantastic. :)

S,
ALR


>
> >
> > S,
> > ALR
> > >
> > > >
> > > > S,
> > > > ALR
> > > >
> > > > >
> > > > > >
> > > > > > >
> > > > > > > S,
> > > > > > > ALR
> > > > > > >
> > > > > > > On Fri, Jun 24, 2016 at 10:57 PM, Ben Parees <bparees at redha
> > > t.co
> > > > > m>
> > > > > > wrote:
> > > > > > >>
> > > > > > >>
> > > > > > >> On Jun 24, 2016 10:30 PM, "Andrew Lee Rubinger" <alr at redha
> > > t.co
> > > > > m>
> > > > > > wrote:
> > > > > > >> >
> > > > > > >> > Hi all:
> > > > > > >> >
> > > > > > >> > So with Ben's new changes in place (thanks!) the k8s
> > > > > namespace
> > > > > > is set in Jenkins kubernetes-plugin:
> > > > > > >> >
> > > > > > >> >   https://ibin.co/2lpVENzMzOGm.png
> > > > > > >> >
> > > > > > >> > This gets us an OpenShift build triggered properly, but
> > > it
> > > > > waits
> > > > > > indefinitely without ever kicking off the build in Jenkins:
> > > > > > >> >
> > > > > > >> >   https://ibin.co/2lpVJNi1p37O.png
> > > > > > >> >
> > > > > > >> > Manually triggering a second build in OpenShift calls
> > > into
> > > > > > Jenkins properly and completes as expected.
> > > > > > >> >
> > > > > > >> > So...race condition?  Tries to kick off a build before
> > > > > namespace
> > > > > > is set?
> > > > > > >>
> > > > > > >> No, the namespace is set in the jenkins config.xml before
> > > > > jenkins
> > > > > > after starts, so it's not that. (also it only affects slave
> > > > > > launching, not pipeline starting) But what it is i'm not
> > > sure.
> > > > > The
> > > > > > first build is created/started by you instantiating your
> > > > > template? I
> > > > > > think it's a question for jimmi as to why it doesn't see the
> > > new
> > > > > > openshift build and start the pipeline in response.
> > > > > > >>
> > > > > > >> >
> > > > > > >> > S,
> > > > > > >> > ALR
> > > > > > >> >
> > > > > > >> > --
> > > > > > >> > Red Hat Developer Programs Architecture
> > > > > > >> > @ALRubinger
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Red Hat Developer Programs Architecture
> > > > > > > @ALRubinger
> > > > >
> > > >
> > > >
> > > > --
> > > > Red Hat Developer Programs Architecture
> > > > @ALRubinger
> > >
> >
> >
> > --
> > Red Hat Developer Programs Architecture
> > @ALRubinger
>



-- 
Red Hat Developer Programs Architecture
@ALRubinger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/kontinuity-dev-public/attachments/20160628/fe7c9fd3/attachment.htm>