Hi All,
Please let me know what do you think on this!
The reasons:
- On Jenkins security authorization matrix, Build and Cancel are listed as different items in same category, this normally implies they are independent permissions. But the current behavior is: Build permission implicitly grants Cancel permission, I find this quite confusing from admin point of view.
- In my company, we have over 20 dev teams and 400+ jobs running on Jenkins, too many build and cancel games going on every day.
From the look of this JIRA, I am not the only one out there having these problem:
The change:
https://github.com/jenkinsci/jenkins/pull/882They are simple enough change, however, after this change is merged, new version of Jenkins will not allow user with Build permissions only to Cancel build, this is going to have impact on jenkins users.
The script:In order to address this, scripts below are developed to make configuration compatible, this will make sure Jenkins doesn't behaviour differently after the fix from user point of view.
The LTS branch:
My company only use LTS Jenkins version. I am wondering how long it normally take for a new change to make into a LTS?