Re: @QueryParameter in form validation is not filled for dropdownDescriptorSelector

On Thu, Feb 14, 2019 at 5:55 PM Ullrich Hafner wrote: > I think there still I a bug in Stapler here Does look that way. Please file it, and of course if you can track down the cause a PR would be great. The only thing unusual I see about your example is the use of `int`, where most check

Re: @QueryParameter in form validation is not filled for dropdownDescriptorSelector

I finally managed it to get it fixed (at least in my plugin). I think there still I a bug in Stapler here: If I define the validation method using: public FormValidation doCheckHighThreshold(@QueryParameter final int highThreshold, @QueryParameter final int normalThreshold) { return

Re: Packing extra files along with depedency jars in hpi

Definitely sounds like a maven-remote-resources-plugin use case. Used this in the past to share versioned pmd rulesets IIRC, worked like a charm. Le mar. 12 févr. 2019 à 20:40, Rajeev Ranjan a écrit : > Hi team, > There's a issue which is bugging me a lot from a while. Don't know if it > has

Re: Access to github for ease-plugin for 2 new developers

It should be done now. They should have invitations to the org that they will need to accept. On Thu, Feb 14, 2019 at 2:32 PM Robert Friedman wrote: > They are jrodgut-sg and fin7710. Thanks! > > On Thursday, February 14, 2019 at 4:22:51 PM UTC-5, slide wrote: >> >> What are their GitHub

Re: Access to github for ease-plugin for 2 new developers

They are jrodgut-sg and fin7710. Thanks! On Thursday, February 14, 2019 at 4:22:51 PM UTC-5, slide wrote: > > What are their GitHub usernames? > > On Thu, Feb 14, 2019, 14:09 Robert Friedman wrote: > >> Help here would be appreciated, it is still unresolved. Thanks! >> >> >> On Wednesday,

Re: Access to github for ease-plugin for 2 new developers

What are their GitHub usernames? On Thu, Feb 14, 2019, 14:09 Robert Friedman Help here would be appreciated, it is still unresolved. Thanks! > > > On Wednesday, January 30, 2019 at 3:33:13 PM UTC-5, Robert Friedman wrote: >> >> I need some help with getting new maintainers added to >>

Re: Access to github for ease-plugin for 2 new developers

Help here would be appreciated, it is still unresolved. Thanks! On Wednesday, January 30, 2019 at 3:33:13 PM UTC-5, Robert Friedman wrote: > > I need some help with getting new maintainers added to > https://github.com/jenkinsci/ease-plugin so that they have commit access. > They were added to

Re: Backporting for LTS 2.164.1 started

On 14/02/2019 16.38, Daniel Beck wrote: On 14. Feb 2019, at 11:03, Oliver Gondža wrote: Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 Could you update this filter to include 'Fixed but Unreleased'? We're not consistently keeping the statuses up to date after a weekly

Re: GlobalConfiguration.all() throws IllegalStateException

Getting the configuration at the StepExecution fixed it, thanks a lot for the help and the revelations! El lunes, 4 de febrero de 2019, 15:21:28 (UTC+1), Jesse Glick escribió: > > On Mon, Feb 4, 2019 at 4:49 AM Carles Capdevila Tejada > > wrote: > > I thought that pipeline code is always

Re: Backporting for LTS 2.164.1 started

> On 14. Feb 2019, at 11:03, Oliver Gondža wrote: > > Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 Could you update this filter to include 'Fixed but Unreleased'? We're not consistently keeping the statuses up to date after a weekly release, and while we should fix that,

Re: Setup external Jenkins processes to test via JCasC

On Thu, Feb 14, 2019 at 6:34 AM Oliver Gondža wrote: > Does it sound useful to you? Yes! My main feedback is that, if possible, this should be reworked to use a Docker container to launch Jenkins, with the image configurable on a per-test basis. (That does not preclude mounting Maven-specific

Re: Request for Input: 2 weeks comment period for moving to the CDF

(replies inline) On Mon, 11 Feb 2019, Kohsuke Kawaguchi wrote: > This is the formal call for input for the decision to move the Jenkins > project to the newly forming Continuous Delivery Foundation. (I was told > that my earlier attempt >

Setup external Jenkins processes to test via JCasC

The other day, I have spent a week on crafting a reusable JUnit rule to complement JenkinsConfiguredWithCodeRule[2] that create Jenkins SUTs as independent local processes. The use case here is starting Jenkins with realistic classloading environment, testing realistic start/stop/restart

Re: Missing permission for the github repository

I’m also using travis for my plugin builds (additionally to ci.jenkins.io ) :-) It is much faster and sends mails if there are some failures. Also there is an out of box integration of some external tools (codacy, codecov, etc.). > Am 14.02.2019 um 00:57 schrieb Gavin

Backporting for LTS 2.164.1 started

Backporting has started and the RC is scheduled for 2019-02-27. Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 Fixed: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.164.1-fixed Rejected: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.164.1-rejected --

Re: Request for Input: 2 weeks comment period for moving to the CDF

Thanks for your explanation. It's helpful to me. On Thu, Feb 14, 2019 at 4:19 AM Kohsuke Kawaguchi wrote: > Thanks for the question, Rick. > > There will be Jenkins level things and CDF level things. > > The SIGs that we currently have are Jenkins level entities. In the short > term all of