Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 435518

Summary: Committers should be given with permissions on their own gerrit jobs
Product: Community Reporter: Victor Rubezhny <vrubezhny>
Component: CI-JenkinsAssignee: CI Admin Inbox <ci.admin-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: thanh.ha, webmaster
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Victor Rubezhny CLA 2014-05-22 09:12:39 EDT 
Committers should be given with permissions on their own gerrit jobs, specifically so they can re-trigger on failures (which can happen because of reasons unrelated to the patch).

For example: We have a fix for Bug #423274 in Gerrit: https://git.eclipse.org/r/#/c/26355/ and there was a Hudson CI Build job was created for that change. The Hudson CI jon for Patch Set 1 was finished with success so we had Verfied+1 from Hudson CI.

Upon receiving PMC Review Approval I had to rebase that change in Gerrit, so Patch Set 2 was created and a new Hudson CI Job was created in order to verify the change. That new job has failed by a reason that is not related to the fix itself (see; https://hudson.eclipse.org/webtools/job/jsdt-gerrit/22/).

I had the same failures locally last night, but now I can successfully build and test JSDT locally (with the mentioned fix included), but cannot re-start the Hudson CI Job in order to get Verified+1 from Hudson.
Comment 1 Thanh Ha CLA 2014-05-22 09:32:10 EDT 
I added webtools.jsdt to the permissions list for the job [1]. I also added webtools.jsdt group to the Gerrit Trigger manual build command too so you should now have permission to relaunch builds using the button on the left called "Query and Trigger Gerrit Patches".

[1]  https://hudson.eclipse.org/webtools/job/jsdt-gerrit