[JIRA] (JENKINS-55106) Build stuck on final "exit 0"
Title: Message Title Shawn Baker edited a comment on JENKINS-55106 Re: Build stuck on final "exit 0" Any progress with this? I understand that there is a workaround, but shouldn't the issue commit that broke it be looked at to at least see why it's broken? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196167.1544451681000.9118.1562959741566%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55106) Build stuck on final "exit 0"
Title: Message Title Shawn Baker commented on JENKINS-55106 Re: Build stuck on final "exit 0" Any progress with this? I understand that there is a workaround, but shouldn't the issue that broke it be looked at to at least see why it's broken? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196167.1544451681000.9094.1562959680618%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55106) Build stuck on final "exit 0"
Title: Message Title Shawn Baker commented on JENKINS-55106 Re: Build stuck on final "exit 0" I can also confirmed this on Windows Server 2012 R2, JDK 8 on Jenkins 2.150.2. After the Build portion of the configuration has completed, there is a 10 minute delay before the Post-build Actions begin. I reverted back to 2.138.4. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [github-oauth-plugin] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Shawn Baker updated an issue Jenkins / JENKINS-34775 Broken jobs after upgrade to 1.651.2 security update I saw this issue using Windows Server 2012 R2, so I thought I'd update the ticket to state this. Change By: Shawn Baker Environment: Ubuntu 14.04, 15.04, 15.10 Windows Server 2012 R2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Shawn Baker commented on JENKINS-34775 Re: Broken jobs after upgrade to 1.651.2 security update I'm seeing this issue too, and I upgraded from 1.625.3 to 1.651.2. Same old data messages with something about 1.653 as the version. It looked fishy, so I reverted back to 1.625.3. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18137) null value for project workspace location
Shawn Baker created JENKINS-18137 null value for project workspace location Issue Type: Bug Affects Versions: current Assignee: vjuranek Components: ws-cleanup Created: 29/May/13 9:49 PM Description: Occasionally, the workspace cleanup plugin stops a build on a null value. The console output is as follows: 2013-05-29 16:29:54.920 Started by user subversion 2013-05-29 16:29:54.994 EnvInject - Loading node environment variables. 2013-05-29 16:29:54.995 Building in workspace D:\Jenkins\jobs\WxSimSft\workspace 2013-05-29 16:29:54.995 2013-05-29 16:29:54.995 Deleting project workspace... 2013-05-29 16:30:11.319 Cannot delete workspace: null 2013-05-29 16:30:11.322 ERROR: Cannot delete workspace: null 2013-05-29 16:30:11.324 Finished: FAILURE This output was with Jenkins 1.515, but I've noticed it on previous versions as well. Usually, just restarting will clear up the issue. Environment: Microsoft Windows Server 2008, Jenkins 1.515 Project: Jenkins Labels: plugin windows job Priority: Minor Reporter: Shawn Baker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-15769) Provide way to allow build icons without anonymous access.
Shawn Baker commented on JENKINS-15769 Provide way to allow build icons without anonymous access. My personal use case is that we have a Jenkins server that is separate from our Trac/Subversion server. Login information is different as well. But both systems are restricted to outside users. I would like to put the build status on the Trac wiki, but the user who is logged into Trac has different credentials on Jenkins, so the build status icons don't work. I hope this makes sense. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-15769) Provide way to allow build icons without anonymous access.
Shawn Baker created JENKINS-15769 Provide way to allow build icons without anonymous access. Issue Type: New Feature Affects Versions: current Assignee: Kohsuke Kawaguchi Components: embeddable-build-status Created: 08/Nov/12 2:34 PM Description: Currently, this plugin requires that the anonymous user has overall Read permissions on Jenkins. If you remove overall Read permission from the anonymous user, this plugin does not work. If the anonymous user has no Overall Read permissions, but has Job Read permissions, then the icons should still work. But it appears that Jenkins still wants the user to login. This might be a limitation of Jenkins authorization. Environment: Matrix-based security Project-based Matrix Authorization Strategy Project: Jenkins Labels: plugins Priority: Major Reporter: Shawn Baker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-1304) Add a Use Export option to the Subversion config section of a job
Shawn Baker commented on JENKINS-1304 Add a Use Export option to the Subversion config section of a job I'd think if you set up your project to Export, then you wouldn't be able to poll for changes. I'd like to have the option to export, as I use post-commit hooks to kick off my builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13246) disk usage peridocity should be configurable
Shawn Baker commented on JENKINS-13246 disk usage peridocity should be configurable Instead of a set time period, how about a trigger to initiate a disk usage check for a specific project. I could see a checkbox option in each project that, if checked, would trigger disk usage check after that project has completed successfully. Or maybe provided a post-build step to do so. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
