[JIRA] (JENKINS-5371) Cannot push tags back
Title: Message Title David Antliff reopened an issue Please reconsider this issue in light of my earlier comment. Jenkins / JENKINS-5371 Cannot push tags back Change By: David Antliff Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-5371) Cannot push tags back
Title: Message Title David Antliff commented on JENKINS-5371 Re: Cannot push tags back This isn't really fixed in my opinion - the plugin page still mentions the non-existent option, and the GitPublisher plugin doesn't have a way to push all tags - it can only push tags that can be explicitly named, so it's not useful for dynamically named tags that Jenkins doesn't know about. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22761) Missing links to source in cppcheck plugin
Title: Message Title David Antliff commented on JENKINS-22761 Re: Missing links to source in cppcheck plugin Just a note that the wiki, as currently written, does not cope with result entries that contain the optional file0 attribute. I've posted a comment to elaborate here: https://wiki.jenkins-ci.org/display/JENKINS/Cppcheck+Plugin?focusedCommentId=100697392#comment-100697392 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38081) Shared Workspace with empty Name becomes the default Shared Workspace in new jobs
Title: Message Title David Antliff created an issue Jenkins / JENKINS-38081 Shared Workspace with empty Name becomes the default Shared Workspace in new jobs Issue Type: Bug Assignee: Unassigned Components: shared-workspace-plugin Created: 2016/Sep/08 10:55 PM Environment: Jenkins 2.21 Priority: Minor Reporter: David Antliff If, under Configure System, a new entry is created for Workspace Sharing and it is not given a Name or Repository URL (i.e. left blank), it is still useable as a shared workspace. However when new Freestyle jobs are created they now default to using this shared workspace. This has unintended consequences as users do not realise they need to select "None" under a job's Shared Workspace config section. If they fail to do this, the job will use the shared workspace, which is unexpected and a source of problems. If a name is defined, new jobs no longer default to this workspace - they default to None instead, as I believe the should. Add Comment
