You can now choose (J) to add a Jenkinsfile to your module containing one Stage to build,test etc. in one single step
or you can choose (M) too add a multistage Jenkinsfile containing 6 stages for every single step of the build.
Related Issue
none
Motivation and Context
I wanted to use a Jenkins multibranch pipeline to build my module after it was created with Stucco
How Has This Been Tested?
Created a Testmodule with option (J) in Stucco, added a multibranch pipeline to Jenkins, setting a secret "PSGALLERY_API_KEY" for $env:PSGALLERY_API_KEY
Created a Testmodule with option (M) in Stucco, added a multibranch pipeline to Jenkins, setting a secret "PSGALLERY_API_KEY" for $env:PSGALLERY_API_KEY
Successful push to internal repository
Screenshots (if appropriate):
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[X] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Added support for Jenkins CI in module template
Description
You can now choose (J) to add a Jenkinsfile to your module containing one Stage to build,test etc. in one single step or you can choose (M) too add a multistage Jenkinsfile containing 6 stages for every single step of the build.
Related Issue
none
Motivation and Context
I wanted to use a Jenkins multibranch pipeline to build my module after it was created with Stucco
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: