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 test from the example and directly hit some problem I
don't know how to solve.
I setup a job that used the " pipeline script from SCM" method. I point
out the repo and branch and everything works fine. here is the parameter
section.
parameters {
string(name: 'PERSON', defaultValue: 'Mr Jenkins', description:
'Who should I say hello to?')
}
then I change it to
parameters {
string(name: 'PERSON', defaultValue: 'Mr Jenkins', description:
'Who should I say hello to?')
string(name: 'PERSON2', defaultValue: 'Mr Jenkins',
description: 'Who should I say hello to?')
}
but then I build with parameters and I only see the first parameter.
First I thought I did something wrong but it turns out what is really
happening is that jenkins do not understand that the parameter section
has changed. It do get the new script as changes to the stage section is
done it's just the parameters that is from the previous run.
This is a quite serious problem especially when you are writing a new
script and need to test it. but also if the parameters is truly dynamic
then it simply is not working.
I need to find out how to solve this issue.
--
You received this message because you are subscribed to the Google Groups "Jenkins
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/a3e11ed9-558b-73cc-8062-5a7276f3c748%40inteno.se.
For more options, visit https://groups.google.com/d/optout.
