[JIRA] [docker-build-step] (JENKINS-23704) Control over ports with docker build steps
vjuranek reopened JENKINS-23704 Control over ports with docker build steps Reopening - I forgot to implement exporting ports as evn. vars. Change By: vjuranek (03/Aug/14 8:03 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
vjuranek commented on JENKINS-23693 Cannot delete workspace I've just released ws-clenaup 0.22 which contains small fix for expanding env. var. on nodes and may be related to this issue. Could you please try it and let me know if it fixes the issue? If not, could anyone provide a reproducer for this issue? Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-20307) Job status page shows Build has been executing for null on master
Daniel Beck updated JENKINS-20307 Job status page shows Build has been executing for null on master Change By: Daniel Beck (03/Aug/14 9:53 AM) Status: Reopened Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-20307) Job status page shows Build has been executing for null on master
Daniel Beck started work on JENKINS-20307 Job status page shows Build has been executing for null on master Change By: Daniel Beck (03/Aug/14 9:53 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24088) Stack trace java.lang.OutOfMemoryError: Java heap space
Daniel Beck updated JENKINS-24088 Stack trace java.lang.OutOfMemoryError: Java heap space Change By: Daniel Beck (03/Aug/14 11:18 AM) Component/s: core 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] [core] (JENKINS-24088) Stack trace java.lang.OutOfMemoryError: Java heap space
Daniel Beck resolved JENKINS-24088 as Not A Defect Stack trace java.lang.OutOfMemoryError: Java heap space Not a defect: Jenkins needs more memory than what the JVM is currently allowed. Please do a web search to find out how to do that. Change By: Daniel Beck (03/Aug/14 11:19 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24091) Support for Git Plugin localBranch extension
Christian Galsterer created JENKINS-24091 Support for Git Plugin localBranch extension Issue Type: New Feature Assignee: Christian Galsterer Components: job-dsl-plugin Created: 03/Aug/14 11:43 AM Project: Jenkins Priority: Major Reporter: Christian Galsterer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [promoted-builds] (JENKINS-20492) Re-Execute promotion button is gone
Scott Roberts commented on JENKINS-20492 Re-Execute promotion button is gone The only work around I found for this issue is to make sure you do an 'Approve' promotion first instead of 'Force Promotion'. If you do a force promotion first, there is no re-execute. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24092) Matrix Project Plugin- Success and Failed filter: doesn't work
Aviv Yam created JENKINS-24092 Matrix Project Plugin- Success and Failed filter: doesnt work Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: Capture.PNG Components: matrix-project, plugin Created: 03/Aug/14 1:22 PM Description: currently, when trying to hit the Success OR Failed filters under the matrix job table, it doesn't mark the related jobs (Success OR Failed). Please see attached. Project: Jenkins Priority: Major Reporter: Aviv Yam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24032) Jenkins offers restart even though its Lifecycle does not support it
Daniel Beck started work on JENKINS-24032 Jenkins offers restart even though its Lifecycle does not support it Change By: Daniel Beck (03/Aug/14 1:31 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24091) Support for Git Plugin localBranch extension
Christian Galsterer started work on JENKINS-24091 Support for Git Plugin localBranch extension Change By: Christian Galsterer (03/Aug/14 2:00 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24091) Support for Git Plugin localBranch extension
Christian Galsterer commented on JENKINS-24091 Support for Git Plugin localBranch extension PR available at https://github.com/jenkinsci/job-dsl-plugin/pull/253 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration Hi Martin, Some good news. I noticed your recent changes and I pulled them to my fork ( https://github.com/alexouzounis/jenkins-inheritance-plugin ) which in turn is a fork of https://github.com/afitz/jenkins-inheritance-plugin because I need the changes for the SCM trigger etc. As a quick Sunday project I pulled your changes from https://github.com/i-m-c/jenkins-inheritance-plugin and apart from a few conflicts in the InheritanceGovernor the merge went fine. Rebooted Jenkins and it seems that now the Role Strategy plugins works as expected. Creating a role for some inheritance projects to have build rights works now as expected. As far as I am concerned the issue is now resolved from your latest changes and the ticket can be closed. It would be nice though for you to merge the changes from https://github.com/afitz/jenkins-inheritance-plugin ( I think there is a pull request from him already ) so that we can stop maintaining our own forks. Thanks, Alex This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration please ignore the above comment.. unfortunately I spoke too soon.. I just had a misconfiguration in the role strategies.. Well it was worth the try anyway.. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis edited a comment on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration Hi Martin, Some good news. I noticed your recent changes and I pulled them to my fork ( https://github.com/alexouzounis/jenkins-inheritance-plugin ) which in turn is a fork of https://github.com/afitz/jenkins-inheritance-plugin because I need the changes for the SCM trigger etc. As a quick Sunday project I pulled your changes from https://github.com/i-m-c/jenkins-inheritance-plugin and apart from a few conflicts in the InheritanceGovernor the merge went fine. Rebooted Jenkins and it seems that now the Role Strategy plugins works as expected. Creating a role for some inheritance projects to have build rights works now as expected. As far as I am concerned the issue is now resolved from your latest changes and the ticket can be closed. It would be nice though for you to merge the changes from https://github.com/afitz/jenkins-inheritance-plugin ( I think there is a pull request from him already ) so that we can stop maintaining our own forks. Thanks, Alex == UPATE: see comment below, still it does not work This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis edited a comment on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration please ignore the above comment.. unfortunately I spoke too soon.. I just had a misconfiguration in the role strategies.. Well it was worth the try anyway.. All I get is: INFO: While serving http://JENKINS_HOME/job/JOB_TO_BUILD/build: hudson.security.AccessDeniedException2: USER is missing the Job/Build permission no exception or anything which is rather confusing This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [promoted-builds] (JENKINS-20492) Re-Execute promotion button is gone
Trey Duskin commented on JENKINS-20492 Re-Execute promotion button is gone I don't seem to have an 'Approve' button, only a 'Force Promotion' button. I'm doing manual approvals only, and the only thing the promotion does is trigger a downstream parameterized deploy job. It is strange, though, because the help text indicates there should be an 'Approve' button in the UI. I'm using plugin version 2.17 and Jenkins version 1.568 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration found the bug and fixed it in my fork. The problem was in the doBuild method of the InheritanceProject where you call the ACL to see if the user has permissions to build. Problem was you were not using the super method checkPermission from the AbstractItem but implementing your self. here is my commit: https://github.com/alexouzounis/jenkins-inheritance-plugin/commit/05263af27577387f8c4b014a60a11ec94a0a81ef As you can see, what was currently happening is: ACL acl = Jenkins.getInstance().getACL(); acl.checkPermission(BUILD); whereas the super.checkPermission does: Jenkins.getInstance().getAuthorizationStrategy().getACL(this).checkPermission(BUILD); The difference is that before the ROOT ACL was used (i.e. the global config) whereas not it also taken into account permissions available specify to that project. Feel free to merge back. Alex This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis edited a comment on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration found the bug and fixed it in my fork. The problem was in the doBuild method of the InheritanceProject where you call the ACL to see if the user has permissions to build. Problem was you were not using the super method checkPermission from the AbstractItem but implementing it your self. here is my commit: https://github.com/alexouzounis/jenkins-inheritance-plugin/commit/05263af27577387f8c4b014a60a11ec94a0a81ef As you can see, what was currently happening is: ACL acl = Jenkins.getInstance().getACL(); acl.checkPermission(BUILD); whereas the super.checkPermission does: Jenkins.getInstance().getAuthorizationStrategy().getACL(this).checkPermission(BUILD); The difference is that before the ROOT ACL was used (i.e. the global config) whereas not it also taken into account permissions available specify to that project. Feel free to merge back. Alex This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis edited a comment on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration found the bug and fixed it in my fork. The problem was in the doBuild method of the InheritanceProject where you call the ACL to see if the user has permissions to build. Problem was you were not using the super method checkPermission from the AbstractItem but implementing it your self. here is my commit: https://github.com/alexouzounis/jenkins-inheritance-plugin/commit/05263af27577387f8c4b014a60a11ec94a0a81ef As you can see, what was currently happening is: ACL acl = Jenkins.getInstance().getACL(); acl.checkPermission(BUILD); whereas the super.checkPermission does: Jenkins.getInstance().getAuthorizationStrategy().getACL(this).checkPermission(BUILD); The difference is that before the ROOT ACL was used (i.e. the global config) whereas now it also takes into account permissions available specifically for that project. Feel free to merge back. Alex This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sloccount] (JENKINS-24093) Clean jelly code
Michal Turek started work on JENKINS-24093 Clean jelly code Change By: Michal Turek (03/Aug/14 3:31 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sloccount] (JENKINS-24093) Clean jelly code
Michal Turek created JENKINS-24093 Clean jelly code Issue Type: Task Affects Versions: current Assignee: Michal Turek Components: sloccount Created: 03/Aug/14 3:31 PM Description: There are some errors and warnings reported by IDE in jelly files, solve them. Environment: all Project: Jenkins Priority: Minor Reporter: Michal Turek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-11337) Git plugin only triggers a build for one branch
Mark Waite closed JENKINS-11337 as Fixed Git plugin only triggers a build for one branch Was fixed a long time ago. Confirmed still working as expected with git client plugin 1.10.1 and git plugin 2.2.2 Change By: Mark Waite (03/Aug/14 3:46 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] [sloccount] (JENKINS-24093) Clean jelly code
SCM/JIRA link daemon commented on JENKINS-24093 Clean jelly code Code changed in jenkins User: Michal Turek Path: src/main/resources/hudson/plugins/sloccount/SloccountBuildAction/summary.jelly src/main/resources/hudson/plugins/sloccount/SloccountProjectAction/floatingBox.jelly src/main/resources/hudson/plugins/sloccount/SloccountPublisher/config.jelly src/main/resources/hudson/plugins/sloccount/SloccountResult/files.jelly src/main/resources/hudson/plugins/sloccount/SloccountResult/folders.jelly src/main/resources/hudson/plugins/sloccount/SloccountResult/index.jelly src/main/resources/hudson/plugins/sloccount/SloccountResult/languages.jelly src/main/resources/hudson/plugins/sloccount/SloccountResult/modules.jelly src/main/resources/hudson/plugins/sloccount/dashboard/SloccountTablePortlet/portlet.jelly src/main/resources/hudson/plugins/sloccount/dashboard/SloccountTablePortlet/table.jelly src/main/resources/tabview/css.jelly src/main/resources/tabview/distribution-graph.jelly src/main/resources/tabview/main.jelly http://jenkins-ci.org/commit/sloccount-plugin/2c4cba54121082b50b0d0f3dc6d8b05067c45844 Log: Merge pull request #43 from mixalturek/master JENKINS-24093 Clean jelly code Compare: https://github.com/jenkinsci/sloccount-plugin/compare/891f749ecc0d...2c4cba541210 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sloccount] (JENKINS-24093) Clean jelly code
SCM/JIRA link daemon commented on JENKINS-24093 Clean jelly code Code changed in jenkins User: Michal Turek Path: src/main/resources/hudson/plugins/sloccount/SloccountBuildAction/summary.jelly src/main/resources/hudson/plugins/sloccount/SloccountProjectAction/floatingBox.jelly src/main/resources/hudson/plugins/sloccount/SloccountPublisher/config.jelly src/main/resources/hudson/plugins/sloccount/SloccountResult/files.jelly src/main/resources/hudson/plugins/sloccount/SloccountResult/folders.jelly src/main/resources/hudson/plugins/sloccount/SloccountResult/index.jelly src/main/resources/hudson/plugins/sloccount/SloccountResult/languages.jelly src/main/resources/hudson/plugins/sloccount/SloccountResult/modules.jelly src/main/resources/hudson/plugins/sloccount/dashboard/SloccountTablePortlet/portlet.jelly src/main/resources/hudson/plugins/sloccount/dashboard/SloccountTablePortlet/table.jelly src/main/resources/tabview/css.jelly src/main/resources/tabview/distribution-graph.jelly src/main/resources/tabview/main.jelly http://jenkins-ci.org/commit/sloccount-plugin/36b251776c2bb886c3531bc25a1a7e48f9aaa3d0 Log: JENKINS-24093 Clean jelly code This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sloccount] (JENKINS-24093) Clean jelly code
Michal Turek resolved JENKINS-24093 as Fixed Clean jelly code Version 1.20. Change By: Michal Turek (03/Aug/14 4:28 PM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sloccount] (JENKINS-24094) Folding help in configuration
Michal Turek created JENKINS-24094 Folding help in configuration Issue Type: Improvement Affects Versions: current Assignee: Michal Turek Components: sloccount Created: 03/Aug/14 5:13 PM Description: Update the configuration page to use folding help for all fields instead of long hard coded texts. Environment: all Project: Jenkins Priority: Minor Reporter: Michal Turek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sloccount] (JENKINS-24094) Folding help in configuration
SCM/JIRA link daemon commented on JENKINS-24094 Folding help in configuration Code changed in jenkins User: Michal Turek Path: src/main/resources/hudson/plugins/sloccount/SloccountPublisher/config.jelly src/main/resources/hudson/plugins/sloccount/SloccountPublisher/config.properties src/main/resources/hudson/plugins/sloccount/SloccountPublisher/config_de.properties src/main/resources/hudson/plugins/sloccount/SloccountPublisher/config_ja.properties src/main/resources/hudson/plugins/sloccount/SloccountPublisher/help-encoding.html src/main/resources/hudson/plugins/sloccount/SloccountPublisher/help-encoding_de.html src/main/resources/hudson/plugins/sloccount/SloccountPublisher/help-encoding_ja.html src/main/resources/hudson/plugins/sloccount/SloccountPublisher/help-numBuildsInGraph.html src/main/resources/hudson/plugins/sloccount/SloccountPublisher/help-pattern.html src/main/resources/hudson/plugins/sloccount/SloccountPublisher/help-pattern_de.html src/main/resources/hudson/plugins/sloccount/SloccountPublisher/help-pattern_ja.html http://jenkins-ci.org/commit/sloccount-plugin/0a4c1fb75b874f98c693c808123abd70b70879fb Log: JENKINS-24094 Folding help in 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] [sloccount] (JENKINS-24094) Folding help in configuration
Michal Turek resolved JENKINS-24094 as Fixed Folding help in configuration Implemented, will be released in version 1.20. Change By: Michal Turek (03/Aug/14 5:43 PM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sloccount] (JENKINS-24094) Folding help in configuration
Michal Turek started work on JENKINS-24094 Folding help in configuration Change By: Michal Turek (03/Aug/14 5:42 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sloccount] (JENKINS-24094) Folding help in configuration
SCM/JIRA link daemon commented on JENKINS-24094 Folding help in configuration Code changed in jenkins User: Michal Turek Path: src/main/java/hudson/plugins/sloccount/SloccountChartBuilder.java src/main/resources/hudson/plugins/sloccount/Messages.properties src/main/resources/hudson/plugins/sloccount/SloccountPublisher/config.jelly src/main/resources/hudson/plugins/sloccount/SloccountPublisher/config.properties src/main/resources/hudson/plugins/sloccount/SloccountPublisher/config_de.properties src/main/resources/hudson/plugins/sloccount/SloccountPublisher/config_ja.properties src/main/resources/hudson/plugins/sloccount/SloccountPublisher/help-encoding.html src/main/resources/hudson/plugins/sloccount/SloccountPublisher/help-encoding_de.html src/main/resources/hudson/plugins/sloccount/SloccountPublisher/help-encoding_ja.html src/main/resources/hudson/plugins/sloccount/SloccountPublisher/help-numBuildsInGraph.html src/main/resources/hudson/plugins/sloccount/SloccountPublisher/help-pattern.html src/main/resources/hudson/plugins/sloccount/SloccountPublisher/help-pattern_de.html src/main/resources/hudson/plugins/sloccount/SloccountPublisher/help-pattern_ja.html http://jenkins-ci.org/commit/sloccount-plugin/8d04f3daebc63c286131bcf74546f74835633098 Log: Merge pull request #44 from mixalturek/master JENKINS-24094 Folding help in configuration Compare: https://github.com/jenkinsci/sloccount-plugin/compare/2c4cba541210...8d04f3daebc6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cppcheck] (JENKINS-24037) CPPCheck Plugin: You need worspace message instead of workspace
Michal Turek assigned JENKINS-24037 to Michal Turek CPPCheck Plugin: You need worspace message instead of workspace Change By: Michal Turek (03/Aug/14 5:50 PM) Assignee: GregoryBoissinot MichalTurek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cppcheck] (JENKINS-24037) CPPCheck Plugin: You need worspace message instead of workspace
Michal Turek started work on JENKINS-24037 CPPCheck Plugin: You need worspace message instead of workspace Change By: Michal Turek (03/Aug/14 5:50 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-24037) CPPCheck Plugin: You need worspace message instead of workspace
SCM/JIRA link daemon commented on JENKINS-24037 CPPCheck Plugin: You need worspace message instead of workspace Code changed in jenkins User: Michal Turek Path: src/main/resources/com/thalesgroup/hudson/plugins/cppcheck/CppcheckProjectAction/nodata.jelly src/main/resources/com/thalesgroup/hudson/plugins/cppcheck/CppcheckResult/nosourcepermission.jelly src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckProjectAction/nodata.jelly src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckResult/nosourcepermission.jelly http://jenkins-ci.org/commit/cppcheck-plugin/aca8ecb08112ca265cf3dd1344aef942813c930b Log: JENKINS-24037 CPPCheck Plugin: You need "worspace" message instead of "workspace" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cppcheck] (JENKINS-24037) CPPCheck Plugin: You need worspace message instead of workspace
SCM/JIRA link daemon commented on JENKINS-24037 CPPCheck Plugin: You need worspace message instead of workspace Code changed in jenkins User: Michal Turek Path: src/main/resources/com/thalesgroup/hudson/plugins/cppcheck/CppcheckProjectAction/nodata.jelly src/main/resources/com/thalesgroup/hudson/plugins/cppcheck/CppcheckResult/nosourcepermission.jelly src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckProjectAction/nodata.jelly src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckResult/nosourcepermission.jelly http://jenkins-ci.org/commit/cppcheck-plugin/53b0e1f3a40ace4f04c62d1bb1f1e741aaf785f3 Log: Merge pull request #23 from mixalturek/master JENKINS-24037 CPPCheck Plugin: You need "worspace" message instead of ... Compare: https://github.com/jenkinsci/cppcheck-plugin/compare/61e07237bdd4...53b0e1f3a40a This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cppcheck] (JENKINS-24037) CPPCheck Plugin: You need worspace message instead of workspace
Michal Turek resolved JENKINS-24037 as Fixed CPPCheck Plugin: You need worspace message instead of workspace Fixed, will be released in version 1.20. Change By: Michal Turek (03/Aug/14 5:54 PM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24019) Absolute URLs in delivery pipeline break reverse proxy setups
Patrik Boström commented on JENKINS-24019 Absolute URLs in delivery pipeline break reverse proxy setups Verified fix on a Apache SSL frontend proxying Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24019) Absolute URLs in delivery pipeline break reverse proxy setups
Patrik Boström commented on JENKINS-24019 Absolute URLs in delivery pipeline break reverse proxy setups Merged PR https://github.com/Diabol/delivery-pipeline-plugin/pull/74 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24019) Absolute URLs in delivery pipeline break reverse proxy setups
Patrik Boström resolved JENKINS-24019 as Fixed Absolute URLs in delivery pipeline break reverse proxy setups Change By: Patrik Boström (03/Aug/14 6:10 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-22472) CommandDuringBuild not automatically authenticated
Daniel Beck commented on JENKINS-22472 CommandDuringBuild not automatically authenticated Make it an extension point and allow users to choose their favorite compromise of security vs. convenience, with the default a neutral "don't authenticate", a bit like the current markup formatter config? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-17957) Crowd plugin - remember me doesn't work
Kanstantsin Shautsou commented on JENKINS-17957 Crowd plugin - remember me doesnt work Could you try new 1.8 version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-17957) Crowd plugin - remember me doesn't work
Nathan Neulinger commented on JENKINS-17957 Crowd plugin - remember me doesnt work Just deployed 1.8. No longer generates an exception. Note - it doesn't actually "remember me", but at least it doesn't crash. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-17957) Crowd plugin - remember me doesn't work
knalli commented on JENKINS-17957 Crowd plugin - remember me doesnt work Yep, I can confirm 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] [crowd2] (JENKINS-17957) Crowd plugin - remember me doesn't work
Kanstantsin Shautsou commented on JENKINS-17957 Crowd plugin - remember me doesnt work 1) List cookies for your jenkins. I have ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE that marked as Expired on +14 days 2) add org.acegisecurity.ui.rememberme to jenkins logging (in "manage jenkins"-"System logging") 3) close browser 4) open browser and go to jenkins, without loggin check what cookies exist (at firefox ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE disappeared) And again, what browser do you use? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-17957) Crowd plugin - remember me doesn't work
Kanstantsin Shautsou edited a comment on JENKINS-17957 Crowd plugin - remember me doesnt work 1) List cookies for your jenkins. I have ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE that marked as Expired on +14 days 2) add org.acegisecurity.ui.rememberme to jenkins logging (in "manage jenkins"-"System logging") 3) close browser 4) open browser and go to jenkins, without loggin check what cookies exist (at firefox ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE disappeared) 5) navigate to jenkins log and check messages... And again, what browser do you use? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-17957) Crowd plugin - remember me doesn't work
Nathan Neulinger commented on JENKINS-17957 Crowd plugin - remember me doesnt work Personally, the lack of remember me is an annoyance, but at least it's not crashing the page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-17957) Crowd plugin - remember me doesn't work
Kanstantsin Shautsou commented on JENKINS-17957 Crowd plugin - remember me doesnt work Could you join to IRC freenode.net on #jenkins channel it will be easier for me to compare configurations? And again, crash was only when you checked "remember me" auth was working. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Frédéric Camblor commented on JENKINS-22820 Changes are not commited when using a recent git client ok, since it was quite a long time (sorry for the late reply ), I would have thought you tested with a version before 1.9 (which seems to contain a fix for the --porcelain command line) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24095) When node is active, reducing number of executors does not reflect reality
Marco Zanchi created JENKINS-24095 When node is active, reducing number of executors does not reflect reality Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 04/Aug/14 4:05 AM Description: I have a node with 3 executors. There is currently a job running against that node. I go to the configuration page for that node and change the number of executors to 1. The node now has 2 executors, instead of 1. If I do the same procedure on an idle node, it reduces the number of executors to 1 correctly. Project: Jenkins Priority: Minor Reporter: Marco Zanchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
