-
Notifications
You must be signed in to change notification settings - Fork 6
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
how to handle config/gpi_pipeline_primitives.xml in git #104
Comments
Could the rescan could be done in a pull hook?
|
Correct me if I'm wrong, but I believe the hooks are not on version control so we'd something like a script that writes the appropriate git hook into each person's .git directory. |
On launch of the pipeline, can we check the date modified of |
The
config/gpi_pipeline_primitives.xml
file has to be auto-generated by the "Rescan Pipeline Config" whenever new primitives are added. Since it's a machine-generated data file it probably shouldn't be in the version control system. If it is, then it adds more work to frequently commit changes to that which don't really need to be tracked since it's derived from primitives metadata.But if we take it out, that means that everyone is going to have to remember to rescan their pipeline configs when they pull in new changes, and new users are going to need to do that after installing the pipeline before they can run it. So that adds extra steps too.
Which is preferable? @semaphoreP @kfollette opinions?
The text was updated successfully, but these errors were encountered: