[workflow] StringParameterDefinition exception when asking for a string

Hi all, I've been trying to implement a simple workflow, and I want to get a value given by an user. So I wrote this : node { myvar = input message: 'Version?', parameters: [ [$class: 'StringParameterDefinition', defaultValue: '', description: '', name: 'ver'] ]

Re: [workflow] StringParameterDefinition exception when asking for a string

Does it work if you use instead: [$class: 'hudson.model.StringParameterDefinition', defaultValue: '', description: '', name: 'ver'] ? 2015-12-24 8:53 GMT+00:00 Erwan de Ferrières : > Hi all, > > I've been trying to implement a simple workflow, and I want to get a value > given by an user. > S

CodeDeploy plugin using proxy authentication

Hi, the CodeDeploy plugin allows you to specify a proxy server and port but not username and password. How do we make it work with proxy authentication? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop re

Re: [workflow] StringParameterDefinition exception when asking for a string

Yes, it works ! thanks Le jeudi 24 décembre 2015 11:23:18 UTC+1, Baptiste Mathus a écrit : > > Does it work if you use instead: > > [$class: 'hudson.model.StringParameterDefinition', defaultValue: '', > description: '', name: 'ver'] > > > ? > > > 2015-12-24 8:53 GMT+00:00 Erwan de Ferrières >:

Re: how to execute a shell script in build flow "flow" dsl section

Here is my buildflow which executes a shell script... Remember buildflow is DSL which is Groovy.. --- def JobCode = "REL" def JobName = build.environment.get( "JOB_NAME" ) def BuildURL = build.environment.get( "BUILD_URL" ) def BuildNum = build.environment.get( "BU

Re: Approaches for sharing workspace in a pipeline

Hi, I definitely thought about workflow. It looks promising. One question though - I can't seem to archive/unarchive everything. It looks like to use unarchiver you need to know the paths that will be exposed, and instead I'd like to just get everything, including class files. Is that possi

Re: Approaches for sharing workspace in a pipeline

Isn't the "get everything" Ant regex something like or ***/**? If you continue looking at workflow, also check out the *stash* and *unstash *steps. Similar purpose and syntax but more applicable to intermediate stages where you don't need to retain the artifacts. You can also refer to the

Re: Approaches for sharing workspace in a pipeline

Creating the archive doesn't seem to be an issue. Its the unarchive step where things don't quite work for me. If I read this info, it implies that the mapping step is not required. https://github.com/jenkinsci/workflow-plugin/blob/master/basic-steps/src/main/resources/org/jenkinsci/plugins/w