[JIRA] [core] (JENKINS-34642) Jenkins 2.0: pinning plugins no longer works

[marc.esher@gmail.com (JIRA)]

Marc Esher created an issue

Jenkins / JENKINS-34642 Jenkins 2.0: pinning plugins no longer works Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/May/06 12:58 PM Environment: jenkins 2.1, installed via yum Priority: Minor Reporter: Marc Esher Creating a ".pinned" file used to cause the Jenkins UI to show a "pinned" label in the plugin update center, as documented at https://wiki.jenkins-ci.org/display/JENKINS/Pinned+Plugins This was extremely useful for dealing with plugins that caused problems after updating, and was a real help for Jenkins administrators because we could just pin the plugin rather than having to remember which plugins to leave alone during our scheduled plugin update cycle. It looks like pinning has gone away in Jenkins 2, as evidenced by the fact that we have half a dozen plugins with a ".pinned" file, and yet none of them show up as pinned in the Jenkins UI, and all of them are updatable in the plugin center. I do not know whether this is a half-implemented change, i.e. pinning was removed but the UI wasn't changed to reflect that, or whether pinning is broken. Thanks for considering. Pinning is really useful... unfortunately, not all plugins "Just work" when updating them. Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[dbeck@cloudbees.com (JIRA)]

Daniel Beck resolved as Not A Defect

Pinning was never intended to be used the way you did, so that justification is not sufficient to bring it back. Pinning was removed because support for bundling plugins was removed.

Jenkins / JENKINS-34642 Jenkins 2.0: pinning plugins no longer works

Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect

Add Comment

[dirk.heinrichs@recommind.com (JIRA)]

Dirk Heinrichs commented on JENKINS-34642

Re: Jenkins 2.0: pinning plugins no longer works /me also thinks this was a bad decision. The pinning functionality shouldn't be coupled to bundled plugins. The use case is also quite simple. There's one plugin in we make use of in several hundred jobs, but it once introduced a backwards incompatible change, which prevents us from updating it. Since we cannot pin it anymore, we need to be careful when updating our plugins not to update this single plugin also, since it would break 80% of our jobs when we do so. Pinning it once would really save us a lot of hassle.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[dirk.heinrichs@recommind.com (JIRA)]

Dirk Heinrichs edited a comment on JENKINS-34642

[dbeck@cloudbees.com (JIRA)]

Daniel Beck commented on JENKINS-34642

Re: Jenkins 2.0: pinning plugins no longer works

Dirk Heinrichs Pinning did nothing for your use case, except show a label on the UI that you used to mean something different, as it could still be updated. The same thing could be accomplished by adding something like labels to installed plugins without all the baggage that came with pinning.

Add Comment

[dbeck@cloudbees.com (JIRA)]

Daniel Beck edited a comment on JENKINS-34642

Re: Jenkins 2.0: pinning plugins no longer works

[~dhs] Pinning did _nothing_ for your use case, except show a label on the UI that you used to mean something different, as it could still be updated. The same thing could be accomplished by adding something like labels to installed plugins without all the baggage that came with pinning. Or editable descriptions.

Add Comment