You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One major weakness of developing reusable Github Actions (GHA) build workflows such as those in ITKRemoteModuleBuildTestPackageAction is that it is difficult to test the automated tools in an automated fashion. It would be useful to be able to test proposed changes against some minimal project to ensure that build/test/package functionality is as expected.
Proposed Investigative Paths
Embed workflows-under-test within another workflow in ITKRemoteModuleBuildTestPackageAction/.github/workflows. The outer workflow could checkout a small demo project from another module and use the inner workflow to build/test/package said project. Unclear at the moment whether the reusable workflow can be embedded in this way.
Direct users to manually run the test external module against their PR. This method is known to work due to testing with ITKSplitComponents, but requires extra effort and is therefore less approachable and less sustainable.
Overview
One major weakness of developing reusable Github Actions (GHA) build workflows such as those in
ITKRemoteModuleBuildTestPackageAction
is that it is difficult to test the automated tools in an automated fashion. It would be useful to be able to test proposed changes against some minimal project to ensure that build/test/package functionality is as expected.Proposed Investigative Paths
ITKRemoteModuleBuildTestPackageAction/.github/workflows
. The outer workflow could checkout a small demo project from another module and use the inner workflow to build/test/package said project. Unclear at the moment whether the reusable workflow can be embedded in this way.Additional Notes
See original discussion by @jhlegarreta in #45 (comment)
The text was updated successfully, but these errors were encountered: