[JIRA] (JENKINS-35350) New 2.7 install ignores the plugins I deselect and installs everything anyway.
Title: Message Title Matthew Adams commented on JENKINS-35350 Re: New 2.7 install ignores the plugins I deselect and installs everything anyway. The only suggestion I have related to the original ticket summary is to indicate that a plugin on the main list is getting installed b/c it is a dependency even if you don't check the box. For example: If I select pipeline, even if you don't check the box for the git plugin put something like (will be installed due to dependencies of pipeline) next to the empty checkbox for git plugin? That idea and checking the box automatically sucks and sounds hard to implement, but maybe there is a better way 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-35350) New 2.7 install ignores the plugins I deselect and installs everything anyway.
Title: Message Title Matthew Adams updated an issue Jenkins / JENKINS-35350 New 2.7 install ignores the plugins I deselect and installs everything anyway. Change By: Matthew Adams Labels: plugin 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-35350) New 2.7 install ignores the plugins I deselect and installs everything anyway.
Title: Message Title Matthew Adams updated an issue Jenkins / JENKINS-35350 New 2.7 install ignores the plugins I deselect and installs everything anyway. Change By: Matthew Adams Issue Type: Bug Improvement 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-35350) New 2.7 install ignores the plugins I deselect and installs everything anyway.
Title: Message Title Matthew Adams commented on JENKINS-35350 Re: New 2.7 install ignores the plugins I deselect and installs everything anyway. Perhaps it was a dependency issue. I didn't realize things like pipeline depended on the universe. Can you point me to any reference on why Jenkins plugins seemingly need to import completely unrelated plugins in general? Cleanup Workspace for instance needs 11 dependent plugins to clear out a folder, and I need 13 dependencies to ssh into a slave? Seems there is no hope of keeping the plugin footprint minimized to try and control random breakage 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-35350) New 2.7 install ignores the plugins I deselect and installs everything anyway.
Title: Message Title Matthew Adams updated an issue Jenkins / JENKINS-35350 New 2.7 install ignores the plugins I deselect and installs everything anyway. Change By: Matthew Adams Priority: Major Minor 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] [core] (JENKINS-35350) New 2.7 install ignores the plugins I deselect and installs everything anyway.
Title: Message Title Matthew Adams created an issue Jenkins / JENKINS-35350 New 2.7 install ignores the plugins I deselect and installs everything anyway. Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jun/03 8:59 PM Environment: ubuntu 14.04, jenkins 2.7, chrome, java 1.7 Priority: Major Reporter: Matthew Adams During fresh jenkins setup when I am asked to select my plugins, I uncheck things like ant, maven, git, etc, but they all get installed anyway. Add Comment
[JIRA] [build-pipeline-plugin] (JENKINS-33187) Manual Job Trigger Broken when triggering from Build Pipeline Plugin
Title: Message Title Matthew Adams updated an issue Jenkins / JENKINS-33187 Manual Job Trigger Broken when triggering from Build Pipeline Plugin Change By: Matthew Adams Environment: Manual Job Trigger Broken in Pipeline v1.5.1 with Jenkins 1.642.1 OS = Centos7 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] [build-pipeline-plugin] (JENKINS-33187) Manual Job Trigger Broken when triggering from Build Pipeline Plugin
Title: Message Title Matthew Adams created an issue Jenkins / JENKINS-33187 Manual Job Trigger Broken when triggering from Build Pipeline Plugin Issue Type: Bug Assignee: Unassigned Attachments: ManualBuildStackTrace Components: build-pipeline-plugin Created: 26/Feb/16 6:54 PM Environment: Manual Job Trigger Broken in Pipeline v1.5.1 with Jenkins 1.642.1 Priority: Blocker Reporter: Matthew Adams When Creating a manual trigger downstream of a pipeline flow, I get the attached error in the log when trying to trigger the manual step and the job never starts.
[JIRA] [git-plugin] (JENKINS-30316) Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of sine last build.
Title: Message Title Matthew Adams commented on JENKINS-30316 Re: Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of sine last build. For me it happens with every job. I just made a new job with a echo shell script and give it a git repo and then set up the hook in stash to notify on commits. Perhaps it is a stash hook problem? 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] [git-plugin] (JENKINS-30316) Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of since last build.
Title: Message Title Matthew Adams updated an issue Jenkins / JENKINS-30316 Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of since last build. Change By: Matthew Adams Summary: Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of sine since last build. 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] [git-plugin] (JENKINS-30316) Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of sine last build.
Title: Message Title Matthew Adams created an issue Jenkins / JENKINS-30316 Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of sine last build. Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 04/Sep/15 11:09 PM Environment: Jenkins 1.609.2 Git plugin 2.4.0 Priority: Minor Reporter: Matthew Adams If I push to source control in Stash and the hook notifies jenkins to build a job, it correctly shows the change log of only the commits since the last build. If i ever trigger the build manually from jenkins UI, the change log will show every change I have made since the last manual build (days, weeks or months worth of commits) Able to reproduce in many older version combos of jenkins/git as well like 1.592 and 2.2.2 Talked with Mark Waite about this briefly at JUC on 9/2 and it is believed to be a bug.
[JIRA] [git-plugin] (JENKINS-30316) Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of sine last build.
Title: Message Title Matthew Adams updated an issue Jenkins / JENKINS-30316 Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of sine last build. Change By: Matthew Adams If I push to source control in Stash and the hook notifies jenkins to build a job, it correctly shows the change log of only the commits since the last build. If i ever trigger the build manually from jenkins UI, the change log will show every change I have made since the last manual build (days, weeks or months worth of commits) Able to reproduce in many older version combos of jenkins/git as well like 1.592 and 2.2.2 Talked with Mark Waite about this briefly at JUC on 9/2 and it is believed to be a bug. 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] [git-plugin] (JENKINS-30316) Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of since last build.
Title: Message Title Matthew Adams edited a comment on JENKINS-30316 Re: Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of since last build. For me it happens with every job. I just made a new job with a aa echo shell script and give it a git repo and then set up the hook in stash to notify on commits. Perhaps it is a stash hook problem? 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.
