We are using Jenkinsfile and multibranch for the continuous part of our development pipeline, which ends with code deployed into the integration environment. Moving forward into QA, UA, Prod etc we have scheduled or as-needed releases. We would like to reuse the deployment part of our pipeline-as-code in those higher environments, but at this point, code, provisioning, and deployment scripts are all versioned together and stored inside the release tarball and the Jenkinsfile in source control may no longer be valid for that version. Is it possible to devise a Jenkins deployment job that reads the job configuration from a release tarball?
-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e1b4dd4d-561d-4e92-bc48-fefc6533ae49%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
