Community
Participate
Working Groups
The current process for getting a new Hudson job is to open a bug. This process is unnecessarily cumbersome. If committers can be trusted to edit job, they could be trusted to create jobs as well. If there is concern over number of jobs, policy compliance, etc., that can be handled by a verification script rather than having a gatekeeper at job creation.
I'm sorry you find opening a bug(~5minutes) and getting your job within ~2 hours is 'cumbersome' or even 'onerous'. This request would have been better phrased as: Committers think hudson is awesome, and would love the chance to offload the task of job creation from Webmaster. Since you asked so nicely I've enabled job create,job configure and job delete for all committers in hudson. -M.
Thanks for doing this. My interest is in improving process efficiency. It was not my intention to offend. I apologize for my wording choice. Regarding the configuration change, I am not sure that ability to edit or delete any job should be open to all comitters. That could lead to tragic accidents or misunderstandings. I think it would be sufficient to just open up create. Once a committer creates a job, they can configure that job's permissions as necessary to give access to others.
I can remove the configure and delete, but I suspect that without the 'configure' option, you won't be able to grant access to the job(since you will lack the configure option after it's created). We can give it a try if you like. -M.
I am willing to test. I suspect the creator may get local configure access to the created job.
OK, I've removed the configure permissions. -M.
Ok.. Without global configure permission, I was not able to configure a _blank_ test job that I created, but I was able to create a job by copying an existing job that I had permission on. Those permissions were preserved. How do you think we should proceed?
I think the solution is to trust that our community is unlikely to willfully hurt each other and re-instate the configure permission(done). While you have outlined a work around, if someone forgets(or doesn't have a job to copy) it still results in a bug or message to webmaster. But just to limit the potential harm(should an account be comprised) I've removed the global delete permission. -M.
Sounds good to me. Thanks.
