[JIRA] (JENKINS-14144) Build config history getting spammed
Jørgen Tjernø commented on JENKINS-14144 Build config history getting spammed I'm seeing this issue too, and I'd love to see it fixed - it makes the Job Config History plugin a lot less usable. 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-13959) StackOverflowException on Job Finish
Massimiliano Turri commented on JENKINS-13959 StackOverflowException on Job Finish For me the problem occurs only when the job is triggered by an scm change (svn in my case). If triggered by an upstream project or started by a user, the execution is successful and complete with no exception. Another piece of information is that with the exception the job log terminates with: Email was triggered for: Success Sending email for trigger: Success without the exception it terminates with: Email was triggered for: Success Sending email for trigger: Success Sending email to: abc@somewhere Finished: SUCCESS 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-14661) Context Menu URLs wrong
Jacque Khalil created JENKINS-14661 Context Menu URLs wrong Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Screen Shot 2012-08-01 at 3.00.16 PM.png Components: core Created: 02/Aug/12 12:21 AM Description: when hovering over clicking anything from the top drop down context menu,it sets the wrong url. It trys to send you to http://contextmenu/blah instead of http://jenkinsurl/blah. See attached picture for example of scroll over and url in the bottom of browser Environment: Ubuntu 10.04, Latest Jenkins Release. Project: Jenkins Priority: Major Reporter: Jacque Khalil 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-14662) Allow upload of a script file
Jan Vansteenkiste created JENKINS-14662 Allow upload of a script file Issue Type: New Feature Assignee: domi Components: config-file-provider, managed-scripts Created: 02/Aug/12 10:18 AM Description: For long scripts, It can be a hastle to copy paste them if you already have them locally. Allowing an upload of a file could improve on this. Project: Jenkins Priority: Major Reporter: Jan Vansteenkiste 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-2548) Node does not come back online after disk space cleared
hiteswar kumar commented on JENKINS-2548 Node does not come back online after disk space cleared another way to make slave online by running cli java -jar $CLIJAR -s $URL -i $sshkey online-node $SLAVE but at my jenkins environment (1.447.2 LTS jenkins) (Ubuntu 10.04.3 LTS ) , after running above cli, it make slave online but again in few second, jenkins make it offline... after running cli for few times(ore than 2 and 3), slave appears online. seems need change in jenkins core to make it stable. please share your comments if any. 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-14634) Add support for customized username to email-address inference
Slide-O-Mix resolved JENKINS-14634 as Not A Defect Add support for customized username to email-address inference Please setup something that implements MailAddressResolver (perforce, svn, etc all have implementations). Change By: Slide-O-Mix (03/Aug/12 1:45 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-14636) Create Artifacts From an Wrong Build
rocky wang updated JENKINS-14636 Create Artifacts From an Wrong Build previous script have a little problem, attach the new one Change By: rocky wang (02/Aug/12 6:45 AM) Attachment: TriggeredBuildSelector.java 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-8503) Git submodules are cloned too early and not removed once the revToBuild has been checked out
Orgad Shaneh commented on JENKINS-8503 Git submodules are cloned too early and not removed once the revToBuild has been checked out Any news on this? 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-14663) Allow running of scripts on the local filesystem.
Jan Vansteenkiste created JENKINS-14663 Allow running of scripts on the local filesystem. Issue Type: New Feature Assignee: domi Components: config-file-provider, managed-scripts Created: 02/Aug/12 10:19 AM Description: Sometimes, it might make sense to deploy scripts to jenkins using external packaging or pretty much anything. Having scripts behave more as tools can improve on manageability and keeping your scripts in version control. Project: Jenkins Priority: Major Reporter: Jan Vansteenkiste 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-13935) Debian Squeeze Installation
Adrien Lecharpentier commented on JENKINS-13935 Debian Squeeze Installation Could you please make sure that your locale is defined with command 'locale'. If not, please purge your installation (sudo apt-get purge jenkins sudo apt-get autoremove), set your locale (sudo dpkg-reconfigure locales) with at least one locale and re-install jenkins (sudo apt-get install jenkins). 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-7162) specifying a cli parameter causes unspecified parameters to be blank
Danny Staple commented on JENKINS-7162 specifying a cli parameter causes unspecified parameters to be blank This also affects the SSH cli access. #JENKINS-11691 looks like a duplicate of this. 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-14660) Plugin doesn't work when using the Nested View plugin
SCM/JIRA link daemon commented on JENKINS-14660 Plugin doesnt work when using the Nested View plugin Code changed in jenkins User: Samuel Van Reeth Path: pom.xml src/main/java/de/pellepelster/jenkins/walldisplay/WallDisplayTransientViewActionFactory.java http://jenkins-ci.org/commit/walldisplay-plugin/ec9adea2a382674958eb8fe4ba219b40c25df51a Log: JENKINS-14660 add support for Nested View 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-14666) Environment Variables in Generic-Artifactory Integration do not expand
Evgeni Wachnowezki
created JENKINS-14666
Environment Variables in Generic-Artifactory Integration do not expand
Issue Type:
Bug
Affects Versions:
current
Assignee:
Gregory Boissinot
Components:
artifactdeployer
Created:
02/Aug/12 1:31 PM
Description:
Hello,
i´m trying to deploy an artifact to a folder with an generic name depending on the verison (the version numver is set as an environment variable in Jenkins}:
../../dist/artfactname-version.war=com/bosch/common/${version}
but the variable is not expandet so the deployment run into an error:
For pattern: ../../dist/artfactname-version.war 1 artifacts were found
Deploying artifact: http://localhost:8081/artifactory/plugins-snapshot-local/com/common/${version}/artfactname-version.war
ERROR: null
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:859)
at org.apache.http.client.methods.HttpPut.init(HttpPut.java:68)
at org.jfrog.build.client.ArtifactoryBuildInfoClient.createHttpPutMethod(ArtifactoryBuildInfoClient.java:559)
at org.jfrog.build.client.ArtifactoryBuildInfoClient.tryChecksumDeploy(ArtifactoryBuildInfoClient.java:533)
at org.jfrog.build.client.ArtifactoryBuildInfoClient.uploadFile(ArtifactoryBuildInfoClient.java:501)
at org.jfrog.build.client.ArtifactoryBuildInfoClient.deployArtifact(ArtifactoryBuildInfoClient.java:291)
at org.jfrog.hudson.generic.GenericArtifactsDeployer.deploy(GenericArtifactsDeployer.java:69)
at org.jfrog.hudson.generic.ArtifactoryGenericConfigurator$1.tearDown(ArtifactoryGenericConfigurator.java:225)
at hudson.model.Build$BuildExecution.doRun(Build.java:171)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
at hudson.model.Run.execute(Run.java:1488)
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.net.URISyntaxException: Illegal character in path at index 89: http://localhost:8081/artifactory/plugins-snapshot-local/com/common/${version}/artfactname-version.war;build.name=artfactname;build.timestamp=1343909154981;build.number=44;vcs.revision=9036
at java.net.URI$Parser.fail(URI.java:2825)
at java.net.URI$Parser.checkChars(URI.java:2998)
at java.net.URI$Parser.parseHierarchical(URI.java:3082)
at java.net.URI$Parser.parse(URI.java:3030)
at java.net.URI.init(URI.java:595)
at java.net.URI.create(URI.java:857)
... 13 more
Finished: FAILURE
I think this is big improvement with small effort. I realy dont want to mess with maven/ivy for this projects.
Project:
Jenkins
Priority:
Blocker
Reporter:
Evgeni Wachnowezki
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-7162) specifying a cli parameter causes unspecified parameters to be blank
Danny Staple updated JENKINS-7162 specifying a cli parameter causes unspecified parameters to be blank Change By: Danny Staple (02/Aug/12 3:03 PM) Component/s: parameters Component/s: ssh 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-14163) CVS Polling Log error
Oliver Whiteman commented on JENKINS-14163 CVS Polling Log error Is there any update on this please Thanks 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-14666) Environment Variables in Generic-Artifactory Integration do not expand
Evgeni Wachnowezki updated JENKINS-14666 Environment Variables in Generic-Artifactory Integration do not expand Change By: Evgeni Wachnowezki (02/Aug/12 1:35 PM) Assignee: GregoryBoissinot yossis Component/s: artifactory Component/s: artifactdeployer 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-14668) failure to load without ivy plugin installed
Nicolas De Loof created JENKINS-14668 failure to load without ivy plugin installed Issue Type: Bug Assignee: Nicolas De Loof Components: postbuildscript Created: 02/Aug/12 2:23 PM Description: plugin fails to load as ivy plugin isn't installed: WARNING: Failed to load org.jenkinsci.plugins.postbuildscript.PostBuildScriptListener ... Caused by: java.lang.ClassNotFoundException: hudson.ivy.IvyModuleSet Project: Jenkins Priority: Major Reporter: Nicolas De Loof 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-14668) failure to load without ivy plugin installed
SCM/JIRA link daemon resolved JENKINS-14668 as Fixed failure to load without ivy plugin installed Change By: SCM/JIRA link daemon (02/Aug/12 2:25 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-7162) specifying a cli parameter causes unspecified parameters to be blank
Danny Staple edited a comment on JENKINS-7162 specifying a cli parameter causes unspecified parameters to be blank Oh and the dogfood comment about integrating a patch is most certainly not mcrooney's patch. As mcrooney mentions - it is a completely different patch for #JENKINS-7261. 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-14626) Specify file name generated to deploy
Daniel Laffan commented on JENKINS-14626 Specify file name generated to deploy Thanks for swift response, How do I find out when this is released? 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-14664) URLTrigger: Takes many iterations to Trigger
Sean DeNigris created JENKINS-14664 URLTrigger: Takes many iterations to Trigger Issue Type: Bug Assignee: Gregory Boissinot Components: urltrigger Created: 02/Aug/12 1:01 PM Description: In v. 0.23: trigger is set to poll url contents every minute 1 log is updated every minute 2 when the polled URL 3 changes, it takes many iterations before URLTrigger reports the change and triggers the build. In the build list for 1, see build #246, where the url changed and someone built the job manually on Aug 1, 2012 5:14:43 PM. URLTrigger did not trigger the build until Aug 1, 2012 5:25:20 PM (#247). For build #248, it's two hours after the url has changed, and URLTrigger still hasn't triggered the build. 1 https://ci.lille.inria.fr/pharo/view/Pharo%202.0/job/Pharo-2.0/configure 2 https://ci.lille.inria.fr/pharo/view/Pharo%202.0/job/Pharo-2.0/urltriggerPollLog/? 3 http://pharo.gforge.inria.fr/updates/pharo2.0/updates20.list Project: Jenkins Labels: plugin Priority: Major Reporter: Sean DeNigris 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-14667) java.io.InvalidClassException
Krzysztof Pędrys created JENKINS-14667 java.io.InvalidClassException Issue Type: Bug Assignee: Unassigned Components: core Created: 02/Aug/12 2:17 PM Description: After upgrading jenkins to latest I'm having issues like this one below: Building remotely on jenkins-ptc in workspace /home/jenkins/workspace/PTC-EA_integration-tests-deploy java.io.InvalidClassException: hudson.tools.JDKInstaller$Platform$1; local class incompatible: stream classdesc serialVersionUID = -8896131865330068025, local class serialVersionUID = 6097725669216027397 at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:632) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1600) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1513) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1749) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:365) at hudson.remoting.UserRequest.deserialize(UserRequest.java:182) at hudson.remoting.UserRequest.perform(UserRequest.java:98) 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 java.lang.Thread.run(Thread.java:736) Project: Jenkins Priority: Critical Reporter: Krzysztof Pędrys 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-14665) Quality center plugin for Hudson does not work properly
Max Lake created JENKINS-14665 Quality center plugin for Hudson does not work properly Issue Type: Bug Affects Versions: current Assignee: Daniel Petisme Components: qc Created: 02/Aug/12 1:19 PM Description: We probably have the same problem as in JENKINS-9459: when starting the test we get the following output. We tried to start the hudson service under different users, but with no luck Started by user u_ workspace $ cscript /nologo "C:\Documents and Settings\u_\.hudson\jobs\AutoTest\workspace\runTestSet.vbs" http://qc/qcbin/ user CORPORATE XXX\ XXX1 qcreport-Отладка-18.xml 600 RUN_LOCAL 02.08.2012 17:00:48 : Script parameters: 02.08.2012 17:00:48 : * 02.08.2012 17:00:48 : QC Server : http://qc/qcbin/ 02.08.2012 17:00:48 : QC UserName : user 02.08.2012 17:00:48 : QC Password : 02.08.2012 17:00:48 : QC Domain : CORPORATE 02.08.2012 17:00:48 : QC Project : 02.08.2012 17:00:48 : QC TestSetFolder: XXX\ 02.08.2012 17:00:48 : QC TestSetName : XXX1 02.08.2012 17:00:48 : XML Junit File : qcreport-Отладка-18.xml 02.08.2012 17:00:48 : Timeout : 600 02.08.2012 17:00:48 : * 02.08.2012 17:00:48 : RunMode : RUN_LOCAL 02.08.2012 17:00:48 : RunHost : CODEREV 02.08.2012 17:00:48 : * Connected to server http://qc/qcbin/ Logged in with user user Opened project CORPORATE\ -- TestSet Name ID -- XXX1 251 -- Could not instantiate test set scheduler Creating report... Generating report file Report file path: qcreport-Отладка-18.xml -- Test Name Status -- Report Created FATAL: Couldn't run tests DEBUG Skipping watched dependency update for build: AutoTest #18 due to result: FAILURE Finished: FAILURE Environment: Windows Server 2003, Hudson run as windows service Project: Jenkins Priority: Major Reporter: Max Lake 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-14668) failure to load without ivy plugin installed
SCM/JIRA link daemon commented on JENKINS-14668 failure to load without ivy plugin installed Code changed in jenkins User: Nicolas De Loof Path: src/main/java/org/jenkinsci/plugins/postbuildscript/PostBuildScriptListener.java http://jenkins-ci.org/commit/postbuildscript-plugin/30b3345d90b89a548a9340a1cf5117abe4ff061e Log: FIXED JENKINS-14668 failure to load without ivy plugin installed 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-14480) Git plugin 1.1.21 cannot build branches with repository specified but no wildcards
Joe Hansche commented on JENKINS-14480 Git plugin 1.1.21 cannot build branches with repository specified but no wildcards Any news on when 1.1.22 will be released? I see it's already in the changelog on the wiki, but hasn't been released yet. Are you just looking for testers to make sure the update fixes the bug? 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-14495) Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder
cjo9900 commented on JENKINS-14495 Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder I think I have tracked the error down to the hetro list which in this case asserts because the prototypes variable, is undefined at this point https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/lib/form/hetero-list/hetero-list.js#L17 so calling previous() fails. Putting an if check in for prototypes == null and returning at that point, seems to allow the the page to load correctly and the configuration to be saved correctly. Not sure of the side affects as I am not a JS expert. 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-14670) Node Label Parameter Plugin - Choose whether to queue builds for offline nodes or not.
Eric Chang created JENKINS-14670 Node Label Parameter Plugin - Choose whether to queue builds for offline nodes or not. Issue Type: New Feature Assignee: domi Components: nodelabelparameter Created: 02/Aug/12 5:11 PM Description: It would help exceedingly if there was an option to enable or disable queuing builds for offline nodes or not. As it is, it will always queue builds for offline nodes, so if there are any dependencies waiting on a build using the node label parameter plugin to finish, they will never run. Project: Jenkins Priority: Major Reporter: Eric Chang 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-14537) Template SCMs + Multiple SCMs results in failure parsing change log
Joe Hansche
commented on JENKINS-14537
Template SCMs + Multiple SCMs results in failure parsing change log
I've written a sed script that worked to resolve the issue on my existing changelog.xml files. It will need to be tweaked for any file that is not in the same format as mine.
$ cat fix-changelog.sh
#!/bin/sh
sed -n -r -i '1h;1!H;$ {;g;s#sub-log scm="hudson.plugins.templateproject.ProxySCM"\n!\[CDATA\[multi-scm-log\nsub-log scm="hudson.plugins.git.GitSCM"\n!\[CDATA\[((.*\n)*?)\]\]\n/sub-log\nsub-log scm="hudson.plugins.git.GitSCM"\n!\[CDATA\[((.*\n)*?)\]\]\n/sub-log\n/multi-scm-log\n\]\]\n/sub-log#sub-log scm="hudson.plugins.templateproject.ProxySCM"\n!\[CDATA\[multi-scm-log\nsub-log scm="hudson.plugins.git.GitSCM"\n!\[CDATA\[\2\93;\93;\gt;\n/sub-log\nsub-log scm="hudson.plugins.git.GitSCM"\n!\[CDATA\[\4\93;\93;\gt;\n/sub-log\n/multi-scm-log\n\]\]\n/sub-log#g;p;}' "$1"
Then just pass the filename you want to change into the script, or do all at once:
$ ./fix-changelog.sh path/to/changelog.xml
: or to find and fix all:
$ find . -name 'changelog.xml' -print0 | xargs -0 -n1 ./fix-changelog.sh
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-14674) When Use emulator snapshots isn't checked emulator system process crashes when installing apk
oseparovic updated JENKINS-14674 When Use emulator snapshots isnt checked emulator system process crashes when installing apk Change By: oseparovic (02/Aug/12 10:15 PM) Description: Ihaverunemulatorwithproperties:AndroidOSversion:4.0.3ScreenDensity:160ScreenResolution:HVGADevicelocale:en_usSDcardsize:128Mhw.ramSize:712vm.heapSize:48hw.audioInput:noResetemulatorstateatstart-upShowemulatorwindowUseemulatorsnapshotsIfIturnoffUseemulatorsnapshotsIgetthefollowingmessage:[android]InstallingAPKfilecoreTest-debug.apk[bin]$/home/hudson/tools/android-sdk//platform-tools/adb-slocalhost:38260install-rcoreTest-debug.apk534KB/s(1297259bytesin2.370s) pkg:/data/local/tmp/coreTest-debug.apk-waitingfordevice-AfterVNCingintotheemulatorIsawthattheattachedmessagehadappeared.IfIswitched Useemulatorsnapshots on again, thejobworkedonthefirstrunakainstalledproperly,rantestsproperly. 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-14672) deleteAllDisabledModules produced with incorrect basedir
jglick created JENKINS-14672 deleteAllDisabledModules produced with incorrect basedir Issue Type: Bug Assignee: Unassigned Components: maven Created: 02/Aug/12 8:45 PM Description: I have a sample Maven job configured. From /job/mercurial-plugin/ there is a link /job/mercurial-plugin/deleteAllDisabledModules which works (whatever it does). But if I first click on the "Workspace" link, and then click on "Delete All Disabled Modules", I am taken to /job/mercurial-plugin/ws/deleteAllDisabledModules which is a 404. (Similarly for other actions which have a basedir, e.g. /job/mercurial-plugin/move/deleteAllDisabledModules when using the Folders plugin.) Seems like MavenModuleSet/actions.jelly is failing to set a proper base URL. Environment: 1.466.1 Project: Jenkins Priority: Minor Reporter: jglick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-2505) NoSuchMethodError on the end of build
Robert Liotta
reopened JENKINS-2505
NoSuchMethodError on the end of build
Hello
I just started getting this error yesterday. I am on version 1.476 of Jenkins, 2.5 of the CVS plugin, and 2.61 of the Promoted Builds Plugin. It started on version 1.475.
I agree with the findings of the issue as the problem started after some updates.
I can manually promote it when it fails and it works. Seems to be just the poller.
What to do?
Attached is a dump after a clean startup.
Running from: /usr/lib/jenkins/jenkins.war
webroot: System.getProperty("JENKINS_HOME")
Aug 02, 2012 9:55:13 PM winstone.Logger logInternal
INFO: Beginning extraction from war file
Jenkins home directory: /var/lib/jenkins found at: System.getProperty("JENKINS_HOME")
Aug 02, 2012 9:55:14 PM winstone.Logger logInternal
INFO: HTTP Listener started: port=8080
Aug 02, 2012 9:55:14 PM winstone.Logger logInternal
INFO: AJP13 Listener started: port=8009
Aug 02, 2012 9:55:14 PM winstone.Logger logInternal
INFO: Winstone Servlet Engine v0.9.10 running: controlPort=disabled
Aug 02, 2012 9:55:14 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
Aug 02, 2012 9:55:14 PM hudson.ClassicPluginStrategy createPluginWrapper
INFO: Plugin active-directory.jpi is disabled
Aug 02, 2012 9:55:14 PM jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
Aug 02, 2012 9:55:14 PM jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
Aug 02, 2012 9:55:18 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started all plugins
Aug 02, 2012 9:55:18 PM jenkins.InitReactorRunner$1 onAttained
INFO: Augmented all extensions
Aug 02, 2012 9:55:20 PM jenkins.InitReactorRunner$1 onAttained
INFO: Loaded all jobs
Aug 02, 2012 9:55:20 PM org.apache.sshd.common.util.SecurityUtils$BouncyCastleRegistration run
INFO: Trying to register BouncyCastle as a JCE provider
Aug 02, 2012 9:55:21 PM org.apache.sshd.common.util.SecurityUtils$BouncyCastleRegistration run
INFO: Registration succeeded
Aug 02, 2012 9:55:21 PM org.jenkinsci.main.modules.sshd.SSHD start
INFO: Started SSHD at port 35205
Aug 02, 2012 9:55:21 PM jenkins.InitReactorRunner$1 onAttained
INFO: Completed initialization
Aug 02, 2012 9:55:22 PM org.springframework.context.support.AbstractApplicationContext prepareRefresh
INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@75ee3e8b: display name Root WebApplicationContext; startup date Thu Aug 02 21:55:22 EDT 2012; root of context hierarchy
Aug 02, 2012 9:55:22 PM org.springframework.context.support.AbstractApplicationContext obtainFreshBeanFactory
INFO: Bean factory for application context org.springframework.web.context.support.StaticWebApplicationContext@75ee3e8b: org.springframework.beans.factory.support.DefaultListableBeanFactory@4b8f383f
Aug 02, 2012 9:55:22 PM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@4b8f383f: defining beans initialDirContextFactory,bindAuthenticator,ldapUserSearch,authenticationManager,authoritiesPopulator; root of factory hierarchy
Aug 02, 2012 9:55:22 PM org.acegisecurity.ldap.DefaultInitialDirContextFactory setProviderUrl
INFO: URL 'ldap://ad.fifthlayer.net:389/dc=win,dc=fifthlayer,dc=net', root DN is 'dc=win,dc=fifthlayer,dc=net'
Aug 02, 2012 9:55:22 PM org.acegisecurity.providers.ldap.populator.DefaultLdapAuthoritiesPopulator setGroupSearchBase
INFO: groupSearchBase is empty. Searches will be performed from the root: dc=win,dc=fifthlayer,dc=net
Aug 02, 2012 9:55:22 PM org.springframework.context.support.AbstractApplicationContext prepareRefresh
INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@70e9779b: display name Root WebApplicationContext; startup date Thu Aug 02 21:55:22 EDT 2012; root of context hierarchy
Aug 02, 2012 9:55:22 PM org.springframework.context.support.AbstractApplicationContext obtainFreshBeanFactory
INFO: Bean factory for application context org.springframework.web.context.support.StaticWebApplicationContext@70e9779b: org.springframework.beans.factory.support.DefaultListableBeanFactory@17a7164f
Aug 02, 2012 9:55:22 PM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@17a7164f: defining beans filter,legacy;
[JIRA] (JENKINS-14676) take care of the dependency in the cron column instead of show nothing
Valin Frederic created JENKINS-14676 take care of the dependency in the cron column instead of show nothing Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: cron_column Created: 03/Aug/12 7:51 AM Description: Hi, This plugin is great to view the next execution of my jobs, but i have some jobs which are dependent with cron jobs. So it would be nice if the plugin instead of showing nothing could show the dependence. Project: Jenkins Priority: Minor Reporter: Valin Frederic 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-14669) downstream-buildview incompatible with folders
SCM/JIRA link daemon resolved JENKINS-14669 as Fixed downstream-buildview incompatible with folders Change By: SCM/JIRA link daemon (02/Aug/12 4:22 PM) 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-7782) Excessive logging causes the Hudson log to flood and memory to leak
jglick resolved JENKINS-7782 as Fixed Excessive logging causes the Hudson log to flood and memory to leak recampbell seems to have fixed this in 1a0a6b2b5fd5d71fba43ef4fdfb6836ed087abd7. Change By: jglick (02/Aug/12 3:47 PM) Status: Open Resolved Assignee: shinodkm recampbell 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-14669) downstream-buildview incompatible with folders
jglick created JENKINS-14669 downstream-buildview incompatible with folders Issue Type: Bug Assignee: jglick Components: downstream-buildview Created: 02/Aug/12 3:43 PM Description: User of this plugin in combination with CloudBees Folders Plugin reports exceptions such as java.lang.NullPointerException at org.jvnet.hudson.plugins.DownstreamBuildViewUpdateListener.onStarted(DownstreamBuildViewUpdateListener.java:85) at org.jvnet.hudson.plugins.DownstreamBuildViewUpdateListener.onStarted(DownstreamBuildViewUpdateListener.java:46) at hudson.model.listeners.RunListeners.fireStarted(RunListener.java:188) at hudson.model.Run.run(Run.java:1371) at hudson.ivy.IvyModuleSetBuild.run(IvyModuleSetBuild.java:282) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:175) Also observed: java.lang.NullPointerException at org.jvnet.hudson.plugins.DownstreamBuildViewAction.findDownstream(DownstreamBuildViewAction.java:66) at org.jvnet.hudson.plugins.DownstreamBuildViewAction.getDownstreamBuildList(DownstreamBuildViewAction.java:221) (JENKINS-14325 also observed, but this is unrelated to the downstream-buildview plugin.) Project: Jenkins Labels: exception folders Priority: Major Reporter: jglick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13779) Git Publisher (tagging) can't work with multipe SCM (ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCM cannot be cast to hudson.plugins.git.GitSCM)
Srinath C commented on JENKINS-13779 Git Publisher (tagging) cant work with multipe SCM (ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCM cannot be cast to hudson.plugins.git.GitSCM) Doesn't work when even when using the template plugin to use git configuration from another project. Exception: java.lang.ClassCastException: hudson.plugins.templateproject.ProxySCM cannot be cast to hudson.plugins.git.GitSCM Stacktrace: javax.servlet.ServletException: java.lang.ClassCastException: hudson.plugins.templateproject.ProxySCM cannot be cast to hudson.plugins.git.GitSCM at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at
[JIRA] (JENKINS-14669) downstream-buildview incompatible with folders
SCM/JIRA link daemon commented on JENKINS-14669 downstream-buildview incompatible with folders Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jvnet/hudson/plugins/DownstreamBuildViewAction.java src/main/java/org/jvnet/hudson/plugins/DownstreamBuildViewUpdateListener.java http://jenkins-ci.org/commit/downstream-buildview-plugin/76f2f5fa902bb9b625c642d31b2c69bf67e5ad38 Log: FIXED JENKINS-14669 Compatibility with hierarchical projects (folders). Compare: https://github.com/jenkinsci/downstream-buildview-plugin/compare/1a0a6b2b5fd5...76f2f5fa902b 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-14675) Schema 'DBUSER' does not exist error in integrity plugin
Hamdanil Rasyid created JENKINS-14675 Schema DBUSER does not exist error in integrity plugin Issue Type: Bug Affects Versions: current Assignee: Cletus DSouza Components: integrity-plugin Created: 03/Aug/12 7:29 AM Description: MKS integrity polling occassionaly fail due to this exception, see error below: Started by user Hamdanil Rasyid Building in workspace C:\Program Files\Jenkins\jobs[removed by poster]\workspace Change Log: http://localhost:8081/job/removed by poster/changes Build Log: http://localhost:8081/job/removed by poster/57/console Preparing to execute si projectinfo for #/removed by poster Preparing to execute si viewproject for #/removed by poster A SQL Exception was caught! Schema 'DBUSER' does not exist Sending e-mails to: removed by poster Finished: FAILURE Project: Jenkins Labels: plugin scm database Priority: Major Reporter: Hamdanil Rasyid 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-14646) Replace old name HudsonXXXX by XXXX
Raphael CHAUMIER edited a comment on JENKINS-14646 Replace old name Hudson by No more HudsonX resource exists in the plugin. Release in version 1.2 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-13935) Debian Squeeze Installation
Adrien Lecharpentier edited a comment on JENKINS-13935 Debian Squeeze Installation Could you please make sure that your locale is defined with command 'locale'. If not, please purge your installation (sudo apt-get purge jenkins sudo apt-get autoremove), set your locale (sudo dpkg-reconfigure locales) with at least one locale and re-install jenkins (sudo apt-get install jenkins). EDIT: It seems more a problem due to kernel version. In the case of Clement Gautier, the kernel is causing a JVM crash. 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-12390) Jira plugin cannot be configured to connect to Atlassian on demand instances
howama commented on JENKINS-12390 Jira plugin cannot be configured to connect to Atlassian on demand instances The plugin does work with onDeman, just gives a warning in the configuration screen. 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-14673) Multiple regular expressions to include jobs into a view.
tillu sri created JENKINS-14673 Multiple regular expressions to include jobs into a view. Issue Type: Improvement Assignee: Jacob Robertson Components: view-job-filters Created: 02/Aug/12 8:55 PM Description: we can enter only one regular _expression_ to include jobs in a view. I came across a situation where i need to use two regular expressions to include jobs into a view. Can you please provide a solution to accomplish this. Also to use an existing view in a nested view. Project: Jenkins Priority: Major Reporter: tillu sri 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-14674) When Use emulator snapshots isn't checked emulator system process crashes when installing apk
oseparovic created JENKINS-14674 When Use emulator snapshots isnt checked emulator system process crashes when installing apk Issue Type: Bug Affects Versions: current Assignee: Christopher Orr Attachments: system_nr.png Components: android-emulator Created: 02/Aug/12 10:14 PM Description: I have run emulator with properties: Android OS version: 4.0.3 Screen Density: 160 Screen Resolution: HVGA Device locale: en_us SD card size: 128M hw.ramSize: 712 vm.heapSize: 48 hw.audioInput: no Reset emulator state at start-up Show emulator window Use emulator snapshots If I turn off "Use emulator snapshots" I get the following message: android Installing APK file 'coreTest-debug.apk' bin $ /home/hudson/tools/android-sdk//platform-tools/adb -s localhost:38260 install -r coreTest-debug.apk 534 KB/s (1297259 bytes in 2.370s) pkg: /data/local/tmp/coreTest-debug.apk waiting for device - After VNCing into the emulator I saw that the attached message had appeared. If I switched Use emulator snapshots on the job worked on the first run aka installed properly, ran tests properly. Environment: android-emulator version 2.2 Jenkins ver. 1.472 CentOS release 5.4 (Final) Android SDK Tools Revision 20 Project: Jenkins Priority: Major Reporter: oseparovic 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-14646) Replace old name HudsonXXXX by XXXX
SCM/JIRA link daemon commented on JENKINS-14646 Replace old name Hudson by Code changed in jenkins User: RaphC Path: src/main/java/org/jenkinsci/plugins/deploy/weblogic/MavenJobArtifactSelectorImpl.java http://jenkins-ci.org/commit/weblogic-deployer-plugin/fbdb5f73675953953aeca87148214ed333f7fbec Log: JENKINS-14646 Replace old name Hudson by 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-13521) Missing option E-mail notification (Post-build Actions)
Daniel White commented on JENKINS-13521 Missing option E-mail notification (Post-build Actions) Please add email notification on the status of the build. I would like to have just one email for all the build results in the Flow. Thanks 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-14669) downstream-buildview incompatible with folders
jglick started work on JENKINS-14669 downstream-buildview incompatible with folders Change By: jglick (02/Aug/12 4:09 PM) 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-14671) Use JIRA Remote application links instead of comments
howama created JENKINS-14671 Use JIRA Remote application links instead of comments Issue Type: New Feature Assignee: Unassigned Components: jira Created: 02/Aug/12 6:03 PM Description: Many people have requested that this plugin doesn't spam the jira comments section (e.g. JENKINS-12605). JIRA plugins such as marvalution may work for in-house jira instances, but not hosted or on-demand instances. Instead of using comments, could the new jira remote issue links be created instead. These will be shown separately from the comments and could link directly to the jenkins builds. https://developer.atlassian.com/display/JIRADEV/Fields+in+Remote+Issue+Links Project: Jenkins Priority: Major Reporter: howama 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-14670) Node Label Parameter Plugin - Choose whether to queue builds for offline nodes or not.
Eric Chang updated JENKINS-14670 Node Label Parameter Plugin - Choose whether to queue builds for offline nodes or not. Change By: Eric Chang (02/Aug/12 5:15 PM) Description: Itwouldhelpexceedinglyiftherewasanoptiontoenableordisablequeuingbuildsforofflinenodesornot.Asitis,itwillalwaysqueuebuildsforofflinenodes,soifthereareanydependencieswaitingonabuildusingthenodelabelparameterplugintofinish,theywillneverrun. RightnowIhaveasetofjobsthatrunseverytwohours24/7withdifferentsettingsforeachnodelabel.Thesettingswewanttorunoneachmachinechangeoften,solabelsseemedtheeasiestsolution.However,themachinesImusingareoftentakenofflineformanualuse,orhavetobeswappedoutorotherwisemodified,soweoftenhaveofflinenodes.Sincethebuildqueuedforanofflinenodejusthangsandanotherjobdependsonallthebuildsfinishinginakindofdiamondstructure. 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-14163) CVS Polling Log error
Michael Clarke commented on JENKINS-14163 CVS Polling Log error Kohsuke made a change which is included in the current release which may fix the parsing of the changelog, although I'm looking to change the whole way the changelog is parsed in the current iteration which will fix your issue. I'm not going to be able to start work on this for a couple of weeks, but will link changes back to this defect so they are visible. 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-14626) Specify file name generated to deploy
Raphael CHAUMIER resolved JENKINS-14626 as Fixed Specify file name generated to deploy The 1.2 plugin version with this enhancement has been released. Change By: Raphael CHAUMIER (03/Aug/12 8:37 AM) Status: Open Resolved Fix Version/s: current 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-2505) NoSuchMethodError on the end of build
Michael Clarke commented on JENKINS-2505 NoSuchMethodError on the end of build This seems to be an issue with the CvsTag plugin not being compatible with anything above V2 of the CVS plugin. You'll need to raise an issue against the CVSTag plugin to get this sorted. 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-14495) Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder
cjo9900 commented on JENKINS-14495 Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder The type error occurs with call stack pointing to the hetero-list.js, full call stack is in image JS_typeError_JENKINS-14495.png Looking back the stack we see this is invoked from the render event, this event is caused by the loading of the triggerbuilder descriptor elements. The outerHTML at that point is the data from the descriptor see gist 1 At the point of failure the element that was being processed has the following outerHTML div class="hetero-list-container with-drag-drop one-each " div class="repeatable-insertion-point" /div div span class="yui-button yui-menu-button" id="yui-gen22" span class="first-child" button type="button" tabindex="0" id="yui-gen22-button" class="hetero-list-add" suffix="configs"Add Parameters /button /span /span /div /div which seems to indicate that the element has already been processed once. looking at the registered behaviours, there are 10 elements in the list, including duplicate entries that are added by hetero-list.js and repeatable.js. see image JS_registered_Behaviours_JENKINS-14495.png (element 5 is from hudson-behaviour.js). so as Behaviour.applySubtree() runs over each item in the list some behaviours are getting run multiple times, which is causing the problem. 1 https://gist.github.com/3246770 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-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
stephane mainchain commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed Any idea when this will be fixed? this one's a blocker for 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-14646) Replace old name HudsonXXXX by XXXX
Raphael CHAUMIER resolved JENKINS-14646 as Fixed Replace old name Hudson by No more HudsonX resource exists in the plugin Change By: Raphael CHAUMIER (03/Aug/12 8:28 AM) Status: Open Resolved Fix Version/s: current 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-14201) Git submodules checked out in wrong place
Matt Willsher commented on JENKINS-14201 Git submodules checked out in wrong place I'm seeing the same issue, compounded by the fact that even clearing down the workspace doesn't resolve the problem. In the output below (censored for security/privacy reasons, intent is the same). origin/requirejs-2.0-upgrade is not part of REMOVEDPROJECT-pkg, but a branch in the submodule contained with in. This did work, but after changing the submodule locations and updating via git submodule sync each build gets the following error. Work around will be to add a git checkout as a manual step, so not entirely a blocker but a significant problem none the less. Jenkins ver. 1.473 Jenkins GIT plugin org.jenkinsci.plugins:git:1.1.21 annotation-indexer org.jvnet.hudson:annotation-indexer:1.2 Joda time joda-time:joda-time:1.5.1 JSchcom.jcraft:jsch:0.1.44-1 Bridge method injection com.infradna.tool:bridge-method-annotation:1.4 annotations JGit - Core org.eclipse.jgit:org.eclipse.jgit:0.12.1 Building remotely on RPM build slave 1 in workspace /home/jenkins/workspace/REMOVEDPROJECT-pkg Checkout:REMOVEDPROJECT-pkg / /home/jenkins/workspace/REMOVEDPROJECT-pkg - hudson.remoting.Channel@aef8664:RPM build slave 1 Using strategy: Default Last Built Revision: Revision e0fb13e7b464d812a90d7d73b1df06cf09d27c56 (origin/requirejs-2.0-upgrade) Fetching changes from 1 remote Git repository Fetching upstream changes from git@gitlab.REMOVED:REMOVEDPROJECT-pkg.git Seen branch in repository origin/HEAD Seen branch in repository origin/master Commencing build of Revision e0fb13e7b464d812a90d7d73b1df06cf09d27c56 (origin/requirejs-2.0-upgrade) Checking out Revision e0fb13e7b464d812a90d7d73b1df06cf09d27c56 (origin/requirejs-2.0-upgrade) FATAL: Could not checkout null with start point e0fb13e7b464d812a90d7d73b1df06cf09d27c56 hudson.plugins.git.GitException: Could not checkout null with start point e0fb13e7b464d812a90d7d73b1df06cf09d27c56 at hudson.plugins.git.GitAPI.checkoutBranch(GitAPI.java:931) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1285) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1269) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2196) 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:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git checkout -f e0fb13e7b464d812a90d7d73b1df06cf09d27c56" returned status code 128: stdout: stderr: fatal: reference is not a tree: e0fb13e7b464d812a90d7d73b1df06cf09d27c56 at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:838) at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:800) at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:810) at hudson.plugins.git.GitAPI.checkoutBranch(GitAPI.java:918) ... 12 more 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-14679) Mercurial cache is not used
Ronald Klop commented on JENKINS-14679 Mercurial cache is not used I installed a vanilla Jenkins on my Windows 7 64-bits workstation. Caching does not work either on latest Jenkins 1.476. Started by user anonymous Building in workspace C:\Users\ronald\.jenkins\workspace\test $ hg clone --rev default --noupdate http://ronaldradial:8000/ C:\Users\ronald\.jenkins\workspace\test 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-14495) Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder
cjo9900 updated JENKINS-14495 Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder Change By: cjo9900 (03/Aug/12 11:46 AM) Attachment: JS_typeError_JENKINS-14495.png Attachment: JS_registered_Behaviours_JENKINS-14495.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-14679) Mercurial cache is not used
Ronald Klop created JENKINS-14679 Mercurial cache is not used Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: mercurial Created: 03/Aug/12 12:10 PM Description: Caching is enabled in Jenkins, but it is not used. The $HUDSON_HOME/hgcache directory is not created. No errors are logged about something missing or failing in relation to the cache. Sharing is disabled, but enabling it does not help or show any different in the logs. I think it worked in the past, but can't find any logs about that anymore. I searched on the internet and in the Jenkins mailinglists, but found no solution. Environment: Windows 2003 32-bits Jenkins 1.466.1 LTS (running as a Windows service) Mercurial plugin 1.41 Mercurial 2.2.3 Project: Jenkins Priority: Major Reporter: Ronald Klop 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-14677) Parametized build default values from URL
wernight created JENKINS-14677 Parametized build default values from URL Issue Type: Improvement Assignee: Unassigned Components: parameters Created: 03/Aug/12 10:30 AM Description: http://example.com/job/Foo/build?PARAMETER_NAME=SomeValue Should set the value default for 'PARAMETER_NAME' parameter but still ask the user to input other parameters. So 'build' URL should work like 'buildWithParameters' URL except it doesn't start immediately but asks for parameters. Project: Jenkins Priority: Minor Reporter: wernight 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-14678) change description containing national characters not showing in changelog
Krzysztof Kosmatka created JENKINS-14678 change description containing national characters not showing in changelog Issue Type: Bug Assignee: Unassigned Components: cvs Created: 03/Aug/12 11:23 AM Description: I have a "free-style software project" job, that checkouts project from CVS. If I add a description to cvs commit that contains national characters (Polish in my case, e.g. ą, ę, ł, ó), Jenkins doesn't show these changes in changelog (in fact Jenkins show no changes for entire build containing such a commit, even though there are other commits not containing national characters). But changelog.xml files seems to be generated properly. I think this behaviour started after upgrading cvs plugin from 1.6 to 2.4 (but i am not 100% sure). I also noticed a problem with jabber notifications, that may by connected to this issue. If a build contains such an "invalid" commit, then cvs commiters are not notified on broken build. I'm not sure, if these two issues are realy connected, but thought it might be helpfull. Environment: Windows Server 2008 r2, Jenkins running as windows service Project: Jenkins Priority: Major Reporter: Krzysztof Kosmatka 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-1677) External job will not be executed of connection to Hudson can't be obtained.
Daniel de Wildt updated JENKINS-1677 External job will not be executed of connection to Hudson cant be obtained. Change By: Daniel de Wildt (03/Aug/12 1:52 PM) Assignee: DanieldeWildt 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-14637) Maven Deployment Linker does not support all permalinks types
Radim Kubacki commented on JENKINS-14637 Maven Deployment Linker does not support all permalinks types AFAICT the functionality of Maven Deployment Linker is not only to put hyperlinks to build/job pages but it also registers a build step that can be used by a downstream build to get linked artifacts from the another build (upstream) build. This makes it possible to create a pipeline of builds where artifact created by first build will be used in the second (downstream) build. My complaint is that this action (hudson/plugins/mavendeploymentlinker/MavenDeploymentDownloader.java) can only by used for builds specified by simple criteria and I cannot ask to get artifacts generated by last release build (last release build can be accessed through a permalink). 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-14637) Maven Deployment Linker does not support all permalinks types
Larry Shatzer, Jr. assigned JENKINS-14637 to Dominik Bartholdi Maven Deployment Linker does not support all permalinks types Ahhh, that functionality was not added by me, but Dominik Bartholdi (imod). I'll assign it to him to look at. Change By: Larry Shatzer, Jr. (03/Aug/12 2:08 PM) Assignee: LarryShatzer,Jr. DominikBartholdi 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-14681) Constrain the list of artifacts deployed
Bill Packard updated JENKINS-14681 Constrain the list of artifacts deployed Change By: Bill Packard (03/Aug/12 2:09 PM) Summary: Constrainthelist of artifactsdeployed 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-14681) Constrain the list artifacts deployed
Bill Packard created JENKINS-14681 Constrain the list artifacts deployed Issue Type: Improvement Affects Versions: current Assignee: Gregory Boissinot Components: artifactdeployer Created: 03/Aug/12 2:09 PM Description: I am currently using the artifactDeployer (0.13) to transfer a successful build to a shared folder, where it can be retained indefinitely. This works well, however each file transferred is listed with a link, and this list is quite long. It would be useful to display a single link to the remote directory, or perhaps a subset of files transferred (perhaps via regex). Environment: Windows 2008 R2 java 1.6.0_26-b03 Jenkins 1.467 Project: Jenkins Priority: Minor Reporter: Bill Packard 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-14514) Repeatable jelly tag appears to be broken in 1.474+
jglick commented on JENKINS-14514 Repeatable jelly tag appears to be broken in 1.474+ @Brian: not really sure what is in 1.476; http://jenkins-ci.org/changelog does not list it, and there is no tag for it! I think I specifically tested the HTML Publisher plugin against this change, but if you still see the bug when running against master (currently 1.477-SNAPSHOT) please reopen JENKINS-14381. 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-14495) Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder
jglick commented on JENKINS-14495 Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder I think you are getting at the crux of the problem when you find that there are duplicates in registered behaviors. My fix of JENKINS-14514 was just a blind workaround for that, and it seems like pull #533 is very similar. My guess is that splitting _javascript_ into separate files resulted in behavior registration being run repeatedly from the same st:adjunct/, and apparently this was not idempotent. Will look deeper. 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-14495) Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder
jglick started work on JENKINS-14495 Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder Change By: jglick (03/Aug/12 2:30 PM) 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-14682) Vagrant Plugin Doesn't Install
Jason Cramer created JENKINS-14682 Vagrant Plugin Doesnt Install Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: plugin Created: 03/Aug/12 3:24 PM Description: I have tried installing the Vagrant plugin, both manually and through the plugin manager. After I install it, I restart Jenkins, but it is not listed in the installed plugins, nor does the build options for Vagrant appear in the build configuration. Environment: Windows Server 2008 R2 (inside a VirtualBox running on Windows 7), and Windows 7 Project: Jenkins Labels: plugin jenkins vagrant Priority: Minor Reporter: Jason Cramer 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-10274) Can this plugin support CLOC for even more languages and better Windows support
Andreas Zoufal commented on JENKINS-10274 Can this plugin support CLOC for even more languages and better Windows support It does not work for me, maybe I use wrong options? What I do is: 1: run cloc: cloc.pl --by-file --exclude-dir=.svn,build --xml -out=build/cloc.xml mysourcedir 2: run xsltproc using your example XML file: xsltproc sloccount.xsl build/cloc.xml Result: compilation error: file /home/zoufala/Downloads/sloccount.xsl line 1 element stylesheet xsl:version: only 1.0 features are supported xmlXPathCompOpEval: function replace not found XPath error : Unregistered function xmlXPathCompiledEval: 2 objects left on the stack. runtime error: file /home/zoufala/Downloads/sloccount.xsl line 5 element variable Failed to evaluate the _expression_ of variable 'file_path'. This report has been generated by cloc 1.56. For more details see: http://cloc.sourceforge.net Is there an obvious mistake in my usage? 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-14679) Mercurial cache is not used
jglick assigned JENKINS-14679 to jglick Mercurial cache is not used Change By: jglick (03/Aug/12 3:32 PM) Assignee: KohsukeKawaguchi jglick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9944) job triggered by join didn't wait for all downstream jobs to finish
cjo9900 commented on JENKINS-9944 job triggered by join didnt wait for all downstream jobs to finish From your description/comment I think you have confused the setup. Case 1 tick "join trigger" start F when all downstreawm jobs have finished tick 'run post-build actions at join' tick in post-join actions "trigger parameterized build" and build jobs B, C, D and E Case 2 tick "join trigger" start F when all downstreawm jobs have finished tick 'run post-build actions at join' ignore the Post-Join Actions (don't tick or fill in anything) use "trigger parameterized build" at the bottom of the job config instead The projects you add to the join trigger are run after all of the downstream jobs have finished, this includes the ones included in the post join parameter-trigger action. So case 1 has no downstream jobs therefore jobs B-F are started at the same time. In case 2 B-E are downstream jobs and F is triggered after these finish. Cannot see any error in this case so closing. 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-9944) job triggered by join didn't wait for all downstream jobs to finish
cjo9900 resolved JENKINS-9944 as Not A Defect job triggered by join didnt wait for all downstream jobs to finish Change By: cjo9900 (03/Aug/12 3:53 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-14108) Multiple parameterized upstreams with joined in one blocked while.. job result in multiple executions rather one only
cjo9900 commented on JENKINS-14108 Multiple parameterized upstreams with joined in one blocked while.. job result in multiple executions rather one only Can you add some details on the config so this can be reproduced. 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-14518) Failed first job still triggers second job
Marc Günther commented on JENKINS-14518 Failed first job still triggers second job Thanks for that idea, that never occurred to me. Maybe a good idea to add this to the help somehow. I found it confusing that the "fail this build step" option still triggered the next build. But it was of course still the same build step, so it makes kind of sense when you think about 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-14514) Repeatable jelly tag appears to be broken in 1.474+
SCM/JIRA link daemon commented on JENKINS-14514 Repeatable jelly tag appears to be broken in 1.474+ Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/resources/lib/form/repeatable/repeatable.js war/src/main/webapp/scripts/behavior.js http://jenkins-ci.org/commit/jenkins/dbb100da58a084fb0a6ce129d3f2b7ad827e87ee Log: FIXED JENKINS-14495 Hetero lists not working correctly after adding elements. Unlike JENKINS-14514 this is a true fix rather than a workaround (now removed), and is more general. cjo9900 discovered that behaviors were being redundantly registered (as of 1.474 the monolithic JS is broken up); this caused some behaviors to be run repeatedly on the same elements, breaking reasonable expectations of some behaviors. The ideal fix would be to change Behavior.register to be idempotent: for example, key it by selector, then maintain a set of distinct behavior functions for each. Unfortunately some adjuncts directly call Behavior.list.unshift, bypassing register(...), which would be tricky to intercept (would need to make a mock of Array). The known one cases are in core, but it is possible plugin adjuncts do this too, in which case it would be incompatible to (say) change the ArrayMapString,Behavior to a MapString,ArrayBehavior. Instead, permitting redundant registrations as before, and just silently skipping all but the first at runtime when applying behaviors. Beware that since adjuncts are loaded from multiple places, different JS function objects are registered each time, so a naive set of behavior functions does not work; have to identify functions by their toString in order to ensure that each is run only once. (Currently once per selector, conceivably 1x per element; could if necessary be refined to make sure a given behavior is only run once on a given element during one call to applySubtree even if the element matches multiple selectors.) 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-14495) Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder
SCM/JIRA link daemon commented on JENKINS-14495 Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/resources/lib/form/repeatable/repeatable.js war/src/main/webapp/scripts/behavior.js http://jenkins-ci.org/commit/jenkins/dbb100da58a084fb0a6ce129d3f2b7ad827e87ee Log: FIXED JENKINS-14495 Hetero lists not working correctly after adding elements. Unlike JENKINS-14514 this is a true fix rather than a workaround (now removed), and is more general. cjo9900 discovered that behaviors were being redundantly registered (as of 1.474 the monolithic JS is broken up); this caused some behaviors to be run repeatedly on the same elements, breaking reasonable expectations of some behaviors. The ideal fix would be to change Behavior.register to be idempotent: for example, key it by selector, then maintain a set of distinct behavior functions for each. Unfortunately some adjuncts directly call Behavior.list.unshift, bypassing register(...), which would be tricky to intercept (would need to make a mock of Array). The known one cases are in core, but it is possible plugin adjuncts do this too, in which case it would be incompatible to (say) change the ArrayMapString,Behavior to a MapString,ArrayBehavior. Instead, permitting redundant registrations as before, and just silently skipping all but the first at runtime when applying behaviors. Beware that since adjuncts are loaded from multiple places, different JS function objects are registered each time, so a naive set of behavior functions does not work; have to identify functions by their toString in order to ensure that each is run only once. (Currently once per selector, conceivably 1x per element; could if necessary be refined to make sure a given behavior is only run once on a given element during one call to applySubtree even if the element matches multiple selectors.) 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-14478) 1.474 breaks adding a list-view to sectioned-view plugin
jglick resolved JENKINS-14478 as Duplicate 1.474 breaks adding a list-view to sectioned-view plugin Change By: jglick (03/Aug/12 4:58 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-14495) Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder
jglick resolved JENKINS-14495 as Fixed Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder Change By: jglick (03/Aug/12 5:00 PM) 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-14632) Hetero lists broken in Jenkins 1.455+ by introduction of resource adjuncts
jglick assigned JENKINS-14632 to Kohsuke Kawaguchi Hetero lists broken in Jenkins 1.455+ by introduction of resource adjuncts Change By: jglick (03/Aug/12 5:00 PM) Assignee: KohsukeKawaguchi 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-14495) Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder
dogfood commented on JENKINS-14495 Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder Integrated in jenkins_main_trunk #1834 FIXED JENKINS-14495 Hetero lists not working correctly after adding elements. (Revision dbb100da58a084fb0a6ce129d3f2b7ad827e87ee) Result = UNSTABLE Jesse Glick : dbb100da58a084fb0a6ce129d3f2b7ad827e87ee Files : core/src/main/resources/lib/form/repeatable/repeatable.js changelog.html war/src/main/webapp/scripts/behavior.js 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-14625) Exception no page found
mcrooney commented on JENKINS-14625 Exception no page found Thanks for the report! Unfortunately I'm on Snow Leopard and don't have a Mountain Lion machine to test with. Is this the only problem you are experiencing with Mountain Lion + Jenkins? 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-14495) Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder
jglick commented on JENKINS-14495 Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder Looks like my change caused a couple of test failures, investigating... 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-11856) Jenkins Slave fail to start on Windows 2008 R2 64-bit as windows service
Denis Blanchette commented on JENKINS-11856 Jenkins Slave fail to start on Windows 2008 R2 64-bit as windows service We have the same problem. We are using Jenkins 1.472 running on Windows Server 2008 R2 master and slaves. Connecting to server.example.com ERROR: Message not found for errorCode: 0x8001 org.jinterop.dcom.common.JIException: Message not found for errorCode: 0x8001 at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:546) at org.jinterop.dcom.core.JIComServer.initialise(JIComServer.java:458) at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:427) at org.jvnet.hudson.wmi.WMI.connect(WMI.java:59) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:220) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200) 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 java.lang.Thread.run(Unknown Source) Caused by: rpc.BindException: Unable to bind. (unknown) at rpc.security.ntlm.NtlmConnectionContext.accept(NtlmConnectionContext.java:137) at rpc.ConnectionOrientedEndpoint.connect(ConnectionOrientedEndpoint.java:252) at rpc.ConnectionOrientedEndpoint.bind(ConnectionOrientedEndpoint.java:217) at rpc.ConnectionOrientedEndpoint.rebind(ConnectionOrientedEndpoint.java:153) at org.jinterop.dcom.transport.JIComEndpoint.rebindEndPoint(JIComEndpoint.java:40) at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:529) ... 10 more I was able to connect using Jeebitesh Kalantri workaround (launch via Java web start). I then reconfigured the slave to launch via the windows service. However, each time the slave is restarted, someone need to start the service manually, even if the service is set to start automatically. 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-14680) CVS Plugin v2.5 throws NPE
Michael Clarke assigned JENKINS-14680 to Michael Clarke CVS Plugin v2.5 throws NPE Change By: Michael Clarke (03/Aug/12 7:13 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-14680) CVS Plugin v2.5 throws NPE
Michael Clarke resolved JENKINS-14680 as Fixed CVS Plugin v2.5 throws NPE Fixed in latest snapshot. Being caused by trying to list all files in an empty directory Change By: Michael Clarke (03/Aug/12 7:14 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-14625) Exception no page found
Peter Florijn commented on JENKINS-14625 Exception no page found I see no other problems with Jenkins on Mountain Lion. Can I switch on some extra logging to provide you with some morde debug info ? Is this te correct string for the Jenkins Logger ? jenkins.plugins.htmlpublisher 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-14625) Exception no page found
Peter Florijn edited a comment on JENKINS-14625 Exception no page found I see no other problems with Jenkins on Mountain Lion. Can I switch on some extra logging to provide you with some more debug info ? Is this te correct string for the Jenkins Logger ? jenkins.plugins.htmlpublisher 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-14157) allow to set subversion workspace version per slave
Fritz Elfert commented on JENKINS-14157 allow to set subversion workspace version per slave +1 from me. The global setting is pretty useless in a mixed environment. It should move to the node and the main setting might be serve as a default for new nodes. 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-14495) Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder
SCM/JIRA link daemon commented on JENKINS-14495 Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder Code changed in jenkins User: Jesse Glick Path: test/src/test/java/scripts/BehaviorTest.java test/src/test/resources/scripts/BehaviorTest/testDuplicateRegistrations.jelly war/src/main/webapp/scripts/behavior.js http://jenkins-ci.org/commit/jenkins/f39fbdb312c3c87ef77a72446273423d906942ed Log: JENKINS-14495 Refined fix - needed to pull uniqueness check out of apply() fn in case we were being passed an Array of nodes. Fixes test failures introduced by dbb100d, and adds a test for it now that I know it can be 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-14683) TFS Plugin parses pt_BR dates incorrectly
Gabriel Speckhahn
created JENKINS-14683
TFS Plugin parses pt_BR dates incorrectly
Issue Type:
Bug
Affects Versions:
current
Assignee:
redsolo
Components:
tfs
Created:
03/Aug/12 8:06 PM
Description:
The TFS SCM plugin cannot parse the date output by the TFS detailed history command if the system locale is set to Brazilian Portuguese.
Therefore, SCM polling always fails to detect any changes, for the month and day of the last change get swapped.
For instance:
Started on Aug 3, 2012 4:30:38 PM
foundation-v2.06b $ C:\apps\TEE-CLC-10.1.0\tf.cmd history $/redacted -noprompt -version2012-08-02T19:17:11Z~D2012-08-03T19:30:39Z -recursive -format:detailed -server:redacted
Changeset: 107235
User: redacted
Date: 03/08/2012 10:13:46
This date is August 3rd, 2012, but the TFS plugins interprets it as March 8th because it attempts to parse the date string with Java's deprecated Date.parse method:
hudson.plugins.tfs.util.DateUtil:
@SuppressWarnings("deprecation")
public static Date parseDate(String dateString, Locale locale, TimeZone timezone) throws ParseException {
Date date = null;
dateString = dateString.replaceAll("(p|P)\\.(m|M).", "PM").replaceAll("(a|A)\\.(m|M).", "AM");
try {
// Use the deprecated Date.parse method as this is very good at detecting
// dates commonly output by the US and UK standard locales of dotnet that
// are output by the Microsoft command line client.
date = new Date(Date.parse(dateString));
} catch (IllegalArgumentException e) {
// ignore - parse failed.
}
if (date == null) {
// The old fashioned way did not work. Let's try it using a more
// complex alternative.
DateFormat[] formats = createDateFormatsForLocaleAndTimeZone(locale, timezone);
return parseWithFormats(dateString, formats);
}
return date;
}
I copied this class to a standalone project on Eclipse and printed the parsed date. The result with the original code for 03/08/2012 10:13:46 was:
Thu Mar 08 10:13:46 BRT 2012
After I changed the class to remove the call to the deprecated method, the date was parsed correctly:
Fri Aug 03 10:13:46 BRT 2012
Environment:
Windows 7 x86
Project:
Jenkins
Priority:
Major
Reporter:
Gabriel Speckhahn
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-14633) Ruby Plugin causes jobs to fail to load
Jørgen Tjernø assigned JENKINS-14633 to Charles Lowell Ruby Plugin causes jobs to fail to load Assigning to Charles (I hope this is allright?) Change By: Jørgen Tjernø (03/Aug/12 8:14 PM) Assignee: JørgenTjernø CharlesLowell 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-14683) TFS Plugin parses pt_BR dates incorrectly
Gabriel Speckhahn resolved JENKINS-14683 as Incomplete TFS Plugin parses pt_BR dates incorrectly canceling Change By: Gabriel Speckhahn (03/Aug/12 8:20 PM) Status: Open Resolved Resolution: Incomplete 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-14495) Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder
dogfood commented on JENKINS-14495 Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder Integrated in jenkins_main_trunk #1835 JENKINS-14495 Refined fix - needed to pull uniqueness check out of apply() fn in case we were being passed an Array of nodes. (Revision f39fbdb312c3c87ef77a72446273423d906942ed) Result = SUCCESS Jesse Glick : f39fbdb312c3c87ef77a72446273423d906942ed Files : test/src/test/resources/scripts/BehaviorTest/testDuplicateRegistrations.jelly test/src/test/java/scripts/BehaviorTest.java war/src/main/webapp/scripts/behavior.js 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-11739) Mysterious FilerException: Attempt to reopen a file for path ...
SCM/JIRA link daemon commented on JENKINS-11739 Mysterious FilerException: Attempt to reopen a file for path ... Code changed in jenkins User: Jesse Glick Path: changelog.html core/pom.xml war/pom.xml http://jenkins-ci.org/commit/jenkins/10dddebf7bd86e30b630038e5ebe0295f190a8de Log: FIXED JENKINS-11739 Various mistakes in annotation processors affecting some plugins. 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-11739) Mysterious FilerException: Attempt to reopen a file for path ...
SCM/JIRA link daemon resolved JENKINS-11739 as Fixed Mysterious FilerException: Attempt to reopen a file for path ... Change By: SCM/JIRA link daemon (03/Aug/12 9:45 PM) 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-14684) exception occurs when trying to view the read only configuration for job or global
Slide-O-Mix created JENKINS-14684 exception occurs when trying to view the read only configuration for job or global Issue Type: Bug Assignee: Slide-O-Mix Components: read-only-configurations Created: 03/Aug/12 10:10 PM Description: WARNING: Caught exception evaluating: it.transformToReadOnly(). Reason: ClientAbortException: java.io.IOException ClientAbortException: java.io.IOException at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:369) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:356) at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:392) at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:381) at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:93) at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:86) at org.jenkinsci.plugins.readonly.JobConfiguration.transformToReadOnly(JobConfiguration.java:66) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72) at org.apache.commons.jelly.parser.EscapingExpression.evaluate(EscapingExpression.java:24) at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:107) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:65) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at
[JIRA] (JENKINS-11739) Mysterious FilerException: Attempt to reopen a file for path ...
dogfood commented on JENKINS-11739 Mysterious FilerException: Attempt to reopen a file for path ... Integrated in jenkins_main_trunk #1836 FIXED JENKINS-11739 Various mistakes in annotation processors affecting some plugins. (Revision 10dddebf7bd86e30b630038e5ebe0295f190a8de) Result = UNSTABLE Jesse Glick : 10dddebf7bd86e30b630038e5ebe0295f190a8de Files : core/pom.xml changelog.html war/pom.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
