[JIRA] (JENKINS-15328) Build name in promotion log is broken
OHTAKE Tomohiro created JENKINS-15328 Build name in promotion log is broken Issue Type: Bug Assignee: OHTAKE Tomohiro Attachments: Untitled.png Components: promoted-builds Created: 27/Sep/12 6:04 AM Description: Promoted builds 2.7 does not show build name correctly. See the attached image. Workarounds Downgrade to 2.6.2 Append "console" to URL Environment: Promoted builds 2.7 Project: Jenkins Priority: Minor Reporter: OHTAKE Tomohiro 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-15328) Build name in promotion log is broken
OHTAKE Tomohiro started work on JENKINS-15328 Build name in promotion log is broken Change By: OHTAKE Tomohiro (27/Sep/12 6:05 AM) Status: Open InProgress 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-7880) HTTP request for checkArtifacts hangs Hudson for a long time on large workarea
evernat resolved JENKINS-7880 as Duplicate HTTP request for checkArtifacts hangs Hudson for a long time on large workarea Change By: evernat (27/Sep/12 6:25 AM) 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-15328) Build name in promotion log is broken
OHTAKE Tomohiro resolved JENKINS-15328 as Fixed Build name in promotion log is broken Change By: OHTAKE Tomohiro (27/Sep/12 7:01 AM) Status: InProgress 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-12861) klocwork - update to recognize 9.5.x xml schema
Waldek M commented on JENKINS-12861 klocwork - update to recognize 9.5.x xml schema I'll give it a try. Thank you! BTW, could you please write what logger should I subscribe to to gather some more kw plugin debug information in future? 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-15293) Can't configure Maven Installations on Jenkins ver. 1.483
Jeroen Ferdinandus updated JENKINS-15293 Cant configure Maven Installations on Jenkins ver. 1.483 Updated title to reflect the general problem with 1.483, since it seems it is not related to the upgrade from 1.470. Change By: Jeroen Ferdinandus (27/Sep/12 7:44 AM) Summary: CantconfigureMavenInstallationsonJenkinsver.1.483 aftermanualupgradefrom1.470 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-15320) Add 'Ignore missing file' option.
Verbitan commented on JENKINS-15320 Add Ignore missing file option. I've installed that plugin before, but it never showed up as an option when configuring builds. I don't know if it's a bug with the plugin, or I'm just plain stupid. Does it work on post-build actions as well as build steps? 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-15329) build.xml no longer optimizing upstreamCauses element using references
Anze Zagar created JENKINS-15329 build.xml no longer optimizing upstreamCauses element using references Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 27/Sep/12 8:55 AM Description: Jobs built after being triggered by a large chain of upstream jobs produce tremendous build.xml and log files. For example, previously (in past Jenkins versions, not sure which but it must have been from like 3 months ago that I last built such a chain of jobs) build.xml's causes element consisted of elements like this: hudson.model.Cause_-UpstreamCause upstreamProjectproject2/upstreamProject upstreamUrljob/project2//upstreamUrl upstreamBuild5/upstreamBuild upstreamCauses hudson.model.Cause_-UpstreamCause upstreamProjectproject1/upstreamProject upstreamUrljob/project1//upstreamUrl upstreamBuild3/upstreamBuild upstreamCauses hudson.model.Cause_-UpstreamCause reference="../../../../../hudson.model.Cause_-UpstreamCause2/upstreamCauses/hudson.model.Cause_-UpstreamCause"/ /upstreamCauses /hudson.model.Cause_-UpstreamCause /upstreamCauses /hudson.model.Cause_-UpstreamCause The upstream cause which is already listed previously in the build.xml is simply just referenced so the whole tree of upstream causes doesn't need to repeat. But now instead of having the hudson.model.Cause_-UpstreamCause reference..., build.xml contains completely dereferenced chanin of upstream causes. This of course doesn't scale because build.xml files will grow exponentally with the size of the job dependency chain. The same problem is also with the console log files. Efectivelly, I now have jobs which were triggered by a chain of nearly 100 other jobs and which have build.xml and console log files of sizes of several GBs (just for one build of one job!?). This of course also crashes Jenkins on startup when it wants to load these files. Project: Jenkins Priority: Major Reporter: Anze Zagar 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-14939) Support single jacoco.exec + multiple modules for sources and classes (based on patterns)
Mickael Istria updated JENKINS-14939 Support single jacoco.exec + multiple modules for sources and classes (based on patterns) Made it blocker since it make the plugin not usable in many cases Change By: Mickael Istria (27/Sep/12 9:01 AM) Priority: Major Blocker 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-15166) Gradle plugin fails to save selected Gradle Version in Project configuration
Johannes Rost closed JENKINS-15166 as Fixed Gradle plugin fails to save selected Gradle Version in Project configuration Version 1.20 of the Plugin works as expected. Change By: Johannes Rost (27/Sep/12 9:19 AM) Status: Resolved Closed 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-15261) Mobile browsers not selectable
Ross Rowe assigned JENKINS-15261 to Ross Rowe Mobile browsers not selectable Change By: Ross Rowe (27/Sep/12 9:51 AM) Assignee: KohsukeKawaguchi RossRowe 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-15326) Error running ant with matrix build
Ross Rowe assigned JENKINS-15326 to Ross Rowe Error running ant with matrix build Change By: Ross Rowe (27/Sep/12 9:52 AM) Assignee: KohsukeKawaguchi RossRowe 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-15261) Mobile browsers not selectable
Ross Rowe started work on JENKINS-15261 Mobile browsers not selectable Change By: Ross Rowe (27/Sep/12 9:51 AM) Status: Open InProgress 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-15330) Test Connection error
Ross Rowe created JENKINS-15330 Test Connection error Issue Type: Bug Assignee: Ross Rowe Components: sauce-ondemand Created: 27/Sep/12 9:55 AM Description: Test Connection generates an error when 'Use authentication details in ~/.sauce-ondemand' selected and ~/.sauce-ondemand file doesn't exist Project: Jenkins Priority: Minor Reporter: Ross Rowe 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-15330) Test Connection error
Ross Rowe started work on JENKINS-15330 Test Connection error Change By: Ross Rowe (27/Sep/12 9:56 AM) Status: Open InProgress 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-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
pjdarton created JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive Issue Type: Improvement Assignee: Unassigned Components: core Created: 27/Sep/12 10:09 AM Description: Please enhance the hudson.Util.deleteContentsRecursive method to: delete everything it can try several times to delete everything only throw an exception if it can't delete everything (listing everything that it can't delete) Reasoning... Unlike unix, the Microsoft Windows OS does not allow a file to be deleted if something has that file open. This causes delete operations to fail. Furthermore, most installations of Windows have software that monitors the filesystem for activity and then inspects the contents of recently added/removed files (which means that it'll lock them, albeit temporarily), e.g. the Windows Search service anti-virus software to name but two (but Windows Vista Windows 7 seem to have additional complications) This means that builds which rely on cleaning a workspace before they start will sometimes fail (claiming that they couldn't delete everything because a file was locked), resulting in a build failing with the following output: Started by an SCM change Building remotely on jenkinsslave27 in workspace C:\hudsonSlave\workspace\MyProject Purging workspace... hudson.util.IOException2: remote file operation failed: C:\hudsonSlave\workspace\MyProject at hudson.remoting.Channel@6f0564d7:jenkinsslave27 at hudson.FilePath.act(FilePath.java:835) at hudson.FilePath.act(FilePath.java:821) at hudson.plugins.accurev.AccurevSCM.checkout(AccurevSCM.java:331) at hudson.model.AbstractProject.checkout(AbstractProject.java:1218) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:586) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475) at hudson.model.Run.run(Run.java:1434) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Caused by: java.io.IOException: Unable to delete C:\hudsonSlave\workspace\MyProject\...\src\...\foo - files in dir: [C:\hudsonSlave\workspace\MyProject\...\src\...\foo\bar] at hudson.Util.deleteFile(Util.java:236) at hudson.Util.deleteRecursive(Util.java:287) at hudson.Util.deleteContentsRecursive(Util.java:198) at hudson.Util.deleteRecursive(Util.java:278) at hudson.Util.deleteContentsRecursive(Util.java:198) at hudson.Util.deleteRecursive(Util.java:278) at hudson.Util.deleteContentsRecursive(Util.java:198) at hudson.Util.deleteRecursive(Util.java:278) at hudson.Util.deleteContentsRecursive(Util.java:198) at hudson.Util.deleteRecursive(Util.java:278) at hudson.Util.deleteContentsRecursive(Util.java:198) at hudson.Util.deleteRecursive(Util.java:278) at hudson.Util.deleteContentsRecursive(Util.java:198) at hudson.Util.deleteRecursive(Util.java:278) at hudson.Util.deleteContentsRecursive(Util.java:198) at hudson.Util.deleteRecursive(Util.java:278) at hudson.Util.deleteContentsRecursive(Util.java:198) at hudson.plugins.accurev.PurgeWorkspaceContents.invoke(PurgeWorkspaceContents.java:28) at hudson.plugins.accurev.PurgeWorkspaceContents.invoke(PurgeWorkspaceContents.java:11) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2161) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) 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$Worker.runTask(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) What's needed is a retry mechanism. i.e. the equivalent of using Ant's retrydelete file="foo"//retry, but with a (small) delay between attempts (and
[JIRA] (JENKINS-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
pjdarton commented on JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive Note: This file locking behavior also causes non-Jenkins issues, e.g. deleting multiple folders using Windows explorer will sometimes leave one (usually empty) folder behind, and even a simple "RD /S /Q MyFolder" will sometimes fail to delete the folder on its first attempt. In these cases, simply retrying the operation will succeed. Personally, I think it's a Windows "feature". As a workaround, I've wrapped most of my calls to Ant's delete task in retry, and this has eliminated this problem from any of my builds that manage to start BUT this doesn't help if Jenkins doesn't get as far as running my builds. e.g. I'm using the accurev plugin for my SCM and it cleans the working directory before it grabs the source - I typically get about a 1% failure rate at this stage. Whilst 1% is not a blocking issue, it's not reliable, which is not what one wants from a build system. Personally, I've found that excluding the build areas from Search anti-virus helps reduce the problem, but it is insufficient to stop these failures completely (at least on Windows 7) - something, somewhere, will still lock files, sometimes, but any investigation (after the build has failed failed) shows that no process has the file "open". 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-15332) NPE in Klocwork KloBuildAction
Krzysztof Malinowski created JENKINS-15332 NPE in Klocwork KloBuildAction Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: klocwork Created: 27/Sep/12 10:37 AM Description: Sep 27, 2012 12:32:48 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.isSummary(). Reason: java.lang.NullPointerException java.lang.NullPointerException at com.thalesgroup.hudson.plugins.klocwork.KloBuildAction.isSummary(KloBuildAction.java:102) Environment: Jenkins 1.483 on RHEL 5 x86_64, Klocwork plugin 1.12 Project: Jenkins Priority: Major Reporter: Krzysztof Malinowski 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-11160) Community ratings aren't available for 1.409.2
evernat resolved JENKINS-11160 as Fixed Community ratings arent available for 1.409.2 As I see it, there are now "Community ratings" after clicking on the link in: http://jenkins-ci.org/changelog-stable Change By: evernat (27/Sep/12 11:04 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-15333) Unable to see build history after upgrade
Ian Rogers created JENKINS-15333 Unable to see build history after upgrade Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 27/Sep/12 11:16 AM Description: Upgraded from 1.474 to 1.483 and am now unable to see old build history. New builds are creating history that can be viewed. Old builds exist on the filesystem, but no build.xml within build subdirectory. New builds also exist, with build.xml. Environment: RedHat Linux 5.6 x86_64 Tomcat 6.0.32 Java 1.6.0_24 64-bit Project: Jenkins Priority: Major Reporter: Ian Rogers 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-15334) BRakeman plugin not aviailable as a post-build step for multi-configuration projects
Matt Conway created JENKINS-15334 BRakeman plugin not aviailable as a post-build step for multi-configuration projects Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: brakeman Created: 27/Sep/12 11:25 AM Description: I have the brakeman plugin setup in jenkins, and it is available as a post-build step for a normal project, but does not show up in the post-build dropdowns for multi-configuration projects. Environment: Ubuntu 12.04 Project: Jenkins Priority: Major Reporter: Matt Conway 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-15261) Mobile browsers not selectable
SCM/JIRA link daemon commented on JENKINS-15261 Mobile browsers not selectable Code changed in jenkins User: Ross Rowe Path: pom.xml src/main/java/hudson/plugins/sauce_ondemand/BrowserAxis.java src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandBuildWrapper.java src/main/resources/hudson/plugins/sauce_ondemand/SauceOnDemandBuildWrapper/config.jelly http://jenkins-ci.org/commit/sauce-ondemand-plugin/ee1ebed44601f332dcc538a9fe5af91930cf6159 Log: JENKINS-15261 Retrieve webdriver/seleniumrc-specific browsers Compare: https://github.com/jenkinsci/sauce-ondemand-plugin/compare/58a3a6333ac4...ee1ebed44601 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-15330) Test Connection error
SCM/JIRA link daemon commented on JENKINS-15330 Test Connection error Code changed in jenkins User: Ross Rowe Path: src/main/java/hudson/plugins/sauce_ondemand/PluginImpl.java http://jenkins-ci.org/commit/sauce-ondemand-plugin/590e694d6c92e2b987ffa0ea7f031ab27e5f2f29 Log: JENKINS-15330 Handle .sauce-ondemand file not existing 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-15326) Error running ant with matrix build
Ross Rowe commented on JENKINS-15326 Error running ant with matrix build Hi Roger, could you tell me if this is still an issue for you? Cheers, Ross 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-15335) Jenkins briefly displays build queue and then it disappears until the page is reloaded
Jason Spotswood created JENKINS-15335 Jenkins briefly displays build queue and then it disappears until the page is reloaded Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 27/Sep/12 12:51 PM Description: After updating to the current released version of Jenkins, when the build queue has a number of job in it, they are briefly displayed and then they disappear. If the page is refreshed, then jobs will appear briefly again before the same thing occurs. Environment: Windows 7 using Chrome v21 Project: Jenkins Labels: queue jenkins build Priority: Major Reporter: Jason Spotswood 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-15336) Provide sample jelly template for including results from coverity plugin in email
Tim Mason created JENKINS-15336 Provide sample jelly template for including results from coverity plugin in email Issue Type: Improvement Assignee: Slide-O-Mix Components: coverity, email-ext Created: 27/Sep/12 1:20 PM Description: It would be nice if there was a sample jelly template that showed how to get results from the coverity plugin into an email. Something similar to the static-analysis.jelly file that is included with the email-ext plugin. Project: Jenkins Priority: Major Reporter: Tim Mason 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-15326) Error running ant with matrix build
Roger Lopez commented on JENKINS-15326 Error running ant with matrix build Yes this is still an issue. To make it simple to replicate the issue, I created a gist (https://gist.github.com/3793861) with a simple ant build file. With that repo I can replicate the issue like so: Create a new job, selecting the "Build multi-configuration project" option. Name the job whatever you want. Choose git for your SCM and use git://gist.github.com/3793861.git as the repo URL. Add a "Sauce OnDemand Cross-browser tests" axis. Select any combination of browsers. Add an "Invoke ant" build step and using the "test" target (without quotes). Save and build. The console output varies based on the browser selected. Here are some samples: Windows 2003 IE6 Started by upstream project "JENKINS-15326" build number 3 Building on master in workspace /Users/zroger/.jenkins/jobs/JENKINS-15326/workspace/SELENIUM_DRIVER/Windows 2003iexploreproxy6 Checkout:Windows 2003iexploreproxy6 / /Users/zroger/.jenkins/jobs/JENKINS-15326/workspace/SELENIUM_DRIVER/Windows 2003iexploreproxy6 - hudson.remoting.LocalChannel@9cd1d3c Using strategy: Default Cloning the remote Git repository Cloning repository origin Fetching upstream changes from git://gist.github.com/3793861.git Commencing build of Revision 30967741d6003357a91d27c04a030e33af1a73f4 (origin/HEAD, origin/master) Checking out Revision 30967741d6003357a91d27c04a030e33af1a73f4 (origin/HEAD, origin/master) No change to record in branch origin/HEAD No change to record in branch origin/master [Windows 2003iexploreproxy6] $ ant "-DSELENIUM_DRIVER=sauce-ondemand:?os=Windows 2003browser=iexploreproxybrowser-version=6" '-Darguments="-DSELENIUM_DRIVER=sauce-ondemand:?os=Windows 2003browser=iexploreproxybrowser-version=6"' test /usr/bin/ant: line 335: browser-version=6: command not found Buildfile: /Users/zroger/.jenkins/jobs/JENKINS-15326/workspace/SELENIUM_DRIVER/Windows 2003iexploreproxy6/build.xml BUILD FAILED Target "2003" does not exist in the project "JENKINS-15326". Total time: 0 seconds Build step 'Invoke Ant' marked build as failure Finished: FAILURE Linux Google Chrome Started by upstream project "JENKINS-15326" build number 4 Building on master in workspace /Users/zroger/.jenkins/jobs/JENKINS-15326/workspace/SELENIUM_DRIVER/Linuxgooglechrome Checkout:Linuxgooglechrome / /Users/zroger/.jenkins/jobs/JENKINS-15326/workspace/SELENIUM_DRIVER/Linuxgooglechrome - hudson.remoting.LocalChannel@9cd1d3c Using strategy: Default Last Built Revision: Revision 30967741d6003357a91d27c04a030e33af1a73f4 (origin/HEAD, origin/master) Fetching changes from 1 remote Git repository Fetching upstream changes from git://gist.github.com/3793861.git Commencing build of Revision 30967741d6003357a91d27c04a030e33af1a73f4 (origin/HEAD, origin/master) Checking out Revision 30967741d6003357a91d27c04a030e33af1a73f4 (origin/HEAD, origin/master) Warning : There are multiple branch changesets here [Linuxgooglechrome] $ ant -DSELENIUM_DRIVER=sauce-ondemand:?os=Linuxbrowser=googlechromebrowser-version= -Darguments="-DSELENIUM_DRIVER=sauce-ondemand:?os=Linuxbrowser=googlechromebrowser-version=" test /usr/bin/ant: line 335: browser-version=: command not found Buildfile: /Users/zroger/.jenkins/jobs/JENKINS-15326/workspace/SELENIUM_DRIVER/Linuxgooglechrome/build.xml test: [echo] Hello world BUILD SUCCESSFUL Total time: 0 seconds Build step 'Invoke Ant' marked build as failure Finished: FAILURE Hope this helps. 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-15336) Provide sample jelly template for including results from coverity plugin in email
Slide-O-Mix commented on JENKINS-15336 Provide sample jelly template for including results from coverity plugin in email As the developer of this plugin, I don't use coverity at all, so if you have something, please submit it. Otherwise, it won't get done. 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-15336) Provide sample jelly template for including results from coverity plugin in email
Tim Mason commented on JENKINS-15336 Provide sample jelly template for including results from coverity plugin in email Sure. Sorry, I intended this request to go to the maintainers of the coverity plugin, rather than email-ext. Could you assign it to them? 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-15336) Provide sample jelly template for including results from coverity plugin in email
Slide-O-Mix assigned JENKINS-15336 to Tim Mason Provide sample jelly template for including results from coverity plugin in email I'm not sure who the maintainer of the coverity plugin is. Change By: Slide-O-Mix (27/Sep/12 1:49 PM) Assignee: Slide-O-Mix TimMason 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-15336) Provide sample jelly template for including results from coverity plugin in email
Slide-O-Mix updated JENKINS-15336 Provide sample jelly template for including results from coverity plugin in email Change By: Slide-O-Mix (27/Sep/12 1:49 PM) Component/s: email-ext 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-15336) Provide sample jelly template for including results from coverity plugin in email
Tim Mason assigned JENKINS-15336 to Unassigned Provide sample jelly template for including results from coverity plugin in email Change By: Tim Mason (27/Sep/12 1:54 PM) Assignee: TimMason 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-15336) Provide sample jelly template for including results from coverity plugin in email
Tim Mason assigned JENKINS-15336 to Josh Vinson Provide sample jelly template for including results from coverity plugin in email Hi Josh, assigning this to you. Change By: Tim Mason (27/Sep/12 1:56 PM) Assignee: JoshVinson 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-15335) Jenkins briefly displays build queue and then it disappears until the page is reloaded
Philipp Mohrenweiser commented on JENKINS-15335 Jenkins briefly displays build queue and then it disappears until the page is reloaded can confirm this under various browsers and os clientside with debian squeeze 64 and jenkins 1.483 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-15337) Conflict with Perforce and Jenkins using @ in workspace path
Marek Gimza
created JENKINS-15337
Conflict with Perforce and Jenkins using @ in workspace path
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Unassigned
Components:
perforce
Created:
27/Sep/12 2:54 PM
Description:
We use perforce as our SCM tool.
When multiple builds of the same JOB are run, Jenkins creates a workspace for each build (running job) with an '@n' appended (where n is a digit such as @2, @3, etc... ).
For example:
job1 - /Nodes/path/job
job2 - /Nodes/path/job@2
job3 - /Nodes/path/job@3
job4 - /Nodes/path/job@4
We use the Post-Build Task plugin to run a p4 commands (in a script) on any files where a compile error was introduced during the build.
The perforce command syntax uses '@' to specify specific versions of a file.
For example:
p4 annotate /the/path/to/my/file@45678
...The p4 command fails when the '@' is in the path:
p4 annotate /Nodes/path/job@4/the/path/to/my/file@45678
...Perforce tries to process /Nodes/path/job@4 only!
CODE
The location where the '@' is defined and used in the jenkins-core:
FILE: jenkins-core/src/main/javs/hudson/slaves/WorkspaceList.java
USED HERE
--
public synchronized Lease allocate(FilePath base, Object context) throws InterruptedException {
for (int i=1; ; i++) {
FilePath candidate = i==1 ? base : base.withSuffix(COMBINATOR+i);
Entry e = inUse.get(candidate);
if(e!=null !e.quick e.context!=context)
continue;
return acquire(candidate,false,context);
}
DEFINED HERE
-
private static final String COMBINATOR = System.getProperty(WorkspaceList.class.getName(),"@");
}
Environment:
Any OS that can run the perforce p4 command.
Project:
Jenkins
Labels:
jenkins
Priority:
Major
Reporter:
Marek Gimza
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-15335) Jenkins briefly displays build queue and then it disappears until the page is reloaded
Dirk Kuypers
commented on JENKINS-15335
Jenkins briefly displays build queue and then it disappears until the page is reloaded
thanks for opening, I just asked a question about this on jenkins-users. Here are my thoughts:
I think 1483 introduced a bug with updating the build queue via Ajax.
Initially I can see the waiting jobs and after about 10 seconds there
is the automatic update via ./ajaxBuildQueue which calls t:queue
items="${it.queueItems}"/ if I googled it right.
One changelog entry for 1483 was: Fixed the lock contention problem on
Queue.getItems() but without a correponding JIRA ticket mentioned
which looks suspicious to me.
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-15338) Sonar plugin can't consume installed Maven runtimes
Mickael Istria created JENKINS-15338 Sonar plugin cant consume installed Maven runtimes Issue Type: Bug Assignee: sonarteam Components: sonar Created: 27/Sep/12 3:07 PM Description: I have a machine where I cannot access "mvn" in path directly. Instead, all Maven build steps have to select an installation of Maven to run against. Maven installations are configured for the whole Jenkins. Sonar plugin should follow the same principle and ask user for a Maven installaiton to use, instead of assuming it can use a "mvn" from PATH. Project: Jenkins Priority: Blocker Reporter: Mickael Istria 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-15338) Sonar plugin can't consume installed Maven runtimes
Mickael Istria commented on JENKINS-15338 Sonar plugin cant consume installed Maven runtimes Some background: failing job https://hudson.eclipse.org/sandbox/job/SWTBot-Sonar/3/console workspace $ mvn -f /opt/users/hudsonbuild/.hudson/jobs/SWTBot-Sonar/workspace/pom.xml -e -B sonar:sonar -Dmaven.repo.local=$WORKSPACE/.maven/repo -Dsonar.host.url="" href="http://dev.eclipse.org/sonar">http://dev.eclipse.org/sonar FATAL: command execution failed java.io.IOException: Cannot run program "mvn" (in directory "/opt/users/hudsonbuild/.hudson/jobs/SWTBot-Sonar/workspace"): java.io.IOException: error=13, Permission denied 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-11985) javax.net.ssl.SSLException: Received fatal alert: bad_record_mac with subversion-plugin 1.37
tq rst commented on JENKINS-11985 javax.net.ssl.SSLException: Received fatal alert: bad_record_mac with subversion-plugin 1.37 Same problem here. Adding -Dsvnkit.http.sslProtocols=SSLv3 didn't help. This is with Jenkins 1.443 + svn 1.40 and 1.42, and also with 1.483 + svn 1.43. 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-11985) javax.net.ssl.SSLException: Received fatal alert: bad_record_mac with subversion-plugin 1.37
tq rst edited a comment on JENKINS-11985 javax.net.ssl.SSLException: Received fatal alert: bad_record_mac with subversion-plugin 1.37 Same problem here. Adding -Dsvnkit.http.sslProtocols=SSLv3 didn't help. This is with Jenkins 1.443 + svn 1.40 and 1.42, and also with 1.483 + svn 1.43. This is a showstopper for us. 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-11985) javax.net.ssl.SSLException: Received fatal alert: bad_record_mac with subversion-plugin 1.37
tq rst edited a comment on JENKINS-11985 javax.net.ssl.SSLException: Received fatal alert: bad_record_mac with subversion-plugin 1.37 Same problem here. Adding -Dsvnkit.http.sslProtocols=SSLv3 didn't help. This is with Jenkins 1.443 + svn 1.40 and 1.42, and also with 1.483 + svn 1.43. This is a showstopper for us. Reverting back to 1.34 used to work for us, but the latest version only allows to downgrade to 1.42, so we're pretty much stuck. 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
Ulli Hafner commented on JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project And please also attach the template that you are using. 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
Ulli Hafner commented on JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project I can't reproduce the problem. On my machine I get results even with maven. Can you please attach one of your build.xml files that are produced by the maven job? 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-2614) cvs update fails if there are non-ascii characters in filename
Hannes Kogler assigned JENKINS-2614 to Hannes Kogler cvs update fails if there are non-ascii characters in filename Change By: Hannes Kogler (27/Sep/12 4:16 PM) Assignee: MichaelClarke HannesKogler 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-2614) cvs update fails if there are non-ascii characters in filename
Hannes Kogler assigned JENKINS-2614 to Unassigned cvs update fails if there are non-ascii characters in filename Change By: Hannes Kogler (27/Sep/12 4:17 PM) Assignee: HannesKogler 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-11985) javax.net.ssl.SSLException: Received fatal alert: bad_record_mac with subversion-plugin 1.37
tq rst edited a comment on JENKINS-11985 javax.net.ssl.SSLException: Received fatal alert: bad_record_mac with subversion-plugin 1.37 Same problem here. Adding -Dsvnkit.http.sslProtocols=SSLv3 didn't help. This is with Jenkins 1.443 + svn 1.40 and 1.42, and also with 1.483 + svn 1.43. This is a showstopper for us. Reverting back to 1.34 used to work for us, but the latest version only allows to downgrade to 1.42, so we're pretty much stuck. Update: -Dsvnkit.http.sslProtocols=SSLv3 does work after all. It has to be done on every node, though. 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-13614) archiving artefacts from remote MacOS X, IBM AIX slave fails
Brett Delle Grazie commented on JENKINS-13614 archiving artefacts from remote MacOS X, IBM AIX slave fails We run AIX slaves but with the LTS release, still fails on 1.466.2, stackdump attached. Any chance of an LTS release with the relevant patches applied for testing? (from LTS 1.466.2 on AIX 6.1) ERROR: Failed to archive artifacts: dist/*/ hudson.util.IOException2: java.lang.UnsupportedOperationException at hudson.FilePath.copyRecursiveTo(FilePath.java:1784) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:116) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:685) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:632) at hudson.model.Run.run(Run.java:1463) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Caused by: java.util.concurrent.ExecutionException: java.lang.UnsupportedOperationException at hudson.remoting.Channel$4.adapt(Channel.java:696) at hudson.remoting.Channel$4.adapt(Channel.java:691) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55) at hudson.FilePath.copyRecursiveTo(FilePath.java:1782) ... 10 more Caused by: java.lang.UnsupportedOperationException at hudson.os.PosixAPI$1.getCurrentWorkingDirectory(PosixAPI.java:59) at org.jruby.ext.posix.util.ExecIt.run(ExecIt.java:59) at org.jruby.ext.posix.util.ExecIt.runAndWait(ExecIt.java:51) at org.jruby.ext.posix.JavaLibCHelper.readlink(JavaLibCHelper.java:196) at org.jruby.ext.posix.JavaPOSIX.readlink(JavaPOSIX.java:160) at hudson.Util.resolveSymlink(Util.java:1067) at hudson.Util.resolveSymlink(Util.java:1030) at hudson.util.DirScanner$Glob.scan(DirScanner.java:115) at hudson.FilePath.writeToTar(FilePath.java:1820) at hudson.FilePath.access$1000(FilePath.java:166) at hudson.FilePath$36.invoke(FilePath.java:1761) at hudson.FilePath$36.invoke(FilePath.java:1758) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2193) 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(FutureTask.java:314) at java.util.concurrent.FutureTask.run(FutureTask.java:149) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919) at hudson.remoting.Engine$1$1.run(Engine.java:60) at java.lang.Thread.run(Thread.java:736) 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
hhuynh updated JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project Change By: hhuynh (27/Sep/12 5:01 PM) Attachment: config.xml Attachment: static-analysis.jelly 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-15326) Error running ant with matrix build
Roger Lopez commented on JENKINS-15326 Error running ant with matrix build This patch seems to work for me, but I'm not familiar enough with the project to know why the quotes were there in the first place. https://gist.github.com/3795164 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-13655) Gzipped log are not shown correctly
Martin Schröder commented on JENKINS-13655 Gzipped log are not shown correctly Hello everyone. This issue will be fixed as soon as the following pull request is merged into the Jenkins mainline: https://github.com/jenkinsci/jenkins/pull/549 The only prerequisite is that Jenkins needs to be compiled against Stapler with a version = 1.196, as that includes this Stapler patchset: https://github.com/stapler/stapler/pull/10 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-12735) No upstream or downstream resolution with Maven version ranges
Jay Meyer edited a comment on JENKINS-12735 No upstream or downstream resolution with Maven version ranges in Jenkins 1.482, this is causing Jenkins to kick off downstream builds of un-related versions. Example: mygrp-projCore-3.4 is kicking off mygrp-projWeb-3.4 (which is correct) and also the old mygrp-projWeb-3.3. The old projWeb artifact id matches, but the version does not match. So when Jenkins is configured to build both versions in different jobs, Jenkins is kicking off all versions of old downstream jobs. 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
Ulli Hafner commented on JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project Of course, there is no data when the build failed because Findbugs does not create a result Or am I missing something? 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-15319) Failure starting slave nodes
John Dyer commented on JENKINS-15319 Failure starting slave nodes I have found a few reports of this type of error on the Amazon forums and it seems to be some sort of race condition when calling describeInstance() within a few seconds of creating the instance. I guess that instance hasn't propagated in the AWS system ? I was thinking the simply solution here might be to add a catch this and add a configurable retry counter with a delay on this type of exception. Thoughts? 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
hhuynh commented on JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project There's no build.xml (project is Maven not Ant). The config.xml is of the job, not Jenkins master. Here's the screen shot. I printed out action.result and it's null if the build failed. 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
hhuynh updated JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project Change By: hhuynh (27/Sep/12 7:07 PM) Attachment: build.xml 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
hhuynh updated JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project Change By: hhuynh (27/Sep/12 7:08 PM) Attachment: screenshot-1.jpg 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-15169) Warning Plugin - Graph Configuration Error
Ulli Hafner commented on JENKINS-15169 Warning Plugin - Graph Configuration Error It would help see see the difference between the working and broken URL. Can you please post? 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
Ulli Hafner resolved JENKINS-15324 as Fixed email-ext static-analysis template show empty data for Findbugs if job is a Maven project I see, this is a bug that I already have fixed recently. Now every maven build will always have a result. (Your build is a multi-module build?) The fix will be part of the next analysis core release... Change By: Ulli Hafner (27/Sep/12 7:28 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
hhuynh commented on JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project That's great. My test project is single module though. Can I download the new fix somewhere to test it? 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
Ulli Hafner commented on JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project You can use our public CI: https://buildhive.cloudbees.com/view/My%20Repositories/job/jenkinsci/job/analysis-core-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-15339) Node Label Parameter plugin breaks Windows batch file build steps if Name field not filled in
Glenn Coombs created JENKINS-15339 Node Label Parameter plugin breaks Windows batch file build steps if Name field not filled in Issue Type: Bug Affects Versions: current Assignee: domi Components: nodelabelparameter Created: 27/Sep/12 8:07 PM Description: When using the Node Label Parameter plugin it breaks any build steps that run Windows batch files if you don't fill in a value for the Name field. To reproduce, create a new free style job and select the "This build is parameterized" option. Select a default slave that is a windows machine. Leave the Name field empty. Add a build step to run a Windows batch file and fill in a simple command like echo %PATH% or ver. When you run the job the build step will fail with an error message like this: Building remotely on WINDOWS_SERVER in workspace C:\jenkins\workspace\update-scripts-all-slaves update-scripts-all-slaves $ cmd /c call C:\Users\JENKIN~1.SIM\AppData\Local\Temp\hudson7760734931475434766.bat The parameter is incorrect FATAL: command execution failed java.io.IOException: Cannot run program "cmd" (in directory "C:\jenkins\workspace\update-scripts-all-slaves"): CreateProcess error=87, The parameter is incorrect at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:709) at hudson.Launcher$ProcStarter.start(Launcher.java:338) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:934) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:901) 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) Caused by: java.io.IOException: CreateProcess error=87, The parameter is incorrect at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.init(Unknown Source) at java.lang.ProcessImpl.start(Unknown Source) ... 17 more Build step 'Execute Windows batch command' marked build as failure This only happens if you leave the Name field empty as I originally did. It also only affects Windows batch files, linux shell command build steps work as expected even with an empty Name field. Environment: I am running Jenkins 1.480 with the master installed on a Windows 7 machine although I suspect this problem will be the same if I was using a linux master. Only affects build steps on Windows slaves. Project: Jenkins Labels: plugin nodelabelparameter Priority: Minor Reporter: Glenn Coombs 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-2614) cvs update fails if there are non-ascii characters in filename
Michael Clarke assigned JENKINS-2614 to Michael Clarke cvs update fails if there are non-ascii characters in filename Change By: Michael Clarke (27/Sep/12 8:39 PM) Assignee: MichaelClarke 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-15340) Add 'Are you sure' on Reload configuration from disk
Denis Blanchette created JENKINS-15340 Add Are you sure on Reload configuration from disk Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: core Created: 27/Sep/12 8:41 PM Description: The button "Reload configuration from disk" in Manage Jenkins can be easily pressed by mistake by an administrator. This happened to us and we lost functionality of Jenkins for more than an hour (we waited for Jenkins to come back by itself but it never did and we decided to restart the service on the master). Why not make the link points to an "Are you sure?" page like for the safe restart link? Thank you very much! Project: Jenkins Labels: core configuration management Priority: Minor Reporter: Denis Blanchette 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
Ulli Hafner reopened JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project Hmm, ok maybe the change was not related. (I changed a previous NPE when the maven result was accessed). Change By: Ulli Hafner (27/Sep/12 8:44 PM) Resolution: Fixed Status: Resolved Reopened 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
Ulli Hafner edited a comment on JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project Hmm, ok maybe the change was not related. (I fixed a previous NPE when the maven result was accessed). 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
Ulli Hafner commented on JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project Just a side note: what is shown on the build page for that build? Is there a result visible, or only for the other builds? 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-7487) Make hudson aware of the release artifacts.
lesterp commented on JENKINS-7487 Make hudson aware of the release artifacts. We see similar behavior. To add to what Justin sees above, if we don't check "Disable automatic artifact archiving" under the Maven Build step, and let Jenkins grab the artifacts per module, what gets saved after running the release plugin is the initial SNAPSHOT artifact of the project (from release:prepare, I believe). If we check "Disable automatic artifact archiving" and add a post-build step to archive the artifacts we want, it saves the correct 'release' (non-SNAPSHOT) artifacts, but the Jenkins fingerprints for the artifacts are invalid: "The fingerprint xxx did not match any of the recorded data." 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-15335) Jenkins briefly displays build queue and then it disappears until the page is reloaded
Jason Spotswood commented on JENKINS-15335 Jenkins briefly displays build queue and then it disappears until the page is reloaded I agree that the problem seems to be introduced in 1.483. I have rolled back to 1.480 in the meantime. My experience is that the queue disappears after 5 seconds or so through via ajax refresh of the queue status. 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-7436) Add support for perforce shelve builds
Frank Merrow commented on JENKINS-7436 Add support for perforce shelve builds FWIW: This kind of a "pre-flight" feature has been on our To Do List for awhile now (just like this CR) . . . It would be great if you did it for us. wink Issue "voted" and "watched" 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-2948) Perforce plugin should do validation of configuration options
Frank Merrow commented on JENKINS-2948 Perforce plugin should do validation of configuration options We have started adding the following to all jobs: p4 login -s IF ERRORLEVEL 1 EXIT %ERRORLEVEL% We have tickets setup on all Jenkins and would expect this to NEVER fail . . . but of course it does on occasion because somebody does something to cause a logout. The reason I've posted here, is that even putting this at the start of every job is not enough . . . We really want this done BEFORE all the stuff your plugin does to get the job started . . . and in fact, it would be nice if polling itself could do something similar . . . though in that case where do you report the error? It would be nice to be able to check as "user should already be logged in" check box and have you add a bunch of checking for this . . . the error messages we get now are often obscure and don't immediately lead the uninitiated to the conclusion that the automation username need to be logged in again. IN FACT . . . I'm way out there now, but just a thought . . . one of the annoying things about this happening is that when a single slave has a problem like this, a whole bunch of work will "abort into that slave" . . . it would be nice if when a username isn't logged in, you could affect the scheduling too so that host wasn't used until the username is logged back in or perhaps disable the slave until somebody can bring Perforce on-line again. 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-15292) RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml
sbrinkmeyer commented on JENKINS-15292 RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml i too now have this issue with RedeployPublisher channel stopped Archiving artifacts Maven RedeployPublisher use rhel.61.x32.1 maven settings from : /home/cmadmin/.m2/settings.xml ERROR: Publisher hudson.maven.RedeployPublisher aborted due to exception hudson.util.IOException2: Failed to copy /home/cmadmin/.m2/settings.xml to /usr/local/jenkins-secure/tmp/jenkins314223192807287748temp-settings.xml jenkins version 1.483 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-15267) Git-Gerrit Bug
markewaite resolved JENKINS-15267 as Not A Defect Git-Gerrit Bug It is generally much better to request help from the Jenkins mailing list rather than to open a bug report which ends in the request "please help me". The mailing list is viewed by many more people than those who review bug reports, so you'll have a greater chance of an answer from the mailing list. jenkinsci-us...@googlegroups.com is the address of the users mailing list. Change By: markewaite (27/Sep/12 10:31 PM) Status: Open Resolved Resolution: NotADefect 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-15337) Conflict with Perforce and Jenkins using @ in workspace path
Rob Petti commented on JENKINS-15337 Conflict with Perforce and Jenkins using @ in workspace path This sounds more like an issue with your script to me? 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-15337) Conflict with Perforce and Jenkins using @ in workspace path
Rob Petti commented on JENKINS-15337 Conflict with Perforce and Jenkins using @ in workspace path To clarify, you aren't properly escaping the path before passing it onto the perforce command line. The mapping is here: http://www.perforce.com/perforce/r12.1/manuals/cmdref/o.fspecs.html In your case, you will need to make your script replace @ in the path with %40. It will work properly then (or you can just reference the file using the relative path, rather than the absolute one). 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-15341) New workflow creation should be in the form validation
Kohsuke Kawaguchi created JENKINS-15341 New workflow creation should be in the form validation Issue Type: Bug Assignee: Max Spring Components: jenkow Created: 27/Sep/12 11:15 PM Description: The current user experience in Jenkow plugin is such that. you create a new job, specifying a non-existent workflow name you run the build once, make it fail (this is when the plugin internally creates a skeleton workflow file) you checkout the newly created bpmn file, and edit it. This idea of inducing a failure to have it created it is bit strange, and it also has an undesirable side-effect that if you have a typo in the workflow name, you end up creating one. I think a better user experience is: you create a new job, specifying a non-existent workflow name form validation gives you a button/link that lets you create new template workflow files (or copy from existing one, which is likely useful, too) see Subversion plugin for how it does this, when the user types in a repository URL for which it doesn't yet have a credential. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi 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-15342) NullPointerException in workflow editor trying to move Jenkins task
Kohsuke Kawaguchi created JENKINS-15342 NullPointerException in workflow editor trying to move Jenkins task Issue Type: Bug Assignee: Max Spring Components: jenkow-plugin Created: 27/Sep/12 11:24 PM Description: It's not clear if this is a bug in your Activiti designer extension or a bug in Activity designer itself, but while I was playing with the workflow, I somehow managed to create one Jenkins task that refused to be moved. When I try to drag the task, I get the following NPE: java.lang.NullPointerException at org.activiti.designer.features.MoveActivityFeature.moveBoundaryEvents(MoveActivityFeature.java:139) at org.activiti.designer.features.MoveActivityFeature.moveActivityChilds(MoveActivityFeature.java:118) at org.activiti.designer.features.MoveActivityFeature.postMoveShape(MoveActivityFeature.java:62) at org.eclipse.graphiti.features.impl.DefaultMoveShapeFeature.moveShape(DefaultMoveShapeFeature.java:67) at org.eclipse.graphiti.internal.command.MoveShapeFeatureCommandWithContext.execute(MoveShapeFeatureCommandWithContext.java:81) at org.eclipse.graphiti.internal.command.CommandContainer.execute(CommandContainer.java:81) at org.eclipse.graphiti.ui.internal.command.GefCommandWrapper.execute(GefCommandWrapper.java:51) at org.eclipse.graphiti.ui.internal.editor.EmfOnGefCommand.execute(EmfOnGefCommand.java:54) at org.eclipse.graphiti.internal.command.GFPreparableCommand2.doExecute(GFPreparableCommand2.java:37) at org.eclipse.emf.transaction.RecordingCommand.execute(RecordingCommand.java:135) at org.eclipse.emf.workspace.EMFCommandOperation.doExecute(EMFCommandOperation.java:119) at org.eclipse.emf.workspace.AbstractEMFOperation.execute(AbstractEMFOperation.java:150) at org.eclipse.core.commands.operations.DefaultOperationHistory.execute(DefaultOperationHistory.java:513) at org.eclipse.emf.workspace.impl.WorkspaceCommandStackImpl.doExecute(WorkspaceCommandStackImpl.java:208) at org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:165) at org.eclipse.graphiti.ui.internal.editor.GFWorkspaceCommandStackImpl.execute(GFWorkspaceCommandStackImpl.java:83) at org.eclipse.graphiti.ui.internal.editor.GFCommandStack.execute(GFCommandStack.java:124) at org.eclipse.gef.tools.AbstractTool.executeCommand(AbstractTool.java:425) at org.eclipse.gef.tools.AbstractTool.executeCurrentCommand(AbstractTool.java:438) at org.eclipse.gef.tools.DragEditPartsTracker.performDrag(DragEditPartsTracker.java:496) at org.eclipse.gef.tools.DragEditPartsTracker.handleButtonUp(DragEditPartsTracker.java:351) at org.eclipse.gef.tools.AbstractTool.mouseMove(AbstractTool.java:1159) at org.eclipse.gef.tools.SelectionTool.mouseMove(SelectionTool.java:562) at org.eclipse.gef.EditDomain.mouseMove(EditDomain.java:287) at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseMoved(DomainEventDispatcher.java:365) at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseMove(LightweightSystem.java:543) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:212) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1022) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:916) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:585) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:540) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at
[JIRA] (JENKINS-10434) Git plugin 1.1.10 fails to parse author information
markewaite commented on JENKINS-10434 Git plugin 1.1.10 fails to parse author information I attempted to duplicate this problem with various mixes of slave agents (Windows, Debian, Red Hat, CentOS) and many jobs running concurrently with a very short time to complete the job. With the current released Git plugin, there is no report of a stack trace in the user interface or in the jenkins.log file on the master. I ran both with no other jobs on the server and with multiple high demand jobs on the server. I ran 105 (7*15) configurations across those various platforms and load conditions. I assume the issue is resolved and can be closed. 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-13461) Add Build Step - Execute shell gives a 403 (Forbidden) error (js console)
markewaite updated JENKINS-13461 Add Build Step - Execute shell gives a 403 (Forbidden) error (js console) Change By: markewaite (28/Sep/12 12:09 AM) Component/s: git 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-15261) Mobile browsers not selectable
SCM/JIRA link daemon commented on JENKINS-15261 Mobile browsers not selectable Code changed in jenkins User: Ross Rowe Path: src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandBuildWrapper.java src/main/java/hudson/plugins/sauce_ondemand/SeleniumInformation.java src/main/resources/hudson/plugins/sauce_ondemand/SauceOnDemandBuildWrapper/config.jelly http://jenkins-ci.org/commit/sauce-ondemand-plugin/992e9c62dfcd8af04a45883335e3318b08246fa9 Log: JENKINS-15261 Store selected webdriver/seleniumrc-specific browsers 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
hhuynh commented on JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project I've attached the build page screen shot 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
hhuynh updated JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project Change By: hhuynh (28/Sep/12 12:53 AM) Attachment: screenshot-2.jpg 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-15343) Unable to use Conditional BuildStep Plugin with Testlink Plugin
Nigel McAdam created JENKINS-15343 Unable to use Conditional BuildStep Plugin with Testlink Plugin Issue Type: Bug Affects Versions: current Assignee: Bruno P. Kinoshita Components: testlink Created: 28/Sep/12 3:37 AM Description: Unable to use Conditional BuildStep Plugin with Testlink Plugin Testlink Plugin does not appear as a build step. Need to be able to optional run automated tests using Testlink plugin based on a parameter defined at run time Is this the cause of the issue? If you're not able to add the builder of your choice within a conditional build step (because it's not available within the dropdown), then this is likely because the builder does not provide a @DataBoundConstructor constructor and/or the Descriptor does not extend hudson.tasks.BuildStepDescriptor. For non programmers: the plugin you would like to use does not yet follow the newest Jenkins coding guidelines Environment: Testlink 1.9.3, Testlink-Jenkins Plugin 3.1.7, Conditional BuildStep Plugin 1.1, Windows XP Project: Jenkins Priority: Minor Reporter: Nigel McAdam 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-15326) Error running ant with matrix build
Ross Rowe started work on JENKINS-15326 Error running ant with matrix build Change By: Ross Rowe (28/Sep/12 4:26 AM) Status: Open InProgress 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-15326) Error running ant with matrix build
Ross Rowe commented on JENKINS-15326 Error running ant with matrix build Hi Roger, thanks for the patch, from memory I included the quotes around the arguments for Maven support. The arguments flag is really on needed for Maven builds anyway, so I'll see if I can update the code so that it only adds the build variable if it's building a Maven project. Cheers, Ross 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-15326) Error running ant with matrix build
SCM/JIRA link daemon commented on JENKINS-15326 Error running ant with matrix build Code changed in jenkins User: Ross Rowe Path: pom.xml src/main/java/hudson/plugins/sauce_ondemand/BrowserAxis.java src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandBuildWrapper.java http://jenkins-ci.org/commit/sauce-ondemand-plugin/f8ac508817d4eb4982db07f0c1171c3cda1a6b56 Log: JENKINS-15326 Removed quotes from BrowserAxis arguments 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-13614) archiving artefacts from remote MacOS X, IBM AIX slave fails
Nickolay Martinov commented on JENKINS-13614 archiving artefacts from remote MacOS X, IBM AIX slave fails Try attached patch. It works for HP-UX but since this is pure Java it should also help on AIX with high probability. 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
