-
Notifications
You must be signed in to change notification settings - Fork 928
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
Labels
Milestone
Comments
gschueler
added a commit
that referenced
this issue
Aug 2, 2013
gschueler
added a commit
that referenced
this issue
Aug 2, 2013
gschueler
added a commit
that referenced
this issue
Aug 2, 2013
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
rd-jobs tool using |
gschueler
added a commit
that referenced
this issue
Aug 2, 2013
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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).
The text was updated successfully, but these errors were encountered: