|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I disagree.
The override Parameters option only becomes available if "Prepare an Environment for the run" is selected.
I am not "Preparing an environment".
I just want to alter it further down the line.
In the standard build step i can inject and then use shell to echo out the new value fine.
Why is Post action different now ?
Oh well prob have to use a groovy system script calling:- (SEE BELOW)the at end to MAKE sure this variable is what i want.
def pA = new ParametersAction(new StringParameterValue("BUILD_LOCATION", BUILD_LOCATION"/"BUILD_TYPE))
build.addAction(pA)
P.S Ext email plugin was already at latest.
Inject Environment was at 1.89 now at 1.90
P.P.S Your Line :-
Your mentioning the post-build step and involving email-ext also indicates insufficient attempts at isolating the cause of this issue (frankly, it doesn't look like you did anything in that regard).
Override Build parameters is only available when "Prepare an Environment for the Run" is selected.
I'll try not take this personally, but it is written quite harsh (in my eyes)
I am using the ext email in alot of my build projects, it is not an insufficient attempt to isolate the issue.
My attempt to reproduce the issue (This has got weird):-
1. Remove ext email from equation.
2. create another job that the first one triggers as a post step.
3. 1st Job LOG - "TEST_POST" is custom workspace:-
Started by user Sion OConnor
[EnvInject] - Loading node environment variables.
Building remotely on Saltaire_Pebsy_001_Prebuilds_001 (compile_Linux compile_prebuilt GCOV prebuild_SALTAIRE) in workspace /home/autobuildSA1/data_local/jenkins_SQA/TEST_POST
[TEST_POST] $ /bin/sh -xe /tmp/hudson5685744421231399954.sh
+ echo LOC/TYPE
LOC/TYPE
[EnvInject] - Injecting environment variables from a build step.
[EnvInject] - Injecting as environment variables the properties content
BUILD_LOCATION=LOCTYPE
* Now BUILD_LOCATION should be LOCTYPE
[EnvInject] - Variables injected successfully.
[TEST_POST] $ /bin/sh -xe /tmp/hudson4893696617381316178.sh
+ echo LOC
LOC
* This is echo ${BUILD_LOCATION} WHY is it still LOC - Pleas wait and see!!!
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Returning node parameter for Saltaire_Pebsy_001_Prebuilds_001
Triggering a new build of TEST_JBUGS2_InjectVariablesNotSeenInPostStepPARTB
Collecting metadata...
Metadata collection done.
Finished: SUCCESS
4. 2nd Job - the triggered job - only one step "echo ${BUILD_LOCATION}"
Started by upstream project "TEST_JBUGS2_InjectVariablesNotSeenInPostStep" build number 3
originally caused by:
Started by user Sion OConnor
[EnvInject] - Loading node environment variables.
Building remotely on Saltaire_Pebsy_001_Prebuilds_001 (compile_Linux compile_prebuilt GCOV prebuild_SALTAIRE) in workspace /home/autobuildSA1/data_local/jenkins_SQA/TEST_POST
[TEST_POST] $ /bin/sh -xe /tmp/hudson8828137042210710705.sh
+ echo LOCTYPE
LOCTYPE
Collecting metadata...
Metadata collection done.
Finished: SUCCESS
So why is echo step in first job only showing the "LOC".
Ok different scenario with the email, ill look more into this but i am worried why the first step only showing "LOC".
Siôn