[JIRA] (JENKINS-15849) Wall Display Plugin - walldisplay text - use environment variables
Frode Carlsen
created JENKINS-15849
Wall Display Plugin - walldisplay text - use environment variables
Issue Type:
Improvement
Assignee:
Christian Pelster
Components:
walldisplay
Created:
17/Nov/12 10:09 AM
Description:
The Wall Display plugin allows configuring a custom "walldisplay text"
For builds that are parameterized it would be very useful to allow including the environment variable in the text.
Example
walldisplay text : "Job - ${MY_PARAM}"
Project:
Jenkins
Priority:
Major
Reporter:
Frode Carlsen
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-15849) Wall Display Plugin - walldisplay text - use environment variables
Frode Carlsen updated JENKINS-15849 Wall Display Plugin - walldisplay text - use environment variables Change By: Frode Carlsen (17/Nov/12 10:09 AM) Component/s: jenkinswalldisplay 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-14921) Status Code: 500 If multiple channels should be used
Yves Schumann commented on JENKINS-14921 Status Code: 500 If multiple channels should be used Can't reproduce this issue anymore, so it could be closed. Everything works as expected. Thx for the cool 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-11592) NPE: Failed to record SCM polling
kutzi resolved JENKINS-11592 as Fixed NPE: Failed to record SCM polling Change By: kutzi (17/Nov/12 11:40 AM) Status: Reopened 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-11592) NPE: Failed to record SCM polling
kutzi commented on JENKINS-11592 NPE: Failed to record SCM polling Ken, since you seem to be experiencing a different issue, please open a new Jira issue with all the necessary details - e.g. the full stacktrace of the exception. 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-14921) Status Code: 500 If multiple channels should be used
kutzi resolved JENKINS-14921 as Cannot Reproduce Status Code: 500 If multiple channels should be used Change By: kutzi (17/Nov/12 11:43 AM) Status: Open Resolved 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-15850) JavaScript view fails if one job has a '.' in the name
domi created JENKINS-15850 _javascript_ view fails if one job has a '.' in the name Issue Type: Bug Assignee: wolfs Components: depgraph-view Created: 17/Nov/12 2:39 PM Description: As soon as the name of a job in the dependency graph has a '.' (dot) in the name, the edges in the graph are not displayed anymore. Project: Jenkins Priority: Blocker Reporter: domi 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-15408) Rotation of slave agent launch logs is broken for Windows masters
SCM/JIRA link daemon resolved JENKINS-15408 as Fixed Rotation of slave agent launch logs is broken for Windows masters Change By: SCM/JIRA link daemon (17/Nov/12 3:55 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-15408) Rotation of slave agent launch logs is broken for Windows masters
SCM/JIRA link daemon commented on JENKINS-15408 Rotation of slave agent launch logs is broken for Windows masters Code changed in jenkins User: Erik Molekamp Path: changelog.html http://jenkins-ci.org/commit/jenkins/ebd791a02ee6e53cf0238121d9e500b7ca3da6c5 Log: [FIXED JENKINS-15408] updated changelog 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-15408) Rotation of slave agent launch logs is broken for Windows masters
SCM/JIRA link daemon commented on JENKINS-15408 Rotation of slave agent launch logs is broken for Windows masters Code changed in jenkins User: Erik Molekamp Path: changelog.html http://jenkins-ci.org/commit/jenkins/890001ba9522f2eb94c152597f4cd20122d535b1 Log: [FIXED JENKINS-15408] updated changelog 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-15408) Rotation of slave agent launch logs is broken for Windows masters
SCM/JIRA link daemon commented on JENKINS-15408 Rotation of slave agent launch logs is broken for Windows masters Code changed in jenkins User: Erik Molekamp Path: changelog.html core/src/main/java/hudson/util/io/ReopenableRotatingFileOutputStream.java http://jenkins-ci.org/commit/jenkins/e6553330d678d1bc43961e165753783cbee5d784 Log: Merge pull request #582 from molekamp/ReopenableRotatingFileOutputStream-windows fixed JENKINS-15408: Rotation of slave launch logs on Windows Compare: https://github.com/jenkinsci/jenkins/compare/ec0b59d2306a...e6553330d678 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-15834) It's not possible to specify multiple property files in parametrised trigger
cjo9900 commented on JENKINS-15834 It's not possible to specify multiple property files in parametrised trigger Pull request to allow multiple files as a comma separated list. https://github.com/jenkinsci/parameterized-trigger-plugin/pull/28 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-15408) Rotation of slave agent launch logs is broken for Windows masters
dogfood commented on JENKINS-15408 Rotation of slave agent launch logs is broken for Windows masters Integrated in jenkins_main_trunk #2081 [FIXED JENKINS-15408] updated changelog (Revision ebd791a02ee6e53cf0238121d9e500b7ca3da6c5) [FIXED JENKINS-15408] updated changelog (Revision 890001ba9522f2eb94c152597f4cd20122d535b1) Result = UNSTABLE erik.molekamp : ebd791a02ee6e53cf0238121d9e500b7ca3da6c5 Files : changelog.html erik.molekamp : 890001ba9522f2eb94c152597f4cd20122d535b1 Files : changelog.html 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-15834) It's not possible to specify multiple property files in parametrised trigger
cjo9900 started work on JENKINS-15834 It's not possible to specify multiple property files in parametrised trigger Change By: cjo9900 (17/Nov/12 5:00 PM) Status: Open In Progress 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-15851) SCM Polling consistently fail in 1.490 and TFS plugin 1.20
Ken Egozi created JENKINS-15851 SCM Polling consistently fail in 1.490 and TFS plugin 1.20 Issue Type: Bug Assignee: redsolo Components: tfs Created: 17/Nov/12 6:26 PM Description: polling consistently fail since upgrade to 1.490 with stacktrace: ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@1fee2db[Latest] java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(Unknown Source) at hudson.Launcher.inherit(Launcher.java:1068) at hudson.Launcher.access$100(Launcher.java:80) at hudson.Launcher$LocalLauncher.launch(Launcher.java:756) at hudson.Launcher$ProcStarter.start(Launcher.java:346) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:988) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:955) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:60) at java.lang.Thread.run(Unknown Source) Environment: win2008R2, Jenkings 1.490, java7, tfs plugin 1.20 Project: Jenkins Labels: scm polling Priority: Critical Reporter: Ken Egozi 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-11592) NPE: Failed to record SCM polling
Ken Egozi assigned JENKINS-11592 to Ken Egozi NPE: Failed to record SCM polling Change By: Ken Egozi (17/Nov/12 6:26 PM) Assignee: kutzi Ken Egozi 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-11592) NPE: Failed to record SCM polling
Ken Egozi commented on JENKINS-11592 NPE: Failed to record SCM polling @Kutzi - done. https://issues.jenkins-ci.org/browse/JENKINS-15851 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-15499) HistoryWidget/entry.jelly throws NullPointerException
SCM/JIRA link daemon commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException Code changed in jenkins User: Richard Mortimer Path: changelog.html core/src/main/java/hudson/widgets/HistoryWidget.java http://jenkins-ci.org/commit/jenkins/e429b6979b5d7361168a743c9e32801e2a9b Log: [FIXED JENKINS-15499] HistoryWidget/entry.jelly throws NullPointerException Wrap history iterable to hide class implementation details. Jelly was getting confused by the history underlying class being implemented as an extension of Map 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-15499) HistoryWidget/entry.jelly throws NullPointerException
SCM/JIRA link daemon resolved JENKINS-15499 as Fixed HistoryWidget/entry.jelly throws NullPointerException Change By: SCM/JIRA link daemon (17/Nov/12 7:01 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-15831) Switch line colors in graph
Ognjen Bubalo resolved JENKINS-15831 as Fixed Switch line colors in graph version 1.0.9 fixes it Change By: Ognjen Bubalo (17/Nov/12 7:08 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-15217) Wrong vertical scale in coverage report graph
Ognjen Bubalo resolved JENKINS-15217 as Fixed Wrong vertical scale in coverage report graph version 1.0.9 fixes it Change By: Ognjen Bubalo (17/Nov/12 7:09 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-15158) Sometimes starts the wrong instance
mike bayer commented on JENKINS-15158 Sometimes starts the wrong instance this is likely a duplicate of JENKINS-12332 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-12332) only start an EC2 instance if a build is actually going to occur, per current label expressions
mike bayer commented on JENKINS-12332 only start an EC2 instance if a build is actually going to occur, per current label expressions note that issue JENKINS-15158 seems to describe the same phenomenon. 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-15680) I get this error when using maven release plugin: cvs commit: cannot commit with sticky date for file `pom.xml'
Michael Clarke commented on JENKINS-15680 I get this error when using maven release plugin: cvs commit: cannot commit with sticky date for file `pom.xml' Sorry, I'm not sure what the issue is here. You need to perform a checkout without setting the -d option on the checkout command. This issue isn't a restriction that's being forced by Jenkins, but a restriction on CVS. 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-15842) Jenkins V1.489 ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@17a7476[ProjName] java.lang.StringIndexOutOfBoundsException: String index out of range: -1
kutzi resolved JENKINS-15842 as Duplicate Jenkins V1.489 ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@17a7476[ProjName] java.lang.StringIndexOutOfBoundsException: String index out of range: -1 Change By: kutzi (17/Nov/12 11:05 PM) Status: Open Resolved Resolution: Duplicate 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-15851) SCM Polling consistently fail in 1.490 and TFS plugin 1.20
kutzi resolved JENKINS-15851 as Duplicate SCM Polling consistently fail in 1.490 and TFS plugin 1.20 Change By: kutzi (17/Nov/12 11:06 PM) Status: Open Resolved Resolution: Duplicate 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-4951) JUnit report doesn't distinguish between test failures and errors
Telmo Brugnara commented on JENKINS-4951 JUnit report doesn't distinguish between test failures and errors I've been working on this and I have working code at a forked repo: https://github.com/tbrugz/jenkins/commits/distinguish-test-failures-and-errors Some review is highly needed since this is my first contribution to the project and many files have been changed 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-4951) JUnit report doesn't distinguish between test failures and errors
Telmo Brugnara updated JENKINS-4951 JUnit report doesn't distinguish between test failures and errors Screenshot of test result and test result trend. Dark red are the 'error' tests Change By: Telmo Brugnara (17/Nov/12 11:15 PM) Attachment: test-result.png Attachment: test-result-trend.png 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-15852) Unable to delete workspace
Sean Killeen created JENKINS-15852 Unable to delete workspace Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git, github, msbuild Created: 18/Nov/12 4:18 AM Description: (as an aside, I love the idea of Jenkins. Thanks for your hard work!) New user so it's possible I may have missed something basic, but I've been reading/testing for 4+ hours now. I don't even seem to be able to get to the point where I can pull the source from github (it fails while cleaning the workspace). I have tried reinstalling Jenkins from Program Files (x86) to C:\Jenkins, and then I eventually specified the specific workspace below of E:\JenkinsWorkspace to test it out. All are failing, so I ruled out spaces and extra-long paths I think. Happy to provide any other information to help troubleshoot. Looking forward to getting this solved! Build Output Log tarted by user anonymous Building in workspace E:\JenkinsWorkspace Checkout:JenkinsWorkspace / E:\JenkinsWorkspace - hudson.remoting.LocalChannel@1c1b26c Using strategy: Default Cloning the remote Git repository Cloning repository https://github.com/SeanKilleen/Skillustrator git --version Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information ERROR: Failed to clean the workspace java.io.IOException: Unable to delete E:\JenkinsWorkspace at hudson.Util.deleteFile(Util.java:243) at hudson.Util.deleteRecursive(Util.java:293) at hudson.FilePath$11.invoke(FilePath.java:982) at hudson.FilePath$11.invoke(FilePath.java:980) at hudson.FilePath.act(FilePath.java:851) at hudson.FilePath.act(FilePath.java:824) at hudson.FilePath.deleteRecursive(FilePath.java:980) at hudson.plugins.git.GitAPI.clone(GitAPI.java:241) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1044) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986) at hudson.FilePath.act(FilePath.java:851) at hudson.FilePath.act(FilePath.java:824) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:986) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1142) at hudson.model.AbstractProject.checkout(AbstractProject.java:1325) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1516) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) ERROR: Error cloning remote repo 'origin' : Failed to delete workspace hudson.plugins.git.GitException: Failed to delete workspace at hudson.plugins.git.GitAPI.clone(GitAPI.java:244) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1044) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986) at hudson.FilePath.act(FilePath.java:851) at hudson.FilePath.act(FilePath.java:824) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:986) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1142) at hudson.model.AbstractProject.checkout(AbstractProject.java:1325) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1516) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: java.io.IOException: Unable to delete E:\JenkinsWorkspace at hudson.Util.deleteFile(Util.java:243) at hudson.Util.deleteRecursive(Util.java:293) at hudson.FilePath$11.invoke(FilePath.java:982) at hudson.FilePath$11.invoke(FilePath.java:980) at hudson.FilePath.act(FilePath.jav
[JIRA] (JENKINS-15852) Unable to delete workspace
Sean Killeen commented on JENKINS-15852 Unable to delete workspace Another item of note: This spawns wish.exe (a part of msysgit) and it fails to close. It leaves a handle open on that directory. However, I've tried manually shutting down all instances of wish.exe and double-checking with ProcExp that no handle includes that path, to no avail. 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
