Re: Checker runs once before applyNameRef, causing relative path to fail

Ok so I investigated a bit more, and it seems this is happening because the INPUT.validated rule is coming before the TR.row-set-end rule (priority 26 vs 43). Anyone already had issue with behaviour rules execution order, any way to change this easily? I've tried changing the order using the

Checker runs once before applyNameRef, causing relative path to fail

Hi, I'm trying to use validation on a field with a form a bit unusual because it's using a lot of radioBlock and I need relative path. So I set up my validation method like that: public FormValidation doCheckIdcmsInputFile(@QueryParameter("value") final String value, @RelativePath("../..")

Re: Automate recommended plugin unittest run against latest Jenkins core

With releases coming often, it is hard to test against the latest Jenkins when trying to deal with issues and so forth. Most maintainers just don't have the time to test against the latest release, the latest LTS and a few things in between. On Thu, Aug 4, 2016 at 12:23 AM ogondza

Re: Automate recommended plugin unittest run against latest Jenkins core

On Thu, Aug 4, 2016 at 12:46 PM Manuel Jesús Recena Soto wrote: > Hello Oliver, > > I like the idea. > > General speaking, ATH and PCT are very important and we should look after > its healthy. > > IMHO, PCT results are a nice place to figure out bad symptoms on some > plugins.

Re: Automate recommended plugin unittest run against latest Jenkins core

Hello Oliver, I like the idea. General speaking, ATH and PCT are very important and we should look after its healthy. IMHO, PCT results are a nice place to figure out bad symptoms on some plugins. Please, find here two issues as result of PCT: JENKINS-36646

Re: Plugin to hide/mask/obfuscate regex in all build output?

Yeah, I found the extension point - ConsoleLogFliter. I've opened a pull request for my changes - https://github.com/jenkinsci/mask-passwords-plugin/pull/6 On Thursday, August 4, 2016 at 10:47:04 AM UTC-4, Jesse Glick wrote: > > On Fri, Jul 29, 2016 at 7:19 AM, Jason Antman

Re: Automate recommended plugin unittest run against latest Jenkins core

On Wed, Aug 3, 2016 at 9:31 AM, Oliver Gondža wrote: > Is somebody working on this? Maybe ask andresrc. -- 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,

Re: WorkflowMultiBranchProject getLastBuild

On Wed, Aug 3, 2016 at 5:14 AM, Sverre Moe wrote: > I need to get the latest build job in my Groovy build script. Did you look at the documentation under Global Variables for `currentBuild`? -- You received this message because you are subscribed to the Google Groups

Re: how to create 2 page in RootAction

On Wed, Aug 3, 2016 at 3:11 AM, Shurik wrote: > How in jelly I can configure the next button ? Just a regular HTML link or form. You need to create a second view after `index.jelly`. -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: API access to update pipeline stages

On Tue, Aug 2, 2016 at 12:26 PM, Daniel Watrous wrote: > I'm struggling to find documentation around these or an example that might > help me to accomplish what I'm trying to do. Perhaps you are looking for

Re: combine multiple pipeline steps

On Tue, Aug 2, 2016 at 11:53 AM, Ioannis Canellos wrote: > And how do I wrap a snippet like this inside a jenkins plugin? See `docker-workflow` for an example of `GroovyShellDecorator`. Probably a higher-level API will be introduced in the future. -- You received this

Re: Problem with pipeline as a code dependency (workflow-aggregator)

On Mon, Aug 1, 2016 at 4:54 AM, Ido Gadiel wrote: > I get this exception while Im trying to run the test: "clean test > -DskipTests=false -Dtest=myTest" (but it runs perfectly on regular run, e.g > hpi:run -Djetty.port=9192) > java.lang.InstantiationException:

Re: Plugin to hide/mask/obfuscate regex in all build output?

On Fri, Jul 29, 2016 at 7:19 AM, Jason Antman wrote: > some way to **force** this for EVERY job, > period. I understand that's a feature most people wouldn't want, and I might > well keep that code in an internal branch only, rather than a pull request I > submit.

Re: Pipeline Syntax page and arguments of type Object

On Fri, Jul 29, 2016 at 6:47 AM, David van Laatum wrote: > @DataBoundSetter > public void setValue(String value) { > this.value = value; > } > > @DataBoundSetter > public void setValue(Integer value) { > this.value = value; > } You have to pick different parameters for

Re: slack-plugin

Hi Nadishka, If you haven't checked the source code of above mentioned project, clone it and go through it. It's ok if you can't understand most of it. But if you carefully observe it, you will be able to get an idea about the flow of the code. Furthermore, refer this documentation[1] to get a

Re: How to enable Travis CI for jenkins plugin repo

INFRA-741 fixed. But I agree that it is better to not assign them. Also our community CI should evolve soon with our recent partnership with Azure : https://jenkins.io/blog/2016/05/18/announcing-azure-partnership/ On Thu, Aug 4, 2016 at 9:15 AM, Craig Rodrigues wrote: > I'm

Re: Jenkins Developers for a fun project

Is it description of product or real plan of work? Why do you need "Jenkins developer" for it, all what i see is configure & learn your product? On Wednesday, August 3, 2016 at 11:36:18 PM UTC+3, shay klapper wrote: > > We are looking for experienced Jenkins developers to run a project for us >

Re: IMPORTANT: Do you have any `extends JnlpAgentReceiver` classes?

Bless you! :) On Tuesday, August 2, 2016 at 4:08:59 PM UTC+3, Stephen Connolly wrote: > > The JnlpAgentReceiver API contract is too heavily tied to the > NioChannelHub abstraction (which is fundamentally incompatible with > SSLEngine) > > As such for JNLP4-connect a.k.a. JENKINS-36871 I

Re: Automate recommended plugin unittest run against latest Jenkins core

Right, not the best wording. What I had in mind is: "It is something we would like to have confirmed before declaring the release is good to go". Unfortunately, many maintainers do not put that much effort into making sure their plugins work with latests cores, myself including. -- oliver --

Re: How to enable Travis CI for jenkins plugin repo

I'm OK with Cloudbees using a template to lock things down for jenkins.io.cloudbees.com. One thing I would suggest is that in JIRA, if someone files an issue at https://issues.jenkins-ci.org in Project *Infrastructure*, Component: *ci*, instead of auto-assigning the issue to one person (rtyler),