Ok you should all have Cancel job perms again.

HTH

Gav...

On Mon, Jul 2, 2018 at 8:51 AM, Gav <ipv6g...@gmail.com> wrote:

> Hi,
>
> We upgraded the main Jenkins yesterday to 2.121.1.
>
> The changelog [1] states:-
>
> "...The Job/Build permission no longer implies the Job/Cancel permission.
> The latter needs to be granted explicitly to users who previously got it
> via this relationship. (issue 14713
> <https://issues.jenkins-ci.org/browse/JENKINS-14713>) ..."
>
> The intention being, able to give build permission to folks without
> allowing them to cancel.
>
> I'll be traveling soon, but hope to take a look at our perms before I go,
> if not, when I get back.
>
> As mentioned yesterday in the upgrade email, I encourage everyone to read
> the upgrade docs.
>
> Thanks
>
> Gav...
>
> [1] -  https://jenkins.io/changelog-stable/
>
>
> On Mon, Jul 2, 2018 at 6:55 AM, Jan Matèrne (jhm) <apa...@materne.de>
> wrote:
>
>> > > Our nightly build hangs for seven hours [1].
>> > >
>> > > Could someone kill that so the next could start?
>> >
>> >
>> >
>> > Cancelled via the UI. Did you try that? That’s ordinarily self-service.
>> >
>>
>> Yes - no 'abort job' for me (jhm).
>> Neither on the concrete build, nor on the job, nor in the Ant group, nor
>> on the main page.
>> At work I could cancel the build via the build queue, but nothing here.
>> Maybe missing rights?
>>
>> Jan
>>
>>
>
>
> --
> Gav...
>



-- 
Gav...

Reply via email to