Users of same access group can't restart each other's jobs
I have recently installed a new BF 7.1.2 server and noticed that there is one change of behaviour from BF 7.1.1.4. So I have multiple users belonging to the same access group (Build Engineer). When, say, user A, starts a job and it fails, and when I want to user B from the same team to restart the job, it gives an authentication error when user B clicks on the Restart Job button. In terms of settings, I've compared the 2 servers and found not major differences. I noticed that there are some pemissions being removed in BF 7.1.2 (down from 127 to 105) so I am not sure whether any of the removed pemissions used to control this behaviour. For now, I require the same user who started the job to restart it, which is delaying build fixes. If anyone knows whether there is a solution to this problem, or if I should report it as a bug, please let me know. Thanks.
5 answers
I have recently installed a new BF 7.1.2 server and noticed that there is one change of behaviour from BF 7.1.1.4. So I have multiple users belonging to the same access group (Build Engineer). When, say, user A, starts a job and it fails, and when I want to user B from the same team to restart the job, it gives an authentication error when user B clicks on the Restart Job button. In terms of settings, I've compared the 2 servers and found not major differences. I noticed that there are some pemissions being removed in BF 7.1.2 (down from 127 to 105) so I am not sure whether any of the removed pemissions used to control this behaviour. For now, I require the same user who started the job to restart it, which is delaying build fixes. If anyone knows whether there is a solution to this problem, or if I should report it as a bug, please let me know. Thanks.
This is indeed a defect. Record https://jazz.net/jazz08/resource/itemName/com.ibm.team.workitem.WorkItem/19114 has been opened to address the issue.
This is indeed a defect. Record https://jazz.net/jazz08/resource/itemName/com.ibm.team.workitem.WorkItem/19114 has been opened to address the issue.
Thanks for the information. Do you know if there is any way to obtain a patch to this problem? Perhaps through official support channels? Please advise.
I checked the bug and noticed that it should have been fixed in 7.1.2.1. I've just upgraded my BF Server to 7.1.2.1 but the problem still remains. Has the problem been fixed properly in 7.1.2.1? Please advise.
please note that 7.1.2.1 hasn't been released yet. What you probably have is 7.1.2.0.1 (7.1.2 ifix1)