Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

enforce unique job name & group for jobs within a project

#267

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.

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

State: stalled
Milestone: none
Assigned to: nobody

Activity

  1. Alex-SF
    Alex-SF
    • Milestone cleared.
    • Milestone order changed from 26 to 0

    June 8th, 2011 @ 10:45 AM

  2. Alex-SF
    Alex-SF
    • State changed from new to hold

    How should this be reconciled with the 1.3 UUID feature?

    July 9th, 2011 @ 01:49 PM

  3. Greg Schueler
    Greg Schueler

    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.

    July 11th, 2011 @ 09:27 AM

  4. Greg Schueler
    Greg Schueler
    • State changed from hold to stalled

    June 22nd, 2012 @ 10:46 AM

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.