ENH: Add ITK C++ and Python CI Reusable Workflows#3
Conversation
67c5ebf to
42b706c
Compare
d4104b0 to
885a922
Compare
|
Observed passing CI on ITKSplitComponents: https://github.com/InsightSoftwareConsortium/ITKSplitComponents/actions/runs/3207298168/jobs/5242405654 Changes have been squashed. Ready for review. EDIT: It appears I introduced a yml error somewhere during my squash... will continue to investigate. EDIT2: Fixed and squashed a missing |
885a922 to
adf0d5a
Compare
b32f2d2 to
d5f3ab7
Compare
dzenanz
left a comment
There was a problem hiding this comment.
Code looks good. The big test is whether it works 😄
|
Thanks @dzenanz . Note that development tests in ITKSplitComponents using these workflows are passing: InsightSoftwareConsortium/ITKSplitComponents#63 |
|
Going ahead and merging so that reusable workflows can be tagged and referenced in remote module CI. Additional feedback can be added as discussions here or in the issue tracker. |
Migrate ITK C++ and Python Github CI procedures into reusable workflows that can be called and run by ITK external modules.
Partially addresses InsightSoftwareConsortium/ITKModuleTemplate#131.
Caveats:
ITKModuleTemplateand can in turn be forked as a starting point for a custom pipeline in a remote module repository.