Hi all,
I'm using Jenkins 1.640 and HP Application Automation Tools 4.0. The HP
plugin sets a variable like this:
// This allows a user to access the runId from within Jenkins using a build
variable.
build.addAction(new ParametersAction(new
StringParameterValue(RUNID_BUILD_VARIABLE, "" + runId)));
logger.print("Set " + RUNID_BUILD_VARIABLE + " Env Variable to " + runId +
"\n");
RUNID_BUILD_VARIABLE is "HP_RUN_ID." With this, I can use ${HP_RUN_ID} in
my Ant script. This has worked fine until recently.
However now I've enabled parameterized builds because I need to kick off
the build programmatically and pass a parameter (other than HP_RUN_ID.)
When I do that, I can no longer access the variable set by the HP plugin.
Whether I explicitly define HP_RUN_ID as a parameter or not doesn't
matter. I think if I do define it but leave the default value blank, I get
an empty string in Ant. If I don't define it, Ant prints the literal
${HP_RUN_ID}, as if it had never been set.
Is there something I can do to enable a parameterized build AND use the
value set by the plugin?
thanks
john
--
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/f8ffc8db-e021-4b25-8800-016e7657e6bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
