[kontinuity-dev-public] Visualizing Status for Pipeline Stages That Haven't Yet Started

[Andrew Lee Rubinger]

And to add some more context:

If I manually bump the version from 1.0.44-SNAPSHOT to 1.0.44, we get a
compilation error:

[ERROR]
/home/alr/business/jboss/git/fabric8io/openshift-jenkins-sync-plugin/src/main/java/io/fabric8/jenkins/openshiftsync/BuildConfigToJobMapper.java:[29,38]
cannot find symbol
[ERROR] symbol:   class JenkinsPipelineBuildStrategy
[ERROR] location: package io.fabric8.openshift.api.model

I don't know where JenkinsPipelineBuildStrategy is in kubernetes-model
1.0.44 or in upstream/master; appears to be gone?

Totally open to working on this, but need a buildable thing. :)  Let's try
to get me ramped up next week so I can help out!

S,
ALR

On Fri, Jun 3, 2016 at 6:33 PM, Andrew Lee Rubinger <alr at redhat.com> wrote:

> Thanks for that!  I'd like to dig in this weekend.
>
> On first run of "mvn clean install":
>
> [ERROR] Failed to execute goal on project openshift-jenkins-sync-plugin:
> Could not resolve dependencies for project
> io.fabric8:openshift-jenkins-sync-plugin:hpi:0.1-SNAPSHOT: Could not find
> artifact io.fabric8:kubernetes-model:jar:1.0.44-SNAPSHOT in
> repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/) -> [Help 1]
>
> Is there some other remote repo which is a dependency or do I need to
> build kubernetes-model on my own and install into my local Maven repo?
>
> S,
> ALR
>
>
> On Fri, Jun 3, 2016 at 11:49 AM, Jimmi Dyson <jdyson at redhat.com> wrote:
>
>> Cool! Instructions for local dev:
>>
>> 1. `oc login` to user with enough privileges to update build
>> configs/builds (I use cluster-admin for ease).
>> 2. Run `mvn hpi:run` to start dev Jenkins with required plugins
>> 3. Jenkins will be running at http://localhost:8080/jenkins
>> 4. Hack whatever you need - totally welcome to look at 56 while I work on
>> 70.
>>
>> Testing is all manual right now - yes I know this is bad but it;s just
>> the way it is right now. Anyone fancy adding some integration tests?
>> :)
>>
>> On 3 June 2016 at 16:38, Andrew Lee Rubinger <alr at redhat.com> wrote:
>> > Thanks for the note on #70; added that one to my lurking list. :)
>> >
>> > I'll let ya hack away; let's check in top of the week to see where
>> we're at
>> > -- and remember for any Java stuff I can help with, just get me
>> instructions
>> > for build/test and I'm there.
>> >
>> > S,
>> > ALR
>> >
>> > On Fri, Jun 3, 2016 at 11:03 AM, Fabiano Franz <ffranz at redhat.com>
>> wrote:
>> >>
>> >> Great, thanks Jimmi!
>> >>
>> >> On Fri, Jun 3, 2016 at 11:52 AM, Jimmi Dyson <jdyson at redhat.com>
>> wrote:
>> >>>
>> >>> Yeah I'm working on fixes for those right now. Not quite as simple as
>> >>> I would have hoped as we have to update the kubernetes client to
>> >>> handle PATCHes as opposed to the PUTs that it has always used
>> >>> successfully until now...
>> >>>
>> >>> On 3 June 2016 at 15:42, Fabiano Franz <ffranz at redhat.com> wrote:
>> >>> > +1 about 56, but in terms of priorities I'd say we *need* to
>> address 70
>> >>> > first. The build sync is broken, nothing (status, stages, etc) is
>> being
>> >>> > propagated back to the build in OpenShift at the moment.
>> >>> >
>> >>> > Fabiano Franz
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>> > On Thu, Jun 2, 2016 at 7:26 PM, Andrew Lee Rubinger <alr at redhat.com
>> >
>> >>> > wrote:
>> >>> >>
>> >>> >> Let's shine a light on this one:
>> >>> >>
>> >>> >>
>> https://github.com/fabric8io/openshift-jenkins-sync-plugin/issues/56
>> >>> >>
>> >>> >> So the underlying issue is that the openshift-sync-plugin is not
>> >>> >> currently
>> >>> >> propagating information about future stages, preventing the
>> OpenShift
>> >>> >> Console from building a view of the entire pipeline.
>> >>> >>
>> >>> >> A few questions:
>> >>> >>
>> >>> >> 1) Jimmi, would you mind running point for us to get an update on
>> >>> >> feasibility of a fix?
>> >>> >> 2) I'm available to work on this, but as noted in the comments
>> can't
>> >>> >> find
>> >>> >> instructions to run this component or test it (aside from a couple
>> of
>> >>> >> small
>> >>> >> unit tests); am I missing something that's outside the repo?
>> >>> >>
>> >>> >> So let's prioritize work here; folks are going to be excited to see
>> >>> >> visualized pipelines in OpenShift and 56 is a dependency. :)
>> >>> >>
>> >>> >> S,
>> >>> >> ALR
>> >>> >>
>> >>> >> --
>> >>> >> Red Hat Developer Programs Architecture
>> >>> >> @ALRubinger
>> >>> >>
>> >>> >> _______________________________________________
>> >>> >> kontinuity-dev-public mailing list
>> >>> >> kontinuity-dev-public at redhat.com
>> >>> >> https://www.redhat.com/mailman/listinfo/kontinuity-dev-public
>> >>> >>
>> >>> >
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > 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/20160603/4cefd1f6/attachment.htm>