Hi Folks,
We're looking into upgrading ci.centos.org to the latest LTS release (In the 2.x series). So far this appears to be completely backwards-compatible with the set of plugins we have enabled, though we will continue testing over the next few days.
*JJB USERS READ HERE*
If you use Jenkins Job Builder in your projects, can you please test setting 'query_plugins_info=False' in your jjb.ini file and check for adverse effects? We are still waiting on a fix in Jenkins to allow regular users to access the plugin list, but in the meantime it appears that there are only a few circumstances where this makes a difference.
If all goes well, we will schedule a time and inform the list on our plans for the upgrade itself. As always if you have any questions, please let us know here.
Cheers!
-- Brian Stinson CentOS CI Infrastructure Team
Brian,
I will test with that option on current centos jobs. Is it worth setting up a 2.0 stage environment to verify our jobs can load against it?
Thanks,
On Thu, Aug 11, 2016 at 5:49 PM, Brian Stinson brian@bstinson.com wrote:
Hi Folks,
We're looking into upgrading ci.centos.org to the latest LTS release (In the 2.x series). So far this appears to be completely backwards-compatible with the set of plugins we have enabled, though we will continue testing over the next few days.
*JJB USERS READ HERE*
If you use Jenkins Job Builder in your projects, can you please test setting 'query_plugins_info=False' in your jjb.ini file and check for adverse effects? We are still waiting on a fix in Jenkins to allow regular users to access the plugin list, but in the meantime it appears that there are only a few circumstances where this makes a difference.
If all goes well, we will schedule a time and inform the list on our plans for the upgrade itself. As always if you have any questions, please let us know here.
Cheers!
-- Brian Stinson CentOS CI Infrastructure Team _______________________________________________ Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 16/08/16 15:35, Ari LiVigni wrote:
Brian,
I will test with that option on current centos jobs. Is it worth setting up a 2.0 stage environment to verify our jobs can load against it?
+1, lets get a Jenkins2 setup up to hit up against.
- -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc
On Aug 16 10:35, Ari LiVigni wrote:
Brian,
I will test with that option on current centos jobs. Is it worth setting up a 2.0 stage environment to verify our jobs can load against it?
We're going to do a test instance and sync /var/lib/jenkins once we're ready. The verification of this JJB option can happen against ci.c.o as it currently exists. If it works here, it will work against 2.X
Cheers! --Brian
-
Ari LiVigni -
Brian Stinson -
Karanbir Singh