I'm not sure if this is the right list. In this day and age of automation 
and automatic provisioning I don't understand why Jenkins versions are 
removed  from the  repositoriy for example 

There is always only one version available in the repository
vagrant@devops:~$ sudo apt-cache madison jenkins                           
   jenkins |     2.19.1 | http://pkg.jenkins-ci.org/debian-stable/ binary/ 

When a new version comes available, the previous version is removed. If I 
understand correctly.

This practice of immediately removing the previous version forces all 
organizations and companies to immediately update any automation script 
that might have been developed on top of this Jenkins version. This is no 
longer something they can control. When a new release happens, automation 
scripts starts failing. 

What is the rationale behind forcing organizations to follow 
Jenkins release schedule? Would it no be better to allow Jenkins user to 
upgrade at moment of their choosing?

What is the purpose of having versions when only one version is supported? 
Why not use version capabilities in package management systems?

You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to