Re: [infinispan-dev] Jenkins migration

The test reporting seems broken: in the last master build [1] Jenkins reported 3 failures, but the console output shows: Tests run: 477, Failures: 0, Errors: 340, Skipped: 0 For the JCache TCK build. Not sure if it's the report that is not generated correctly or the plugin who publishes

Re: [infinispan-dev] Jenkins migration

Final update (I hope so)... Phew, it was a busy time http://ci.infinispan.org now points to Jenkins and all agents are up and running. Since all links on Pull Requests were broken (they were pointing to old Jenkins address), I retriggered all builds. The next

Re: [infinispan-dev] Jenkins migration

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,

Re: [infinispan-dev] Jenkins migration

Personally I've always used Jenkins and for that reason I didn't like Infinispan to use TeamCity - mainly as I'm not used to its UI - but I'll admit that its capability to focus on the test history, highlighting the first failure in time and its "stability" over time on a per-test focus rather

Re: [infinispan-dev] Jenkins migration

Radim, it's not like the default UI became much better since we evaluated it against TeamCity, it's just that we no longer have a choice :) And I'm sure in the Blue Ocean UI will get more development effort than the default UI in the future, but at this time it's clearly unfinished. Cheers Dan

Re: [infinispan-dev] Jenkins migration

On 24 April 2017 at 13:08, Tristan Tarrant wrote: > You mean exactly like the current CI is being handled? :-) > ​Cool, that other statement sounded like it could have misled you. > > On 24 Apr 2017 13:33, "Sanne Grinovero" wrote: > >> >> >> On 24

Re: [infinispan-dev] Jenkins migration

You mean exactly like the current CI is being handled? :-) On 24 Apr 2017 13:33, "Sanne Grinovero" wrote: > > > On 24 April 2017 at 12:19, Sebastian Laskawiec > wrote: > >> Hey! >> >> I uninstalled Blue Ocean plugin. I think it's worth to have another

Re: [infinispan-dev] Jenkins migration

On 24 April 2017 at 12:19, Sebastian Laskawiec 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). > >

Re: [infinispan-dev] Jenkins migration

Tristan is on PTO. He'll fix DNS on Wednesday :-) On 24 Apr 2017 13:26, "Sebastian Laskawiec" 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

Re: [infinispan-dev] Jenkins migration

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:

Re: [infinispan-dev] Jenkins migration

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? 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. >

Re: [infinispan-dev] Jenkins migration

I also do not see much value in the current state of Blue Ocean. Better stick with the default ui. On 04/21/2017 06:11 PM, Dan Berindei wrote: Looks like the invalid "control characters from U+ through U+001F" are the ANSI escape codes used by WildFly to color output. So we might be able

Re: [infinispan-dev] Jenkins migration

Looks like the invalid "control characters from U+ 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. OTOH I'm fine with removing the Blue Ocean plugin for now,

[infinispan-dev] Jenkins migration

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