Re: Update one f:dropdownList when a selection is changed in another

On Tue, Oct 27, 2015 at 11:34 AM, Kirill wrote: > what about case when there are two elements? First of all, you should be using `f:dropdownDescriptorSelector` for data binding, rather than a raw `f:dropdownList`. Probably what you are asking for is not possible without

Re: [workflow-plugin] parallel threads greater than matching node label executors silently discard unassigned threads

Figured it out and deleted the original posts because they were effectively noise in the Google Groups. It was developer error. I was looking at a test input that would've generated more branches than free matching slaves, but mistakenly rebuilding my job with another test input where threads <

Re: [proposal] coding style for core (jenkins 2.0?)

JFYI, latest checkstyle version (with latest maven-checkstyle) supports more flexible configurations like allow inline if’s without brackets. Different types of inline annotations (configuration 1.3 DTD). http://checkstyle.sourceforge.net/releasenotes.html

Re: [proposal] coding style for core (jenkins 2.0?)

> My proposal is to chose some coding style ... I thought the project already had a style guide; one has already been published for the project, anyway. The following appears in the "contributing" wiki page, originally authored March 2011 with latest revision in August 2015. This page can be

Re: [proposal] coding style for core (jenkins 2.0?)

Well, yeah, but I guess the thing is: > "We *try* to *loosely* follow" Might have left a lot (too much?) of room for debate :). Le 10 nov. 2015 6:26 PM, a écrit : > > My proposal is to chose some coding style ... > > I thought the project already had a style

Re: [workflow-plugin] parallel threads greater than matching node label executors silently discard unassigned threads

And I'll stick to GG Jenkins Users and SO jenkins-workflow the next time. I appreciate the feedback on where to post. On Tuesday, November 10, 2015 at 9:22:34 AM UTC-8, Brian Ray wrote: > > Figured it out and deleted the original posts because they were > effectively noise in the Google Groups.

Re: [proposal] coding style for core (jenkins 2.0?)

On 10 November 2015 at 21:34, Jesse Glick wrote: > On Tue, Nov 10, 2015 at 3:22 PM, Stephen Connolly > wrote: > > None of those match "Jesse"-style so hopefully we can kill that > abomination off ;-) > > CheckStyle is a syntactic, not

Request to become maintainer of SCM Sync plugin

Hi, Plugin: https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin https://github.com/jenkinsci/scm-sync-configuration-plugin GitHub ID: rodrigc I'd like to request to become a maintainer of the SCM Sync plugin. There are some pull requests pending which fix many issues, but

Re: Commit access to build-pipeline-plugin

Accept the invitation in your spam folder, or on github.com/jenkinsci. On 10.11.2015, at 17:41, Dan Alvizu wrote: > > Dan, but we should be synced in the roadmap of this plugin. Ok? > > Will do > > > Granted committer permission. > > Can you double check please,

Re: [proposal] coding style for core (jenkins 2.0?)

On Tue, Nov 10, 2015 at 3:22 PM, Stephen Connolly wrote: > None of those match "Jesse"-style so hopefully we can kill that abomination > off ;-) CheckStyle is a syntactic, not semantic, processor so it cannot distinguish between adjectival annotations,

1.625.2 status

Oliver, KK is planning to push out 1.625.2 a bit earlier than usual tomorrow, i.e. before the project meeting. From your point of view, is 1.625.2 good to go? Daniel -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from

Request for participation: Jenkins Security Officer candidates

Based on the team lead proposal (https://wiki.jenkins-ci.org/display/JENKINS/Proposal+-+Project+sub-teams) which was approved in the governance meeting last month, I asking on behalf of the Jenkins board[0], for candidates who are willing to act as the Jenkins Security Officer. The

Re: Commit access to build-pipeline-plugin

Ah, got it! Thanks Daniel! On Tuesday, November 10, 2015 at 2:34:23 PM UTC-7, Daniel Beck wrote: > > Accept the invitation in your spam folder, or on github.com/jenkinsci. > > On 10.11.2015, at 17:41, Dan Alvizu > wrote: > > > > Dan, but we should be synced in the

Re: Request to become maintainer of SCM Sync plugin

As I mentioned in the PR #31, I'm strongly in favor of bringing new blood to this plugin as I cannot dedicate much time to it, ans, like you said, there are a tons of PR pending currently +1 then :) @Craig don't you have jenkinsci plugins commit accesses already ? If not, could a jenkins folk

Re: Commit access to build-pipeline-plugin

Hello Dan, I totally agree with "contributors are welcome". We can work together and improve this plugin. I don't know if I can give you grant access, let me check. Regards, 2015-11-10 0:28 GMT+01:00 Dan Alvizu : > I guess I am confused, and maybe we both are as this

Re: Update one f:dropdownList when a selection is changed in another

Do you mean something like return FormValidation.respond(isFieldValid? FormValidation.Kind.ERROR : FormValidation.Kind.OK, "disableBadStuff()"); ? I tried this and it doesn't work :( The tag is injected in validation area, but the script inside it does not get executed :( And there are no

Re: Commit access to build-pipeline-plugin

On 10.11.2015, at 09:45, Manuel Jesús Recena Soto wrote: > I don't know if I can give you grant access, let me check. I can. Just state that you're not opposed to having a co-maintainer. -- You received this message because you are subscribed to the Google Groups "Jenkins

Plugin Hosting Request - qtest-plugin

Hi, I would like to add our plugin to the Jenkins plugin list. - URL: g...@github.com:QASymphony/jenkin-qtest-plugin.git - plugin name: qtest-plugin - github name: gunivan - jenkins-ci.org UserName: gunivan - description: This plugin allow user to submitt JUnit test result to

Re: Commit access to build-pipeline-plugin

Hello, 2015-11-10 11:38 GMT+01:00 Daniel Beck : > > On 10.11.2015, at 09:45, Manuel Jesús Recena Soto wrote: > >> I don't know if I can give you grant access, let me check. > > I can. Just state that you're not opposed to having a co-maintainer. +1. Dan, but

Re: Commit access to build-pipeline-plugin

On 10.11.2015, at 11:55, Manuel Jesús Recena Soto wrote: > +1. Granted committer permission. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an

Re: Hi, I have some newbie questions

Hi thank you Daniel, I don't understand very well what is an action. I read this I think I didn't understand enough : https://wiki.jenkins-ci.org/display/JENKINS/Action+and+its+family+of+subtypes I am sure I have to write in type and creatFor but I don't understand what. Thank you for the

Re: Commit access to build-pipeline-plugin

Hello, 2015-11-10 12:06 GMT+01:00 Daniel Beck : > > On 10.11.2015, at 11:55, Manuel Jesús Recena Soto wrote: > >> +1. > > Granted committer permission. Thanks. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins