[infinispan-dev] Jenkins migration

Dan Berindei dan.berindei at gmail.com
Mon Apr 24 16:42:23 EDT 2017


Thanks Sebastian!

Looks like we can remove the claim plugin, too, because it doesn't work
with pipelines:

https://issues.jenkins-ci.org/browse/JENKINS-33969

Cheers
Dan

PS: I'm the one who installed the Blue Ocean plugin, but I thought it was
opt-in for every user. Sorry about that!


On Mon, Apr 24, 2017 at 2:19 PM, Sebastian Laskawiec <slaskawi at redhat.com>
wrote:

> Hey!
>
> I uninstalled Blue Ocean plugin. I think it's worth to have another look
> at it as soon as 1.1.0 is released [1].
>
> I also plan to migrate 2 TeamCity Agents into Jenkins very shortly (in 30
> mins).
>
> @Tristan - may I ask you to redirect ci.infinispan.org to our new
> installation: http://ec2-52-215-14-157.eu-west-1.compute.amazonaws.com/
>
> More comments inlined.
>
> Thanks,
> Sebastian
>
> [1] https://issues.jenkins-ci.org/browse/JENKINS-43751?
> focusedCommentId=296703
>
> On Mon, Apr 24, 2017 at 9:50 AM Radim Vansa <rvansa at redhat.com> wrote:
>
>> I've heard that the default UI in Jenkins was the reason why we went
>> with TC, and Blue Ocean was supposed to be the cure. Why was the default
>> UI dismissed in the first place?
>>
>
> Once BlueOcean was installed (I think by Dan or Gustavo), it replaced the
> default UI without asking.
>
>
>>
>> R.
>>
>> On 04/23/2017 07:14 PM, Adrian Nistor wrote:
>> > I also do not see much value in the current state of Blue Ocean.
>> > Better stick with the default ui.
>>
>
> +1
>
>
>> >
>> > On 04/21/2017 06:11 PM, Dan Berindei wrote:
>> >> Looks like the invalid "control characters from U+0000 through
>> >> U+001F" are the  ANSI escape codes used by WildFly to color output.
>> >> So we might be able to work around this by disabling the color output
>> >> in WildFly in our integration tests.
>>
>
> I think it's not worth to invest more time in this. Let's switch to
> default UI and then try out BlueOcean once 1.1.0 is out.
>
>
>> >>
>> >> OTOH I'm fine with removing the Blue Ocean plugin for now, because
>> >> its usability is sometime worse than the default UI's. E.g. when I
>> >> click on the build results link in GitHub, 99.999% of the time I want
>> >> to see the test results, but Blue Ocean thinks it's much better to
>> >> show me some circles with question marks and exclamation points
>> >> instead, and then keep me waiting for half a minute after I click on
>> >> the tests link :)
>>
>
> +1
>
>
>> >>
>> >> Cheers
>> >> Dan
>> >>
>> >>
>> >> On Fri, Apr 21, 2017 at 4:55 PM, Sebastian Laskawiec
>> >> <slaskawi at redhat.com <mailto:slaskawi at redhat.com>> wrote:
>> >>
>> >>     Hey!
>> >>
>> >>     As you probably have heard I'm migrating our TeamCity
>> >>     installation [1] into Jenkins (temporarily in [2]).
>> >>
>> >>     So far I've managed to migrate all Infinispan builds (with pull
>> >>     requests), C++/C# clients, JGroups and JGroups Kubernetes. I
>> >>     decided to use the new Pipeline [3] approach for the builds and
>> >>     keep the configuration along with the code (here's an example [4]).
>> >>
>> >>     The configuration builds /refs/pull/<PR>/head/ for Pull Requests
>> >>     at the moment. I will switch it back to /refs/pull/<PR>/merge/ as
>> >>     soon as our PR queue size is ~20.
>> >>
>> >>     Current pain points are:
>> >>
>> >>       * Blue Ocean UI doesn't show tests. It has been reported in
>> >>         [5]. The workaround is to use the old Jenkins UI.
>> >>       * Windows VM doesn't start on demand (together with Vittorio we
>> >>         will be working on this)
>> >>
>> >>     The rough plan is:
>> >>
>> >>       * Apr 24th, move other 2 agents from TeamCity to Jenkins
>> >>       * Apr 24th, redirect ci.infinispan.org
>> >>         <http://ci.infinispan.org> domain
>> >>       * May 4th, remove TeamCity
>> >>
>> >>     Please let me know if you have any questions or concerns.
>> >>
>> >>     Thanks,
>> >>     Sebastian
>> >>
>> >>     [1] http://ci.infinispan.org/
>> >>     [2] http://ec2-52-215-14-157.eu-west-1.compute.amazonaws.com
>> >>     <http://ec2-52-215-14-157.eu-west-1.compute.amazonaws.com>
>> >>     [3] https://jenkins.io/doc/book/pipeline/
>> >>     <https://jenkins.io/doc/book/pipeline/>
>> >>     [4]
>> >>     https://github.com/infinispan/infinispan/blob/master/Jenkinsfile
>> >>     <https://github.com/infinispan/infinispan/blob/master/Jenkinsfile>
>> >>     [5] https://issues.jenkins-ci.org/browse/JENKINS-43751
>> >>     <https://issues.jenkins-ci.org/browse/JENKINS-43751>
>> >>     --
>> >>
>> >>     SEBASTIANŁASKAWIEC
>> >>
>> >>     INFINISPAN DEVELOPER
>> >>
>> >>     Red HatEMEA <https://www.redhat.com/>
>> >>
>> >>     <https://red.ht/sig>
>> >>
>> >>
>> >>     _______________________________________________
>> >>     infinispan-dev mailing list
>> >>     infinispan-dev at lists.jboss.org
>> >>     <mailto:infinispan-dev at lists.jboss.org>
>> >>     https://lists.jboss.org/mailman/listinfo/infinispan-dev
>> >>     <https://lists.jboss.org/mailman/listinfo/infinispan-dev>
>> >>
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> infinispan-dev mailing list
>> >> infinispan-dev at lists.jboss.org
>> >> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > infinispan-dev mailing list
>> > infinispan-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>
>>
>> --
>> Radim Vansa <rvansa at redhat.com>
>> JBoss Performance Team
>>
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
> --
>
> SEBASTIAN ŁASKAWIEC
>
> INFINISPAN DEVELOPER
>
> Red Hat EMEA <https://www.redhat.com/>
> <https://red.ht/sig>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20170424/d54db6ac/attachment-0001.html 


More information about the infinispan-dev mailing list