[JIRA] (JENKINS-9895) Wall Display Plugin shows MavenModuleSet:MavenModuleSet
cforce commented on JENKINS-9895 Wall Display Plugin shows MavenModuleSet:MavenModuleSet Its working now. Tx for fix 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-9895) Wall Display Plugin shows MavenModuleSet:MavenModuleSet
cforce closed JENKINS-9895 as Fixed Wall Display Plugin shows MavenModuleSet:MavenModuleSet Fixed! Change By: cforce (12/Jul/12 6:27 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14261) Builds hanging right before e-mail notifications are sent out - Mercurial
Slide-O-Mix commented on JENKINS-14261 Builds hanging right before e-mail notifications are sent out - Mercurial This looks like its having issues with mail address resolution. This is similar to issues that several other users are having with the email address resolution. 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-14401) Jenkins throws exception iv version colnumn plugin is disabled.
Alexey Gavrilov created JENKINS-14401 Jenkins throws exception iv version colnumn plugin is disabled. Issue Type: Bug Affects Versions: current Assignee: sogabe Components: versioncolumn Created: 12/Jul/12 7:00 AM Description: When versioncolumn plugin is disabled and jenkins is restarted, jenkins throws exception and stops working after restart. Versions: Jenkins 1.470 versioncolumn 0.2 Error org.jvnet.hudson.reactor.ReactorException: hudson.util.IOException2: Unable to read C:\Jenkins\config.xml at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) at jenkins.model.Jenkins.executeReactor(Jenkins.java:885) at jenkins.model.Jenkins.init(Jenkins.java:790) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) Caused by: hudson.util.IOException2: Unable to read C:\Jenkins\config.xml at hudson.XmlFile.unmarshal(XmlFile.java:160) at jenkins.model.Jenkins$15.run(Jenkins.java:2456) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:874) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) 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: com.thoughtworks.xstream.converters.ConversionException: Cannot load java class hudson.plugin.versioncolumn.Messages : hudson.plugin.versioncolumn.Messages Debugging information message : Cannot load java class hudson.plugin.versioncolumn.Messages cause-exception : java.lang.ClassNotFoundException cause-message : hudson.plugin.versioncolumn.Messages class : hudson.model.Hudson required-type : java.lang.Class path: /hudson/slaves/slave4/temporaryOfflineCause/description/holder/owner line number : 349 --- at com.thoughtworks.xstream.converters.extended.JavaClassConverter.fromString(JavaClassConverter.java:52) at com.thoughtworks.xstream.converters.SingleValueConverterWrapper.fromString(SingleValueConverterWrapper.java:41) at com.thoughtworks.xstream.converters.SingleValueConverterWrapper.unmarshal(SingleValueConverterWrapper.java:49) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:292) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:234) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:181) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:292) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:234) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:181) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:292)
[JIRA] (JENKINS-14401) Jenkins throws exception iv version colnumn plugin is disabled.
Alexey Gavrilov updated JENKINS-14401 Jenkins throws exception iv version colnumn plugin is disabled. Change By: Alexey Gavrilov (12/Jul/12 7:10 AM) Labels: configexceptionjenkinsplugin Description: When versioncolumnplugin VersionColumnplug-in isdisabledand jenkins Jenkins isrestarted, jenkins Jenkins throwsexceptionandstopsworkingafterrestart. Important:SomenodesweresetofflinebyVersionColumnplug-inwhenJenkinswasrestarted. Versions:-Jenkins1.470- versioncolumn VersionColumn 0.2Errororg.jvnet.hudson.reactor.ReactorException:hudson.util.IOException2:UnabletoreadC:\Jenkins\config.xml atorg.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) atjenkins.InitReactorRunner.run(InitReactorRunner.java:43) atjenkins.model.Jenkins.executeReactor(Jenkins.java:885) atjenkins.model.Jenkins.init(Jenkins.java:790) athudson.model.Hudson.init(Hudson.java:81) athudson.model.Hudson.init(Hudson.java:77) athudson.WebAppMain$2.run(WebAppMain.java:217)Causedby:hudson.util.IOException2:UnabletoreadC:\Jenkins\config.xml athudson.XmlFile.unmarshal(XmlFile.java:160) atjenkins.model.Jenkins$15.run(Jenkins.java:2456) atorg.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) atorg.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) atjenkins.model.Jenkins$7.runTask(Jenkins.java:874) atorg.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) atorg.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) atjava.util.concurrent.ThreadPoolExecutor$Worker.runTask(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource) atjava.lang.Thread.run(UnknownSource)Causedby:com.thoughtworks.xstream.converters.ConversionException:Cannotloadjavaclasshudson.plugin.versioncolumn.Messages:hudson.plugin.versioncolumn.MessagesDebugginginformationmessage:Cannotloadjavaclasshudson.plugin.versioncolumn.Messagescause-exception:java.lang.ClassNotFoundExceptioncause-message:hudson.plugin.versioncolumn.Messagesclass:hudson.model.Hudsonrequired-type:java.lang.Classpath:/hudson/slaves/slave[4]/temporaryOfflineCause/description/holder/ownerlinenumber:349--- atcom.thoughtworks.xstream.converters.extended.JavaClassConverter.fromString(JavaClassConverter.java:52) atcom.thoughtworks.xstream.converters.SingleValueConverterWrapper.fromString(SingleValueConverterWrapper.java:41) atcom.thoughtworks.xstream.converters.SingleValueConverterWrapper.unmarshal(SingleValueConverterWrapper.java:49) atcom.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) atcom.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) atcom.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) athudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:292) athudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:234) athudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:181) atcom.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) atcom.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) atcom.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) athudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:292) athudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:234) athudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:181) atcom.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) atcom.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) atcom.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) athudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:292) athudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:234) athudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:181)
[JIRA] (JENKINS-14403) Add option to avoid workspace cleanup if job failed
Bjoern Sonntag created JENKINS-14403 Add option to avoid workspace cleanup if job failed Issue Type: Improvement Assignee: vjuranek Components: ws-cleanup Created: 12/Jul/12 7:37 AM Description: For problem analysis, it would be nice if there was an option to only cleanup the workspace in the post-build step, if the job has completed successfully. A build job may fail due to compile errors or a problem with the job configuration. In both cases it can be helpful to retain the workspace for further analysis. We are using workspace cleanup as post build step with all jobs, in order to reduce necessary disk space. Otherwise, cleanup as pre-build step would also be sufficient. Project: Jenkins Priority: Major Reporter: Bjoern Sonntag 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-14404) Selenium Plugin won't compile
Marvi Benedet created JENKINS-14404 Selenium Plugin wont compile Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: selenium Created: 12/Jul/12 8:43 AM Description: Seleniun plugin won't compile any more. Changed the pom: 41 artifactIdselenium-server-standalone/artifactId 41 artifactIdselenium-server/artifactId seems to work. Project: Jenkins Priority: Major Reporter: Marvi Benedet 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-14405) When 'Discard old builds' is specified using 'Max # of builds to keep' in matrix job - all job history is deleted on master together with folder for the last label used in the
Anna Gon created JENKINS-14405 When Discard old builds is specified using Max # of builds to keep in matrix job - all job history is deleted on master together with folder for the last label used in the job Issue Type: Bug Assignee: Unassigned Attachments: Jenkins SystemInfo.txt Components: core Created: 12/Jul/12 9:02 AM Description: I use "Max # of builds to keep" to discard old builds. When "Max # of builds to keep" reaches the max number set for a given job - Jenkins deletes entire folder of last label value used in this job. For example I have labels set to: BldT with value Debug TrgtT with value Win32 slvT with value GP So the internal content of the job folder structure has ../BldT/Debug/TrgT/Win32/slvT/GP/.. Then when "Max # of builds to keep" is reached - directory GP is deleted. This happens to most of the jobs I have. The only way we found to fix this is to 'Save' or 'Apply' changes in the job configuration page (without making any changes to the job). This restores the folder structure on master. Jenkins log for when this happens is: SEVERE: Failed to rotate log java.io.IOException: /jenkins-server/Home/jobs/PCompiler_sshaha2/configurations/axis-BldT/Debug/axis-TrgtT/Win32/axis-slvT/GP/builds/2012-05-06_14-11-06 is in use at hudson.model.Run.delete(Run.java:1239) at hudson.model.AbstractBuild.delete(AbstractBuild.java:380) at hudson.matrix.LinkedLogRotator.perform(LinkedLogRotator.java:64) at hudson.model.Job.logRotate(Job.java:336) at hudson.model.Run.run(Run.java:1478) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Due Date: 19/Jul/12 12:00 AM Environment: java version 1.6.0_20 OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode) Jenkins version 1.458 Jenkins server is being run on Fedora 14 ( as deamon) Jenkins slaves are being run on Windows 7 and Red Hat Operating systems. Project: Jenkins Priority: Critical Reporter: Anna Gon 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
how to use valgrind plugin
Hello everyone, I am trying to use valgrind plugin in my jenkins setup. I want to run valgrind with my maven tests. The tests run as java programs. I configures Run valgrind as following Working Directory - configured a valid directory Executable Pattern - java Output Directory- configured valid directory File Ending - not sure what to give for this filed. The tests exectue without valgrind and I see the following in console output: [Valgrind] executable files: I am not sure what is going wrong. There is no proper documentation as to how various fields for Run valgrind step has to configured. Please help. Thanks Regards, Tanima
[JIRA] (JENKINS-14383) Warnings Plugin: Slow Performance on customized parsing rules with Regular Expression
SCM/JIRA link daemon commented on JENKINS-14383 Warnings Plugin: Slow Performance on customized parsing rules with Regular _expression_ Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/parser/DynamicParser.java src/main/java/hudson/plugins/warnings/parser/GroovyExpressionMatcher.java src/test/java/hudson/plugins/warnings/parser/DynamicParserTest.java src/test/java/hudson/plugins/warnings/parser/ParserSpeed.java src/test/resources/hudson/plugins/warnings/parser/issue14383.txt http://jenkins-ci.org/commit/warnings-plugin/976c8cd3e383bdfb2eab378035d37cff5091e8ef Log: FIXED JENKINS-14383 Parse the groovy script only once. Compare: https://github.com/jenkinsci/warnings-plugin/compare/21a0cedfe5bd...976c8cd3e383 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-14406) It should be possible to set next build number from Command Line Interface
Jose Sa created JENKINS-14406 It should be possible to set next build number from Command Line Interface Issue Type: Bug Assignee: Dean Yu Components: next-build-number Created: 12/Jul/12 9:59 AM Description: The plugin next-build-number allows the override of the Next build number to a value greater than the current one from the Jenkins page, but it should also be possible to do this simple command from CLI interface. The CLI interface already allows to delete specific builds but not set the next build number. This would be very helpfull for automation cases where deploying jobs though command line interface based on templates for migration from other servers or build systems in order to provide continuation of build numbering on same components. Project: Jenkins Priority: Major Reporter: Jose Sa 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-14404) Selenium Plugin won't compile
Marvi Benedet updated JENKINS-14404 Selenium Plugin wont compile Change By: Marvi Benedet (12/Jul/12 10:03 AM) Description: Seleniunpluginwontcompileanymore. Changed Theproblemseem the pom line : 41 artifactIdselenium-server-standalone/artifactId 41 artifactIdselenium-server/artifactId seemstowork inthepomfile . Mavendoesntdownloadthecorrectstuff 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-10832) make testng reporter-output field viewable from testng-plugin generated reports
Pehr Johansson commented on JENKINS-10832 make testng reporter-output field viewable from testng-plugin generated reports This should be possible in the latests 6.6beta version of testng. Changes been made to generate the testng-results.xml in the following format: test-method status="PASS" signature="setUp()pri:0, instance:net.test.web.NewScript@35cf7491" name="setUp" is-config="true" duration-ms="5814" started-at="2012-07-10T22:17:52Z" finished-at="2012-07-10T22:17:58Z" reporter-output /reporter-output /test-method !-- setUp -- test-method status="FAIL" signature="testFail()pri:0, instance:net.test.web.NewScript@35cf7491" name="testFail" duration-ms="5811" started-at="2012-07-10T22:17:58Z" finished-at="2012-07-10T22:18:04Z" reporter-output line ![CDATA[preexpected true but found false/prebr/br]] /line line ![CDATAimg src="" /br] /line /reporter-output 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-14407) Allow multi0value default for Scheduled runs
Martin Leon created JENKINS-14407 Allow multi0value default for Scheduled runs Issue Type: Improvement Assignee: domi Components: nodelabelparameter Created: 12/Jul/12 12:34 PM Description: The feature to allow multiple concurrent builds is great! Would like to be able to do that when the build is triggered on a schedule. I'm hoping that allowing the 'default' field to allow multiple values will enable me to run the build concurrently on multiple slaves without human intervention. Project: Jenkins Priority: Minor Reporter: Martin Leon 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-14408) URLTrigger deletes schedule from config, then does not trigger
Michiel Koster created JENKINS-14408 URLTrigger deletes schedule from config, then does not trigger Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: urltrigger Created: 12/Jul/12 12:41 PM Description: URLTrigger will not trigger when the cron-like 'spec' element is empty. However, on saving the Jenkins job, it will delete the contents of this tag, so triggering never happens. Working config: --- org.jenkinsci.plugins.urltrigger.URLTrigger spec* * * * */spec entries org.jenkinsci.plugins.urltrigger.URLTriggerEntry urlhttp://jenkins-dev.fortes.local:8080/job/Build%205-5-4/lastSuccessfulBuild/buildNumber/url proxyActivatedfalse/proxyActivated checkStatusfalse/checkStatus statusCode200/statusCode checkETagfalse/checkETag checkLastModificationDatetrue/checkLastModificationDate inspectingContenttrue/inspectingContent contentTypes org.jenkinsci.plugins.urltrigger.content.SimpleContentType/ /contentTypes /org.jenkinsci.plugins.urltrigger.URLTriggerEntry /entries labelRestrictionfalse/labelRestriction /org.jenkinsci.plugins.urltrigger.URLTrigger Non-working (after modifying the job spec is cleared): -- org.jenkinsci.plugins.urltrigger.URLTrigger spec/spec entries org.jenkinsci.plugins.urltrigger.URLTriggerEntry urlhttp://jenkins-dev.fortes.local:8080/job/Build%205-5-4/lastSuccessfulBuild/buildNumber/url proxyActivatedfalse/proxyActivated checkStatusfalse/checkStatus statusCode200/statusCode checkETagfalse/checkETag checkLastModificationDatetrue/checkLastModificationDate inspectingContenttrue/inspectingContent contentTypes org.jenkinsci.plugins.urltrigger.content.SimpleContentType/ /contentTypes /org.jenkinsci.plugins.urltrigger.URLTriggerEntry /entries labelRestrictionfalse/labelRestriction /org.jenkinsci.plugins.urltrigger.URLTrigger Jenkins 1.474 on Ubuntu 12.04 URLTrigger 0.23 Project: Jenkins Priority: Major Reporter: Michiel Koster 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-14409) RuntimeException in RunListeners may cause Future.get to never return
rsandell created JENKINS-14409 RuntimeException in RunListeners may cause Future.get to never return Issue Type: Bug Assignee: Unassigned Components: core Created: 12/Jul/12 1:00 PM Description: For example the parameterized-trigger uses Future.get to wait for a triggered build to finish, when a NullpointerException was thrown in the ArtifactDeployer's onDeleted the build that waited was waiting forever. The exception from the log that caused Future.set to not be called correctly was: Jul 5, 2012 11:00:24 PM hudson.model.Executor run SEVERE: Executor threw an exception java.lang.NullPointerException at org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher$DeleteRemoteArtifact.onDeleted(ArtifactDeployerPublisher.java:187) at org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher$DeleteRemoteArtifact.onDeleted(ArtifactDeployerPublisher.java:171) at hudson.model.listeners.RunListener.fireDeleted(RunListener.java:208) at hudson.model.Run.delete(Run.java:1187) at hudson.model.AbstractBuild.delete(AbstractBuild.java:362) at hudson.tasks.LogRotator.perform(LogRotator.java:157) at hudson.model.Job.logRotate(Job.java:315) at hudson.model.Run.run(Run.java:1440) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:175) Although it was due to an exception in a plugin I think the Executor should be a bit more robust in this case. This mail thread has a similar description of the problem: https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-dev/P7XiYknqgoI Environment: Jenkins 1.424.2 Jenkins 1.447.2 Project: Jenkins Priority: Minor Reporter: rsandell 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-12646) API returns previous builds status
rsandell assigned JENKINS-12646 to Unassigned API returns previous builds status Change By: rsandell (12/Jul/12 1:03 PM) Assignee: rsandell 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-12646) API returns previous builds status
rsandell updated JENKINS-12646 API returns previous builds status Change By: rsandell (12/Jul/12 1:03 PM) Component/s: multi-slave-config 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-14394) The version 1.1.21 breaks
David Ehrenberger commented on JENKINS-14394 The version 1.1.21 breaks Same thing happened to me (no job configuration changes); had to roll back. 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-14355) create-fingerprint-plugin cant find .dotfiles (e.g.: .git/FETCH_HEAD)
Antoine Musso commented on JENKINS-14355 create-fingerprint-plugin cant find .dotfiles (e.g.: .git/FETCH_HEAD) Might be related to JENKINS-13165 which is about ant excluding .git directories by default. Looking at core/src/main/java/hudson/tasks/Fingerprinter.java record() calls FileSet src = ""> The fix for the dirScanner was: https://github.com/jenkinsci/jenkins/commit/0725d2765da789e02914deb4893a449eeda6a820 Which added an option to disable the default excludes, aka: FileSet fs = Util.createFileSet(dir,includes,excludes); fs.setDefaultexcludes(useDefaultExcludes); The core/src/main/java/hudson/Util.java createFileSet() method does have an exclude which default to null but does not allow one to disable the useDefaultExcludes. So I guess this bug is about porting the dirScanner fix to Util.createFileSet(). 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-13165) Cloning workspace loses hidden files/directories
Antoine Musso commented on JENKINS-13165 Cloning workspace loses hidden files/directories I have opened JENKINS-14355 about the fingerprint plugin not being able to fingerprint ".git/FETCH_HEAD. I believe it is a similar issue as dirscanner fixed by https://github.com/jenkinsci/jenkins/commit/0725d2765da789e02914deb4893a449eeda6a820#L1R102 but with Util.createFileSet() this time. 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-14355) create-fingerprint-plugin cant find .dotfiles (e.g.: .git/FETCH_HEAD)
Antoine Musso updated JENKINS-14355 create-fingerprint-plugin cant find .dotfiles (e.g.: .git/FETCH_HEAD) Change By: Antoine Musso (12/Jul/12 1:41 PM) Labels: core 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-14355) create-fingerprint-plugin cant find .dotfiles (e.g.: .git/FETCH_HEAD)
Antoine Musso updated JENKINS-14355 create-fingerprint-plugin cant find .dotfiles (e.g.: .git/FETCH_HEAD) Change By: Antoine Musso (12/Jul/12 1:42 PM) Component/s: core 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
Re: [JIRA] (JENKINS-12934) Subversion Tag plugin tries to copy from invalid source path
Hi any one got the above issue solved ? Same issue here, please let me know. -- View this message in context: http://jenkins.361315.n4.nabble.com/JIRA-JENKINS-12934-Subversion-Tag-plugin-tries-to-copy-from-invalid-source-path-tp4432171p4634582.html Sent from the Jenkins issues mailing list archive at Nabble.com.
[JIRA] (JENKINS-14355) create-fingerprint-plugin cant find .dotfiles (e.g.: .git/FETCH_HEAD)
Antoine Musso commented on JENKINS-14355 create-fingerprint-plugin cant find .dotfiles (e.g.: .git/FETCH_HEAD) Moved to core, the Fingerprinter plugin just call the Jenkins core API: Fingerprinter fingerprinter = new Fingerprinter(this.targets, false); return fingerprinter.perform(build, launcher, listener); This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14410) Xvnc does not set DISPLAY variable
Matthias Spiller created JENKINS-14410 Xvnc does not set DISPLAY variable Issue Type: Bug Assignee: Unassigned Components: xvnc Created: 12/Jul/12 1:56 PM Description: I have enabled the Xvnc plugin for a free-style software project. However the windows opened during the build show up on my desktop, not in the vnc session. Environment: RedHat EL 5.8. Jenkins 1.473 Project: Jenkins Priority: Major Reporter: Matthias Spiller 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-12934) Subversion Tag plugin tries to copy from invalid source path
Eswar Samy commented on JENKINS-12934 Subversion Tag plugin tries to copy from invalid source path Hi Arends, did you get this issue solved ? i have the same issue here ..please tell me how did u solve this issue Thanks, Eswarasamy eswarasam...@gmail.com 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-12934) Subversion Tag plugin tries to copy from invalid source path
Peter Lillevold edited a comment on JENKINS-12934 Subversion Tag plugin tries to copy from invalid source path Eswar, what Jenkins and svn versions are you on? Regards, Peter 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-12934) Subversion Tag plugin tries to copy from invalid source path
Peter Lillevold commented on JENKINS-12934 Subversion Tag plugin tries to copy from invalid source path Eswar, what Jenkins and svn versions are you on? Peter 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-12744) Execute a command before timeout
Norman Seidel commented on JENKINS-12744 Execute a command before timeout Exactly what we need / would like to have (thread dump). 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-12744) Execute a command before timeout
Julien Carsique commented on JENKINS-12744 Execute a command before timeout You can build and test it from https://github.com/jcarsique/build-timeout-plugin ; at Nuxeo, we are using it for a few months now. 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-14411) Build Flow jobs not able to start other jobs in Post-Build
Rob Sweet created JENKINS-14411 Build Flow jobs not able to start other jobs in Post-Build Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: build-flow Created: 12/Jul/12 3:10 PM Description: I am unable to add a Post-Build action to start another job from a Build Flow job. The option is there but if I add the action, save the job, and then go back to the configuration screen, my Post-Build action isn't saved. Other configuration params are saved properly. Environment: RHEL6, Jenkins 1.473 Project: Jenkins Priority: Minor Reporter: Rob Sweet 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-14413) TFS plugin: credentials password is in clear text in page source =-O
Vladimir Dyuzhev created JENKINS-14413 TFS plugin: credentials password is in clear text in page source =-O Issue Type: Bug Assignee: redsolo Components: tfs Created: 12/Jul/12 3:13 PM Description: When using Team Foundation Server plugin in Source Control Management section, the entered password can be viewed by anyone by looking into the page source. Suggestion: after the entry of the password, encrypt the password and store it in the file system. Do not show the password in the password field afterwards; instead, show a placeholder/marker message like Password Is Encryped. Environment: Linux Project: Jenkins Labels: plugin jenkins Priority: Critical Reporter: Vladimir Dyuzhev 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-14414) Going from 1.472 to 1.473 breaks Certificate authentication
David Gubler updated JENKINS-14414 Going from 1.472 to 1.473 breaks Certificate authentication Change By: David Gubler (12/Jul/12 3:27 PM) Description: SVNcheckout orupdate doesnotworkanymoreinversion1.473(and1.474).Thecertificateisvalid(worksifIimportitintomybrowser)andeverythingworksagainwhenIgobacktoversion1.472.AffectsbothregularSVNcheckoutsaswellastheSCMSyncConfigurationPlugin.Tryingtore-authenticate(re-uploadpkcs12fileandenterpassword)doesnotwork.Stacktracefromaregularjubrunisattached. 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-14414) Going from 1.472 to 1.473 breaks Certificate authentication
David Gubler created JENKINS-14414 Going from 1.472 to 1.473 breaks Certificate authentication Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: svncheckoutfail.txt Components: subversion Created: 12/Jul/12 3:26 PM Description: SVN checkout does not work any more in version 1.473 (and 1.474). The certificate is valid (works if I import it into my browser) and everything works again when I go back to version 1.472. Affects both regular SVN checkouts as well as the "SCM Sync Configuration Plugin". Trying to re-authenticate (re-upload pkcs12 file and enter password) does not work. Stack trace from a regular jub run is attached. Environment: Package from http://pkg.jenkins-ci.org/debian/ running on Debian Wheezy/Java 7 Project: Jenkins Priority: Major Reporter: David Gubler 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-14414) Going from 1.472 to 1.473 breaks Certificate authentication
David Gubler updated JENKINS-14414 Going from 1.472 to 1.473 breaks Certificate authentication Change By: David Gubler (12/Jul/12 3:28 PM) Description: SVNcheckoutorupdatedoesnotworkanymoreinversion1.473(and1.474).Thecertificate is andpkcs12passwordare valid(worksifIimportitintomybrowser)andeverythingworksagainwhenIgobacktoversion1.472.AffectsbothregularSVNcheckoutsaswellastheSCMSyncConfigurationPlugin.Tryingtore-authenticate(re-uploadpkcs12fileandenterpassword)doesnotwork.Stacktracefromaregularjubrunisattached. 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-14414) Going from 1.472 to 1.473 breaks Certificate authentication
David Gubler updated JENKINS-14414 Going from 1.472 to 1.473 breaks Certificate authentication Change By: David Gubler (12/Jul/12 3:31 PM) Description: SVNcheckoutorupdatedoesnotworkanymoreinversion1.473(and1.474) whenusingSSLclientcertificates . Apachesaysaccessto.../svnfailed,reason:SSLrequirement_expression_notfulfilled(seeSSLlogfileformoredetails).TheresnoSSLlog,sonoideawhatitsays. Thecertificateandpkcs12passwordarevalid(worksifIimportitintomybrowser)andeverythingworksagainwhenIgobacktoversion1.472.AffectsbothregularSVNcheckoutsaswellastheSCMSyncConfigurationPlugin.Tryingtore-authenticate(re-uploadpkcs12fileandenterpassword)doesnotwork.Stacktracefromaregularjubrunisattached. 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-13901) Clearcase plugin tries to use mkview with -vws null/[viewpath] after restart
banoss edited a comment on JENKINS-13901 Clearcase plugin tries to use mkview with -vws null/[viewpath] after restart I get exactly this issue with Solaris 10 slaves, I've never notices this problem on Windows slaves although they are used a lot less. I don't need to restart Jenkins however to see this issue. But I think if the build jumps to a different slave we see this issue, but I'm not sure if this is the only cause. It certainly doesn't occur 100% when a job jumps to a different slave. Workaround is the same, have to re-save each job. We have a lot of jobs ... Jenkins v1.474, Jenkins CC plugin v1.3.7 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-14414) Going from 1.472 to 1.473 breaks SSL certificate authentication
David Gubler updated JENKINS-14414 Going from 1.472 to 1.473 breaks SSL certificate authentication Change By: David Gubler (12/Jul/12 3:33 PM) Summary: Goingfrom1.472to1.473breaks Certificate SSLcertificate authentication 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-14415) 500 when using Google SSO
Julien Duponchelle created JENKINS-14415 500 when using Google SSO Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: openid Created: 12/Jul/12 4:05 PM Description: When i login with google SSO with 1.5 i got this stacktrace: Status Code: 500 Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203) 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:135) 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 winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at
[JIRA] (JENKINS-9216) Make OpenID work with Google Apps accounts
Aaron Stone commented on JENKINS-9216 Make OpenID work with Google Apps accounts Thanks, Kohsuke! This was exactly the OpenId4Java subclass I was hoping would be possible! (Shout out to @autojack for channeling me IRL yesterday on IRC.) I got the hint for this approach from a Ruby gem published by Living Social. The minimum OpenID workaround is encapsulated here: https://github.com/sodabrew/rails-googleapps-auth/blob/master/lib/googleapps_auth.rb#L151-168 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-14159) 404 when trying to see coverage on java code
Mike Bostock commented on JENKINS-14159 404 when trying to see coverage on java code This happens for me also. 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-9216) Make OpenID work with Google Apps accounts
Tony Lampada reopened JENKINS-9216 Make OpenID work with Google Apps accounts Damn it Kohsuke, you resolved it just before I got the chance to make an offer for this issue at FreedomSponsors. I'm taking the liberty of reopening it ONLY to draw your attention for it, hope you don't mind. Here's the offer -- http://www.freedomsponsors.com/core/offer/2/make-openid-work-with-google-apps-accounts Please go there and mark it as resolved and I will gladly pay up - as soon as the fix is available in a release version of Jenkins - (or you can wait a couple of days and maybe someone else will join me as a sponsor, it's up to you, really) Everyone else, just to explain what this is about: I'm a big fan of Jenkins (and Kohsuke's), and I created FreedomSponsors, specifically to make him rich (and maybe other people like him who also deserve it) And this is the very issue that I was looking at, when the whole idea hit me. That was like, 7 weeks ago. Now it's has been up and running for a couple of days. Yes, I have every intention of creating a big positive impact on open source projects like Jenkins. So please feel free to join and spread the word about it. Cheers Tony Lâmpada FreedomSponsors - http://www.freedomsponsors.com Software engineer and CEO, I guess Change By: Tony Lampada (12/Jul/12 5:48 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14087) ScriptTrigger plugin timer issue
amargono commented on JENKINS-14087 ScriptTrigger plugin timer issue Additional Info: In the jenkins UI, some jobs only shows "Polling has not run yet." Those jobs usually run scriptTrigger every 2-4 hours. And many runs at the same time based on timestamp. The timestamp shows the scriptTrigger-polling.log is created but can not be started because there is no content. So it looks timer trigger to start (at least log file is touched) but nothing is able to run. Is that due to too many scriptTrigger so exceed some thread limitation? We have tried to install ver 0.19 and 0.20 but it didn't work either. We notice that 0.13 fixed the open files issue and we will give it a try. Thanks, amargono 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-14416) TFS 2011 PREVIEW Plug in
Boris Martinez created JENKINS-14416 TFS 2011 PREVIEW Plug in Issue Type: New Feature Assignee: Unassigned Components: plugin Created: 12/Jul/12 7:13 PM Description: At the recent BUILD convention in the US, Microsoft announced a series of new Cloud-based services, one in particular being Team Foundation Server. This new product was called TFS 2011 Preview and you can meet all documentation in the following page: http://tfspreview.com/ I am working in a project where we are using TFS PREVIEW as our data repository and i want to work with jenkins as my continues integration server. However jenkins can not connect to the tfs preview 2011 to download the sources using the TFS Plugin. The following is the error: Started by user anonymous Building in workspace C:\Builds Builds $ "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\TF.exe" workspaces -format:brief -server:https://jenkins.tfspreview.com/defaultcollection TF30064: You are not authorized to access the server. FATAL: Executable returned an unexpected result code 100 ERROR: null Finished: FAILURE I think that Jenkins needs an especific Plugin for connecting to the TFS 2011 Preview. How can I solve this? Could you Help me? Project: Jenkins Priority: Major Reporter: Boris Martinez 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-14417) Add Timestamper slicer
Jacob Robertson created JENKINS-14417 Add Timestamper slicer Issue Type: Improvement Assignee: Jacob Robertson Components: configurationslicing Created: 12/Jul/12 7:18 PM Project: Jenkins Priority: Major Reporter: Jacob Robertson 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-14418) deploy artifact to multiple remote environment
Raphael CHAUMIER created JENKINS-14418 deploy artifact to multiple remote environment Issue Type: Task Affects Versions: current Assignee: Raphael CHAUMIER Components: weblogic-deployer Created: 12/Jul/12 7:48 PM Description: It could be possible to deploy an artifact to multiple remote environment. Project: Jenkins Priority: Minor Reporter: Raphael CHAUMIER 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-9216) Make OpenID work with Google Apps accounts
Tony Lampada edited a comment on JENKINS-9216 Make OpenID work with Google Apps accounts Damn it Kohsuke, you resolved it just before I got the chance to make an offer for this issue at FreedomSponsors. I'm taking the liberty of reopening it ONLY to draw your attention for it, hope you don't mind. Here's the offer -- http://www.freedomsponsors.com/core/offer/2/make-openid-work-with-google-apps-accounts Please go there and mark it as resolved and I will gladly pay up - as soon as the fix is available in a release version of Jenkins - (or you can wait a couple of days and maybe someone else will join me as a sponsor, it's up to you, really) Everyone else, just to explain what this is about: I'm a big fan of Jenkins (and Kohsuke's), and I created FreedomSponsors, specifically to make him rich (and maybe other people like him who also deserve it) And this is the very issue that I was looking at, when the whole idea hit me. That was like, 7 weeks ago. Now it has been up and running for a couple of days. Yes, I have every intention of creating a big positive impact on open source projects like Jenkins. So please feel free to join and spread the word about it. Cheers Tony Lâmpada FreedomSponsors - http://www.freedomsponsors.com Software engineer and CEO, I guess 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-9216) Make OpenID work with Google Apps accounts
Kohsuke Kawaguchi resolved JENKINS-9216 as Fixed Make OpenID work with Google Apps accounts Thank you! I just updated that offer and also marking this as closed. Change By: Kohsuke Kawaguchi (12/Jul/12 7:53 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-14419) Error code 403 when trying to rebuild a job from the pipeline view
Avi Saada created JENKINS-14419 Error code 403 when trying to rebuild a job from the pipeline view Issue Type: Bug Affects Versions: current Assignee: ragesh_nair Components: rebuild Created: 12/Jul/12 8:27 PM Description: when clicking on rebuild in the pipeline view we getting the following error: Status Code: 403 Exception: No valid crumb was included in the request Stacktrace: (none) This happens on every job. The jobs are pipelined using the parametrized trigger plugin. Project: Jenkins Priority: Major Reporter: Avi Saada 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-14420) All SSH hosts are changed to be copies of the first SSH host entry after upgrade to 2.0
Aron Sedlack created JENKINS-14420 All SSH hosts are changed to be copies of the first SSH host entry after upgrade to 2.0 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: ssh Created: 12/Jul/12 8:50 PM Description: After upgrading to JIRA 1.474, we upgraded the plugins and version 2.0 of this plugin was available. After installing it, jobs with SSH hosts had their hosts all listed as what was originally the first SSH host entry. Project: Jenkins Labels: jenkins Priority: Major Reporter: Aron Sedlack 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-13835) E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request
Valerie Wagner updated JENKINS-13835 E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request Change By: Valerie Wagner (12/Jul/12 9:04 PM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13835) E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request
Valerie Wagner commented on JENKINS-13835 E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request Using Subversion plugin 1.42. This is another example, as we don't always get the same root cause. The reason this bug is a critical/blocker is because Jenkins does not detect that the update failed, and continues to build the project. If it happens that the project is building successfully, we may not even notice that there is a problem until someone happens to look at the raw output and see this exception. If the build fails, then it triggers in 5 minutes again, tries to build, fails to update, fails to build, spams the team. And repeats again in 5 minutes (as we check for commits every 5 minutes). This results in, for example, dozens of spam emails overnight. The only way we have to fix it is to manually delete the workspace and do a fresh checkout. 14:45:34 org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /svn/desertowl/!svn/vcc/default failed 14:45:34 at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:304) 14:45:34 at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:289) 14:45:34 at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:277) 14:45:34 at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:696) 14:45:34 at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:328) 14:45:34 at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1289) 14:45:34 at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:837) 14:45:34 at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:557) 14:45:34 at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:414) 14:45:34 at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:324) 14:45:34 at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:27) 14:45:34 at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:11) 14:45:34 at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) 14:45:34 at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1221) 14:45:34 at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:292) 14:45:34 at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:315) 14:45:34 at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:295) 14:45:34 at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:391) 14:45:34 at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:136) 14:45:34 at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144) 14:45:34 at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:789) 14:45:34 at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:770) 14:45:34 at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753) 14:45:34 at hudson.FilePath.act(FilePath.java:842) 14:45:34 at hudson.FilePath.act(FilePath.java:824) 14:45:34 at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743) 14:45:34 at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685) 14:45:34 at hudson.model.AbstractProject.checkout(AbstractProject.java:1248) 14:45:34 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589) 14:45:34 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) 14:45:34 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) 14:45:34 at hudson.model.Run.execute(Run.java:1484) 14:45:34 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 14:45:34 at hudson.model.ResourceController.execute(ResourceController.java:88) 14:45:34 at hudson.model.Executor.run(Executor.java:236) 14:45:34 Caused by: svn: E175002: REPORT /svn/desertowl/!svn/vcc/default failed 14:45:34 at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) 14:45:34 at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154) 14:45:34 at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97) 14:45:34 ... 35 more 14:45:34 Caused by:
[JIRA] (JENKINS-14421) Cannot run Xcode instruments command with jenkins mac installer.
dave a created JENKINS-14421 Cannot run Xcode instruments command with jenkins mac installer. Issue Type: Bug Affects Versions: current Assignee: wolfs Components: all-changes Created: 12/Jul/12 10:56 PM Description: Cannot run Xcode "instruments -t path/Automation.tracetemplate path/iPhone.app" command with jenkins mac installer. It seems to fail when running the full instruments command. I used another installer and it works https://github.com/stisti/jenkins-app so it must be the way it is installed with jenkins-1.474.pkg. I've done everything possible. Changing the user/group to user:staff, as well as /Users/Shared/Jenkins, and relaunching with sudo launchctl load -w org.jenkins-ci.plist; sudo launchctl unload -w org.jenkins-ci.plist Currently out of ideas...but this installer does not work well with me. Environment: OSX 10.7.4 Project: Jenkins Priority: Major Reporter: dave a 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-14395) S3 Plugin credentials stored insecurely
mcrooney assigned JENKINS-14395 to Michael Watt S3 Plugin credentials stored insecurely Thanks for the report! I'll assign this to one of the maintainers listed on the Wiki. Change By: mcrooney (13/Jul/12 12:49 AM) Assignee: mcrooney MichaelWatt 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-8563) REOPEN -Can't use parameters in git plugin Branches to build configuration
Lothar Werzinger commented on JENKINS-8563 REOPEN -Cant use parameters in git plugin Branches to build configuration It unfortunately also fails when trying to use a parameter from the Release 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-13990) Polling find old already considered baselines
Bue Petersen resolved JENKINS-13990 as Fixed Polling find old already considered baselines We fixed a threading issues in our libraries, and we made sure polling does not start a new build while an existing build is in queue or building. We have tested with over 100 jobs polling every minute in a master/master setup with 12 executers. Change By: Bue Petersen (13/Jul/12 1:15 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14349) Simple check of configuration and less verbose output
Bue Petersen resolved JENKINS-14349 as Fixed Simple check of configuration and less verbose output We have implemented to levels of check of configuration. The first check is if configuration is loadable in ClearCase. The second level of check is if the configuration added make sense in a context of configuration rotation. Eg. config-rotator does not allow the same component more the once. Polling check the first level, and abort polling if check is not passed. Builds do both checks and fail if not passed. Change By: Bue Petersen (13/Jul/12 1:21 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
