-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins 1.609
We've isolated the problem to Release Plugin version. When downgraded to 2.4.1 "Release" button (the one to schedule new release) appears. Upgrading to 2.5.3 button disappears. Other release-related icons are still visible on past builds. Nothing obvious in the logs.
- relates to
-
-
- Open
-
[JENKINS-28132] Release button disappears after upgrading Release Plugin from 2.4.1 to 2.5.3
Vit Veres
added a comment - You can set the new permission at the Jenkins -> Configure Global Security.
Vit Veres
added a comment - You can set the new permission at the Jenkins -> Configure Global Security.
Go to global settings and set the new permissions.
Details at:
https://issues.jenkins-ci.org/browse/JENKINS-28132
Vit Veres
added a comment - - edited Go to global settings and set the new permissions.
Details at:
https://issues.jenkins-ci.org/browse/JENKINS-28132 Vit Veres
made changes -
| Assignee | Original: Peter Hayes [ petehayes ] | New: Vit Veres [ veresvit ] |
| Resolution | New: Not A Defect [ 7 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Thanks a lot for the fast reply and for a hint to work around the problem (and that's very importent 
)
Thats the solution for people who have enabled "Matrix-based security", but for people who are working witch the option "Logged-in users can do anything" the "Release-Button" still disapears" if you are logged-in or not.
The "work around" for "Anyone can do anything":
- log-in with an existing user
(this is very importend if you are switching from "Anyone can do anything") - enable "Matrix-based security"
- create group "authenticated"
- grant this group all rights
- save changes
After thinking about it several hours, I'm convinced that there is still a bug:
If a jenkins installation use the "Anyone can do anything" or "Logged-in users can do anything" instead of "Matrix-based security" as "Authorization" the "release button" still disappears!
Therefor I reopened this issue.
Kind regards,
Andreas
| Assignee | Original: Vit Veres [ veresvit ] | |
| Resolution | Original: Not A Defect [ 7 ] | |
| Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
I got stung by this bug today when I enabled Active Directory security, and wrote a blog post with the workaround 
It doesn't make sense that "Logged-in users can do anything" does not include "Release", and you should not have to switch to Matrix security to re-enable release!
In case it is helpful to others, I've confirmed Andreas' workaround for "logged-in users can do anything" via the matrix "authenticated" mechanism, on a system using jenkins builtin user database, on LTS 1.642.1.
(I wasn't sure whether it was an LDAP group until I researched it – but "authenticated" is built into Jenkins specially)
If the "authenticated" matrix feature is news to you as much as me, then you may wish to vote on JENKINS-30495
Same issue here:
Jenkins 1.612:
Upgrading "Release Plugin" from 2.4.1 to 2.5.3 the release buttons of all projekts disappears.
Downgrading to 2.4.1, the release button appears again.
Is this an issue related to insufficient permissions? At the release notes there is the entry "Define a new RELEASE permission", but where to grant this permission?