[JIRA] [core] (JENKINS-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Jan Hoppe commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException You should create a thread dump from your vm to enrich this report. Configuration is mentioned in http://devophuman.blogspot.com/2013/04/jenkins-is-going-wild.html. The VisualVM is part of Oracles JDK... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ghprb] (JENKINS-17334) GHPRB fails to use Github server api URL for Github Enterprise
Chris Christensen commented on JENKINS-17334 GHPRB fails to use Github server api URL for Github Enterprise With updates on 1.41 we should be able to use the connectToEnterprise method with either the regular github api or the enterprise api. See: https://github.com/janinko/ghprb/pull/52 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [external-resource-dispatcher] (JENKINS-17469) The External Resources Manager should handle the state changes of the ExternalResource object
SCM/JIRA link daemon resolved JENKINS-17469 as Fixed The External Resources Manager should handle the state changes of the ExternalResource object Change By: SCM/JIRA link daemon (03/May/13 7:16 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [external-resource-dispatcher] (JENKINS-17469) The External Resources Manager should handle the state changes of the ExternalResource object
SCM/JIRA link daemon commented on JENKINS-17469 The External Resources Manager should handle the state changes of the ExternalResource object Code changed in jenkins User: Patrik Johansson Path: src/main/java/com/sonyericsson/jenkins/plugins/externalresource/dispatcher/ExternalResourceQueueTaskDispatcher.java src/main/java/com/sonyericsson/jenkins/plugins/externalresource/dispatcher/ReleaseRunListener.java src/main/java/com/sonyericsson/jenkins/plugins/externalresource/dispatcher/SelectionCriteria.java src/main/java/com/sonyericsson/jenkins/plugins/externalresource/dispatcher/data/ExternalResource.java src/main/java/com/sonyericsson/jenkins/plugins/externalresource/dispatcher/utils/resourcemanagers/DefaultExternalResourceManager.java src/main/java/com/sonyericsson/jenkins/plugins/externalresource/dispatcher/utils/resourcemanagers/ExternalResourceManager.java src/main/java/com/sonyericsson/jenkins/plugins/externalresource/dispatcher/utils/resourcemanagers/NoopExternalResourceManager.java src/main/java/com/sonyericsson/jenkins/plugins/externalresource/dispatcher/utils/resourcemanagers/ResourceMonitorExternalResourceManager.java src/test/java/com/sonyericsson/jenkins/plugins/externalresource/dispatcher/utils/NoopExternalResourceManagerHudsonTest.java src/test/java/com/sonyericsson/jenkins/plugins/externalresource/dispatcher/utils/resourcemanagers/ExternalResourceManagerTest.java http://jenkins-ci.org/commit/external-resource-dispatcher-plugin/b87513b074b74d2cec18945ebe76fb9106faf314 Log: FIXED JENKINS-17469 Clearer separation of concerns Refactoring classses to make the concerns of each class clearer. All state changes of an ExternalResource are now made by the ExternalResourceManager instead of whatever object is requesting the resource. To make this happen, the reserve/lock/release methods have been re-written using the Template Method Pattern, implementing the state change flow in the abstract base class and letting sub-classes continue to implement the inner locking mechanism by calling the abstract method reservation/locking/releasingMechanism(). A sequence diagram of the new plugin flow can be seen here: http://www.websequencediagrams.com/cgi-bin/cdraw?lz=cGFydGljaXBhbnQgRXh0ZXJuYWxSZXNRdWV1ZVRhc2tEaXNwYXRjaGVyCgAfDFNlbGVjdGlvbkNyaXRlcmlhABENUmVsZWFzZVJ1bkxpc3RlbgAuDwBdC291cmNlTWFuYWcAUg9BdmFpbGFiaWxpdHlGaWx0ACQfCgpvcHQgV2hlbiBsb29raW5nIGZvciBleGVjdXRvcgoAgT0eLT4AXRM6IGdldACBGxBzTGlzdChub2RlKQAeNmYAgUcFRW5hYmxlZGFuZACBYQdsZSgAGjdnZXRNYXRjaGluZwCBHAkAKCQAgm4XOiByZXNlcnZlKHIAgxcHAIFcDQCDJAwAMhM6IHNldFIAOwZkKCkKZW5kAIMPC2pvYiBzdGFydHMKAIQvESAtLT4AexgAgQoIKSAgW2lmIG5vdACBHQhkXSAAgQYYIACBURMgOgCBEQ4AcxMAgX4bbG9jawCBXDpMb2NrAIF9F2ZpbmlzaGVzCgCGJhIAgXsaIHIAhl8GKCkAgWoZAIJAEgB-DG51bGwAgxwGs=default This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-17762) Renaming the Clang parsers silently breaks Jenkins configs
Ulli Hafner commented on JENKINS-17762 Renaming the Clang parsers silently breaks Jenkins configs 1. Even though my config.xml had `parserNameApple LLVM Compiler (Clang)/parserName`, the correct parser was still being used after I updated from warnings 4.23 to 4.24. Yes, that is true. 2. The display of "Acu COBOL" on editing my config after updating to warnings 4.24 was a UI-only glitch. Yes. 3. Suppose that, unaware of this issue and running warnings 4.24, I had edited only another aspect of my config (say, the log rotator) and saved the config? Would the parser name have stayed as "Apple LLVM Compiler (Clang)" or would it have been changed to "Acu COBOL"? Just trying to cover all bases. No, then the parser will be changed to the Cobol Compiler. (If you did not manually change the value of the list box). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-17154) CppCheck plugin cannot process result xml from slave node
Balint Kovacs commented on JENKINS-17154 CppCheck plugin cannot process result xml from slave node Now it is working with Jenkins ver. 1.514. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-17154) CppCheck plugin cannot process result xml from slave node
Balint Kovacs closed JENKINS-17154 as Cannot Reproduce CppCheck plugin cannot process result xml from slave node Now it is working with Jenkins ver. 1.514. Change By: Balint Kovacs (03/May/13 7:35 AM) Status: Open Closed Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-16208) TFS SCM Polling: FATAL: Parse error. Unable to find an item within a changeset
david clark commented on JENKINS-16208 TFS SCM Polling: FATAL: Parse error. Unable to find an item within a changeset I am having the same issue, however the commit message is not the issue. Also: The TFS server poller fails forever after a tfs checkin. However, if I manually run the build it will fail once, then work on the next try. Here is the log: Started on May 3, 2013 5:38:07 PM workspace $ /Applications/TEE-CLC-10.0.0/tf history "$/Hotel Search iPhone" -noprompt -version2013-05-03T07:32:40Z~D2013-05-03T07:38:08Z -recursive -format:detailed -server:http://tfs2012:8080/tfs Changeset: 40495 User: AAA\DavidC Date: May 3, 2013 5:37:50 PM Comment: Commit 853906c (Fri May 03 17:37:43 2013 +1000) Author: David Clark david.cl...@hotelscombined.com Committer: David Clark david.cl...@hotelscombined.com - version bump to test CI Items: edit $/Hotel Search iPhone/HCWeb/HCWeb-Info.plist FATAL: Parse error. Unable to find an item within a changeset. Please report this as a bug. Changesetdata = " Changeset: 40495 User: AAA\DavidC Date: May 3, 2013 5:37:50 PM Comment: Commit 853906c (Fri May 03 17:37:43 2013 +1000) Author: David Clark david.cl...@hotelscombined.com Committer: David Clark david.cl...@hotelscombined.com ". null FATAL: Aborted Done. Took 4.1 sec No changes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-16208) TFS SCM Polling: FATAL: Parse error. Unable to find an item within a changeset
david clark edited a comment on JENKINS-16208 TFS SCM Polling: FATAL: Parse error. Unable to find an item within a changeset I am having the same issue, however the commit message is not the problem. Also: The TFS server poller fails forever after a tfs checkin. However, if I manually run the build it will fail once, then work on the next try. Here is the log: Started on May 3, 2013 5:38:07 PM workspace $ /Applications/TEE-CLC-10.0.0/tf history "$/Hotel Search iPhone" -noprompt -version2013-05-03T07:32:40Z~D2013-05-03T07:38:08Z -recursive -format:detailed -server:http://tfs2012:8080/tfs Changeset: 40495 User: AAA\DavidC Date: May 3, 2013 5:37:50 PM Comment: Commit 853906c (Fri May 03 17:37:43 2013 +1000) Author: David Clark david.cl...@hotelscombined.com Committer: David Clark david.cl...@hotelscombined.com - version bump to test CI Items: edit $/Hotel Search iPhone/HCWeb/HCWeb-Info.plist FATAL: Parse error. Unable to find an item within a changeset. Please report this as a bug. Changesetdata = " Changeset: 40495 User: AAA\DavidC Date: May 3, 2013 5:37:50 PM Comment: Commit 853906c (Fri May 03 17:37:43 2013 +1000) Author: David Clark david.cl...@hotelscombined.com Committer: David Clark david.cl...@hotelscombined.com ". null FATAL: Aborted Done. Took 4.1 sec No changes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix] (JENKINS-7773) Matrix sub jobs do not keep n+1 builds, when n is specified.
Christian Wolfgang updated JENKINS-7773 Matrix sub jobs do not keep n+1 builds, when n is specified. This issue has nothing to do with the logging plugin. Change By: Christian Wolfgang (03/May/13 8:35 AM) Labels: logging Component/s: logging This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [htmlpublisher] (JENKINS-17845) missing sidepannel.jelly
Nicolas De Loof created JENKINS-17845 missing sidepannel.jelly Issue Type: Bug Assignee: Nicolas De Loof Components: htmlpublisher Created: 03/May/13 8:50 AM Description: Caused by: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/genesys/cirepository/ci-vm04/hudson/war/WEB-INF/lib/jenkins-core-1.480.3.jar!/hudson/model/DirectoryBrowserSupport/dir.jelly:29:58: st:include No page found 'sidepanel.jelly' for class htmlpublisher.HtmlPublisherTarget$HTMLBuildAction at org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:60) at hudson.model.DirectoryBrowserSupport.serveFile(DirectoryBrowserSupport.java:247) at hudson.model.DirectoryBrowserSupport.generateResponse(DirectoryBrowserSupport.java:108) at htmlpublisher.HtmlPublisherTarget$BaseHTMLAction.doDynamic(HtmlPublisherTarget.java:134) at htmlpublisher.HtmlPublisherTarget$HTMLBuildAction.doDynamic(HtmlPublisherTarget.java:174) 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [htmlpublisher] (JENKINS-17845) missing sidepannel.jelly
SCM/JIRA link daemon commented on JENKINS-17845 missing sidepannel.jelly Code changed in jenkins User: Nicolas De Loof Path: src/main/resources/htmlpublisher/HtmlPublisherTarget/HTMLBuildAction/sidepanel.jelly http://jenkins-ci.org/commit/htmlpublisher-plugin/19afbc3a97ec60b01fd3cfafc76529a8e956cc73 Log: FIXED JENKINS-17845 missing sidepannel.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [htmlpublisher] (JENKINS-17845) missing sidepannel.jelly
SCM/JIRA link daemon resolved JENKINS-17845 as Fixed missing sidepannel.jelly Change By: SCM/JIRA link daemon (03/May/13 8:51 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-cifs] (JENKINS-17846) Rename copy
Markus KARG created JENKINS-17846 Rename copy Issue Type: Improvement Affects Versions: current Assignee: Alex Earl Components: publish-over-cifs Created: 03/May/13 8:55 AM Description: Would be great if one could configure to rename the copy, like: X Rename copy Source: my-file-*.jar Target: some-file.jar Add more Environment: Jenkins 1.512 Project: Jenkins Priority: Major Reporter: Markus KARG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17847) Exception when getting component
Bue Petersen created JENKINS-17847 Exception when getting component Issue Type: Bug Assignee: Praqma Support Components: config-rotator Created: 03/May/13 9:00 AM Description: I get the following error when CR tries to clone: snippet (modified to be anonymous) ConfigRotator Version: 1.1.0 ConfigRotator Configuration from scratch net.praqma.jenkins.configrotator.ConfigurationRotatorException: Unable to get component for http://myrepo:8080/scm/git/project.git, at net.praqma.jenkins.configrotator.scm.git.GitConfiguration.init(GitConfiguration.java:29) at net.praqma.jenkins.configrotator.scm.git.Git$GitPerformer.getInitialConfiguration(Git.java:64) at net.praqma.jenkins.configrotator.scm.git.Git$GitPerformer.getInitialConfiguration(Git.java:56) at net.praqma.jenkins.configrotator.ConfigurationRotator.checkout(ConfigurationRotator.java:153) at hudson.model.AbstractProject.checkout(AbstractProject.java:1325) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1516) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: hudson.util.IOException2: remote file operation failed: /srv/user/.jenkins/workspace/CI-UpgradeScript at hudson.remoting.Channel@1a72772:BuildHostSeven at hudson.FilePath.act(FilePath.java:848) at hudson.FilePath.act(FilePath.java:825) at net.praqma.jenkins.configrotator.scm.git.GitConfiguration.init(GitConfiguration.java:26) ... 11 more Caused by: java.io.IOException: org.eclipse.jgit.api.errors.TransportException: http://myrepo:8080/scm/git/project.git: not authorized at net.praqma.jenkins.configrotator.scm.git.ResolveConfigurationComponent.invoke(ResolveConfigurationComponent.java:117) at net.praqma.jenkins.configrotator.scm.git.ResolveConfigurationComponent.invoke(ResolveConfigurationComponent.java:25) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2309) 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:722) Caused by: org.eclipse.jgit.api.errors.TransportException: http://myrepo:8080/scm/git/project.git: not authorized at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:137) at org.eclipse.jgit.api.CloneCommand.fetch(CloneCommand.java:179) at org.eclipse.jgit.api.CloneCommand.call(CloneCommand.java:125) at net.praqma.jenkins.configrotator.scm.git.ResolveConfigurationComponent.invoke(ResolveConfigurationComponent.java:75) ... 11 more snippet I can login on the build host, and as the user running the jenkins slave manually clone the repository. Two thing are "special": 1) the authentification is read-only, and used git-credentials user@buildhostseven:~$ cat .gitconfig credential helper = store user@buildhostseven:~$ cat .git-credentials http://user:password@myrepo%3a8080 2) Notice the port 8080 Environment: Master + slave, Ubuntu Linux Project: Jenkins Priority: Major Reporter:
[JIRA] [ssh-slaves] (JENKINS-17848) SSH Slaves throw a NoSuchMethodError on SSHAuthenticator.authenticate
Tim Ricketts created JENKINS-17848 SSH Slaves throw a NoSuchMethodError on SSHAuthenticator.authenticate Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ssh-slaves Created: 03/May/13 9:01 AM Description: My Jenkins is on the LTS release. I just upgraded it from 1.480.3 to 1.509.1. Now none of my SSH slaves work. They fail to start and the log contains the following: 05/03/13 09:11:05 SSH Opening SSH connection to ###.local:22. ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins. java.lang.NoSuchMethodError: com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(Lhudson/model/TaskListener;)Z at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:918) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:479) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:222) 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:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) 05/03/13 09:11:05 SSH Connection closed. Environment: RHEL 5.9 Jenkins LTS 1.509.1 Project: Jenkins Priority: Major Reporter: Tim Ricketts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Sergey Grigoriev commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification The body of the email sent by ext-email contains invalid emails. Changes for Build #10770 John Doe _dev@xyz.com_ Fixed JUnit tests This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Sergey Grigoriev edited a comment on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification The body of the email sent by ext-email contains invalid emails. Changes for Build #10770 John Doe _dev@xyz.com_ Fixed JUnit tests However, the Mercurial changeset contain a correct email changeset: 71777:dd8d779c3d30 parent: 71760:76b2fa2dfefb user:John Doe d...@xyz.com date:Thu Apr 18 11:30:02 2013 +0300 summary: Fixed JUnit tests This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Sergey Grigoriev edited a comment on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification The body of the email sent by ext-email contains invalid emails. Changes for Build #10770 John Doe _dev@xyz.com_ Fixed JUnit tests However, the Mercurial changeset contain invalid changelog entries changeset: 71777:dd8d779c3d30 parent: 71760:76b2fa2dfefb user:John Doe d...@xyz.com date:Thu Apr 18 11:30:02 2013 +0300 summary: Fixed JUnit tests This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Sergey Grigoriev edited a comment on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification The body of the email sent by ext-email contains invalid emails. Changes for Build #10770 John Doe _dev@xyz.com_ Fixed JUnit tests However, the Mercurial changeset has a correct email changeset: 71777:dd8d779c3d30 parent: 71760:76b2fa2dfefb user:John Doe d...@xyz.com date:Thu Apr 18 11:30:02 2013 +0300 summary: Fixed JUnit tests This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17849) Collapsing multiple jobs in one project
Markus KARG created JENKINS-17849 Collapsing multiple jobs in one project Issue Type: Improvement Assignee: Unassigned Components: core Created: 03/May/13 9:22 AM Description: According to "The Jenkins Book" it is a good idea to separate different jobs, e. g. to have IT tests running only once a day, but have Unit Tests running after SCM change, etc. In fact this is a good idea, but it results in lots of jobs in the roster. My proposal for improvement would be to make a hierarchic roster which can collapse projects: + MyProject1 + MyProject2 - MyProject3 MyJob1 MyJob2 MyJob3 The default should be "all collapsed", so only project overall status is visiable, and to show up the single jobs of each project only when expanding the tree. Environment: Jenkins 1.512 Project: Jenkins Priority: Major Reporter: Markus KARG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ws-cleanup] (JENKINS-17761) Allow cleanup based on build status
SCM/JIRA link daemon commented on JENKINS-17761 Allow cleanup based on build status Code changed in jenkins User: Kevin Path: src/main/java/hudson/plugins/ws_cleanup/WsCleanup.java src/main/java/hudson/plugins/ws_cleanup/WsCleanupMatrixAggregator.java src/main/resources/hudson/plugins/ws_cleanup/WsCleanup/config.jelly http://jenkins-ci.org/commit/ws-cleanup-plugin/71ee66716f43d046881de857546654a7beea Log: JENKINS-17761 Make ws-cleanup configurable to run or not run on any given build status instead of just 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ws-cleanup] (JENKINS-17761) Allow cleanup based on build status
SCM/JIRA link daemon commented on JENKINS-17761 Allow cleanup based on build status Code changed in jenkins User: Vojtěch Juránek Path: src/main/java/hudson/plugins/ws_cleanup/WsCleanup.java src/main/java/hudson/plugins/ws_cleanup/WsCleanupMatrixAggregator.java src/main/resources/hudson/plugins/ws_cleanup/WsCleanup/config.jelly http://jenkins-ci.org/commit/ws-cleanup-plugin/68011fbe0d56ff68b0bb9dc92a4e5b9235302f1c Log: Merge pull request #7 from Anusien/master Fix JENKINS-17761: configurable based on build status Compare: https://github.com/jenkinsci/ws-cleanup-plugin/compare/ab50a1c8966d...68011fbe0d56 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [timestamper] (JENKINS-16778) Timestamper makes the build fail if the slave if put offline during the build.
Joris De Winne reopened JENKINS-16778 Timestamper makes the build fail if the slave if put offline during the build. I think this is still an issue: When a slave is taken temporary offline, at the end of a build a NullPointer Exception is thrown at src/main/java/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory.java (line 65). String path = request.getPathInfo(); So I think request is null. Change By: Joris De Winne (03/May/13 9:51 AM) 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-17850) Support more than one gerrit-server
Christian Köstlin created JENKINS-17850 Support more than one gerrit-server Issue Type: Bug Assignee: sneha reddy Components: gerrit-trigger Created: 03/May/13 10:27 AM Due Date: 11/Feb/13 12:00 AM Project: Jenkins Priority: Critical Reporter: Christian Köstlin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-17850) Support more than one gerrit-server
Christian Köstlin updated JENKINS-17850 Support more than one gerrit-server Change By: Christian Köstlin (03/May/13 10:28 AM) Issue Type: Bug Improvement Priority: Critical Major Description: Wehavemorethanonegerritserver(oneisaccessibleonlyfromtheintranet,anotheroneisalsoaccessiblefromtheinternet)andwouldliketotriggerbuildsbasedoneventsonbothgerrit-instances. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-cifs] (JENKINS-17846) Rename copy
Alex Earl assigned JENKINS-17846 to Unassigned Rename copy Change By: Alex Earl (03/May/13 11:06 AM) Assignee: AlexEarl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [validating-string-parameter] (JENKINS-16321) An incorrect validating parameter doesn't prevent a post-build step
Khachatur Stepanyan commented on JENKINS-16321 An incorrect validating parameter doesnt prevent a post-build step Please fix this issue, it's really important, it's stops tomcate before validating parameters, it's not a minor one! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [validating-string-parameter] (JENKINS-16321) An incorrect validating parameter doesn't prevent a post-build step
Khachatur Stepanyan updated JENKINS-16321 An incorrect validating parameter doesnt prevent a post-build step Change By: Khachatur Stepanyan (03/May/13 11:15 AM) Priority: Minor Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [update-center] (JENKINS-17029) update-center.json seems to be broken
Andras Milassin commented on JENKINS-17029 update-center.json seems to be broken 1.514 still broken for me on Debian (wheezy). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-17851) Exception with Schedule Maven Release
Markus KARG created JENKINS-17851 Exception with Schedule Maven Release Issue Type: Bug Affects Versions: current Assignee: teilo Components: m2release Created: 03/May/13 11:48 AM Description: Clicked on "Schedule Release" button, got this: Status Code: 500 Exception: java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject Stacktrace: javax.servlet.ServletException: java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) 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:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 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:124) 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:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) 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:67) 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 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at
[JIRA] [weblogic-deployer] (JENKINS-17300) weblogic.Deployer custom arguments
Raphael CHAUMIER started work on JENKINS-17300 weblogic.Deployer custom arguments Change By: Raphael CHAUMIER (03/May/13 1:20 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-17300) weblogic.Deployer custom arguments
Raphael CHAUMIER commented on JENKINS-17300 weblogic.Deployer custom arguments I added a select field to choose stage mode in job advanced options (available from 2.2 version). It's a bit hard to let the user set his own command line because of variables and control realized by the plugin befor performing it. Any idea are welcome. First is to set a simple textbox and provide token variable to place needed element (such as source file so on...) : Very helpful for advanced user who knows well Deployer API but too hard for the other ones. Second : Define different profiles (local deployment, remote deployement ) which format the command line This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-17301) Change JDK used by weblogic.Deployer in Job config
Raphael CHAUMIER closed JENKINS-17301 as Fixed Change JDK used by weblogic.Deployer in Job config Fixed in 2.1 version Change By: Raphael CHAUMIER (03/May/13 1:29 PM) Status: InProgress Closed 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ghprb] (JENKINS-17852) Pull request API information is not fully populated on older versions of the API (enterprise versions could be out of date).
Chris Christensen created JENKINS-17852 Pull request API information is not fully populated on older versions of the API (enterprise versions could be out of date). Issue Type: Bug Assignee: Chris Christensen Components: ghprb Created: 03/May/13 1:47 PM Project: Jenkins Priority: Major Reporter: Chris Christensen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ghprb] (JENKINS-17852) Pull request API information is not fully populated on older versions of the API (enterprise versions could be out of date).
Chris Christensen commented on JENKINS-17852 Pull request API information is not fully populated on older versions of the API (enterprise versions could be out of date). https://github.com/jenkinsci/ghprb-plugin/pull/12 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-17035) Updated wiki
Raphael CHAUMIER resolved JENKINS-17035 as Fixed Updated wiki Change By: Raphael CHAUMIER (03/May/13 1:54 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ghprb] (JENKINS-17852) Pull request API information is not fully populated on older versions of the API (enterprise versions could be out of date).
Chris Christensen edited a comment on JENKINS-17852 Pull request API information is not fully populated on older versions of the API (enterprise versions could be out of date). https://github.com/janinko/ghprb/pull/53 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-3121) Hudson returns http 405 when parameterized option is checked
John Koleszar commented on JENKINS-3121 Hudson returns http 405 when parameterized option is checked Agree, this issue needs to be reopened. Going to /job/x/build doesn't redirect you, it returns a 405, where the content is the parameter entry HTML. The problem is that some reverse proxies will replace this HTML with their own HTML, making the Jenkins UI unreachable. This is generally not configurable other than disabling the behavior entirely, which may not be an option. See ProxyErrorOverride in the Apache docs, for one example. It'd be better to have /job/x/build 302 to a parameter entry page that can be accessed via GET, that then POSTs to the buildWithParameter page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-17853) Populating pending-add members into sandbox results in inconsistent configurations
Martin Bickel created JENKINS-17853 Populating pending-add members into sandbox results in inconsistent configurations Issue Type: Bug Affects Versions: current Assignee: Cletus DSouza Attachments: pending-add.patch Components: integrity-plugin Created: 03/May/13 2:18 PM Description: The Integrity plugin places files into the sandbox that are in state "pending-add". When using transactional changepackages or the changepackage review process, this will often break builds, as the pending files often depend on pending checkins to existing files (for which the Integrity plugin will download the member rev, not the pending rev). Basically, the behavior of downloading pending-add members results in inconsistent configurations. The attached patch will fix this problem. Project: Jenkins Priority: Major Reporter: Martin Bickel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-17854) NTLM v2
Stephen mcGowan created JENKINS-17854 NTLM v2 Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: slave-setup Created: 03/May/13 2:37 PM Description: Cannot get jenkins slave to connect to Windows Server 2008 R2 until i disable NTLM v2 authentication. This presents a security risk and is in breach of our security standards. unsure if there is solution available in later version but could not find a related issue. Thanks, Due Date: 28/Jun/13 12:00 AM Environment: Windows Server 2008 R2 Project: Jenkins Priority: Major Reporter: Stephen mcGowan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17855) TAP Stream results summary page contains links that fail
Alex Newnham created JENKINS-17855 TAP Stream results summary page contains links that fail Issue Type: Bug Affects Versions: current Assignee: Bruno P. Kinoshita Components: tap Created: 03/May/13 3:03 PM Description: The "TAP Test Result" link in Jenkins for the TAP test result summary lists links to a page of links to all the individual TAP test results for. These result links all result in http 404 errors and not the details of the tests. Project: Jenkins Priority: Major Reporter: Alex Newnham This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [msbuild] (JENKINS-5552) MSBuild plugin creates malformed command line
torarvid commented on JENKINS-5552 MSBuild plugin creates malformed command line I have submitted a pull request on GitHub This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-3121) Hudson returns http 405 when parameterized option is checked
John Koleszar reopened JENKINS-3121 Hudson returns http 405 when parameterized option is checked After digging at the source a bit, I think this issue was miscategorized, and is likely not due to the parameterized-trigger plugin. The 405 seems to be coming from one of these views in jenkins-core: core/src/main/resources/hudson/model/ParametersDefinitionProperty/index.jelly core/target/classes/hudson/model/ParametersDefinitionProperty/index.jelly Reopening to change the component. Change By: John Koleszar (03/May/13 3:41 PM) Resolution: WontFix Status: Closed Reopened Assignee: huybrechts JohnKoleszar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17594) incessant jenkins.model.PeepholePermalink updateCache WARNINGS
Dan Lewis edited a comment on JENKINS-17594 incessant jenkins.model.PeepholePermalink updateCache WARNINGS This might be related to issue JENKINS-17681 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17594) incessant jenkins.model.PeepholePermalink updateCache WARNINGS
Dan Lewis commented on JENKINS-17594 incessant jenkins.model.PeepholePermalink updateCache WARNINGS This might be related to issue https://issues.jenkins-ci.org/browse/JENKINS-17681 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-17851) Exception with Schedule Maven Release
teilo commented on JENKINS-17851 Exception with Schedule Maven Release can you ensure you are using the latest release? https://issues.jenkins-ci.org/browse/JENKINS-13465 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-cifs] (JENKINS-17112) Publish over CIFS shares do not persist
Dirk Neuber commented on JENKINS-17112 Publish over CIFS shares do not persist CentOS 6.4 32-bit Jenkins ver. 1.514 Publish Over CIFS 0.2 java version "1.6.0_24" OpenJDK Runtime Environment (IcedTea6 1.11.9) (rhel-1.57.1.11.9.el6_4-i386) OpenJDK Client VM (build 20.0-b12, mixed mode) Publish over FTP 1.9 which we use in almost every configuration is working fine ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-8119) Active Directory Plugin version 1.17 results in org.acegisecurity.BadCredentialsException: Either no such user 'kgraham' or incorrect password, when 1.16 does
wernight reopened JENKINS-8119 Active Directory Plugin version 1.17 results in org.acegisecurity.BadCredentialsException: Either no such user kgraham or incorrect password, when 1.16 does not Same issue after upgrading from 1.2 to 1.4. Note that my LDAP password may have changed in the mean time. Change By: wernight (03/May/13 5:08 PM) Resolution: CannotReproduce 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-8119) Active Directory Plugin version 1.17 results in org.acegisecurity.BadCredentialsException: Either no such user 'kgraham' or incorrect password, when 1.16 does
wernight edited a comment on JENKINS-8119 Active Directory Plugin version 1.17 results in org.acegisecurity.BadCredentialsException: Either no such user kgraham or incorrect password, when 1.16 does not Similar issue after upgrading from 1.2 to 1.4. Note that my LDAP password may have changed in the mean time. org.acegisecurity.BadCredentialsException: Incorrect password for XXX for="" Doe,OU=XX...: error=8007203A; nested exception is com4j.ComException: 8007203a The server is not operational. : The server is not operational. : .\invoke.cpp:517 at hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:109) at hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:30) at org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.loadUserDetails(TokenBasedRememberMeServices.java:308) at org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.autoLogin(TokenBasedRememberMeServices.java:218) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$1.autoLogin(ActiveDirectorySecurityRealm.java:140) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:104) 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:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) 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 winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) 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: com4j.ComException: 8007203a The server is not operational. : The server is not operational. : .\invoke.cpp:517 at com4j.Wrapper.invoke(Wrapper.java:166) at $Proxy43.openDSObject(Unknown Source) at hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:101) ... 35 more Caused by: com4j.ComException: 8007203a The server is not operational. : The server is not operational. : .\invoke.cpp:517 at com4j.Native.invoke(Native Method) at com4j.StandardComMethod.invoke(StandardComMethod.java:35) at com4j.Wrapper$InvocationThunk.call(Wrapper.java:340) at com4j.Task.invoke(Task.java:51) at com4j.ComThread.run0(ComThread.java:153) at com4j.ComThread.run(ComThread.java:134)
[JIRA] [active-directory] (JENKINS-17676) ADSI mode auth no longer working after update to AD plugin v 1.31
kalpesh soni commented on JENKINS-17676 ADSI mode auth no longer working after update to AD plugin v 1.31 https://github.com/jenkinsci/active-directory-plugin/commits/master oh no kohsuke you didnt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17676) ADSI mode auth no longer working after update to AD plugin v 1.31
kalpesh soni assigned JENKINS-17676 to Kohsuke Kawaguchi ADSI mode auth no longer working after update to AD plugin v 1.31 Change By: kalpesh soni (03/May/13 5:39 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-8119) Active Directory Plugin version 1.17 results in org.acegisecurity.BadCredentialsException: Either no such user 'kgraham' or incorrect password, when 1.16 does
wernight edited a comment on JENKINS-8119 Active Directory Plugin version 1.17 results in org.acegisecurity.BadCredentialsException: Either no such user kgraham or incorrect password, when 1.16 does not Similar issue after upgrading from 1.30 to 1.32. Note that my LDAP password may have changed in the mean time. org.acegisecurity.BadCredentialsException: Incorrect password for XXX for=CN=John Doe,OU=XX...: error=8007203A; nested exception is com4j.ComException: 8007203a The server is not operational. : The server is not operational. : .\invoke.cpp:517 at hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:109) at hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:30) at org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.loadUserDetails(TokenBasedRememberMeServices.java:308) at org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.autoLogin(TokenBasedRememberMeServices.java:218) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$1.autoLogin(ActiveDirectorySecurityRealm.java:140) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:104) 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:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) 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 winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) 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: com4j.ComException: 8007203a The server is not operational. : The server is not operational. : .\invoke.cpp:517 at com4j.Wrapper.invoke(Wrapper.java:166) at $Proxy43.openDSObject(Unknown Source) at hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:101) ... 35 more Caused by: com4j.ComException: 8007203a The server is not operational. : The server is not operational. : .\invoke.cpp:517 at com4j.Native.invoke(Native Method) at com4j.StandardComMethod.invoke(StandardComMethod.java:35) at com4j.Wrapper$InvocationThunk.call(Wrapper.java:340) at com4j.Task.invoke(Task.java:51) at com4j.ComThread.run0(ComThread.java:153) at com4j.ComThread.run(ComThread.java:134) Note that deleting my cookies allows me to see the page but then the login just says invalid
[JIRA] [m2release] (JENKINS-17851) Exception with Schedule Maven Release
Markus KARG closed JENKINS-17851 as Fixed Exception with Schedule Maven Release Indeed the installed plugin was outdated. Updating solved the issue. Thanks! -Markus Change By: Markus KARG (03/May/13 5:54 PM) Status: Open Closed 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-17856) Cannot find svn
Markus KARG created JENKINS-17856 Cannot find svn Issue Type: Bug Affects Versions: current Assignee: teilo Components: m2release Created: 03/May/13 5:58 PM Description: Issued a try run. Jenkins checks SVN and says there are no differences, then runs Maven. After Maven is finished, there is a stack trace: ... Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to check for local modifications Provider message: The svn command failed. Command output: /bin/sh: svn: not found at org.apache.maven.shared.release.phase.ScmCheckModificationsPhase.execute(ScmCheckModificationsPhase.java:109) at org.apache.maven.shared.release.phase.ScmCheckModificationsPhase.simulate(ScmCheckModificationsPhase.java:154) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:199) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:140) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:103) at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:211) ... 30 more The funny thing is that Jenkins can use svn, but Maven cannot? Strange! Environment: Jenkins 1.512 / JDK 1.7 / Debian 6 / x86 Project: Jenkins Priority: Blocker Reporter: Markus KARG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-17856) Cannot find svn
teilo resolved JENKINS-17856 as Not A Defect Cannot find svn Jenkins does not use the svn command, but rather it has inbuilt Java code. The release is performed by maven, so access is required to tools required by maven. Change By: teilo (03/May/13 6:52 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-17857) Portlets show times/dates using system time, instead of Jenkins time
owenmehegan created JENKINS-17857 Portlets show times/dates using system time, instead of Jenkins time Issue Type: Bug Affects Versions: current Assignee: Peter Hayes Attachments: Screen shot 2013-05-03 at 12.09.19 PM.png Components: dashboard-view Created: 03/May/13 7:10 PM Description: My Jenkins system clock is set to GMT. In order to display build timestamps using local time, I invoke Jenkins like this: 'java -Dorg.apache.commons.jelly.tags.fmt.timeZone=America/Los_Angeles -jar jenkins.war' In all my regular builds, and at the bottom of every page in the 'Page generated' field, I see the local time. But in the dashboard portlet view, I see the system/GMT time. See attachment for an example - that build was run at 11:53am local time. Environment: Linux Project: Jenkins Priority: Minor Reporter: owenmehegan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17797) x-unit option not to fail if there isn't a test results file
Gregory Boissinot resolved JENKINS-17797 as Fixed x-unit option not to fail if there isnt a test results file Change By: Gregory Boissinot (03/May/13 7:33 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [msbuild] (JENKINS-5552) MSBuild plugin creates malformed command line
Gregory Boissinot resolved JENKINS-5552 as Fixed MSBuild plugin creates malformed command line Change By: Gregory Boissinot (03/May/13 7:52 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copy-to-slave] (JENKINS-16818) Copying of file back to master sometimes fails but subsequent build steps still happen
owenmehegan assigned JENKINS-16818 to Romain Seguy Copying of file back to master sometimes fails but subsequent build steps still happen Assigning to Romain since he seems to be the current maintainer, maybe. Any thoughts? Change By: owenmehegan (03/May/13 8:27 PM) Assignee: DanielPetisme RomainSeguy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-17857) Portlets show times/dates using system time, instead of Jenkins time
owenmehegan resolved JENKINS-17857 as Duplicate Portlets show times/dates using system time, instead of Jenkins time Duplicate of JENKINS-15161, my own bug! Change By: owenmehegan (03/May/13 8:30 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [environment-script] (JENKINS-14887) Script errors produce obtuse error, no stderr/stdout log
owenmehegan resolved JENKINS-14887 as Not A Defect Script errors produce obtuse error, no stderr/stdout log Just user error. Turns out that if you redirect stderr to /dev/null you won't see it in a log Change By: owenmehegan (03/May/13 8:38 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [environment-script] (JENKINS-14794) Console output parsing for env vars is a little too loose
owenmehegan resolved JENKINS-14794 as Not A Defect Console output parsing for env vars is a little too loose Makes sense, thanks! Change By: owenmehegan (03/May/13 8:41 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-9671) NODE_NAME not defined for master node
owenmehegan resolved JENKINS-9671 as Fixed NODE_NAME not defined for master node I don't know when this was fixed, but it's working now in 1.514 on Linux. Change By: owenmehegan (03/May/13 8:47 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
SCM/JIRA link daemon commented on JENKINS-17566 Severe polling error when using script trigger Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/scripttrigger/ScriptTriggerExecutor.java src/main/java/org/jenkinsci/plugins/scripttrigger/groovy/GroovyScriptTrigger.java http://jenkins-ci.org/commit/scripttrigger-plugin/2a270bb56f2be489b2729229c7d66a41b2e5c14a Log: Add check if node is offline - Try to fix JENKINS-17566 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
Gregory Boissinot resolved JENKINS-17566 as Fixed Severe polling error when using script trigger Change By: Gregory Boissinot (03/May/13 9:03 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-8783) Renamin promotion process doesn't remove the original promotion process
owenmehegan resolved JENKINS-8783 as Fixed Renamin promotion process doesnt remove the original promotion process Definitely fixed at least in version 2.10 of the plugin. Change By: owenmehegan (03/May/13 9:18 PM) 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clone-workspace] (JENKINS-8730) Changes to Criteria for build to be archived are never saved
owenmehegan resolved JENKINS-8730 as Fixed Changes to Criteria for build to be archived are never saved Confirmed this is fixed in version 0.5 of the plugin. Change By: owenmehegan (03/May/13 9:45 PM) 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameters] (JENKINS-6682) Dynamic Parameterized Build choices based on Shell command
owenmehegan commented on JENKINS-6682 Dynamic Parameterized Build choices based on Shell command I think you can do this with the Dynamic Parameter plugin. https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Dynamic+Parameter+Plug-in This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-11983) Allow users to manually define job relationships to (in my case) prevent concurrent builds
owenmehegan commented on JENKINS-11983 Allow users to manually define job relationships to (in my case) prevent concurrent builds You can do this with the Throttle Concurrent Builds plugin. Install that, go to the master Jenkins configuration page and create a category in Multi-Project Throttle Categories which specifies 1 for the maximum total number of concurrent builds. Then go to the configuration of your heavy builds, check Throttle Concurrent Builds, then check the box for the throttle category you created. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-8726) Allow users to manually define upstream/downstream relationships
owenmehegan resolved JENKINS-8726 as Not A Defect Allow users to manually define upstream/downstream relationships A combination of the Parameterized Trigger plugin (use a 'Trigger/Call builds on other projects' build step and choose 'Block until the triggered jobs finish their builds') and the Conditional BuildStep plugin (wrap the downstream build trigger in an 'if' statement that checks my job parameters) provides a good solution to this problem. Change By: owenmehegan (03/May/13 10:23 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17824) Error when upgrading from version 1.30: com4j.ComException:The server is not operational.
Matt Kraai resolved JENKINS-17824 as Duplicate Error when upgrading from version 1.30: com4j.ComException:The server is not operational. Change By: Matt Kraai (03/May/13 10:42 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-17762) Renaming the Clang parsers silently breaks Jenkins configs
Richard Buckle commented on JENKINS-17762 Renaming the Clang parsers silently breaks Jenkins configs Thanks again Ulli. I shall update my blog post to reflect this information. Regards, Richard. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [flexible-publish] (JENKINS-14475) Conditional build steps should be available as post-build actions
owenmehegan commented on JENKINS-14475 Conditional build steps should be available as post-build actions What happened to the flexible publish plugin? I can't find it in the plugin manager anymore, though the wiki page is still there. It looks like installations abruptly stopped in March. Did it get replaced with something? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [flexible-publish] (JENKINS-14475) Conditional build steps should be available as post-build actions
owenmehegan commented on JENKINS-14475 Conditional build steps should be available as post-build actions And I can't see anything in the current version of parameterized trigger that gets me what I want. To go back to the original bug request: I want to be able to use conditional build steps in a post-build action. Specifically, I want to be able to say: if $some_build_param = "true" trigger a downstream build with parameters end I need this as a post-build action, in matrix builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-12629) Using jenkins-cli connecting to HTTPS port fails due to hostname mismatch in certificate
Matt Certain reopened JENKINS-12629 Using jenkins-cli connecting to HTTPS port fails due to hostname mismatch in certificate This issue does not seem to be completely fixed. Here's the output I see when trying to use this fix. Skipping HTTPS certificate checks altogether. Note that this is not secure at all. Exception in thread "main" java.io.IOException: Failed to connect to https://REMOVED/ at hudson.cli.CLI.getCliTcpPort(CLI.java:274) at hudson.cli.CLI.init(CLI.java:134) at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) at hudson.cli.CLI._main(CLI.java:469) at hudson.cli.CLI.main(CLI.java:384) Suppressed: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No X509TrustManager implementation available at sun.security.ssl.Alerts.getSSLException(Unknown Source) at sun.security.ssl.SSLSocketImpl.fatal(Unknown Source) at sun.security.ssl.Handshaker.fatalSE(Unknown Source) at sun.security.ssl.Handshaker.fatalSE(Unknown Source) at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source) at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source) at sun.security.ssl.Handshaker.processLoop(Unknown Source) at sun.security.ssl.Handshaker.process_record(Unknown Source) at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source) at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source) at hudson.cli.FullDuplexHttpStream.init(FullDuplexHttpStream.java:77) at hudson.cli.CLI.connectViaHttp(CLI.java:164) at hudson.cli.CLI.init(CLI.java:138) ... 3 more Caused by: java.security.cert.CertificateException: No X509TrustManager implementation available at sun.security.ssl.DummyX509TrustManager.checkServerTrusted(Unknown Source) ... 18 more Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No X509TrustManager implementation available at sun.security.ssl.Alerts.getSSLException(Unknown Source) at sun.security.ssl.SSLSocketImpl.fatal(Unknown Source) at sun.security.ssl.Handshaker.fatalSE(Unknown Source) at sun.security.ssl.Handshaker.fatalSE(Unknown Source) at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source) at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source) at sun.security.ssl.Handshaker.processLoop(Unknown Source) at sun.security.ssl.Handshaker.process_record(Unknown Source) at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source) at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source) at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(Unknown Source) at hudson.cli.CLI.getCliTcpPort(CLI.java:272) ... 4 more Caused by: java.security.cert.CertificateException: No X509TrustManager implementation available at sun.security.ssl.DummyX509TrustManager.checkServerTrusted(Unknown Source) ... 16 more Change By: Matt Certain (04/May/13 1:58 AM) Resolution: Fixed
[JIRA] [tfs] (JENKINS-3002) TFS Support to get labels
Vinicius Kopcheski commented on JENKINS-3002 TFS Support to get labels Code avaliable at: http://github.com/kopcheski/tfs-plugin Pull request created. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
