Chris Withers kirjoitti 5.7.2012 kello 20.27: > I'm a know-nothing when it comes to Jenkins own development process, but does > it perhaps need to slow down a little and focus on quality and stability? > Does the Jenkins build process do anything to check what plugins will break > with a particular release? Could it?
I know nothing either. I think all the people who might know something are on the jenkins-dev list. AFAIK there is nothing in the Jenkins build process that tests plugins. There are something like 700 plugins in github.com and maybe some more on subversion. But, as Jenkins is open-source-software, there aren't too many people who have a lot of time to work on it. I know there are some, but not many. I'm sure any help you can offer to test plugins is welcome. Maybe the plugins do not all need to be tested? Only the plugins that are important to me. :) But, seriously, testing even one plugin would be a start. > jieryn makes mention of Jenkins LTS, how do I get this? How do I stop Jenkins > "offering" me new versions of Jenkins which aren't stable or aren't LTS? Go to http://jenkins-ci.org/, look for the text "Long-Term Support Release". I've understood that when you're running an LTS release, Jenkins will not bother you about new releases until a new LTS is available. -- Sami
