#267 ✓stalled
Greg Schueler

enforce unique job name & group for jobs within a project

Reported by Greg Schueler | April 26th, 2011 @ 06:01 PM

Multiple jobs with the same name & group are allowed within a project, but behavior of CLI tool, Job XML Upload, and Job References must make concessions for this possibility. If job name & group were required to be unique within a project then behavior would be clearer.

CLI Tool: run -j 'group/name' - fails if no unique job found with that group/name
Job Def Upload (GUI,API): option required to 'skip','update', or 'create' the job if same group/name is found. this would be simplified to skip or update.
Job References: fails if no unique job group/name found.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

(DEPRECATED) Please use github issues for issue tracking at http://github.com/dtolabs/rundeck/issues

Shared Ticket Bins

People watching this ticket

Referenced by