Today, I also learned about the new *Declarative Directive Generator* which
is available
in the latest Jenkins and pipeline distributions::
https://jenkins.io/blog/2018/04/09/whats-in-declarative/
If you use that and click on *Sample Directive -> parameters: Parameters*
then you can see the differ
I submitted this pull request which got accepted:
https://github.com/jenkins-infra/jenkins.io/pull/1711
and now there are more examples of parameters at:
https://jenkins.io/doc/book/pipeline/syntax/#parameters
for *text*, *choice*, *password*, *booleanParam*, and *file* parameters.
--
Craig
O
> On 2. Feb 2018, at 17:12, Dave Hallam wrote:
>
> Is there a reason why not?
No such parameter type in Jenkins (without plugins) -- wouldn't make sense for
other job types that typically receive values and env vars anyway.
> I know I could disable the sandbox for the latter issue, but I'd r
Hi,
We have "string", "booleanParam", "choice", etc. but nothing for numeric
types. Is there a reason why not?
I have a pipeline where I would like a parameter to be a duration (in
hours) to invoke a "sleep" step.
Using "string" doesn't work because sleep is expecting an int. And if I try
u
It seems you can use
Library
in a declarative pipeline file to do stuff like
mySpecialPipeline {
someString = 'foo'
}
and have
pipeline { ...
...echo config.someString
}
in vars/mySpecialPipeline.groovy
and you can reference vars/myCustomStep.groovy
but is it possible to share job
p
On 2017-04-26 16:14, Björn Pedersen wrote:
Am Mittwoch, 26. April 2017 14:43:39 UTC+2 schrieb Kenneth Johansson:
hmm I'm starting to question the usefulness of the pipeline
system. Its
very hard to understand how to do even very basic stuff.
Even something as easy as finding o
Am Mittwoch, 26. April 2017 14:43:39 UTC+2 schrieb Kenneth Johansson:
>
> hmm I'm starting to question the usefulness of the pipeline system. Its
> very hard to understand how to do even very basic stuff.
>
> Even something as easy as finding out what type of parameters I can use
> is hard.
>
hmm I'm starting to question the usefulness of the pipeline system. Its
very hard to understand how to do even very basic stuff.
Even something as easy as finding out what type of parameters I can use
is hard.
The documentation on https://jenkins.io/doc/book/pipeline/syntax/ only
mention str
What I want is to have the configuration and build instruction in the
actual project repo and to do that it looked like I should do a pipeline
project. But the documentation is not very easy to follow.
So my first problem is how to generate the built parameters dynamically.
I made a simple tes
