Actions
Idea #8564
closed
[Docs] Pipeline authoring guide suggests how to organize your Git repository
Status:
Resolved
Priority:
Normal
Assigned To:
-
Category:
Documentation
Target version:
-
Start date:
02/26/2016
Due date:
Story points:
-
Description
Help pipeline developers use common Git workflows, while getting all the nice practical benefits they expect, like code and job reuse
- Scripts must go in crunch_scripts
- Shared code can live in module subdirectories under that
- When you should branch, and when you shouldn't
- How to define script_version filters in your pipeline template components to make sure you reuse jobs you want as you develop the pipeline
Updated by Brett Smith about 10 years ago
- Target version set to Arvados Future Sprints
Updated by Radhika Chippada about 10 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|commit:a20494c473ef12cf9cf1ab0f3e398e77012cd1db.
Updated by Brett Smith about 10 years ago
- Target version deleted (
Arvados Future Sprints)
Actions