Re: backward compatibility strategy

2015-01-27 Thread Robert Sandell
We had a show of hands on FOSDEM two years ago for how far people there thought we should keep backwards compatibility. I think most thought 2 years was enough. /B On Tue, Jan 27, 2015 at 1:41 PM, Andrew Gray andrew.paul.g...@gmail.com wrote: +1 for Option 2. Clean up old code and move

Next LTS is 1.596

2015-01-27 Thread oliver gondža
Hi, We have agreed on new LTS baseline version as 1.580 reached its end of life. Users can expect first RC based on 1.596 on 2015-02-04. -- oliver -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop

Office Hours tomorrow

2015-01-27 Thread Jesse Glick
https://wiki.jenkins-ci.org/display/JENKINS/Office+Hours For those of you interested in Workflow, I wanted to talk some about two topics people have asked me about: · Security model: script security, permissions. · Plugin compatibility: SimpleBuildStep and friends, custom steps, etc. -- You

Re: Office Hours tomorrow

2015-01-27 Thread Kohsuke Kawaguchi
To record the session, this office hours will be done in a different from the usual URL: https://plus.google.com/events/c4eagqodepqojlrv7glhc1ctg48 2015-01-27 12:21 GMT-08:00 Jesse Glick jgl...@cloudbees.com: https://wiki.jenkins-ci.org/display/JENKINS/Office+Hours For those of you interested

Re: Next LTS is 1.596

2015-01-27 Thread Francisco Alejandro Lozano López
Hi, Are there any plans for supporting a downgrade to this version? I was using normal releases but after all the 1.589 maven issues I would like to move to LTS - but my metadata was already updated so it maybe too late (all the existing builds are gone after downgrading). I think supporting

Re: Next LTS is 1.596

2015-01-27 Thread Francisco Alejandro Lozano López
Hi, Are there any plans for supporting a downgrade to this version? I was using normal releases but after all the 1.598 maven issues I would like to move to LTS - but my metadata was already updated so it maybe too late (all the existing builds are gone after downgrading). I think supporting

Re: Cloud slave never provisioned (sometimes)

2015-01-27 Thread Suckow, Thomas J
Even with an up-to-date durable-task plugin, it happened again :( I pulled the thread stack traces with the queued builds not building and then restarted jenkins. Comparing the threads, they are nearly identical. I've added fine logging for the NodeProvisioner, hopefully that will show

Re: backward compatibility strategy

2015-01-27 Thread Jesse Glick
On Tue, Jan 27, 2015 at 12:55 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: now jesse has signed up for a third fight Well, I see a lot of problems with using AspectJ as well, starting with the novel source language. I just wonder if there is any less controversial technique that

Re: Next LTS is 1.596

2015-01-27 Thread Daniel Beck
Read the changelog. https://wiki.jenkins-ci.org/display/JENKINS/JENKINS-24380+Migration On 27.01.2015, at 23:29, Francisco Alejandro Lozano López floz...@gmail.com wrote: Hi, Are there any plans for supporting a downgrade to this version? I was using normal releases but after all the

Re: Cloud slave never provisioned (sometimes)

2015-01-27 Thread Stephen Connolly
Note there was another deadlock found. There is an open pull request pending to fix that one On Tuesday, January 27, 2015, Suckow, Thomas J thomas.suc...@pnnl.gov wrote: Even with an up-to-date durable-task plugin, it happened again :( I pulled the thread stack traces with the queued builds

Re: backward compatibility strategy

2015-01-27 Thread nicolas de loof
If you don't like AspectJ, using lombok with custom annotation processors could do something comparable 2015-01-27 23:23 GMT+01:00 Jesse Glick jgl...@cloudbees.com: On Tue, Jan 27, 2015 at 12:55 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: now jesse has signed up for a third

S3 Plugin Changes

2015-01-27 Thread Raymond Huang
Hey Jenkins Developers, I've been interested in working on the S3 Plugin. I have two pull requests in place: https://github.com/jenkinsci/s3-plugin/pull/46 https://github.com/jenkinsci/s3-plugin/pull/49 I'd like to put some work in there and I have some future ideas of stuff to improve on. Is

Re: Jenkins icons for Disabled and Aborted job status plugin

2015-01-27 Thread Rocky Stone
Sorry for the delay. I deleted the repo and created new one that isn't branched from the jenkins repo on the same URL: https://github.com/kralq/distinguishable-gray-balls-plugin On Mon, Jan 26, 2015 at 8:12 PM, Daniel Beck m...@beckweb.net wrote: Thanks for the reminder! I don't know what'll

Re: backward compatibility strategy

2015-01-27 Thread Andrew Gray
+1 for Option 2. Clean up old code and move forward. On Tuesday, 27 January 2015, nicolas de loof nicolas.del...@gmail.com wrote: Hi folks, maintaining backward compatibility on jenkins codebase is hard and introduces hundred @Deprecated methods. I've just read this article :

Re: backward compatibility strategy

2015-01-27 Thread Jesse Glick
On Tue, Jan 27, 2015 at 4:35 AM, nicolas de loof nicolas.del...@gmail.com wrote: http://massol.myxwiki.org/xwiki/bin/view/Blog/BackwardCompatibilityStrategy and wonder if we could apply some of those recipes. In particular the use of AspectJ sounds a lot more attractive and powerful than the

Re: backward compatibility strategy

2015-01-27 Thread Stephen Connolly
And now jesse has signed up for a third fight... After two rounds with KK he will have another round with me over that aspectj shite On Tuesday, January 27, 2015, Jesse Glick jgl...@cloudbees.com wrote: On Tue, Jan 27, 2015 at 4:35 AM, nicolas de loof nicolas.del...@gmail.com javascript:;

Re: backward compatibility strategy

2015-01-27 Thread nicolas de loof
What's wrong with ApsectJ from your pov ? 2015-01-27 18:55 GMT+01:00 Stephen Connolly stephen.alan.conno...@gmail.com : And now jesse has signed up for a third fight... After two rounds with KK he will have another round with me over that aspectj shite On Tuesday, January 27, 2015, Jesse