Re: [hibernate-dev] Re-enabling the BlueOcean interface in Jenkins

2018-08-29 Thread Guillaume Smet
On Wed, Aug 29, 2018 at 2:32 PM Yoann Rodiere wrote: > Just in case someone is annoyed by the notification URL now pointing to the > BlueOcean interface: there is a setting in your account preferences in > Jenkins allowing you to choose between the BlueOcean URL or the classic > URL. > Very help

Re: [hibernate-dev] Re-enabling the BlueOcean interface in Jenkins

2018-08-29 Thread Yoann Rodiere
Just in case someone is annoyed by the notification URL now pointing to the BlueOcean interface: there is a setting in your account preferences in Jenkins allowing you to choose between the BlueOcean URL or the classic URL. See http://ci.hibernate.org/user//configure => "Notification URL" I didn'

Re: [hibernate-dev] Re-enabling the BlueOcean interface in Jenkins

2018-08-27 Thread Yoann Rodiere
Since there was no objections, I re-enabled BlueOcean. See an example here: http://ci.hibernate.org/blue/organizations/jenkins/hibernate-search-6-poc/detail/HSEARCH-3239/142/pipeline When in the BlueOcean interface, you can go back to the classic interface using the button circled in red in this

Re: [hibernate-dev] Re-enabling the BlueOcean interface in Jenkins

2018-08-02 Thread Sanne Grinovero
+1 I think we can live with minor inconveniences, especially as I hope we'll be moving more projects to take advantage of the pipelines. On Thu, 2 Aug 2018 at 17:56, Yoann Rodiere wrote: > > Hi, > > We're about to make use of Jenkins pipelines in Hibernate Search, and for > that purpose, the Blu

[hibernate-dev] Re-enabling the BlueOcean interface in Jenkins

2018-08-02 Thread Yoann Rodiere
Hi, We're about to make use of Jenkins pipelines in Hibernate Search, and for that purpose, the BlueOcean is much easier to read. So I'd like to re-enable it. This should not affect other projects much, as the default interface when you go to ci.hibernate.org will still be the "old" one. However,