1.565.2 LTS RC testing started

2014-08-26 Thread oliver gondža
Hello everyone, Latest RC was made public and it is ready to be tested. We have 8 days to make sure that all the fixes[1] are in place and no new regressions ware introduced. Report your findings in this thread or in the test plan wiki. Download bits from

Re: Updates to plugin code without consulting maintainers

2014-08-26 Thread Christopher Orr
On 26/08/14 07:05, Stephen Connolly wrote: On Monday, 25 August 2014, Slide slide.o@gmail.com mailto:slide.o@gmail.com wrote: There have been a couple times recently where someone from Cloudbees has made changes to email-ext without consulting with me as the maintainer of

Re: Updates to plugin code without consulting maintainers

2014-08-26 Thread Tom Fennelly
Okay... really sorry about that... I did make those changes on a branch but I should have done it on a fork. I actually did create a fork after seeing there was a build tracking branches. Let me know if I should delete the branch I created - I won't touch anything until you let me know what

Re: Listen for discarding build

2014-08-26 Thread Baptiste Mathus
Discard or cancel? From what you say, seems like there's a confusion somewhere I guess. 2014-08-26 14:41 GMT+02:00 Dzmitry Kashlach dzmitrykashl...@gmail.com: I've met with one more difficulty. I've extended RunListener in my project to implement onDeleted() method. I've created an instance

Re: Listen for discarding build

2014-08-26 Thread Dzmitry Kashlach
I want my plugin to do the following: 1. Start performance test as a build step; 2. If user cancels build(pressed red button with x near build link on UI) - stop test and free test resources. On Thursday, August 21, 2014 9:55:16 AM UTC+3, Dzmitry Kashlach wrote: Hi all, I'm developing

Re: Updates to plugin code without consulting maintainers

2014-08-26 Thread Slide
Not a big deal, I've wondered why all branches are tracked on jenkins.ci.cloudbees, I would think only master would be tracked. Don't worry about deleting the branch. If you have specific things you would like added, pull requests are great. On Tue, Aug 26, 2014 at 3:22 AM, Tom Fennelly

Re: Should we come up with a browser support matrix?

2014-08-26 Thread Tom Fennelly
I added a v1 of this to the wiki at https://wiki.jenkins-ci.org/display/JENKINS/Browser+Compatibility+Matrix Of course, feel free to make comments and edits :) -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group

Re: Should we come up with a browser support matrix?

2014-08-26 Thread Baptiste Mathus
Great, thanks Tom. I just reworked the page a bit into a table to help make the information more quickly findable by readers. Hope this suits you and others. 2014-08-26 15:06 GMT+02:00 Tom Fennelly tom.fenne...@gmail.com: I added a v1 of this to the wiki at

Re: workflow-plugin development issue on windows

2014-08-26 Thread Jacob Vallejo
Hey Tom, That's not a bad idea, I'll give cygwin a shot. I've been pulled onto other tasks but I will try to get back to this ASAP. Thanks for the suggestion! -- Jake Vallejo On 26 Aug 2014, at 6:28, Tom Fennelly wrote: Hey Jacob... did you try building through cygwin? A ton of tests

Re: Should we come up with a browser support matrix?

2014-08-26 Thread Daniel Beck
On 26.08.2014, at 15:06, Tom Fennelly tom.fenne...@gmail.com wrote: I added a v1 of this to the wiki at https://wiki.jenkins-ci.org/display/JENKINS/Browser+Compatibility+Matrix Of course, feel free to make comments and edits :) Any particular reason you list Firefox ESR as L2? -- You

Re: Should we come up with a browser support matrix?

2014-08-26 Thread Tom Fennelly
That's great, thanks Baptiste. On Tuesday, August 26, 2014 2:26:18 PM UTC+1, Baptiste Mathus wrote: Great, thanks Tom. I just reworked the page a bit into a table to help make the information more quickly findable by readers. Hope this suits you and others. 2014-08-26 15:06 GMT+02:00 Tom

Re: Should we come up with a browser support matrix?

2014-08-26 Thread Tom Fennelly
Good question... no reason other than being hasty. I'll update it and make it L1. In fact... is there a need to mention it specifically? On Tuesday, August 26, 2014 6:14:05 PM UTC+1, Daniel Beck wrote: On 26.08.2014, at 15:06, Tom Fennelly tom.fe...@gmail.com javascript: wrote: I

Re: Should we come up with a browser support matrix?

2014-08-26 Thread Daniel Beck
On 26.08.2014, at 19:39, Tom Fennelly tom.fenne...@gmail.com wrote: Good question... no reason other than being hasty. I'll update it and make it L1. In fact... is there a need to mention it specifically? Well, it's outdated by ~3 months on average compared to the latest, so telling

Re: Updates to plugin code without consulting maintainers

2014-08-26 Thread Jesse Glick
On Tue, Aug 26, 2014 at 9:01 AM, Slide slide.o@gmail.com wrote: I've wondered why all branches are tracked on jenkins.ci.cloudbees, I would think only master would be tracked. Not sure but I suspect this is necessary for the pull request builder. It is annoying though that when you have a

[HEADS UP] getTestResultAction removed in 1.577

2014-08-26 Thread Jesse Glick
For proper stratification I needed to deprecate AbstractBuild.getTestResultAction (and .getAggregatedTestResultAction) in Jenkins core 1.577, allowing the JUnit test result publisher and associated APIs to be split into junit-plugin. Plugins calling these methods will generally not work in 1.577+.

Re: [HEADS UP] getTestResultAction removed in 1.577

2014-08-26 Thread 'Bruno P. Kinoshita' via Jenkins Developers
Thanks for the heads up Jesse. IIRC the tap-plugin also utilizes these methods. I'll take a look this weekend and will update it. Bruno From: Jesse Glick jgl...@cloudbees.com To: Jenkins Dev jenkinsci-dev@googlegroups.com Sent: Tuesday, August 26, 2014 4:24 PM

Re: [HEADS UP] getTestResultAction removed in 1.577

2014-08-26 Thread Jesse Glick
On Tue, Aug 26, 2014 at 6:51 PM, 'Bruno P. Kinoshita' via Jenkins Developers jenkinsci-dev@googlegroups.com wrote: IIRC the tap-plugin also utilizes these methods. I do not think so—it calls TestObject.getTestResultAction, but that is fine. Only the methods on AbstractBuild are affected. --