[JIRA] (JENKINS-14437) envinject fails to "really" set/override build parameters
Josh Davidson
created JENKINS-14437
envinject fails to "really" set/override build parameters
Issue Type:
Bug
Assignee:
Gregory Boissinot
Attachments:
config.xml
Components:
envinject
Created:
16/Jul/12 12:30 AM
Description:
If you load a properties file as a build step, that overrides one or more build parameters, the injected variables will show up in the "Injected Environment Variables View", but the subsequent build steps will be provided with whatever was specified in the build parameter at the start of the build.
Consider the following:
Step 1 (generate the params.properties file)
cd sast_product
./waf configure
waf params
Here is the resulting file's contents:
SIM_REV = 81b806d6c4165277ad456a3ffd7ee2c5e0a9ed73
SIM_REMOTE_REV = d82501d4a73c200974138016f3b2628d0bbf0366
SIM_UI_REV = 2a0aef21282b1277f7e9c68e4ace8deed055
FSW_CONTAINER_REV = 1e8d2005a045ac51219a1fd8915c7bd0f4f8a177
SIM_COMMON_REV = 6315defaf0c7376f2889bda3473828e2fbf2f743
SIM_INTERFACE_REV = 88c48d1349fb90cddbcaa1a21e93eee20cb15687
AST_REV = 8f947e56c1a6693687e8097fb50bba1626989ea6
WILLY_WONKA = harris
All but the last one map to build parameters. The last one is NOT a build parameter. Just a fake variable I added for test purposes.
Step 2 (Inject Environment variables)
Properties File Path: sast_product/build/params.properties
Console output:
[EnvInject] - Injecting environment variables from a build step.
[EnvInject] - Injecting as environment variables the properties file path 'sast_product/build/params.properties'
[EnvInject] - Variables injected successfully.
Step 3 (Execute shell and print the variables)
echo $SIM_COMMON_REV
echo $SIM_INTERFACE_REV
echo $WILLY_WONKA
Console output:
[sast_product_linux64] $ bash -xe /tmp/hudson6024044080448978568.sh
+ echo default
default
+ echo default
default
+ echo harris
You can see what's set in the environment are the build parameters ("default" is the default parameter value for SIM_COMMON_REV and SIM_INTERFACE_REV) and not the injected variables from the previous step. The dummy variable I added to the properties file that doesn't attempt to shadow a build parameter prints out OK.
I'm attaching the config.xml, but I'm hoping this description will suffice.
Project:
Jenkins
Priority:
Major
Reporter:
Josh Davidson
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
[JIRA] (JENKINS-14239) Sometimes CCUCM finds baselines in other masterships
Christian Wolfgang resolved JENKINS-14239 as Fixed Sometimes CCUCM finds baselines in other masterships Change By: Christian Wolfgang (16/Jul/12 12:13 AM) Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-14241) CCUCM mistreats deliver error
Christian Wolfgang resolved JENKINS-14241 as Fixed CCUCM mistreats deliver error Change By: Christian Wolfgang (16/Jul/12 12:12 AM) Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-14317) Deliver being cancelled not detected
Christian Wolfgang resolved JENKINS-14317 as Fixed Deliver being cancelled not detected Change By: Christian Wolfgang (16/Jul/12 12:11 AM) Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-14318) If deliver fails an undo deliver must always be executed
Christian Wolfgang resolved JENKINS-14318 as Fixed If deliver fails an undo deliver must always be executed Change By: Christian Wolfgang (16/Jul/12 12:05 AM) Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-13944) Missing hyperlink type "tag" in Clearcase does not fail the build
Christian Wolfgang commented on JENKINS-13944 Missing hyperlink type "tag" in Clearcase does not fail the build The build now becomes unstable if the tag hyperlink is not found. 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
[JIRA] (JENKINS-13944) Missing hyperlink type "tag" in Clearcase does not fail the build
Christian Wolfgang resolved JENKINS-13944 as Fixed Missing hyperlink type "tag" in Clearcase does not fail the build Change By: Christian Wolfgang (16/Jul/12 12:02 AM) Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-14436) Don't display all versions in the changeset
Christian Wolfgang resolved JENKINS-14436 as Fixed Don't display all versions in the changeset Change By: Christian Wolfgang (16/Jul/12 12:01 AM) Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-14433) Ant doesn't pass the command line properties correctly and they are null/blank
fmhome closed JENKINS-14433 as Cannot Reproduce Ant doesn't pass the command line properties correctly and they are null/blank This is not a problem anymore. Change By: fmhome (15/Jul/12 10:51 PM) Status: Open Closed Fix Version/s: current Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-14436) Don't display all versions in the changeset
Christian Wolfgang created JENKINS-14436 Don't display all versions in the changeset Issue Type: New Feature Assignee: Christian Wolfgang Components: clearcase-ucm Created: 15/Jul/12 8:41 PM Project: Jenkins Priority: Minor Reporter: Christian Wolfgang 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
[JIRA] (JENKINS-14403) Add option to avoid workspace cleanup if job failed
vjuranek resolved JENKINS-14403 as Fixed Add option to avoid workspace cleanup if job failed Implemented in rel. 0.9. Thanks to fwiegerinck! Change By: vjuranek (15/Jul/12 8:27 PM) Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-14435) No incremental display of progress within a line
jglick
created JENKINS-14435
No incremental display of progress within a line
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
15/Jul/12 4:52 PM
Description:
The /console and /consoleText logs for a job using
set +x
echo -n Sleeping; for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20; do echo -n .; sleep 1; done; echo
do not show progress until the very end, even though the log on disk gets updated every second.
Note that
@Test public void subLineProgress() throws Exception {
ByteBuffer buf = new ByteBuffer();
LargeText text = new LargeText(buf, false);
buf.write("Started.\n".getBytes());
StringWriter w = new StringWriter();
text.writeLogTo(0, w);
assertEquals("Started.\n", w.toString());
buf.write("Running...".getBytes());
w = new StringWriter();
text.writeLogTo(0, w);
assertEquals("Started.\nRunning...", w.toString());
buf.write("done.\n".getBytes());
w = new StringWriter();
text.writeLogTo(0, w);
assertEquals("Started.\nRunning...done.\n", w.toString());
}
fails, but according to the Javadoc this seems to be intentional. A fix would probably need a coordinated fix in Stapler, though AnnotatedLargeText may also contribute to the problem.
Environment:
Linux, JDK 7
Project:
Jenkins
Labels:
console
buffering
Priority:
Major
Reporter:
jglick
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
[JIRA] (JENKINS-14410) Xvnc does not set DISPLAY variable
Matthias Spiller commented on JENKINS-14410 Xvnc does not set DISPLAY variable It was caused by the EnvInject plugin. 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
[JIRA] (JENKINS-14410) Xvnc does not set DISPLAY variable
Matthias Spiller resolved JENKINS-14410 as Not A Defect Xvnc does not set DISPLAY variable Change By: Matthias Spiller (15/Jul/12 11:50 AM) Status: Open Resolved Resolution: Not A Defect 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
[JIRA] (JENKINS-14434) Delete buttons for dashboard view not working
Sebastian Möller updated JENKINS-14434 Delete buttons for dashboard view not working I've attached Jenkins system information, maybe it will be of some help. Change By: Sebastian Möller (15/Jul/12 10:11 AM) Attachment: systemInfo.txt 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
[JIRA] (JENKINS-14434) Delete buttons for dashboard view not working
Sebastian Möller created JENKINS-14434 Delete buttons for dashboard view not working Issue Type: Bug Assignee: Peter Hayes Components: dashboard-view Created: 15/Jul/12 10:08 AM Description: When editing a view the "delete" buttons on the right side don't work. Tried it with firefox and chromium so I guess it's not browser related. Environment: Jenkins v1.474 Dashboard v2.2 Project: Jenkins Priority: Major Reporter: Sebastian Möller 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
[JIRA] (JENKINS-13841) "Base folder" for deploying the artifacty from source folder to remote directory
Gerd Zanker commented on JENKINS-13841 "Base folder" for deploying the artifacty from source folder to remote directory Works perfectly. In the advanced basedir field I can enter a workspace relative path. The included artifacts are now specified basedir relative and the job produces the expected results inside the remote directory. Thank you for implementation. 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
