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
-
Alex-SF June 8th, 2011 @ 10:45 AM
- Milestone cleared.
- Milestone order changed from “26” to “0”
-
Alex-SF July 9th, 2011 @ 01:49 PM
- State changed from “new” to “hold”
How should this be reconciled with the 1.3 UUID feature?
-
Greg Schueler July 11th, 2011 @ 09:27 AM
the issue is still present with UUIDs (uuid is just another primary key like the internal id when it comes to identifying jobs within a single rundeck instance)
i still think the (project,group,name) should have to be unique, unless there's a good reason to allow multiple jobs with different IDs but the same name.
-
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.
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
People watching this ticket
Alex-SF
Greg Schueler
Referenced by
-
332
Job definitions should support an external ID
it also is not very useful I think to allow duplicate
nam...