RD 1.6, Copy job to another project method change

[eddie wizelman]

We tend to copy jobs from one project as a template and use them in another.  Before 1.6 you could duplicate a job and change it's project name in edit, but that's gone now.  If you export the job to YAML, and upload it to another project, there is a UUID clash even if you check 'Create new job'

If you edit the YAML file and clear the 'id:' and 'uuid:' fields, the upload works.  This adds several steps to clone jobs between projects.

Anybody come across this or have an easier GUI method?

Thanks,

-=Eddie.

[Greg Schueler]

Hi Eddie,

Thanks for the message, we'd like to make this a smoother process. Several changes in 1.6 have interrupted your workflow here: we removed the project selection in the Edit form, and we have fixed what we considered a bug in that attempting to import a job definition with the same UUID as an existing job into another project will not work. Sorry for that!

I think an option to ignore UUID on import would fix this issue for you.  We added a similar option to the Project archive import, allowing you to archive an entire project then import into another project within the same Rundeck server by generating new UUIDs.  I think this is what you would need for the job definition import as well.

I've added this as an enhancement request for Rundeck 1.6.1: https://github.com/dtolabs/rundeck/issues/519

--
Greg Schueler

--
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discu...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.