[JIRA] [git] (JENKINS-20585) Git plugin 2.0 prevents project deletion on Windows, changelog.xml is busy
SCM/JIRA link daemon commented on JENKINS-20585 Git plugin 2.0 prevents project deletion on Windows, changelog.xml is busy Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/JGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/25af38588ceb3b7850b940e587ed832423da155c Log: JENKINS-19994 Close files opened by JGit operations The JGit Repository object opens files and requires that the close() method on the repository object is called to close the files. The JGit RevWalk object documentation states that the dispose() method should be called on the RevWalk object to unlock any resources it is holding. The JGit ObjectReader documentation status that its resources should be released by calling the release() method. This change is not enough to allow workspace cleanup in all cases, since there are other cases (outside the JGit implementation) which will cause files to be kept open in the workspace. Refer to JENKINS-20585 for one example. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-19994) Unable to delete workspace
SCM/JIRA link daemon commented on JENKINS-19994 Unable to delete workspace Code changed in jenkins User: Nicolas De loof Path: src/main/java/org/jenkinsci/plugins/gitclient/ChangelogCommand.java src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java src/main/java/org/jenkinsci/plugins/gitclient/JGitAPIImpl.java src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java http://jenkins-ci.org/commit/git-client-plugin/8ffb0e7140445deb41c960eff01878b7c9f8e93d Log: Merge pull request #61 from MarkEWaite/JENKINS-19994-jgit-close-files JENKINS-19994 jgit close files Compare: https://github.com/jenkinsci/git-client-plugin/compare/7fd8d1604ea8...8ffb0e714044 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-19994) Unable to delete workspace
SCM/JIRA link daemon commented on JENKINS-19994 Unable to delete workspace Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/JGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/25af38588ceb3b7850b940e587ed832423da155c Log: JENKINS-19994 Close files opened by JGit operations The JGit Repository object opens files and requires that the close() method on the repository object is called to close the files. The JGit RevWalk object documentation states that the dispose() method should be called on the RevWalk object to unlock any resources it is holding. The JGit ObjectReader documentation status that its resources should be released by calling the release() method. This change is not enough to allow workspace cleanup in all cases, since there are other cases (outside the JGit implementation) which will cause files to be kept open in the workspace. Refer to JENKINS-20585 for one example. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21229) Possible resource leak in parser
Michal Turek
created JENKINS-21229
Possible resource leak in parser
Issue Type:
Bug
Affects Versions:
current
Assignee:
Michal Turek
Components:
sloccount
Created:
05/Jan/14 10:18 AM
Description:
If an exception occurs before the stream is closed there will be a resource leak since close() won't be called. Use try-finally pattern.
private void parse(java.io.File file, SloccountReportInterface report) throws IOException {
InputStreamReader in = new InputStreamReader(new FileInputStream(file), encoding);
this.parse(in, report);
in.close();
}
Environment:
Bug in code logic
Project:
Jenkins
Priority:
Major
Reporter:
Michal Turek
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21229) Possible resource leak in parser
Michal Turek started work on JENKINS-21229 Possible resource leak in parser Change By: Michal Turek (05/Jan/14 10:18 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21229) Possible resource leak in parser
Michal Turek commented on JENKINS-21229 Possible resource leak in parser Fixed in https://github.com/mixalturek/sloccount-plugin/commit/22fe90021f243b01905e0b4c5ba6f5e03208ac9b. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-cifs] (JENKINS-17112) Publish over CIFS shares do not persist
Horia Constantin commented on JENKINS-17112 Publish over CIFS shares do not persist Had the same problem, updated to version 0.3 today and it seems to be fixed. I'd suggest you try it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-19994) Unable to delete workspace
Mark Waite resolved JENKINS-19994 as Fixed Unable to delete workspace git client plugin 1.6.1 or git client plugin 1.7.0 (which ever is chosen as the next release version number of the git client plugin) should resolve some of the cases where this problem happens. There are likely still other cases which are not yet fixed (like the case documented in JENKINS-20585). Change By: Mark Waite (05/Jan/14 12:04 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21230) Broken HTML code on results page
Michal Turek
created JENKINS-21230
Broken HTML code on results page
Issue Type:
Bug
Affects Versions:
current
Assignee:
Michal Turek
Components:
sloccount
Created:
05/Jan/14 12:09 PM
Description:
The following code is incorrect. should not be inside , optional is missing.
http://www.w3schools.com/tags/tag_thead.asp
http://www.w3schools.com/tags/tag_tbody.asp
http://www.w3schools.com/tags/tag_tfoot.asp
${%File}
${%Language}
${%Lines}
${%Distribution}
...
...
Environment:
Incorrect code.
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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21230) Broken HTML code on results page
Michal Turek started work on JENKINS-21230 Broken HTML code on results page Change By: Michal Turek (05/Jan/14 12:09 PM) 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21230) Broken HTML code on results page
Michal Turek commented on JENKINS-21230 Broken HTML code on results page Fixed in https://github.com/mixalturek/sloccount-plugin/commit/710599c6588dc2771b96b84b63d2d65ee2fa5cf5. Total number of lines in the footer extended by total number of files and total number of folders. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-21013) Matrix project support for "Parameters from properties file"
ikedam commented on JENKINS-21013 Matrix project support for "Parameters from properties file" Pull request: https://github.com/jenkinsci/parameterized-trigger-plugin/pull/60 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [crowd2] (JENKINS-21184) SSO Appears to be Broken
Kanstantsin Shautsou commented on JENKINS-21184 SSO Appears to be Broken What crowd2 plugin version do you have now and what was before? Do you have any information in jenkins log? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [crowd2] (JENKINS-21184) SSO Appears to be Broken
Kanstantsin Shautsou assigned JENKINS-21184 to Kanstantsin Shautsou SSO Appears to be Broken Change By: Kanstantsin Shautsou (05/Jan/14 4:30 PM) Assignee: Thorsten Heit Kanstantsin Shautsou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21228) add "shell" variable into "pre-send" groovy script context
Alex Earl commented on JENKINS-21228 add "shell" variable into "pre-send" groovy script context You can already do something similar to this by putting the default pre-send script in the global config and using $DEFAULT_PRESEND_SCRIPT in the project. I am also adding the ability to use managed scripts, so I am not sure there is a big usage model for this and I think it opens a security hole I don't really want to deal with. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [crowd2] (JENKINS-21184) SSO Appears to be Broken
Jared Griffith commented on JENKINS-21184 SSO Appears to be Broken It's 1.6. I haven't seen anything in the logs unfortunately. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20928) l:breakable mishandles HTML metacharacters
SCM/JIRA link daemon commented on JENKINS-20928 l:breakable mishandles HTML metacharacters Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/Functions.java core/src/test/java/hudson/FunctionsTest.java http://jenkins-ci.org/commit/jenkins/0c455e1ecfb10a1dc2ebcd3d1c4de67623e627a3 Log: [FIXED JENKINS-20928] l:breakable mishandles HTML metacharacters (cherry picked from commit 3f1f122ff415319b6408ab89f8b3ff0bf4da597d) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-9120) RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow
SCM/JIRA link daemon commented on JENKINS-9120 RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow Code changed in jenkins User: Oliver Gondža Path: test/src/test/java/hudson/util/RingBufferLogHandlerTest.java http://jenkins-ci.org/commit/jenkins/754ef75447d83767b4485ee8b15bb097f65838c4 Log: JENKINS-9120 Add test (cherry picked from commit 777d232053488b2dcedc122529283c6e69e99c95) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18410) Use RunAction2 from TestResultAction
SCM/JIRA link daemon commented on JENKINS-18410 Use RunAction2 from TestResultAction Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/tasks/junit/JUnitResultArchiver.java core/src/main/java/hudson/tasks/junit/TestResultAction.java core/src/main/java/hudson/tasks/test/AbstractTestResultAction.java core/src/main/java/hudson/tasks/test/AggregatedTestResultAction.java core/src/main/java/hudson/tasks/test/AggregatedTestResultPublisher.java core/src/main/java/hudson/tasks/test/MatrixTestResult.java core/src/main/java/hudson/tasks/test/TestResultAggregator.java test/src/test/java/hudson/tasks/test/TrivialTestResultAction.java test/src/test/java/hudson/tasks/test/TrivialTestResultRecorder.java http://jenkins-ci.org/commit/jenkins/b53770c70f53084bb98e61985a6a9ba0bebdeb75 Log: [FIXED JENKINS-18410] AbstractTestResultAction should be a RunAction2 so it need not persist its owning build. (cherry picked from commit fcdf74991226fb6869052caa89ed8d678944b6fc) Conflicts: changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-9120) RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow
SCM/JIRA link daemon commented on JENKINS-9120 RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow Code changed in jenkins User: Josh Gibbs Path: core/src/main/java/hudson/util/RingBufferLogHandler.java http://jenkins-ci.org/commit/jenkins/9cc2bc21307326fd8f92a0c67401d17357ab0390 Log: [FIXED JENKINS-9120] RingBufferLogHandler has int that needs to be reset. (cherry picked from commit 67838866c6c851adc8e39dbd20ff81a434cf6cc6) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21078) Loading projects too slow because of File.isDirectory calls
SCM/JIRA link daemon commented on JENKINS-21078 Loading projects too slow because of File.isDirectory calls Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/RunMap.java core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java http://jenkins-ci.org/commit/jenkins/70989d965fd630134b38b610f19a3661e65ceb5f Log: [FIXED JENKINS-21078] Optimizing loadIdOnDisk. (cherry picked from commit a6e01f77c6d3d72f7ac9e99ce061ce04dbf4b515) Conflicts: changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-17929) Fail to run 'groovysh' in CLI due to insufficient permission
SCM/JIRA link daemon commented on JENKINS-17929 Fail to run 'groovysh' in CLI due to insufficient permission Code changed in jenkins User: Jesse Glick Path: http://jenkins-ci.org/commit/jenkins/0b2068661dec858d585dba9855b6127793611663 Log: JENKINS-17929 Noting that authentication does not work in the groovysh command. (cherry picked from commit b9e227e65bff87949d46fc4313020428f48d0fa4) Conflicts: core/src/main/java/hudson/cli/GroovyshCommand.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [crowd2] (JENKINS-21184) SSO Appears to be Broken
Jared Griffith commented on JENKINS-21184 SSO Appears to be Broken Here's the only thing in the logs: Jan 05, 2014 9:36:57 AM de.theit.jenkins.crowd.CrowdConfigurationService INFO: Groups given for Crowd configuration service: tech Jan 05, 2014 9:36:57 AM com.atlassian.crowd.service.client.ClientPropertiesImpl loadAndLogPropertyString INFO: Loading property: 'application.name' : 'jenkins' Jan 05, 2014 9:36:57 AM com.atlassian.crowd.service.client.ClientPropertiesImpl loadAndLogPropertyString INFO: Loading property: 'application.login.url' : 'http://crowd.picsauditing.com:8095/crowd/console/' Jan 05, 2014 9:36:57 AM com.atlassian.crowd.service.client.ClientPropertiesImpl loadAndLogPropertyString INFO: Loading property: 'session.tokenkey' : 'session.tokenkey' Jan 05, 2014 9:36:57 AM com.atlassian.crowd.service.client.ClientPropertiesImpl loadAndLogPropertyString INFO: Loading property: 'session.lastvalidation' : 'session.lastvalidation' Jan 05, 2014 9:36:57 AM com.atlassian.crowd.service.client.ClientPropertiesImpl loadAndLogPropertyString INFO: Loading property: 'session.validationinterval' : '2' Jan 05, 2014 9:36:57 AM com.atlassian.crowd.service.client.ClientPropertiesImpl loadAndLogPropertyString INFO: Failed to find value for property: cookie.domain Also, I don't know if I had upgraded the Crowd2 plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18410) Use RunAction2 from TestResultAction
SCM/JIRA link daemon commented on JENKINS-18410 Use RunAction2 from TestResultAction Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/tasks/test/AggregatedTestResultPublisher.java test/src/test/java/hudson/tasks/test/AggregatedTestResultPublisherTest.java http://jenkins-ci.org/commit/jenkins/b5ec39f0734d05f1de05406a2dddc0bed4440d60 Log: JENKINS-18410 NPE from previous fix (fcdf749) under some conditions, which the test case was not exercising. java.lang.NullPointerException at hudson.tasks.test.AggregatedTestResultPublisher$TestResultAction.getProject(AggregatedTestResultPublisher.java:173) at hudson.tasks.test.AggregatedTestResultPublisher$TestResultAction.(AggregatedTestResultPublisher.java:146) at hudson.tasks.test.AggregatedTestResultPublisher$TestResultAction.(AggregatedTestResultPublisher.java:135) at hudson.tasks.test.AggregatedTestResultPublisher.perform(AggregatedTestResultPublisher.java:90) (cherry picked from commit bfaab5118d079405b82b80301d90e19f39970366) Conflicts: changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-17929) Fail to run 'groovysh' in CLI due to insufficient permission
SCM/JIRA link daemon commented on JENKINS-17929 Fail to run 'groovysh' in CLI due to insufficient permission Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/cli/CLICommand.java core/src/main/java/hudson/cli/GroovyshCommand.java test/src/main/java/hudson/cli/CLICommandInvoker.java test/src/test/java/hudson/cli/GroovyshCommandTest.java http://jenkins-ci.org/commit/jenkins/6d88c0175cba3d96273da58b4c3a0e57fcd36203 Log: [FIXED JENKINS-17929] Pick up transport authentication from groovysh command, by overriding run rather than main. (cherry picked from commit 3896aabc0bee39fd94366f5b2dd6bc191c040e40) Conflicts: changelog.html core/src/main/java/hudson/cli/GroovyshCommand.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Pedro Algarvio commented on JENKINS-14546 Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated Using 1.5.45, this is still present for, at least, list views. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21228) add "shell" variable into "pre-send" groovy script context
Mike Dubman commented on JENKINS-21228 add "shell" variable into "pre-send" groovy script context Thanks you for quick reply. The problem with setting $DEFAULT_PRESEND_SCRIPT is that it accepts "string script" only. having a way to load script from file is more friendly for admin who can "vi" and change behave, w/o changing jenkins config. What type of security hole do you mean? The job config is a privilege operation and available for sys-adm type users. btw, the reason I wish to have it, is to be able fetch console log from failed slaves and attach it to the email. Currently, we do it as part of post-build action script on every slave, which "wget"`s console into file which is then picked by pre-send script from parent job. Do you see more elegant way to do it from pre-send script only? 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/groups/opt_out.
[JIRA] [xunit] (JENKINS-18277) Testcase isn't marked as failed
Ivan Kurnosov commented on JENKINS-18277 Testcase isn't marked as failed @Gregory Boissinot, Here is the configuration that is reproduces the issue false "hudson.scm.NullSCM"/> true false false false "vector"/> false log.xml false true true true 1 So you just create a log file with contents I attached in the ticket and get successful job, whereas there is one test failed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20231) Wipe out repository & force clone option is broken since GIT plugin version 2.0
jpschewe commented on JENKINS-20231 Wipe out repository & force clone option is broken since GIT plugin version 2.0 Manually wiping out a workspace and trying to clone again is broken too. I'm using Jenkins 1.509.4 with git plugin 2.0 and I can't get the repository to clone because of this error: 16:14:02 Started by user Jon Schewe 16:14:02 Building in workspace /home/hudson/.hudson/jobs/fll-sw-feature-branches/workspace 16:14:02 Pruning obsolete local branches 16:14:02 FATAL: Command "git config --get remote.origin.url" returned status code 1: 16:14:02 stdout: 16:14:02 stderr: 16:14:02 hudson.plugins.git.GitException: Command "git config --get remote.origin.url" returned status code 1: 16:14:02 stdout: 16:14:02 stderr: 16:14:02 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1099) 16:14:02 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1076) 16:14:02 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:917) 16:14:02 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:927) 16:14:02 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteUrl(CliGitAPIImpl.java:656) 16:14:02 at hudson.plugins.git.GitAPI.getRemoteUrl(GitAPI.java:61) 16:14:02 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.prune(CliGitAPIImpl.java:446) 16:14:02 at hudson.plugins.git.extensions.impl.PruneStaleBranch.beforeCheckout(PruneStaleBranch.java:31) 16:14:02 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:858) 16:14:02 at hudson.model.AbstractProject.checkout(AbstractProject.java:1376) 16:14:02 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:655) 16:14:02 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) 16:14:02 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560) 16:14:02 at hudson.model.Run.execute(Run.java:1592) 16:14:02 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 16:14:02 at hudson.model.ResourceController.execute(ResourceController.java:88) 16:14:02 at hudson.model.Executor.run(Executor.java:237) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20231) Wipe out repository & force clone option is broken since GIT plugin version 2.0
jpschewe commented on JENKINS-20231 Wipe out repository & force clone option is broken since GIT plugin version 2.0 I'm using Jenkins 1.509.4 and Git Plugin 2.0 and I can't clone my git repository after manually wiping out my workspace. 16:14:02 Started by user Jon Schewe 16:14:02 Building in workspace /home/hudson/.hudson/jobs/fll-sw-feature-branches/workspace 16:14:02 Pruning obsolete local branches 16:14:02 FATAL: Command "git config --get remote.origin.url" returned status code 1: 16:14:02 stdout: 16:14:02 stderr: 16:14:02 hudson.plugins.git.GitException: Command "git config --get remote.origin.url" returned status code 1: 16:14:02 stdout: 16:14:02 stderr: 16:14:02 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1099) 16:14:02 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1076) 16:14:02 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:917) 16:14:02 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:927) 16:14:02 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteUrl(CliGitAPIImpl.java:656) 16:14:02 at hudson.plugins.git.GitAPI.getRemoteUrl(GitAPI.java:61) 16:14:02 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.prune(CliGitAPIImpl.java:446) 16:14:02 at hudson.plugins.git.extensions.impl.PruneStaleBranch.beforeCheckout(PruneStaleBranch.java:31) 16:14:02 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:858) 16:14:02 at hudson.model.AbstractProject.checkout(AbstractProject.java:1376) 16:14:02 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:655) 16:14:02 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) 16:14:02 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560) 16:14:02 at hudson.model.Run.execute(Run.java:1592) 16:14:02 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 16:14:02 at hudson.model.ResourceController.execute(ResourceController.java:88) 16:14:02 at hudson.model.Executor.run(Executor.java:237) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20231) Wipe out repository & force clone option is broken since GIT plugin version 2.0
jpschewe edited a comment on JENKINS-20231 Wipe out repository & force clone option is broken since GIT plugin version 2.0 Any chance this can get fixed soon? This seems like a pretty basic problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21196) Thread has died
vjuranek commented on JENKINS-21196 Thread has died Hi, is there any reproducer? This was introduced in 06c211c6b425e313f and IMHO it's correct as parent build shouldn't be null, so I wonder, how it could happen (maybe some plugin like MatrixReloaded?). 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/groups/opt_out.
[JIRA] [deploy] (JENKINS-12825) Allow expansion of environment variables in the configuration
Wojtek TRocki commented on JENKINS-12825 Allow expansion of environment variables in the configuration If anyone interested: It's fixed on my fork: https://github.com/fexcowtr/deploy-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-poll-action] (JENKINS-21231) /poll/ leads to a redirect loop
Nathaniel Irons created JENKINS-21231 /poll/ leads to a redirect loop Issue Type: Bug Affects Versions: current Assignee: jieryn Components: job-poll-action Created: 06/Jan/14 6:43 AM Description: After installing Job Poll Action 1.0 on Jenkins 1.545, the "Poll SCM" link appears in the job sidebar, but clicking it (which leads to http://jenkinshost/job/jobname/poll) results in a redirect loop, and does not trigger a poll. Project: Jenkins Priority: Major Reporter: Nathaniel Irons This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-13887) Ability to change the Bundle identifier (CFBundleIdentifier) for an xcode build
Esteban Bouza started work on JENKINS-13887 Ability to change the Bundle identifier (CFBundleIdentifier) for an xcode build Change By: Esteban Bouza (06/Jan/14 6:53 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/groups/opt_out.
[JIRA] [ghprb] (JENKINS-19123) ghprb prevents Jenkins cron thread from running
Ray Sennewald commented on JENKINS-19123 ghprb prevents Jenkins cron thread from running I've seen the same behavior as well on our Jenkins servers running GHPRB. This only happens from time to time, and the temporary fix is to reboot Jenkins when this occurs. Would be nice if we could have a timeout for these as recampbell mentioned. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
