[JIRA] [export-params] (JENKINS-23849) Relative path "/../" in "File path" are ignored
rin_ne closed JENKINS-23849 as Fixed Relative path "/../" in "File path" are ignored Change By: rin_ne (29/Jul/14 6:59 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [export-params] (JENKINS-23849) Relative path "/../" in "File path" are ignored
rin_ne resolved JENKINS-23849 as Fixed Relative path "/../" in "File path" are ignored Change By: rin_ne (29/Jul/14 6:58 AM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [rqm] (JENKINS-23618) Update plugin description (case 11541)
Mads Nielsen resolved JENKINS-23618 as Fixed Update plugin description (case 11541) Change By: Mads Nielsen (29/Jul/14 8:17 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/d/optout.
[JIRA] [email-ext] (JENKINS-16181) Jenkins does not try to resend a failed e-mail
Alexander Ost reopened JENKINS-16181 Jenkins does not try to resend a failed e-mail Apparently, retry handling for the "connetion refused" case does not yet work properly. I do observe the following stack trace whenever the SMTP server is unreachable: javax.mail.MessagingException: Could not connect to SMTP host: mail.example.net, port: 25; nested exception is: java.net.ConnectException: Connection refused at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1934) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:638) at javax.mail.Service.connect(Service.java:295) at javax.mail.Service.connect(Service.java:176) at javax.mail.Service.connect(Service.java:125) at javax.mail.Transport.send0(Transport.java:194) at javax.mail.Transport.send(Transport.java:124) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:305) ...but I can never see a "Socket error sending email, retrying once more in 10 seconds" message. I suspect that the root cause is that Transport.send() will not throw a SendFailedException in this case, but rather a MessagingException. However, the plugin code only catches SendFailedException. (Tested with version email-ext-2.37.2.2, but exception type handling is identical on master.) Could you please check? Change By: Alexander Ost (29/Jul/14 8:42 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/d/optout.
[JIRA] [bitbucket] (JENKINS-22724) Git merge before build does not work with bitbucket SCM trigger
Loren Lang commented on JENKINS-22724 Git merge before build does not work with bitbucket SCM trigger I just ran into this bug myself, although not with bitbucket. It comes down to how the notifyCommit hook handles receiving a sha1 hash parameter. It actually triggers a build solely for the provided commit referenced in the sha1 parameter passed to notifyCommit instead of attempting to merge that commit into the integration branch. The workaround is to not send the sha1 parameter if possible. I'd like to see this fixed, but I expect it's more deeply ingrained in how the merging strategy works. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [jenkinswalldisplay] (JENKINS-23620) The periodic refresh shows "loading jobs.."
Lars Hagström commented on JENKINS-23620 The periodic refresh shows "loading jobs.." I have an suggestion as to what the problem could be: My jenkins server is quite heavily loaded most of the time, and the API calls in getJenkinsApi (where updateRunning[viewName] is set) may take quite a long time. This causes the "loading jobs..." message to be displayed. You can check what it looks like on our jenkins server at https://projekt.consoden.se/safir//plugin/jenkinswalldisplay/walldisplay.html?viewName=Default&jenkinsUrl=https%3A%2F%2Fprojekt.consoden.se%2Fsafir%2F This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [jenkinswalldisplay] (JENKINS-23620) The periodic refresh shows "loading jobs.."
Lars Hagström commented on JENKINS-23620 The periodic refresh shows "loading jobs.." Hmm, I've just had a vague flashback. It might be that I've previously gone in and commented out the "Loading jobs..." line in walldisplay.js... So it might be that the issue was introduced earlier than indicated above. Anyway, the issue goes away if I comment out that line in the current version. But I've left it in on my server so that you'll be able to see the issue. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
Laszlo Papp commented on JENKINS-6817 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel Same issue her with 1.567: NOTE: recipe attr-native-2.4.46-r4: task do_configure: Succeeded FATAL: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:739) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168) at com.sun.proxy.$Proxy70.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:951) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1710) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Caused by: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:802) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:951) at hudson.remoting.Channel$2.handle(Channel.java:475) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: hudson.remoting.Channel$OrderlyShutdown ... 3 more Caused by: Command close created at at hudson.remoting.Command.(Command.java:56) at hudson.remoting.Channel$CloseCommand.(Channel.java:945) at hudson.remoting.Channel$CloseCommand.(Channel.java:943) at hudson.remoting.Channel.close(Channel.java:1026) at hudson.remoting.Channel.close(Channel.java:1009) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:950) ... 2 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [gui] (JENKINS-24013) Using buildnamesetter plugin causes layout issues
Arnt Witteveen created JENKINS-24013 Using buildnamesetter plugin causes layout issues Issue Type: Bug Assignee: Unassigned Components: gui Created: 29/Jul/14 9:57 AM Description: When using the build name setter plugin to set build names to something more than #number, the build history in the left column will overlap the page content in many places, e.g. in job//configure. The same thing happens on the 'project page' job/ if that has a bit of content (e.g with a long list of artefacts). Environment: Firefox 29.0, Jenkins 1.572 Project: Jenkins Priority: Minor Reporter: Arnt Witteveen This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-23872) Jenkins users disappeared!
stephenconnolly commented on JENKINS-23872 Jenkins users disappeared! Just an update. You should only have to change the filenames to lowercase: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/model/IdStrategy.java#L144 I am seeing if I can add some migration mechanism This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [gui] (JENKINS-24013) Using buildnamesetter plugin causes layout issues
Arnt Witteveen updated JENKINS-24013 Using buildnamesetter plugin causes layout issues Change By: Arnt Witteveen (29/Jul/14 10:02 AM) Attachment: OverlapJenkins.PNG Description: When using the build name setter plugin to set build names to something more than #number, the build history in the left column will overlap the page content in many places, e.g. in job//configure.The same thing happens on the 'project page' job/ if that has a bit of content (e.g with a long list of artefacts). I've added a small screenshot.I noticed the overlap depends on the witdh of the browser window (very narrow window: everything is ok because everything goes below the build history, very wide window: everything is ok because it fits, in between those 2 you can see the issue). This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [gui] (JENKINS-24013) Using buildnamesetter plugin causes layout issues
Arnt Witteveen commented on JENKINS-24013 Using buildnamesetter plugin causes layout issues Looking though some more open issues, I think JENKINS-13266 may be reporting the same issue. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [gui] (JENKINS-24013) Using buildnamesetter plugin causes layout issues
Arnt Witteveen edited a comment on JENKINS-24013 Using buildnamesetter plugin causes layout issues Looking though some more open issues, I think JENKINS-13266, JENKINS-23829 may be reporting the same issue. Sorry for the possible duplication. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout
Fabrice Robin commented on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout Hi, We also have the same issue. And we also need the svnexternals fix from 2.4... Reece Johnston: I am interested in your build. Could you please share your hpi with us ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout
Fabrice Robin edited a comment on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout Hi, We also have the same issue. And we also need the svnexternals fix from 2.4... Reece Johnston : I am interested in your build. Could you please share your hpi with us ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [core] (JENKINS-23872) Jenkins users disappeared!
SCM/JIRA link daemon commented on JENKINS-23872 Jenkins users disappeared! Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/model/User.java http://jenkins-ci.org/commit/jenkins/46c58c52256c16dff076b92a97290f3930e3d49c Log: [FIXED JENKINS-23872] Jenkins users disappeared! Added migration logic to move the config files This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-23872) Jenkins users disappeared!
SCM/JIRA link daemon resolved JENKINS-23872 as Fixed Jenkins users disappeared! Change By: SCM/JIRA link daemon (29/Jul/14 10:18 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/d/optout.
[JIRA] [core] (JENKINS-23872) Jenkins users disappeared!
e. cresta commented on JENKINS-23872 Jenkins users disappeared! It' not enough to change filename. It is necessary to change all entries in config.xml for all users from uppercase to lowercase. For now I'll not upgrade Jenkins until the problem will be resolved This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [gui] (JENKINS-24013) Using buildnamesetter plugin causes layout issues
Daniel Beck resolved JENKINS-24013 as Duplicate Using buildnamesetter plugin causes layout issues Duplicates JENKINS-23829 Change By: Daniel Beck (29/Jul/14 11:14 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [ui-changes] (JENKINS-13266) In fluid layout, side-panel may overflow into main-panel
Daniel Beck resolved JENKINS-13266 as Duplicate In fluid layout, side-panel may overflow into main-panel 1.572 has a new layout, and JENKINS-23829 is the issue for that implementation's identical problem, so resolving as duplicate. Change By: Daniel Beck (29/Jul/14 11:16 AM) Status: In Progress 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/d/optout.
[JIRA] [testng] (JENKINS-19217) Change class names to not contain package names on result pages (increases readability)
Paul Danyliuk commented on JENKINS-19217 Change class names to not contain package names on result pages (increases readability) @Nalin, thank you! This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22186) ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
Mark Waite closed JENKINS-22186 as Fixed ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. Change By: Mark Waite (29/Jul/14 11:28 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [core] (JENKINS-23872) Jenkins users disappeared!
dogfood commented on JENKINS-23872 Jenkins users disappeared! Integrated in jenkins_main_trunk #3562 [FIXED JENKINS-23872] Jenkins users disappeared! (Revision 46c58c52256c16dff076b92a97290f3930e3d49c) Result = SUCCESS Stephen Connolly : 46c58c52256c16dff076b92a97290f3930e3d49c Files : core/src/main/java/hudson/model/User.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [associated-files] (JENKINS-18818) Jenkins can't launch a C++ application which uses commandes from Tekvisa Library
David Boyce commented on JENKINS-18818 Jenkins can't launch a C++ application which uses commandes from Tekvisa Library This is likely to be due to a difference in the PATH variable for Jenkins compared to your local user account. You can examine this by running "set PATH" as a command in the two environments. See also http://msdn.microsoft.com/en-us/library/7d83bc18.aspx "Search Path Used by Windows to Locate a DLL" This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-24014) Jenkins wrongly(?) warns that "reverse proxy set up is broken" when using autorefresh link.
Arnt Witteveen created JENKINS-24014 Jenkins wrongly(?) warns that "reverse proxy set up is broken" when using autorefresh link. Issue Type: Bug Assignee: Unassigned Components: core Created: 29/Jul/14 11:49 AM Description: When I go to /manage, there is no warning. When I click "ENABLE AUTO REFRESH" (or "disable .." if it was on already), the page suddenly shows a big red warning "It appears that your reverse proxy set up is broken." I haven't set up any reverse proxy, so this seems wrong. I think Jenkins is confused by the parameter in the url formed: /manage?auto_refresh=false. Using the network trace in firefox shows the response header's location is set to: http://XXX:8080/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testForReverseProxySetup/http%3A%2F%2FXXX%3A8080%2Fmanage%3Fauto_refresh=false/ for a request to: http://XXX:8080/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test which had a referrer of http://XXX:8080/manage?auto_refresh=false (I cannot determine from the description if JENKINS-23280 has the same cause, if so, it wasn't detected or described there.) Environment: Jenkins 1.572 (not under any form of reverse proxy, simply set up with the installer, not using tomcat/apache/..), firefox 29.0 Project: Jenkins Labels: user-experience Priority: Minor Reporter: Arnt Witteveen This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [build-name-setter] (JENKINS-24015) Job overview becomes unreadable with long(er) names in build history
Koen Franken created JENKINS-24015 Job overview becomes unreadable with long(er) names in build history Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Attachments: 29-7-2014 13-52-11.png Components: build-name-setter Created: 29/Jul/14 12:06 PM Description: When using build-name-setter, the Build History pane will start overlapping the main section when names get longer. This effectively makes the main section unreadable (as shown in attachment). Environment: Running Jenkins 1.574 on Ubuntu 12.04.4 LTS (installed and updated using apt-get) and using browsers Firefox 24.7.0 & IE 11.0.10. Project: Jenkins Labels: gui Priority: Minor Reporter: Koen Franken This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
Christian Galsterer commented on JENKINS-23693 Cannot delete workspace We have the same problem on RHEL/CentOS and there is no external delete command defined. The config.xml has an empty element. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-24014) Jenkins wrongly(?) warns that "reverse proxy set up is broken" when using autorefresh link.
Daniel Beck commented on JENKINS-24014 Jenkins wrongly(?) warns that "reverse proxy set up is broken" when using autorefresh link. This is what's expected https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/diagnosis/ReverseProxySetupMonitor.java#L75 But the parameter passed to the method contains the query string, resulting in a mismatch. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [crowd2] (JENKINS-23208) Backtrace when trying to use 'remember me' with latest crowd auth plugin
Kanstantsin Shautsou commented on JENKINS-23208 Backtrace when trying to use 'remember me' with latest crowd auth plugin And please try this https://jenkins.ci.cloudbees.com/job/plugins/job/crowd2-plugin/17/org.jenkins-ci.plugins$crowd2/artifact/org.jenkins-ci.plugins/crowd2/1.8-SNAPSHOT/crowd2-1.8-SNAPSHOT.hpi i added fast patch but have no time to check it... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Frédéric Camblor commented on JENKINS-22820 Changes are not commited when using a recent git client Hi there ! It seems Emmanuel was right. First, there seems to have a "simple" workaround described here (setting LANG to en_US.UTF-8) @Brice did you try to use maven-scm-provider-gitexe v1.9 (or above) as stated here ? If this confirm the resolution, I'll align on this version of the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Brice Jaglin edited a comment on JENKINS-22820 Changes are not commited when using a recent git client Great news! About the gitexe bump: I had only tried to upgrade the project dependency (which didn't help), not to force the dependency of the maven-release-plugin plugin, so I can't tell whether that would solve the problem. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Brice Jaglin commented on JENKINS-22820 Changes are not commited when using a recent git client Great news! About the gitexe bump: I had only tried to upgrade the project dependency (which didn't help), not to force the dependency of the maven-release-plugin plugin, so I can't tell whether what that would solve the problem. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [tfs] (JENKINS-24016) TFS_CHANGE_SET is not always correctly set for executing build steps.
Karl-Heinz Marbaise
created JENKINS-24016
TFS_CHANGE_SET is not always correctly set for executing build steps.
Issue Type:
Bug
Affects Versions:
current
Assignee:
redsolo
Components:
tfs
Created:
29/Jul/14 1:55 PM
Description:
Configured TFS Plugin to use update only
Build Step 1: Execute Shell (Print out TFS_CHANGESET)
Build Step 2: Execute Maven Build (Maven 3.1.1)
Build Step 3: Execute Shell (rolling_label.sh ${WORKSPACE} ${BUILD_NUMBER} ${TFS_CHANGESET})
The execution build step Nr. 3 fails from time to time by the cause that the TFS_CHANGESET variable has not been set which can't be cause within the build step 1 it will be correctly printed out to the jenkins console.
The following is the output in case of a failure:
[portal-HEAD] $ /usr/bin/bash -xe /temp/hudson1539801749356572417.sh
+ /build/label.sh /opt/build/x-HEAD 4855
The following is the output in case of success:
[Current build status] check if current [SUCCESS] is worse or equals then [SUCCESS] and better or equals then [SUCCESS]
Run condition [Current build status] enabling perform for step [Execute shell]
[-HEAD] $ /usr/bin/bash -xe /temp/hudson3621978596655594520.sh
[WARNINGS] Parsing warnings in console log with parser Maven
Email was triggered for: Success
which shows that only the TFS_CHANGESET is not being set.
Environment:
Currently running a build in Jenkins (1.546) using the TFS Plugin 3.1.1.
Project:
Jenkins
Priority:
Blocker
Reporter:
Karl-Heinz Marbaise
This message is automatically generated by JIRA.
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/d/optout.
[JIRA] [core] (JENKINS-23829) Layout: Job history may overlap main job status
Tom FENNELLY commented on JENKINS-23829 Layout: Job history may overlap main job status I tested https://github.com/jenkinsci/jenkins/pull/1321 with long job names and descriptions and it a lot works better IMO. So hopefully we'll have a resolution for this issue soon. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-23829) Layout: Job history may overlap main job status
Tom FENNELLY edited a comment on JENKINS-23829 Layout: Job history may overlap main job status I tested https://github.com/jenkinsci/jenkins/pull/1321 with long job names and descriptions and it's a lot works better IMO. So hopefully we'll have a resolution for this issue soon. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [git] (JENKINS-21309) Git plugins changes URL for Bitbucket is incorrect
John Dyer commented on JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect It's not just this job, its every job, and they are all created differently. Most are standard "free-style software project" and many are maven style. Here is the config.xml from one of them "maven-plugin@2.3"> Tropo intergrated gateway for TropoNG
Owned by Sean Guo "hudson.tasks.LogRotator"> -1 20 -1 -1 false hudson.model.Item.Configure:sguo hudson.model.Item.Configure:automation hudson.model.Item.Discover:sguo hudson.model.Run.Update:sguo hudson.model.Item.Build:sguo hudson.model.Item.Build:automation hudson.model.Item.Read:sguo hudson.model.Item.Read:automation hudson.scm.SCM.Tag:sguo hudson.model.Run.Delete:sguo hudson.model.Item.Delete:sguo hudson.model.Item.Cancel:sguo hudson.model.Item.Workspace:sguo hudson.model.Item.Workspace:automation "hipchat@0.1.4"> false "notification@1.5"> HTTP JSON xx "throttle-concurrents@1.8.2"> 1 1 true project "disk-usage@0.23"/> "hudson.plugins.git.GitSCM" plugin="git@2.2.1"> 2 g...@bitbucket.org:/xxx.git master false "list"/> 64medium.centos.berkshelf3 false false false false (默认) xx-xx false com.x.x x-gateway clean package Maven 3.1.1 true false false false false false false -1 false false "jenkins.mvn.DefaultSettingsProvider"/> "jenkins.mvn.DefaultGlobalSettingsProvider"/> engineering-...@xx.com false false true xxx-gateway-assemble/target/*.zip,xxx-gateway-assemble/target/*.tar.gz false false maven.voxeolabs.net http://x:8081/nexus/content/repositories/snapshots/ true false "hipchat@0.1.4"> xxx xx cd ./cookbook/xxx-gateway/ export KITCHEN_YAML=./.kitchen_jenkins.yml kitchen test knife cookbook upload xxx-gateway -o ../../cookbook SUCCESS 0 BLUE true This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [build-name-setter] (JENKINS-24015) Job overview becomes unreadable with long(er) names in build history
Daniel Beck resolved JENKINS-24015 as Duplicate Job overview becomes unreadable with long(er) names in build history Duplicates JENKINS-24013. Has nothing to do with build name setter plugin, happens with manually set build names (or even build badges) as well. Change By: Daniel Beck (29/Jul/14 2:08 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/d/optout.
[JIRA] [plugin] (JENKINS-23626) Implement "cancel all" action for the Build Queue (like Hudson version 2.2.1)
Jonathan Grant commented on JENKINS-23626 Implement "cancel all" action for the Build Queue (like Hudson version 2.2.1) I stopped after 20 mins after trying to satisfy all the Maven install requirements. Can you put together a step by step guide and an installer EXE for me to run? This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [tfs] (JENKINS-24016) TFS_CHANGE_SET is not always correctly set for executing build steps.
Karl-Heinz Marbaise
updated JENKINS-24016
TFS_CHANGE_SET is not always correctly set for executing build steps.
Change By:
Karl-Heinz Marbaise
(29/Jul/14 2:22 PM)
Description:
Configured TFS Plugin to use update only * Build Step 1: Execute Shell (Print out TFS_CHANGESET) * Build Step 2: Execute Maven Build (Maven 3.1.1) * Build Step 3: Execute Shell (rolling_label.sh ${WORKSPACE} ${BUILD_NUMBER} ${TFS_CHANGESET})The execution build step Nr. 3 fails from time to time by the cause that the TFS_CHANGESET variable has not been set which can't be cause within the build step 1 it will be correctly printed out to the jenkins console.The following is the output in case of a failure:{code}[portal-HEAD] $ /usr/bin/bash -xe /temp/hudson1539801749356572417.sh+ /build/label.sh /opt/build/x-HEAD 4855{code}The following is the output in case of success:{code}[Current build status] check if current [SUCCESS] is worse or equals then [SUCCESS] and better or equals then [SUCCESS]Run condition [Current build status] enabling perform for step [Execute shell][
x
-HEAD] $ /usr/bin/bash -xe /temp/
hudson3621978596655594520
hudson7426258207171993715
.sh
+ /build/label.sh /opt/build/x-HEAD 4856 173224 Updated label xx_HEAD@$/CCB
[WARNINGS] Parsing warnings in console log with parser Maven
Email was triggered for: Success
{code}which shows that only the TFS_CHANGESET is not being set.
This message is automatically generated by JIRA.
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/d/optout.
[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout
Fabrice Robin commented on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout Reece Johnston : ok thanks I will try that. This bug is a real pain. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout
Reece Johnston commented on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout Unfortunately, my company's policy dictates that all developed code is proprietary, and I'm not sure whether merging other's code falls into this category. I'd rather err on the side of caution for my sake. Also, the merge was not too bad: simply download the 2.4 source and Beck's branch source, merge (keeping changes from both except on conflicts keeping Beck's), compile, and load the hpi through the updates manager. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Jeff Geerling commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection In my case (1.574, CentOS 6.5), I was getting the same error, but it seems it was a case of DNS resolution failure with my URL. I had to explicitly map the IP of the server to the server's hostname (as used in the jenkins-cli command) and this error went away. The diyChunking property was false when I checked. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [rebuild] (JENKINS-24017) "Rebuild Last" can trigger the wrong build
Marc Günther created JENKINS-24017 "Rebuild Last" can trigger the wrong build Issue Type: Bug Assignee: ragesh_nair Components: rebuild Created: 29/Jul/14 2:48 PM Description: When you click on the "Rebuild Last" link in the main menu, it will trigger the build which was the last one when the page was loaded. If there have been other builds in the mean time, they will be skipped. This is especially annoying for parameterized jobs, of course. The reason for this is because the link contains the fixed build number in its URL, eg. ../jenkins/job/my-job/6139/rebuild. A simple solution would be to simply use lastCompletedBuild instead of the build number in the link. It will then always use the last build that is not currently running. Project: Jenkins Priority: Minor Reporter: Marc Günther This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [rebuild] (JENKINS-24017) "Rebuild Last" can trigger the wrong build
Marc Günther commented on JENKINS-24017 "Rebuild Last" can trigger the wrong build One more comment, I was first thinking of using lastBuild, but that gave me a NullPointerException if (and only if) the job was currently running. The NPE involved Naginator, though Caused by: java.lang.NullPointerException at com.chikli.hudson.plugin.naginator.NaginatorActionFactory.createFor(NaginatorActionFactory.java:20) at hudson.model.Run.getTransientActions(Run.java:351) ... This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [plugin] (JENKINS-4824) No available plugins found
Swapnil Kotwal reopened JENKINS-4824 No available plugins found Change By: Swapnil Kotwal (29/Jul/14 2:59 PM) Resolution: Duplicate Status: Closed 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/d/optout.
[JIRA] [rebuild] (JENKINS-24017) "Rebuild Last" can trigger the wrong build
Marc Günther edited a comment on JENKINS-24017 "Rebuild Last" can trigger the wrong build One more comment, I was first thinking of using lastBuild, but that gave me a NullPointerException if (and only if) the job was currently running. The NPE involved Naginator, though Caused by: java.lang.NullPointerException at com.chikli.hudson.plugin.naginator.NaginatorActionFactory.createFor(NaginatorActionFactory.java:20) at hudson.model.Run.getTransientActions(Run.java:351) ... So, using lastCompletedBuild would still give you "wrong" results if a job is currently running, but it's still better than the current behaviour, and seems to be a trivial change. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [plugin] (JENKINS-4824) No available plugins found
Swapnil Kotwal commented on JENKINS-4824 No available plugins found I'm also not able see Available plugins on Win 7, 64 bit machine. I tried Advance option Check Updates. Tried to install git plugins by git.hpi file upload but it throws error Stack trace javax.servlet.ServletException: org.apache.commons.fileupload.FileUploadBase$InvalidContentTypeException: the request doesn't contain a multipart/form-data or multipart/mixed stream, content type header is null at hudson.PluginManager.doUploadPlugin(PluginManager.java:832) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:182) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) 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 jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) 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:79) 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.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedCh
[JIRA] [core] (JENKINS-23829) Layout: Job history may overlap main job status
Tom FENNELLY edited a comment on JENKINS-23829 Layout: Job history may overlap main job status I tested https://github.com/jenkinsci/jenkins/pull/1321 with long job names and descriptions and it's a lot better IMO. So hopefully we'll have a resolution for this issue soon. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [ssh] (JENKINS-18769) SSH Publish Plugin - Unable to use the private key provided in the key path
John Knight commented on JENKINS-18769 SSH Publish Plugin - Unable to use the private key provided in the key path I have the same issue. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [flexible-publish] (JENKINS-23984) Retry build after failure not working
Tonatiuh Romero updated JENKINS-23984 Retry build after failure not working Change By: Tonatiuh Romero (29/Jul/14 3:37 PM) Attachment: Screen Shot 2014-07-29 at 17.36.57.png Attachment: Screen Shot 2014-07-29 at 17.36.29.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [flexible-publish] (JENKINS-23984) Retry build after failure not working
Tonatiuh Romero commented on JENKINS-23984 Retry build after failure not working Normally if I configure "Retry build after failure" it will trigger another build. If I use Flexible publish with the same configuration it does not trigger another build This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [slave-status] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Andy Pham commented on JENKINS-22932 Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted I also hit the same problem as Patricia and Kevin with Jenkins 1.571. Slave.jar 2.37. Master on Red Hat Enterprise Linux Server release 6.5 and slave on a Windows 7 VM. Will try to restart Jenkins and see if that helps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [xvfb] (JENKINS-23980) Xvfb doesn't remove /tmp/.X-* locks after a build has finished
Stefan Schultz commented on JENKINS-23980 Xvfb doesn't remove /tmp/.X-* locks after a build has finished Got it! So i guess this is an xvfb problem. Would it be possible to add a check if the PID in the lock file is still valid? I'm not sure if this has any bad side effects, maybe you could add an opt-in for that? That would be great! Or is this covered by the so called "zombie process handling" you talked about? Thanks, Stefan This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-23248) CLI calls are causing file descriptor leaks.
Daniel Beck updated JENKINS-23248 CLI calls are causing file descriptor leaks. Change By: Daniel Beck (29/Jul/14 3:58 PM) Labels: lts-candidate remoting This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [email-ext-template] (JENKINS-24018) RTC changes dont work in the email template
Kelsey Steinbeck created JENKINS-24018 RTC changes dont work in the email template Issue Type: Bug Assignee: Alex Earl Components: email-ext-template, teamconcert Created: 29/Jul/14 4:14 PM Description: When using the jelly email template with RTC source control it shows up as 'No Changes'. Is there a way to get a new jelly script that works with RTC for the change set portion on the emails. Due Date: 08/Aug/14 12:00 AM Environment: All Project: Jenkins Priority: Minor Reporter: Kelsey Steinbeck This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [ec2] (JENKINS-23792) PATCH: EC2 plugin idles-down nodes that are still launching
SCM/JIRA link daemon commented on JENKINS-23792 PATCH: EC2 plugin idles-down nodes that are still launching Code changed in jenkins User: Craig Ringer Path: src/main/java/hudson/plugins/ec2/EC2RetentionStrategy.java http://jenkins-ci.org/commit/ec2-plugin/d0cd0db5b845c747607a60759eebb7d31e4ea32b Log: Prevent nodes that are still starting up from being idle-stopped Per JENKINS-23792, the EC2 plugin will shut down nodes that're still starting up if the idle timeout is shorter than the time the node takes to go from launch request to successfully starting its first job on an executor. To prevent this, don't perform idle shutdown on a node that is marked offline. When it comes online, executors will be created and the new idle time will become the executor creation time, effectively resetting the timer. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [email-ext-template] (JENKINS-24018) RTC changes dont work in the email template
Alex Earl closed JENKINS-24018 as Not A Defect RTC changes dont work in the email template I've never even heard of RTC. If RTC doesn't provide the functionality to get changes for the job, then there is nothing that email-ext can do. It is up to the SCM plugin to implement specific functionality. Otherwise, you will have to create your own template that gets the information somehow. Change By: Alex Earl (29/Jul/14 4:17 PM) Status: Open Closed Resolution: Not A Defect This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24019) Absolute URLs in delivery pipeline break reverse proxy setups
Josh Hansen
created JENKINS-24019
Absolute URLs in delivery pipeline break reverse proxy setups
Issue Type:
Bug
Assignee:
Patrik Boström
Attachments:
Screen Shot 2014-07-29 at 9.45.24 AM.png, Screen Shot 2014-07-29 at 9.49.12 AM.png
Components:
delivery-pipeline
Created:
29/Jul/14 4:50 PM
Description:
I'm having trouble with the URLs being generated for XMLHttpRequests behind a reverse proxy. The URLs generated have the http scheme instead of https.
I believe this could be solved by changing the URL to be relative instead of absolute.
public String getApiBaseUrl() {
return Jenkins.getInstance().getRootUrlFromRequest() + getViewUrl();
}
See attached screen caps demonstrating the behavior I'm seeing.
Project:
Jenkins
Priority:
Major
Reporter:
Josh Hansen
This message is automatically generated by JIRA.
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/d/optout.
[JIRA] [matrix-project] (JENKINS-24020) Fail-fast Matrix builds, as soon some configuration fail
Bruno Meneguello created JENKINS-24020 Fail-fast Matrix builds, as soon some configuration fail Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: matrix-project Created: 29/Jul/14 5:03 PM Description: If my latest matrix build was successful, during my next execution, the overall project status is the same as the latest build status until the entire build is done. I was checking the sources and noted the "problem" is the hudson.matrix.DefaultMatrixExecutionStrategyImpl.waitForCompletion(MatrixBuildExecution, MatrixConfiguration) method that blocks until the configuration is done, inside a loop over all configurations. Maybe if this method do a "checkForCompletion" and update the build status for every configurations that finishes (I know it's not a trivial solution), we could have a fail-fast solution for matrix projects. Project: Jenkins Priority: Major Reporter: Bruno Meneguello This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout
Josh Kelley commented on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout @Fabrice - We've been using the snapshot mentioned in this comment (if I remember correctly). Although it's a 2.3 snapshot, it's from after the svn:externals bug was fixed and before the StringIndexOutOfBoundsException bug was introduced. (I think. I admit I've had trouble keeping track of which bug is which and which versions are affected. It's been working well for us, at any rate.) That build has apparently expired from the Jenkins server, but I've put a copy on Dropbox in case it helps anyone. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [build-monitor] (JENKINS-20852) Support more build statuses: unstable, not-yet-built
Kyle Leinen commented on JENKINS-20852 Support more build statuses: unstable, not-yet-built I would also find value in this, especially the support for unstable (yellow). This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-23872) Jenkins users disappeared!
Daniel Beck commented on JENKINS-23872 Jenkins users disappeared! Stephen: User.getOrCreate uses keyFor(String) which by default lowercases the user name in the case-insensitive strategy. But the authorization strategy is configured for uppercase user names, and there never was a need before to do case insensitive comparison. E.g. https://github.com/jenkinsci/role-strategy-plugin/blob/master/src/main/java/com/michelin/cio/hudson/plugins/rolestrategy/RoleMap.java#L71 So, no permissions for the newly lowercased user (even if he now retains his custom name, email address, password, ...) This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-23872) Jenkins users disappeared!
SCM/JIRA link daemon commented on JENKINS-23872 Jenkins users disappeared! Code changed in jenkins User: Daniel Beck Path: changelog.html http://jenkins-ci.org/commit/jenkins/02b46fc5ddb32548019591c63d5700f8d3228b8e Log: Noting JENKINS-23872, JENKINS-24006, 19d8b80 This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [junit] (JENKINS-24006) Customize number of Junit test failures that affect weather
SCM/JIRA link daemon commented on JENKINS-24006 Customize number of Junit test failures that affect weather Code changed in jenkins User: Daniel Beck Path: changelog.html http://jenkins-ci.org/commit/jenkins/02b46fc5ddb32548019591c63d5700f8d3228b8e Log: Noting JENKINS-23872, JENKINS-24006, 19d8b80 This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [junit] (JENKINS-13709) ClassCast Exception when parsing JUnit surefire reports during website generation
Andreas Horst commented on JENKINS-13709 ClassCast Exception when parsing JUnit surefire reports during website generation I can still confirm this on 1.574 with maven-site-plugin 3.3. Also the workaround to additionally invoke the default lifecycle (e.g. "clean package site-deploy") works. Though it would be nice to be able to just do a "clean site-deploy" in a dedicated site job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [junit] (JENKINS-24006) Customize number of Junit test failures that affect weather
Daniel Beck resolved JENKINS-24006 as Fixed Customize number of Junit test failures that affect weather Fixed in https://github.com/jenkinsci/jenkins/commit/17fdfab3cd43b03732f322162fac16df87c604f1 by Stephen Connolly. Scheduled for 1.576. Change By: Daniel Beck (29/Jul/14 5:52 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/d/optout.
[JIRA] [findbugs] (JENKINS-15344) ClassCastException when reports are created with maven-site-plugin
Andreas Horst commented on JENKINS-15344 ClassCastException when reports are created with maven-site-plugin I can still confirm this on 1.574 with maven-site-plugin 3.3. Also the workaround to additionally invoke the default lifecycle (e.g. "clean package site-deploy") works. Though it would be nice to be able to just do a "clean site-deploy" in a dedicated site job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [junit] (JENKINS-7666) ClassCastException parsing JUnit result
Andreas Horst commented on JENKINS-7666 ClassCastException parsing JUnit result I can still confirm this on 1.574 with maven-site-plugin 3.3. Also the workaround to additionally invoke the default lifecycle (e.g. "clean package site-deploy") works. Though it would be nice to be able to just do a "clean site-deploy" in a dedicated site job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [job-parameter-summary] (JENKINS-23695) Passwords are shown in plaintext for parameter summary
SCM/JIRA link daemon resolved JENKINS-23695 as Fixed Passwords are shown in plaintext for parameter summary Change By: SCM/JIRA link daemon (29/Jul/14 6:05 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/d/optout.
[JIRA] [job-parameter-summary] (JENKINS-22746) Job Parameter Summary Plugin not reporing Choice Parameters
SCM/JIRA link daemon commented on JENKINS-22746 Job Parameter Summary Plugin not reporing Choice Parameters Code changed in jenkins User: mcupak Path: src/main/java/org/jenkinsci/plugins/jobparametersummary/Summary.java src/test/java/org/jenkinsci/plugins/jobparametersummary/SummaryTest.java http://jenkins-ci.org/commit/job-parameter-summary-plugin/5ec36a4e6242fda8b60aab680061ed6a42e203c3 Log: [FIXED JENKINS-22746] added support for choice parameters This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [job-parameter-summary] (JENKINS-23695) Passwords are shown in plaintext for parameter summary
SCM/JIRA link daemon commented on JENKINS-23695 Passwords are shown in plaintext for parameter summary Code changed in jenkins User: Oliver Gondža Path: src/main/java/org/jenkinsci/plugins/jobparametersummary/Summary.java src/test/java/org/jenkinsci/plugins/jobparametersummary/SummaryTest.java http://jenkins-ci.org/commit/job-parameter-summary-plugin/add809949c01baac3bc176f3e33b603c28581877 Log: Merge pull request #1 from mcupak/extended-param-handling addressing JENKINS-23695 and JENKINS-22746 - properly showing values for choice and password parameters Compare: https://github.com/jenkinsci/job-parameter-summary-plugin/compare/47316af5cd8d...add809949c01 This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [job-parameter-summary] (JENKINS-22746) Job Parameter Summary Plugin not reporing Choice Parameters
SCM/JIRA link daemon resolved JENKINS-22746 as Fixed Job Parameter Summary Plugin not reporing Choice Parameters Change By: SCM/JIRA link daemon (29/Jul/14 6:05 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/d/optout.
[JIRA] [job-parameter-summary] (JENKINS-22746) Job Parameter Summary Plugin not reporing Choice Parameters
SCM/JIRA link daemon commented on JENKINS-22746 Job Parameter Summary Plugin not reporing Choice Parameters Code changed in jenkins User: Oliver Gondža Path: src/main/java/org/jenkinsci/plugins/jobparametersummary/Summary.java src/test/java/org/jenkinsci/plugins/jobparametersummary/SummaryTest.java http://jenkins-ci.org/commit/job-parameter-summary-plugin/add809949c01baac3bc176f3e33b603c28581877 Log: Merge pull request #1 from mcupak/extended-param-handling addressing JENKINS-23695 and JENKINS-22746 - properly showing values for choice and password parameters Compare: https://github.com/jenkinsci/job-parameter-summary-plugin/compare/47316af5cd8d...add809949c01 This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [job-parameter-summary] (JENKINS-23695) Passwords are shown in plaintext for parameter summary
SCM/JIRA link daemon commented on JENKINS-23695 Passwords are shown in plaintext for parameter summary Code changed in jenkins User: mcupak Path: src/main/java/org/jenkinsci/plugins/jobparametersummary/Summary.java http://jenkins-ci.org/commit/job-parameter-summary-plugin/d0cb5d24ef37797677caa59758ab55c53440fde9 Log: [FIXED JENKINS-23695] showing encrypted default value of password parameters This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [sloccount] (JENKINS-24021) Show statistics from last build on main job page
Michal Turek created JENKINS-24021 Show statistics from last build on main job page Issue Type: Improvement Affects Versions: current Assignee: Michal Turek Components: sloccount Created: 29/Jul/14 7:45 PM Description: Show the same table with statistics from last SloccountBuildAction in SloccountProjectAction page. Environment: all Project: Jenkins Priority: Major Reporter: Michal Turek This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [sloccount] (JENKINS-24021) Show statistics from last build on main job page
Michal Turek updated JENKINS-24021 Show statistics from last build on main job page Change By: Michal Turek (29/Jul/14 7:54 PM) Description: Show the same table with statistics from last SloccountBuildAction in SloccountProjectAction page. Similar task in Cppcheck plugin is JENKINS-22388. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [sloccount] (JENKINS-24021) Show statistics from last build on main job page
SCM/JIRA link daemon commented on JENKINS-24021 Show statistics from last build on main job page Code changed in jenkins User: Michal Turek Path: .gitignore src/main/java/hudson/plugins/sloccount/SloccountBuildAction.java src/main/java/hudson/plugins/sloccount/SloccountProjectAction.java src/main/resources/hudson/plugins/sloccount/Messages.properties src/main/resources/hudson/plugins/sloccount/Messages_de.properties src/main/resources/hudson/plugins/sloccount/Messages_ja.properties src/main/resources/hudson/plugins/sloccount/SloccountBuildAction/statistics.jelly src/main/resources/hudson/plugins/sloccount/SloccountBuildAction/summary.jelly src/main/resources/hudson/plugins/sloccount/SloccountProjectAction/jobMain.jelly http://jenkins-ci.org/commit/sloccount-plugin/891f749ecc0d3e873754a5f5cfaa765435bef11e Log: Merge pull request #42 from mixalturek/master JENKINS-24021 Show statistics from last build on main job page Compare: https://github.com/jenkinsci/sloccount-plugin/compare/a8b8e250780a...891f749ecc0d This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [sloccount] (JENKINS-24021) Show statistics from last build on main job page
Michal Turek updated JENKINS-24021 Show statistics from last build on main job page Change By: Michal Turek (29/Jul/14 7:56 PM) Attachment: project_action.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [sloccount] (JENKINS-24021) Show statistics from last build on main job page
SCM/JIRA link daemon commented on JENKINS-24021 Show statistics from last build on main job page Code changed in jenkins User: Michal Turek Path: .gitignore src/main/java/hudson/plugins/sloccount/SloccountBuildAction.java src/main/java/hudson/plugins/sloccount/SloccountProjectAction.java src/main/resources/hudson/plugins/sloccount/Messages.properties src/main/resources/hudson/plugins/sloccount/Messages_de.properties src/main/resources/hudson/plugins/sloccount/Messages_ja.properties src/main/resources/hudson/plugins/sloccount/SloccountBuildAction/statistics.jelly src/main/resources/hudson/plugins/sloccount/SloccountBuildAction/summary.jelly src/main/resources/hudson/plugins/sloccount/SloccountProjectAction/jobMain.jelly http://jenkins-ci.org/commit/sloccount-plugin/f73ff44d85c2c2ee3aab0baffe8ebde9a9d4b33b Log: JENKINS-24021 Show statistics from last build on main job 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/d/optout.
[JIRA] [sloccount] (JENKINS-24021) Show statistics from last build on main job page
Michal Turek resolved JENKINS-24021 as Fixed Show statistics from last build on main job page Implemented, will be released in version 1.20. Change By: Michal Turek (29/Jul/14 7:57 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/d/optout.
[JIRA] [git] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Ken Poole commented on JENKINS-14276 Git SCM-polling doesn't work when using a parametrized branch-name We are trying to switch to a configuration where we use a parameter with a default value for the branch to poll/update to - the update part works great - but the poll always says it is not up to date so we get continuous rebuilds as indicated above. We have git client 1.9.1, git plugin 2.2.2, Jenkins 1.571 This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Saad Rahim commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 It is time for the Jenkins project to either formally issue an end of life statement for the subversion plugin or commit to a timeline to fixing the plugin. If this is the end of Jenkins and Subversion, I can move on and investigate if Git fits our needs. This uncertainty is costing our business the productivity and features associated with running an up to date version control software. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Jeff Dege commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 I share in the frustration, that Jenkins hasn't current with svnkit. But for all those who are insisting that the Jenkins team do something about this, there's a "Sponsor this" link in the top right corner of the page for this issue. Instead of complaining to us, who agree with you, why don't you suggest to your bosses that they could improve the software and gain some goodwill in the community? This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-23872) Jenkins users disappeared!
stephenconnolly commented on JENKINS-23872 Jenkins users disappeared! Daniel, the authorization strategies need updating to reflect the case sensitivity strategy exposed by the security realm. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [p4] (JENKINS-24022) Running 'files' command for multiple hours with a label
Ryan Hummer created JENKINS-24022 Running 'files' command for multiple hours with a label Issue Type: Bug Affects Versions: current Assignee: Paul Allen Components: p4 Created: 29/Jul/14 9:06 PM Description: I have kicked off a build using the pin job at label functionality, not sure if that is related or not. The job appears to kick off just fine as I see this output: 10:47:59 [EnvInject] - Loading node environment variables. 10:47:59 Building remotely on rsmsnbuild114 in workspace c:\trees 10:48:56 SCM Task: cleanup workspace: RSMSNBUILD114 10:48:57 SCM Task: syncing files at label: my_label 10:48:57 ... sync c:\trees/...@my_label 10:48:57 ... force update false 10:48:57 ... bypass have false It appears the sync works, but I see the machine that runs the Jenkins server under heavy CPU load and the monitor running a 'p4 files'. Is this expected? Project: Jenkins Priority: Major Reporter: Ryan Hummer This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [msbuild] (JENKINS-22461) New MSBuild release has a space in the installation path; causes msbuild plugin to fail
SCM/JIRA link daemon commented on JENKINS-22461 New MSBuild release has a space in the installation path; causes msbuild plugin to fail Code changed in jenkins User: Gregory Boissinot Path: src/main/java/hudson/plugins/msbuild/MsBuildBuilder.java http://jenkins-ci.org/commit/msbuild-plugin/da904ff4b558ce6ca4ca14ada2eecc423a56d941 Log: Merge pull request #15 from XitasoChris/master Fix: MSBuild can now be in a path containing spaces (JENKINS-22461) Compare: https://github.com/jenkinsci/msbuild-plugin/compare/635691a03d43...da904ff4b558 This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [msbuild] (JENKINS-22461) New MSBuild release has a space in the installation path; causes msbuild plugin to fail
SCM/JIRA link daemon commented on JENKINS-22461 New MSBuild release has a space in the installation path; causes msbuild plugin to fail Code changed in jenkins User: Christopher Gross Path: src/main/java/hudson/plugins/msbuild/MsBuildBuilder.java http://jenkins-ci.org/commit/msbuild-plugin/f72edcd8642832542c807db4939ec7c5bbab1a27 Log: fix: msbuild can now be in a path containing spaces (fix provided via comment on JENKINS-22461 by Thorsten Bojer) This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-20550) download artifacts is very slow
stephenconnolly commented on JENKINS-20550 download artifacts is very slow It would be good if you could put enough logging on the SSH server side to see if there is a different cipher being used with the newer lib This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Saad Rahim commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 It is not so easy to gain approval to pay for free software. If Jenkins charged $1000 a year to use, I would have a PO signed tomorrow. We discussed sponsoring here, unlikely anything less than $1000 would entice the developers to prioritize this. Management would never approve that sum for a donation, accounting wouldn't know how to classify it and the auditors would wonder what it is. That is the case with many small businesses. Perhaps a year after svn 1.9 is release, I could convince them to take the effort. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-7025) Workspace permissions don't work with Project-based Matrix Authorization Strategy
Ulli Hafner commented on JENKINS-7025 Workspace permissions don't work with Project-based Matrix Authorization Strategy I don't know if this is still valid: With Project-based Matrix Authorization Strategy configured in Jenkins a user needs to have global rights to access workspace files rather then job-level rights. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
mark 3000 commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 If someone would commit to fixing it for a set price, that could possibly make it easier to sell to management. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Quentin Hartman commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 @Saad Rahim - I've had luck coding such things as a "Computer Consulting Fee" at other organizations. The accountants knew how to handle it, and management thought it accurately captured the spirit of the expenditure. If you are working for a governmental agency they likely already have an accounting code for such things. The one time I did this, I engaged the developers before hand to ensure that our problem was likely to be solved in a timely manner, and we paid the "fee" half up front and half after delivery. It worked out well for everyone, and the items we needed materialized in just a couple weeks. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [matrix-combinations-parameter] (JENKINS-24023) Matrix unformatted
Roger Silva created JENKINS-24023 Matrix unformatted Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: matrix-combinations-parameter Created: 29/Jul/14 9:56 PM Description: Matrix bad formatted when there is just an axis. Project: Jenkins Priority: Minor Reporter: Roger Silva This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [p4] (JENKINS-24024) Opt-out of pulling changelist info for Build Changes
Ryan Hummer created JENKINS-24024 Opt-out of pulling changelist info for Build Changes Issue Type: New Feature Affects Versions: current Assignee: Paul Allen Components: p4 Created: 29/Jul/14 10:15 PM Description: The other Perforce plugin has this functionality where you can opt-out of the job querying for changelist information to display as the changes for the build. We have jobs where they are essentially a 'fire and forget' where we don't care what changes are part of the build. Now that it appears the changes are pulled on-demand when viewing that job. We'd like to see that feature return. Project: Jenkins Priority: Minor Reporter: Ryan Hummer This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [ec2] (JENKINS-4995) Support windows AMI's in EC2 plugin
SCM/JIRA link daemon commented on JENKINS-4995 Support windows AMI's in EC2 plugin Code changed in jenkins User: Francis Upton IV Path: pom.xml src/main/java/hudson/plugins/ec2/AMITypeData.java src/main/java/hudson/plugins/ec2/EC2AbstractSlave.java src/main/java/hudson/plugins/ec2/EC2OndemandSlave.java src/main/java/hudson/plugins/ec2/EC2SpotSlave.java src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/main/java/hudson/plugins/ec2/UnixData.java src/main/java/hudson/plugins/ec2/WindowsData.java src/main/java/hudson/plugins/ec2/win/EC2WindowsLauncher.java src/main/java/hudson/plugins/ec2/win/WinConnection.java src/main/java/hudson/plugins/ec2/win/winrm/RuntimeIOException.java src/main/java/hudson/plugins/ec2/win/winrm/WinRM.java src/main/java/hudson/plugins/ec2/win/winrm/WinRMClient.java src/main/java/hudson/plugins/ec2/win/winrm/WinRMConnectException.java src/main/java/hudson/plugins/ec2/win/winrm/WindowsProcess.java src/main/java/hudson/plugins/ec2/win/winrm/request/AbstractWinRMRequest.java src/main/java/hudson/plugins/ec2/win/winrm/request/DeleteShellRequest.java src/main/java/hudson/plugins/ec2/win/winrm/request/ExecuteCommandRequest.java src/main/java/hudson/plugins/ec2/win/winrm/request/GetOutputRequest.java src/main/java/hudson/plugins/ec2/win/winrm/request/OpenShellRequest.java src/main/java/hudson/plugins/ec2/win/winrm/request/RequestFactory.java src/main/java/hudson/plugins/ec2/win/winrm/request/SendInputRequest.java src/main/java/hudson/plugins/ec2/win/winrm/request/SignalRequest.java src/main/java/hudson/plugins/ec2/win/winrm/request/WinRMRequest.java src/main/java/hudson/plugins/ec2/win/winrm/soap/Header.java src/main/java/hudson/plugins/ec2/win/winrm/soap/HeaderBuilder.java src/main/java/hudson/plugins/ec2/win/winrm/soap/MessageBuilder.java src/main/java/hudson/plugins/ec2/win/winrm/soap/Namespaces.java src/main/java/hudson/plugins/ec2/win/winrm/soap/Option.java src/main/resources/hudson/plugins/ec2/EC2Computer/configure.jelly src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly src/main/resources/hudson/plugins/ec2/SlaveTemplate/help-amiType.html src/main/resources/hudson/plugins/ec2/UnixData/config.jelly src/main/resources/hudson/plugins/ec2/WindowsData/config.jelly src/main/resources/hudson/plugins/ec2/WindowsData/help-bootDelay.html src/test/java/hudson/plugins/ec2/EC2AbstractSlaveTest.java src/test/java/hudson/plugins/ec2/EC2OndemandSlaveTest.java src/test/java/hudson/plugins/ec2/EC2RetentionStrategyTest.java src/test/java/hudson/plugins/ec2/SlaveTemplateTest.java src/test/java/hudson/plugins/ec2/TemplateLabelsTest.java src/test/java/hudson/plugins/ec2/WinRMMessageTest.java http://jenkins-ci.org/commit/ec2-plugin/859dd4ea8aeedaad2484454df58d31b94fdcd472 Log: JENKINS-4995 Support Windows AMIs This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [ec2] (JENKINS-4995) Support windows AMI's in EC2 plugin
SCM/JIRA link daemon commented on JENKINS-4995 Support windows AMI's in EC2 plugin Code changed in jenkins User: Francis Upton Path: pom.xml src/main/java/hudson/plugins/ec2/AMITypeData.java src/main/java/hudson/plugins/ec2/EC2AbstractSlave.java src/main/java/hudson/plugins/ec2/EC2OndemandSlave.java src/main/java/hudson/plugins/ec2/EC2SpotSlave.java src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/main/java/hudson/plugins/ec2/UnixData.java src/main/java/hudson/plugins/ec2/WindowsData.java src/main/java/hudson/plugins/ec2/win/EC2WindowsLauncher.java src/main/java/hudson/plugins/ec2/win/WinConnection.java src/main/java/hudson/plugins/ec2/win/winrm/RuntimeIOException.java src/main/java/hudson/plugins/ec2/win/winrm/WinRM.java src/main/java/hudson/plugins/ec2/win/winrm/WinRMClient.java src/main/java/hudson/plugins/ec2/win/winrm/WinRMConnectException.java src/main/java/hudson/plugins/ec2/win/winrm/WindowsProcess.java src/main/java/hudson/plugins/ec2/win/winrm/request/AbstractWinRMRequest.java src/main/java/hudson/plugins/ec2/win/winrm/request/DeleteShellRequest.java src/main/java/hudson/plugins/ec2/win/winrm/request/ExecuteCommandRequest.java src/main/java/hudson/plugins/ec2/win/winrm/request/GetOutputRequest.java src/main/java/hudson/plugins/ec2/win/winrm/request/OpenShellRequest.java src/main/java/hudson/plugins/ec2/win/winrm/request/RequestFactory.java src/main/java/hudson/plugins/ec2/win/winrm/request/SendInputRequest.java src/main/java/hudson/plugins/ec2/win/winrm/request/SignalRequest.java src/main/java/hudson/plugins/ec2/win/winrm/request/WinRMRequest.java src/main/java/hudson/plugins/ec2/win/winrm/soap/Header.java src/main/java/hudson/plugins/ec2/win/winrm/soap/HeaderBuilder.java src/main/java/hudson/plugins/ec2/win/winrm/soap/MessageBuilder.java src/main/java/hudson/plugins/ec2/win/winrm/soap/Namespaces.java src/main/java/hudson/plugins/ec2/win/winrm/soap/Option.java src/main/resources/hudson/plugins/ec2/EC2Computer/configure.jelly src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly src/main/resources/hudson/plugins/ec2/SlaveTemplate/help-amiType.html src/main/resources/hudson/plugins/ec2/UnixData/config.jelly src/main/resources/hudson/plugins/ec2/WindowsData/config.jelly src/main/resources/hudson/plugins/ec2/WindowsData/help-bootDelay.html src/test/java/hudson/plugins/ec2/EC2AbstractSlaveTest.java src/test/java/hudson/plugins/ec2/EC2OndemandSlaveTest.java src/test/java/hudson/plugins/ec2/EC2RetentionStrategyTest.java src/test/java/hudson/plugins/ec2/SlaveTemplateTest.java src/test/java/hudson/plugins/ec2/TemplateLabelsTest.java src/test/java/hudson/plugins/ec2/WinRMMessageTest.java http://jenkins-ci.org/commit/ec2-plugin/a3bd08def1ed2d2f30c5fa73be707fb702c2a9e5 Log: Merge pull request #105 from jenkinsci/feature/windows-slave-support JENKINS-4995 Support Windows AMIs Compare: https://github.com/jenkinsci/ec2-plugin/compare/04cd780ebe71...a3bd08def1ed This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-7025) Workspace permissions don't work with Project-based Matrix Authorization Strategy
Daniel Beck commented on JENKINS-7025 Workspace permissions don't work with Project-based Matrix Authorization Strategy Cannot reproduce on Jenkins 1.574 with Matrix Auth 1.2: User with global Overall/Read and one job's Job/Read and Job/Workspace can access the workspace (tried both authenticated user and anon). Can we resolve this as Cannot Reproduce? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [ec2] (JENKINS-4995) Support windows AMI's in EC2 plugin
Francis Upton commented on JENKINS-4995 Support windows AMI's in EC2 plugin Even with the checkins to date, this is not quite complete. More testing it required. It has been integrated with the master source in the plugin so that hopefully others can test it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [ec2] (JENKINS-4995) Support windows AMI's in EC2 plugin
Francis Upton assigned JENKINS-4995 to Francis Upton Support windows AMI's in EC2 plugin Change By: Francis Upton (29/Jul/14 11:15 PM) Assignee: Francis Upton This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-10407) builds/1234, lastSuccessful and lastStable symlinks not created
Daniel Beck resolved JENKINS-10407 as Incomplete builds/1234, lastSuccessful and lastStable symlinks not created No response to comments asking for updated and additional information in several weeks/months, so resolving this issue as Incomplete. If you're experiencing a similar problem on newer Jenkins versions than reported here (should be at least 1.554.x or newer as of now), please just file a new issue instead of reopening this one. Change By: Daniel Beck (29/Jul/14 11:42 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
