Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optional project element for job definitions #474

Closed
ahonor opened this issue Jul 31, 2013 · 1 comment
Closed

Optional project element for job definitions #474

ahonor opened this issue Jul 31, 2013 · 1 comment
Milestone

Comments

@ahonor
Copy link
Contributor

ahonor commented Jul 31, 2013

Jobs that are meant to be generic across projects must be re-written to include the needed project name. This is too cumbersome and defeats software config management best practices.

The project element should be optional allowing a user to load a job definition into any project. Secondly, it should be possible upload a job definition with or without a project element and have the one in context take precedence (similar to how archive import works).

gschueler added a commit that referenced this issue Aug 2, 2013
* specify the project to import jobs to
gschueler added a commit that referenced this issue Aug 2, 2013
gschueler added a commit that referenced this issue Aug 2, 2013
@gschueler
Copy link
Member

rd-jobs tool using load -p project -f file.xml fails

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants