[JIRA] [slave-setup] (JENKINS-23143) FATAL: hudson.remoting.RequestAbortedException
Oleg Nenashev commented on JENKINS-23143 FATAL: hudson.remoting.RequestAbortedException The issue seems to be a duplicate of JENKINS-6817 or JENKINS-23120 The messaging/behavior in remoting library changed, but I supposeissues have the same origin This message is automatically generated by JIRA. 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-14253) Discard Old Builds does not remove builds from Matrix-Axes
Matthias Kraft closed JENKINS-14253 as Fixed Discard Old Builds does not remove builds from Matrix-Axes I haven't heard anything back from our Jenkins admins. As I already wrote, there doesn't seem to be an issue anymore. I have no idea when or how this was resolved, though. Nevertheless I am closing this now. If a watcher to this issue disagrees, feel free to reopen or duplicate and explain to Daniel, how this behavior can be reproduced. Change By: Matthias Kraft (22/May/14 6:28 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-3858) New builder for use when replacing Hudson configuration
jskovjyskebankdk closed JENKINS-3858 as Postponed New builder for use when replacing Hudson configuration Less clutter Change By: jskovjyskebankdk (22/May/14 6:16 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-14189) Discover permission gives Status Code 500 and Stacktrace
Matthias Kraft closed JENKINS-14189 as Fixed Discover permission gives Status Code 500 and Stacktrace This went away some time ago, already. But I am unable to say which version actually fixed it. Thanks for digging up ... closing it now. Change By: Matthias Kraft (22/May/14 6:13 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-setup] (JENKINS-23143) FATAL: hudson.remoting.RequestAbortedException
Rainy John created JENKINS-23143 FATAL: hudson.remoting.RequestAbortedException Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: Build Error.txt Components: slave-setup Created: 22/May/14 6:09 AM Description: From the Master Server if I trigger job execution at Slave PC (both Windows) the build is braeking often. Error log attached.. Project: Jenkins Priority: Major Reporter: Rainy John This message is automatically generated by JIRA. 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-15156) Builds disappear from build history after completion
Vlad Aginsky commented on JENKINS-15156 Builds disappear from build history after completion Guys i also see it with gerrit builds. there is no one assigned to this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [timestamper] (JENKINS-23108) Printout different between current and previous line
stevengbrown resolved JENKINS-23108 as Duplicate Printout different between current and previous line Change By: stevengbrown (22/May/14 5:54 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] [timestamper] (JENKINS-23108) Printout different between current and previous line
stevengbrown closed JENKINS-23108 as Duplicate Printout different between current and previous line Change By: stevengbrown (22/May/14 5:54 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-19303) Renaming a job looses changes
Dirk Heinrichs commented on JENKINS-19303 Renaming a job looses changes Both "Workspace Root Directory" and "Build Record Root Directory" are set to their defaults. This message is automatically generated by JIRA. 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] [jobrequeue] (JENKINS-23142) rerun of a job with identical parameters does not enter it to the queue
ziv SHAPIRA created JENKINS-23142 rerun of a job with identical parameters does not enter it to the queue Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jobrequeue Created: 22/May/14 5:41 AM Description: rerun of a job with identical parameters does not enter it to the queue I wanted to rerun a job several times, by filling in the parameters and sending it. after the first success, the other jobs would not enter the queue. when changing one of the parameters, the job would enter the queue. jenkins 1.563 on windows 7 Environment: windows 7 Project: Jenkins Labels: jenkins queue parameter Priority: Major Reporter: ziv SHAPIRA This message is automatically generated by JIRA. 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-22693) Resource leak in hudson.model.FileParameterValue
Oleg Nenashev commented on JENKINS-22693 Resource leak in hudson.model.FileParameterValue The PR just hangs for several weeks... https://github.com/jenkinsci/jenkins/pull/1225 This message is automatically generated by JIRA. 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-22693) Resource leak in hudson.model.FileParameterValue
Oleg Nenashev started work on JENKINS-22693 Resource leak in hudson.model.FileParameterValue Change By: Oleg Nenashev (22/May/14 5:24 AM) Status: Open In Progress This message is automatically generated by JIRA. 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-17589) show project type somewhere
Oleg Nenashev resolved JENKINS-17589 as Fixed show project type somewhere Marking as resolved. Change By: Oleg Nenashev (22/May/14 5: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] [cloudbees-folder] (JENKINS-17820) Deadlock between a folder copy and job deletion
Oleg Nenashev updated JENKINS-17820 Deadlock between a folder copy and job deletion Change By: Oleg Nenashev (22/May/14 5:15 AM) Assignee: Jesse Glick Component/s: cloudbees-folder This message is automatically generated by JIRA. 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-17820) Deadlock between a folder copy and job deletion
Oleg Nenashev commented on JENKINS-17820 Deadlock between a folder copy and job deletion @Vincent Does the issue appear on newest versions? There were many change in core and Folders plugin after the request This message is automatically generated by JIRA. 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-17881) patch for Jenkin Client Console output encoding(charset) issue
Oleg Nenashev commented on JENKINS-17881 patch for Jenkin Client Console output encoding(charset) issue The PR has been declined, no response from the author... This message is automatically generated by JIRA. 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-18204) Support to environment variables
Oleg Nenashev resolved JENKINS-18204 as Incomplete Support to environment variables Jenkins provides built-in mechanisms for the handling of environment variables. There's no proposals about a feature to be implemented Change By: Oleg Nenashev (22/May/14 5:09 AM) 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.
[JIRA] [core] (JENKINS-18513) Slowness in Jenkins
Oleg Nenashev resolved JENKINS-18513 as Fixed Slowness in Jenkins According to the thread dump, the issue seems to be a duplicate of JENKINS-14362 (there're multiple deflater threads) Change By: Oleg Nenashev (22/May/14 5:04 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-18513) Slowness in Jenkins
Oleg Nenashev commented on JENKINS-18513 Slowness in Jenkins @Aswini You use the Monitoring plugin. Please provide thread statistics from it if the issue appears again. It will greatly help to find the hanging thread This message is automatically generated by JIRA. 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-6199) When a project is disabled, it should accept a small text message to gather why it is disabled
Oleg Nenashev resolved JENKINS-6199 as Duplicate When a project is disabled, it should accept a small text message to gather why it is disabled Closed as a duplicate of JENKINS-15181, because it has some discussion/activity inside Change By: Oleg Nenashev (22/May/14 4:56 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] [gui] (JENKINS-6216) Better progress feedback during workspace deletion
Oleg Nenashev assigned JENKINS-6216 to Nicolas De Loof Better progress feedback during workspace deletion Change By: Oleg Nenashev (22/May/14 4:52 AM) Assignee: Nicolas De Loof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gui] (JENKINS-6216) Better progress feedback during workspace deletion
Oleg Nenashev started work on JENKINS-6216 Better progress feedback during workspace deletion Change By: Oleg Nenashev (22/May/14 4:52 AM) Status: Open In Progress This message is automatically generated by JIRA. 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-7713) Plugin Manager "Advanced" tab should offer the restart button
Oleg Nenashev commented on JENKINS-7713 Plugin Manager "Advanced" tab should offer the restart button Safe Restart Plugin provides the action on http://yourserver/manage page Does it resolve 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] [matrix-auth] (JENKINS-7103) Horizontal scrollbars on Configure page when using matrix-based security
Oleg Nenashev updated JENKINS-7103 Horizontal scrollbars on Configure page when using matrix-based security Change By: Oleg Nenashev (22/May/14 4:50 AM) Component/s: matrix-auth Component/s: gui This message is automatically generated by JIRA. 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-23140) Add the "ViewListener" extension point
Oleg Nenashev commented on JENKINS-23140 Add the "ViewListener" extension point Regarding the JENKINS-17384... It's just a top-level use-case. Listener should not provide callbacks to manage columns directly. It should just notify implementations that something has changed in Views. 1) User creates a new view 2) ViewListener fires the onCreated(View view) event 3) The "DefaultColumnsViewListener" from a plugin catches the event, alters the configuration and then saves the view 4) Other ViewListeners do other actions Actually, such approach is not required for JENKINS-17378, but it could be used for more complex cases This message is automatically generated by JIRA. 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] [embeddable-build-status] (JENKINS-22875) Image does not appear on "Embeddable Build Status" page or in Github
Sean Feldman commented on JENKINS-22875 Image does not appear on "Embeddable Build Status" page or in Github Experiencing the same problem. Used fiddler to watch what headers are returned, and didn't see "Cache-Control: no-cache" coming down (according to this thread it is needed - https://github.com/github/markup/issues/224) Version:1.4 Header for response: HTTP/1.1 200 OK Date: Thu, 22 May 2014 02:18:19 GMT ETag: /static/1a041373/success.png Expires: Fri, 01 Jan 1984 00:00:00 GMT Content-Type: image/png Content-Length: 2339 Server: Jetty(8.y.z-SNAPSHOT) proxy-connection: keep-alive keep-alive: 60 via: HTTP/1.1 proxy2444 This message is automatically generated by JIRA. 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] [svnmerge] (JENKINS-15830) Error: Unable to infer the new branch name from XXX
SCM/JIRA link daemon commented on JENKINS-15830 Error: Unable to infer the new branch name from XXX Code changed in jenkins User: Hugues Chabot Path: .gitignore src/main/java/jenkins/plugins/svnmerge/IntegratableProjectAction.java src/main/java/jenkins/plugins/svnmerge/RepositoryLayoutEnum.java src/main/java/jenkins/plugins/svnmerge/RepositoryLayoutInfo.java src/main/resources/jenkins/plugins/svnmerge/IntegratableProjectAction/_attach.groovy src/main/resources/jenkins/plugins/svnmerge/IntegratableProjectAction/_attach.properties src/main/resources/jenkins/plugins/svnmerge/IntegratableProjectAction/index.groovy src/main/resources/jenkins/plugins/svnmerge/IntegratableProjectAction/index.properties src/test/java/jenkins/plugins/svnmerge/RepositoryLayoutInfoTest.java http://jenkins-ci.org/commit/svnmerge-plugin/6598e037fd58781bbc0c1965e322219cca2c535d Log: Merge pull request #13 from hugueschabot/jenkins-22284 [FIXED JENKINS-22284] Improve branch creation [FIXED JENKINS-15830] Error: Unable to infer the new branch name from XXX Compare: https://github.com/jenkinsci/svnmerge-plugin/compare/ca285ed64c31...6598e037fd58 This message is automatically generated by JIRA. 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] [svnmerge] (JENKINS-22284) new field in the "feature branch" creation form, to manage multi-project repository layout
SCM/JIRA link daemon commented on JENKINS-22284 new field in the "feature branch" creation form, to manage multi-project repository layout Code changed in jenkins User: Hugues Chabot Path: .gitignore src/main/java/jenkins/plugins/svnmerge/IntegratableProjectAction.java src/main/java/jenkins/plugins/svnmerge/RepositoryLayoutEnum.java src/main/java/jenkins/plugins/svnmerge/RepositoryLayoutInfo.java src/main/resources/jenkins/plugins/svnmerge/IntegratableProjectAction/_attach.groovy src/main/resources/jenkins/plugins/svnmerge/IntegratableProjectAction/_attach.properties src/main/resources/jenkins/plugins/svnmerge/IntegratableProjectAction/index.groovy src/main/resources/jenkins/plugins/svnmerge/IntegratableProjectAction/index.properties src/test/java/jenkins/plugins/svnmerge/RepositoryLayoutInfoTest.java http://jenkins-ci.org/commit/svnmerge-plugin/6598e037fd58781bbc0c1965e322219cca2c535d Log: Merge pull request #13 from hugueschabot/jenkins-22284 [FIXED JENKINS-22284] Improve branch creation [FIXED JENKINS-15830] Error: Unable to infer the new branch name from XXX Compare: https://github.com/jenkinsci/svnmerge-plugin/compare/ca285ed64c31...6598e037fd58 This message is automatically generated by JIRA. 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] [websphere-deployer] (JENKINS-23141) Location for Installcert
art med updated JENKINS-23141 Location for Installcert Change By: art med (22/May/14 2:24 AM) Component/s: websphere-deployer Component/s: jenkins-tracker This message is automatically generated by JIRA. 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] [analysis-core] (JENKINS-20185) Long pause after end of run
Ivan Kurnosov commented on JENKINS-20185 Long pause after end of run Just to confirm it happens to me as well on v1.554.1 LTS @DevTeam, any ideas what it could be? This message is automatically generated by JIRA. 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] [jenkins-tracker] (JENKINS-23141) Location for Installcert
art med created JENKINS-23141 Location for Installcert Issue Type: Improvement Affects Versions: current Assignee: Unassigned Attachments: Jenkins Question.JPG Components: jenkins-tracker Created: 22/May/14 2:02 AM Description: 1. Which location should we copy to for the file which generate by InstallCert? “JAVA_HOME/jre/lib/security” or “Jenkins installation home/jre/lib/security”? 2. The same question like above. Which location should we import to for the “DummyClientTrustFile.jks”? “JAVA_HOME/jre/lib/security” or “Jenkins installation home/jre/lib/security”?(refer to picture) 3. How to import the “DummyClientTrustFile.jks” to cacerts? Current what I did is: 1. Export all the certificate from the “DummyClientTrustFile.jks” as “.cer” files via keytool command 2. Import these “.cer” files to cacerts via keytool command. Is this correct? Fix Versions: current Project: Jenkins Labels: jenkins Priority: Minor Reporter: art med This message is automatically generated by JIRA. 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] [ghprb] (JENKINS-17097) Changes are not present in builds started by a pull request
Gennady Feldman commented on JENKINS-17097 Changes are not present in builds started by a pull request Actually Github API does provide an api endpoint to pull the changes/commits for a perticular PR: https://developer.github.com/v3/pulls/#list-commits-on-a-pull-request Current issue is creating a lot of noise if we merging PRs into different branches (seeing lots of commits unrelated at times). This message is automatically generated by JIRA. 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-23140) Add the "ViewListener" extension point
Daniel Beck edited a comment on JENKINS-23140 Add the "ViewListener" extension point Actually, that first one should probably not be in here. Listener is more passive recipient of information. jglick also mentioned in JENKINS-21224 that I'm doing it wrong by trying to change things from a listener. Also, the rationale isn't clear why this needs to be configured in an extension point. Is there a need to get more flexibility than to specify which columns should be added by default? Also, how would multiple Listeners interact wrt to column selection? This message is automatically generated by JIRA. 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-23140) Add the "ViewListener" extension point
Daniel Beck commented on JENKINS-23140 Add the "ViewListener" extension point Actually, that first one should probably not be in here. Listener is more passive recipient of information. jglick also mentioned in JENKINS-21224 that I'm doing it wrong by trying to change things from a listener. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-11658) After upgrading from 1.424 to 1.434 Jenkins won't restart
Oleg Nenashev resolved JENKINS-11658 as Not A Defect After upgrading from 1.424 to 1.434 Jenkins won't restart BTW, the main issue is not a defect Change By: Oleg Nenashev (21/May/14 11:51 PM) Status: Open Resolved 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] [core] (JENKINS-12032) Include SCM changes in environment variables
Oleg Nenashev commented on JENKINS-12032 Include SCM changes in environment variables @Daniel I suppose this is a case for the SCM-API plugin instead of the core. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [maven2] (JENKINS-11333) Make fingerprinting configurable in Maven projects
SCM/JIRA link daemon commented on JENKINS-11333 Make fingerprinting configurable in Maven projects Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/maven/MavenModule.java src/main/java/hudson/maven/MavenModuleSet.java src/main/java/hudson/maven/reporters/MavenArtifactArchiver.java src/main/java/hudson/maven/reporters/MavenFingerprinter.java src/main/resources/hudson/maven/MavenModuleSet/configure-entries.jelly src/main/webapp/fingerprintingDisabled.html src/test/java/hudson/maven/MavenModuleSetTest.java http://jenkins-ci.org/commit/maven-plugin/728878bed3c854dcc5c63aec1b7b12e3a133da51 Log: [FIXED JENKINS-11333] Allow users to disable automatic fingerprinting, but add in explicit fingerprinting if desired. Conflicts: src/main/java/hudson/maven/MavenModuleSet.java src/main/resources/hudson/maven/MavenModuleSet/configure-entries.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco] (JENKINS-22716) Jacoco: Zero coverage with java8
peterkittreilly commented on JENKINS-22716 Jacoco: Zero coverage with java8 I have the same problem with gradle jacocoTestReport (sourceCompatibility 1.8 targetCompatibility 1.8), the html reports are great This message is automatically generated by JIRA. 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-client] (JENKINS-21559) Default GIT to run 'git clone' instead of 'git fetch'
Mark Waite edited a comment on JENKINS-21559 Default GIT to run 'git clone' instead of 'git fetch' Wipe out repository and force clone is a last-ditch technique to handle those cases where the repository is no longer usable. It should generally only be needed for recovery, not for everyday operation. Wipe out workspace is the same type of operation, and I use it with about the same frequency to recover from some form of repository damage. I need to use that setting at times when I'm testing bug reports in the git plugin or the git client plugin because a repository was only partially cloned, or because a build operation damaged the contents of the git repository. If you're using Unix based (Linux, FreeBSD, OpenBSD, Solaris, HP-UX, AIX, etc.) slave agents, you could consider reducing the disc space and the clone time of your large repository by using a "reference repository" on each slave machine. A reference repository is a bare repository kept at a known location on the slave machine, referenced by Jenkins jobs which need the contents of that repository. The Jenkins job repository then include pointers into the bare repository instead of copying the content from the central repository. I've found it saves significant time on my large repositories. The "reference repository" setting is under "Advanced clone options" in the "Additional behaviours". This message is automatically generated by JIRA. 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-12343) Action (e.g. Open) on all builds in a list in new tab/window?
Oleg Nenashev updated JENKINS-12343 Action (e.g. Open) on all builds in a list in new tab/window? Just a new plugin request. Nothing to do within core and existing plugins (or no?) Change By: Oleg Nenashev (21/May/14 11:48 PM) Component/s: plugin Component/s: warnings Component/s: core Component/s: dashboard-view This message is automatically generated by JIRA. 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-client] (JENKINS-21559) Default GIT to run 'git clone' instead of 'git fetch'
Mark Waite commented on JENKINS-21559 Default GIT to run 'git clone' instead of 'git fetch' Wipe out repository and force clone is a last-ditch technique to handle those cases where the repository is no longer usable. It should generally only be needed for recovery, not for everyday operation. Wipe out workspace is the same type of operation, and I use it with about the same frequency to recover from some form of repository damage. I need to use that setting at times when I'm testing bug reports in the git plugin or the git client plugin because a repository was only partially cloned, or because a build operation damaged the contents of the git repository. If you're using Unix based (Linux, FreeBSD, OpenBSD, Solaris, HP-UX, AIX, etc.) slave agents, you could consider reducing the disc space and the clone time of your large repository by using a "reference repository" on each slave machine. A reference repository is a bare repository kept at a known location on the slave machine, referenced by Jenkins jobs which need the contents of that repository. The Jenkins job repository then include pointers into the bare repository instead of copying the content from the central repository. I've found it saves significant time on my large repositories. This message is automatically generated by JIRA. 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-15179) Restrict slaves usage for a subset of jobs
Oleg Nenashev resolved JENKINS-15179 as Fixed Restrict slaves usage for a subset of jobs https://wiki.jenkins-ci.org/display/JENKINS/Job+Restrictions+Plugin Please re-open the issue or open feature requests if you need the additional functionality in the plugin Change By: Oleg Nenashev (21/May/14 11:45 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] [core] (JENKINS-12248) Concatenate changelogs from prior failed builds
Daniel Beck commented on JENKINS-12248 Concatenate changelogs from prior failed builds if those builds are deleted the information is lost. https://wiki.jenkins-ci.org/display/JENKINS/Change+Log+History+Plugin It has one issue though, it keeps changelogs of builds older than the oldest existing build, i.e. you can easily collect hundreds or thousands of changelog.xml files on your oldest build if you have log rotation. Is this still an unresolved problem? IMO this would be better suited for a plugin as well. This message is automatically generated by JIRA. 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-17650) Build doesn't start at the slave, being cancelled automatically by unknown cause
Oleg Nenashev commented on JENKINS-17650 Build doesn't start at the slave, being cancelled automatically by unknown cause Logs and job configuration could be useful as well... Nothing to analyze here This message is automatically generated by JIRA. 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-17650) Build doesn't start at the slave, being cancelled automatically by unknown cause
Daniel Beck resolved JENKINS-17650 as Incomplete Build doesn't start at the slave, being cancelled automatically by unknown cause Report does not include Jenkins version. Change By: Daniel Beck (21/May/14 11:37 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.
[JIRA] [core] (JENKINS-16385) Not to bring up Jenkins server
Oleg Nenashev updated JENKINS-16385 Not to bring up Jenkins server The component was incorrect (BTW, it is not obvious for users). I'm not sure the issue is actual on newest versions Change By: Oleg Nenashev (21/May/14 11:37 PM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-client] (JENKINS-21559) Default GIT to run 'git clone' instead of 'git fetch'
Matt Evans commented on JENKINS-21559 Default GIT to run 'git clone' instead of 'git fetch' We have poll scm setup to poll our repos every 5 minutes. For example, we specific a job to poll origin/master for a specific project. The plugin would successfully find a new commit at the HEAD and start a new build, and create a new artifact (even referencing the new commit hash in the manifest of the artifact - using maven). When we deployed the artifact we discovered the new code didn't actually get added, even though it shows it was built off the recent commit hash. I never found the culprit,but what I did find out is this issue is resolved by enabling 'wipe out repository and force new clone'. During my analysis before making this setting change I saw in the logs it ran a simple 'git fetch'. I assumed what was happening is it was pulling down the changes from origin, but not merging them into our local branches, that Jenkins actually builds from on the file system. This is why I recommended to change it to a 'git pull'. However, our company was running a really old version of git plugin and git client plugin. We updated the git plugin from 2.0 to 2.2.1 and client plugin from 1.45 to 1.90. Now in the console output, I see it runs a 'git checkout -f commit' so hopefully that was cuasing the issues (it wasn't forcing the checkout). Although we should never have situations where a force is required. Long story short, the main goal here would be to able to disable the advanced feature of 'wipe out repository and force clone' and not have to worry that our artifacts won't have the code from the most recent commit (tip of branch). I'll try disabling this feature for some of our builds now that we have new versions, to see if I can reproduce. Hopefully I can reproduce this and we can go from there. But I'd really like to know why there is a feature 'wipe out repository and force clone' it must be to work around something, correct? It's really not ideal to clone an entire 8gb repository everytime we need a new 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] [git-client] (JENKINS-21520) NoClassDefFoundError in git client 1.6.1
Mark Waite commented on JENKINS-21520 NoClassDefFoundError in git client 1.6.1 A comment in JENKINS-20254 indicates that the ssh-credentials plugin must also be enabled. Could you double check that your ssh-credentials plugin is enabled on the failing configuration? This message is automatically generated by JIRA. 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-19142) Don't add jobs to a view
Oleg Nenashev commented on JENKINS-19142 Don't add jobs to a view There's a simple workaround. 1) Install View Job Filters Plugin. https://wiki.jenkins-ci.org/display/JENKINS/View+Job+Filters 2) Add the "Exclude all" as a first filter 3) Insert all filters you need after the first one This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-17529) Broken symlinks during creating wrtifacts
Daniel Beck resolved JENKINS-17529 as Incomplete Broken symlinks during creating wrtifacts It's not clear what the expected and actual behavior is, how to reproduce this, and the versions of Jenkins and Copy Artifacts this occurs with. Change By: Daniel Beck (21/May/14 11:30 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.
[JIRA] [other] (JENKINS-1036) job collision groups
Oleg Nenashev commented on JENKINS-1036 job collision groups Actually, throttling categories resolve the initial 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] [matrix-project] (JENKINS-17924) Matrix jobs should be able to checkout a repository just once
Daniel Beck updated JENKINS-17924 Matrix jobs should be able to checkout a repository just once Not a core issue. Change By: Daniel Beck (21/May/14 11:25 PM) Component/s: matrix-project Component/s: core Component/s: matrix This message is automatically generated by JIRA. 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-13475) Matrix Authorization Strategy for anonymous with read permission caused connection problem
Daniel Beck resolved JENKINS-13475 as Incomplete Matrix Authorization Strategy for anonymous with read permission caused connection problem Reporter did not respond to comment posted a year ago. Assuming this is obsolete. Change By: Daniel Beck (21/May/14 11:26 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.
[JIRA] [other] (JENKINS-1036) job collision groups
Oleg Nenashev resolved JENKINS-1036 as Fixed job collision groups Lock-and-latches Plugin has been deprecated https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Exclusion-Plugin https://wiki.jenkins-ci.org/display/JENKINS/Build+Blocker+Plugin ... Marking the issue as "Resolved" Change By: Oleg Nenashev (21/May/14 11:26 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] [core] (JENKINS-18071) Dead Lock - Remote Api
Daniel Beck resolved JENKINS-18071 as Duplicate Dead Lock - Remote Api Duplicates JENKINS-19446. Change By: Daniel Beck (21/May/14 11:24 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] [core] (JENKINS-14189) Discover permission gives Status Code 500 and Stacktrace
Daniel Beck commented on JENKINS-14189 Discover permission gives Status Code 500 and Stacktrace Can this issue be reproduced on recent Jenkins versions? If so, how? (Please be specific) This message is automatically generated by JIRA. 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-9536) Because the unit of build setting is called job or project, it is not consistent.
Oleg Nenashev commented on JENKINS-9536 Because the unit of build setting is called job or project, it is not consistent. Please just welcome the "Item" term in newest Jenkins versions... This message is automatically generated by JIRA. 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-9827) Display next Execution Time on Job
Oleg Nenashev resolved JENKINS-9827 as Fixed Display next Execution Time on Job The solution has been proposed, no response Change By: Oleg Nenashev (21/May/14 11:19 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] [fail-the-build-plugin] (JENKINS-9808) Ability to change the status of a build
Oleg Nenashev resolved JENKINS-9808 as Fixed Ability to change the status of a build Use "Fail The Build Plugin". Even if it does not completely fit your use-case, you could just update it https://wiki.jenkins-ci.org/display/JENKINS/Fail+The+Build+Plugin Change By: Oleg Nenashev (21/May/14 11:17 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] [fail-the-build-plugin] (JENKINS-9808) Ability to change the status of a build
Oleg Nenashev updated JENKINS-9808 Ability to change the status of a build Change By: Oleg Nenashev (21/May/14 11:18 PM) Component/s: fail-the-build-plugin Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-15361) Usability: selection buttons like "add post-build action" should close on escape
Daniel Beck resolved JENKINS-15361 as Cannot Reproduce Usability: selection buttons like "add post-build action" should close on escape Cannot reproduce on 1.564(ish, SNAPSHOT). Possibly resolved by the recent change to these menus also closing when clicking somewhere else? Change By: Daniel Beck (21/May/14 11:15 PM) Status: Open Resolved Resolution: 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] [core] (JENKINS-18375) Request handlers take forever to respond 2 (blocks)
Daniel Beck resolved JENKINS-18375 as Cannot Reproduce Request handlers take forever to respond 2 (blocks) Reporter did not update issue in almost a year, so assuming this caused no further issues. Plugins might have simply taken some time to figure out how to deal with lazy loading. Needs to be reproduced in recent Jenkins version to be relevant. Also, some view configs (like use of Project Statistics Plugin) simply are incredibly expensive as they cause all records to load. Should be better when loading the view a second time though. Change By: Daniel Beck (21/May/14 11:13 PM) Status: Open Resolved Resolution: 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] [plugin] (JENKINS-1797) Support radius authentication
Oleg Nenashev resolved JENKINS-1797 as Postponed Support radius authentication No votes/no activity. Marking as "postponed" Change By: Oleg Nenashev (21/May/14 11:14 PM) Status: Open Resolved Resolution: Postponed This message is automatically generated by JIRA. 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-3858) New builder for use when replacing Hudson configuration
Oleg Nenashev resolved JENKINS-3858 as Postponed New builder for use when replacing Hudson configuration No votes/no activity. Marking as "postponed" Change By: Oleg Nenashev (21/May/14 11:12 PM) Status: Open Resolved Resolution: Postponed This message is automatically generated by JIRA. 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-23140) Add the "ViewListener" extension point
Oleg Nenashev created JENKINS-23140 Add the "ViewListener" extension point Issue Type: New Feature Assignee: Unassigned Components: core Created: 21/May/14 11:09 PM Description: Use-cases: Modify columns on the View creation (JENKINS-17384) Send notifications on view configuration changes onCreated() onCopy() ondeleted() ... Project: Jenkins Labels: extension Priority: Major Reporter: Oleg Nenashev This message is automatically generated by JIRA. 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-client] (JENKINS-21559) Default GIT to run 'git clone' instead of 'git fetch'
Mark Waite commented on JENKINS-21559 Default GIT to run 'git clone' instead of 'git fetch' Can you expand more of what you mean when you say "the branches on our build boxes aren't updated"? When I define a job with the git plugin, I define "branches to build" as "*/master". Once I've done that, then any changes I submit to the master branch on the central repository are detected, pulled into the Jenkins job repository, and built. Those changes appear in the list as "recent changes" and are used by the build. A "merge" is not shown in the Jenkins build log because no merge is needed. The plugin checks out the tip of the branch "origin/master" by SHA1 and thus does not need to perform a merge (in that case). The plugin can be configured to perform a merge, but usually that is a merge from some other branch to the current branch, not a merge from origin/master to master. If you want to merge multiple branches before build, there is an "Additional Behaviour" "Merge before build". It's help says "These options allow you to perform a merge to a particular branch before building. For example, you could specify an integration branch to be built, and to merge to master. In this scenario, on every change of integration, Jenkins will perform a merge with the master branch, and try to perform a build if the merge is successful. It then may push the merge back to the remote repository if the Git Push post-build action is selected." This message is automatically generated by JIRA. 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-17384) Cannot specify default columns for new views
Oleg Nenashev commented on JENKINS-17384 Cannot specify default columns for new views Agreed. Actually, there's no "ViewListener" extension at all, hence the core modification is required in any case This message is automatically generated by JIRA. 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-17181) A list of all bugs/issues per project
Daniel Beck resolved JENKINS-17181 as Won't Fix A list of all bugs/issues per project This is the job of a plugin providing integration with an issue tracker. I doubt this can be solved generically in Jenkins core using an extension point. Change By: Daniel Beck (21/May/14 11:03 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-17384) Cannot specify default columns for new views
Oleg Nenashev edited a comment on JENKINS-17384 Cannot specify default columns for new views Not a bug. The feature should be implemented by a plugin, but it would require a ViewListener extension point This message is automatically generated by JIRA. 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-6645) show build parameters on mouse-over of queued/running build
Oleg Nenashev resolved JENKINS-6645 as Duplicate show build parameters on mouse-over of queued/running build No response from the submitter. Closing as duplicate according to Alan's last comment Change By: Oleg Nenashev (21/May/14 11:02 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] [core] (JENKINS-6645) show build parameters on mouse-over of queued/running build
Oleg Nenashev closed JENKINS-6645 as Duplicate show build parameters on mouse-over of queued/running build Change By: Oleg Nenashev (21/May/14 11:02 PM) 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-17384) Cannot specify default columns for new views
Daniel Beck commented on JENKINS-17384 Cannot specify default columns for new views Oleg: ListViewColumn.createDefaultInitialColumnList() is static, called from the ListView constructor. This needs to be solved in core. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-7128) Usability Issue
Oleg Nenashev resolved JENKINS-7128 as Postponed Usability Issue Marking as "Postponed", because there's no activity. Improvement proposals are unclear as well Change By: Oleg Nenashev (21/May/14 11:00 PM) Status: Open Resolved Resolution: Postponed This message is automatically generated by JIRA. 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-5150) Race condition for feature "Block build when upstream project is building"
Daniel Beck commented on JENKINS-5150 Race condition for feature "Block build when upstream project is building" Can anyone reproduce this issue on Jenkins versions released this year, or is this report obsolete? This message is automatically generated by JIRA. 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-8927) Create a view from the XML API
Daniel Beck commented on JENKINS-8927 Create a view from the XML API Oleg: Needs to be documented on the /view/Foo/api page, similar to 'Create Job' on /api. This message is automatically generated by JIRA. 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] [parameters] (JENKINS-8349) RFE: allow parameter references in paramter values
Oleg Nenashev resolved JENKINS-8349 as Postponed RFE: allow parameter references in paramter values This can be done in calling scripts. Marking as "Postponed", because there's no activity Change By: Oleg Nenashev (21/May/14 10:57 PM) Status: Open Resolved Resolution: Postponed This message is automatically generated by JIRA. 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] [active-directory] (JENKINS-9348) Error in LDAP Users list after upgrade from Hudson to Jenkins
Oleg Nenashev updated JENKINS-9348 Error in LDAP Users list after upgrade from Hudson to Jenkins Change By: Oleg Nenashev (21/May/14 10:55 PM) Component/s: matrix-auth Component/s: matrix This message is automatically generated by JIRA. 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] [update-center] (JENKINS-12514) .hpi versus .jpi causes inability to upgrade Subversion Plugin
Oleg Nenashev commented on JENKINS-12514 .hpi versus .jpi causes inability to upgrade Subversion Plugin Does anyone see the issue on newest Jenkins versions (1.532+)? This message is automatically generated by JIRA. 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-12051) Latest jenkins running on tomcat prevents me from configuring
Daniel Beck resolved JENKINS-12051 as Cannot Reproduce Latest jenkins running on tomcat prevents me from configuring Newer versions of Jenkins added robustness code to the job config page. So unless someone can show the issue still occurs in newer Jenkins versions, this report is obsolete. If you open a new issue about this or a similar problem, please also include output of your web browser's error console, and in which browsers the problem occurs. Change By: Daniel Beck (21/May/14 10:52 PM) Status: Open Resolved Resolution: 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] [subversion] (JENKINS-14550) "Checksum mismatch while updating" with Subversion Plugin 1.42
Oleg Nenashev commented on JENKINS-14550 "Checksum mismatch while updating" with Subversion Plugin 1.42 Does anyone see the issue on Subversion 2.0+? This message is automatically generated by JIRA. 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] [ldap] (JENKINS-15847) LDAP plus SASL
Oleg Nenashev closed JENKINS-15847 as Not A Defect LDAP plus SASL Change By: Oleg Nenashev (21/May/14 10:45 PM) 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-17382) Consider display name for sorting on main page
Daniel Beck resolved JENKINS-17382 as Cannot Reproduce Consider display name for sorting on main page This has been fixed some time before 1.532.3. If this still happens for you, it's likely a problem with your web browser (try others as well!). Please file a new issue in that case. Change By: Daniel Beck (21/May/14 10:45 PM) Status: Open Resolved Resolution: 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] [cli] (JENKINS-9677) add blocking call to get build id (CLI or build url)
Oleg Nenashev resolved JENKINS-9677 as Fixed add blocking call to get build id (CLI or build url) "build -w" provides such feature in newest versions Change By: Oleg Nenashev (21/May/14 10:43 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] [core] (JENKINS-18613) Smaller description boxes
Daniel Beck commented on JENKINS-18613 Smaller description boxes Is this still a problem for you? What screen resolution do you have? Could you provide (redacted) screenshots showing the problem? It's trivial to reduce from 5 to, say, 3 lines by default, but I'd like to understand the problem first. This message is automatically generated by JIRA. 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-8784) Spell equivalent CLI command for a job
Oleg Nenashev resolved JENKINS-8784 as Won't Fix Spell equivalent CLI command for a job There's no console command for any GUI operation. Such request is also impossible due to the external plugins, which should implement such features on their own. I suppose the existing help is enough. Change By: Oleg Nenashev (21/May/14 10:41 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-7566) Could you add a verbose option to cli
Oleg Nenashev resolved JENKINS-7566 as Incomplete Could you add a verbose option to cli The request is unclear and outdated. "CLI build" provides various options to get the build progress and the console output. Change By: Oleg Nenashev (21/May/14 10:39 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.
[JIRA] [distfork] (JENKINS-11323) dist-fork allows me too much privilege
Oleg Nenashev updated JENKINS-11323 dist-fork allows me too much privilege Fixed the component Change By: Oleg Nenashev (21/May/14 10:36 PM) Component/s: distfork Component/s: cli This message is automatically generated by JIRA. 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-11888) Jenkins CLI does not supports stopping jobs
Oleg Nenashev updated JENKINS-11888 Jenkins CLI does not supports stopping jobs Change By: Oleg Nenashev (21/May/14 10:35 PM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [maven2] (JENKINS-11333) Make fingerprinting configurable in Maven projects
SCM/JIRA link daemon commented on JENKINS-11333 Make fingerprinting configurable in Maven projects Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/maven/MavenModule.java src/main/java/hudson/maven/MavenModuleSet.java src/main/java/hudson/maven/reporters/MavenArtifactArchiver.java src/main/java/hudson/maven/reporters/MavenFingerprinter.java src/main/resources/hudson/maven/MavenModuleSet/configure-entries.jelly src/main/webapp/fingerprintingDisabled.html src/test/java/hudson/maven/MavenModuleSetTest.java http://jenkins-ci.org/commit/maven-plugin/33c52c897e893029631615cc5bebacd15d535454 Log: [FIXED JENKINS-11333] Allow users to disable automatic fingerprinting, but add in explicit fingerprinting if desired. This message is automatically generated by JIRA. 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] [maven2] (JENKINS-11333) Make fingerprinting configurable in Maven projects
SCM/JIRA link daemon resolved JENKINS-11333 as Fixed Make fingerprinting configurable in Maven projects Change By: SCM/JIRA link daemon (21/May/14 10:34 PM) Status: In Progress 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] [cli] (JENKINS-11888) Jenkins CLI does not supports stopping jobs
Oleg Nenashev commented on JENKINS-11888 Jenkins CLI does not supports stopping jobs The issue is actual This message is automatically generated by JIRA. 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-12899) How to create a new job using jenkins-cli.jar with specific SVN credential
Oleg Nenashev resolved JENKINS-12899 as Won't Fix How to create a new job using jenkins-cli.jar with specific SVN credential The request is outdated, because Subversion 2.0+ uses the generic cretentials management approach Change By: Oleg Nenashev (21/May/14 10:31 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-12646) API returns previous builds status
Daniel Beck resolved JENKINS-12646 as Incomplete API returns previous builds status Issue report is difficult to understand, and reporter did not respond to question asking for clarification, so closing as Incomplete. New report needs to be filed against Matrix Project plugin as well – Make sure this can be reproduced in 1.561 with Matrix Project plugin 1.2+ Change By: Daniel Beck (21/May/14 10:31 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.
[JIRA] [cli] (JENKINS-12899) How to create a new job using jenkins-cli.jar with specific SVN credential
Oleg Nenashev updated JENKINS-12899 How to create a new job using jenkins-cli.jar with specific SVN credential Fixed the component Change By: Oleg Nenashev (21/May/14 10:30 PM) Component/s: subversion This message is automatically generated by JIRA. 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-13999) The new discover permission breaks the tabbed view
Joshua ayson commented on JENKINS-13999 The new discover permission breaks the tabbed view @Daniel - I stopped trying to use Jenkins this way and got over the fact that anonymous users can see all the builds and view the logs. This message is automatically generated by JIRA. 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-13707) Job disables itself during execution, when using environment variables in repository url
Daniel Beck resolved JENKINS-13707 as Cannot Reproduce Job disables itself during execution, when using environment variables in repository url Cannot reproduce on my instance. Needs to be reproduced on a recent Jenkins version with Subversion plugin 2.4 or newer as well to still be relevant. Also, needs to specify where that variable is defined. It's possible the context is not included during polling, only during building. Change By: Daniel Beck (21/May/14 10:28 PM) Status: Open Resolved Resolution: 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] [cli] (JENKINS-13585) Need an update for JDKs installed on http://ci.jenkins-ci.org
Oleg Nenashev commented on JENKINS-13585 Need an update for JDKs installed on http://ci.jenkins-ci.org I'll move the ticket to the INFRA project This message is automatically generated by JIRA. 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-13707) Job disables itself during execution, when using environment variables in repository url
Daniel Beck updated JENKINS-13707 Job disables itself during execution, when using environment variables in repository url Change By: Daniel Beck (21/May/14 10:26 PM) Component/s: subversion Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16309) CLI errors with Job names containing dashes
Oleg Nenashev resolved JENKINS-16309 as Cannot Reproduce CLI errors with Job names containing dashes No response from the submitter after the "cannot reproduce" notification. The case work for me as well Change By: Oleg Nenashev (21/May/14 10:27 PM) Status: Open Resolved Resolution: 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] [core] (JENKINS-18689) slave unstable become online and offline
Daniel Beck resolved JENKINS-18689 as Incomplete slave unstable become online and offline Needs to be reproduced with recent Jenkins versions, with log excerpts from both Jenkins master and from the slave file system attached. If it happens again, please file a new issue so anyone investigating this doesn't confuse old and new information Change By: Daniel Beck (21/May/14 10:25 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.
