I have a job (with a script task) defined in Stage A to deploy the artifacts to QA environment. The inline script which deploys the artifacts to the destination server is parameterized. Now in the next stage, I want to deploy the artifacts to my integration environment.
I was wondering if I could (re)use the same job in this new Stage to deploy the artifacts to the higher environments (integration in this case)?
I am afraid you have to recreate the job in the other stage as well. There is no way to share the jobs or clone the jobs.
A best practice is to have a build job that generates the artifact and then have a deployment project with environments defined under it.
I appreciate your approach with having a deployment project with different environments defined. But then I was missing the functionality of having a fully automated pipeline which starts from triggering the build and end up in deploying it to the prod environment (obviously with some manual stages in between). As far as I know, deployment project is kind of an always manual step. Let me know if I am missing something obvious here.
@Obaid Maroof It seems that have no option to export/import stages/job as code, let's say on Bamboo 6. However, there's the same function named View plan as Java specs. Just choose plan that need to export. Then look on option list from right-top action menu, we can choose the function to export entire plan configuration. Take a look inside and we'll see all configurations for stages and jobs.
Hi Community! I’m Elaine, Confluence Product Manager. You may have read my earlier post about page tree in space navigation sidebar. I'm excited to share another improvement that helps you organize ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs