Jenkins pipeline plugin - Jenkins as code

0
votes

Just trying to understand the pipeline as code along with pipeline plugin in jenkins 2.0. I know the advantage of that , but my question is around the deployment workflow in any company, for example , we can deploy to dev , qa , prod , whenever we want, Now if I go with the pipeline plugin , is like with every commit it will run the whole pipeline , commit , tests , deploy dev , qa , prod, it will be deploying always the latest commit. Is there any way to run a manual trigger to deploy any version of my code and don't the latest? Is pipeline plugin a replacement of build pipeline view?

1
jenkinsjenkins-pluginsjenkins-pipeline
Just because you can do everything in a single pipeline doesn't mean you have to do everything in a single pipeline. My apps go through several different pipelines between dev and prod. I think the point of pipelines is to provide flexibility, as opposed to putting your processes on rails. - Jacob

1 Answers

0
votes

You can run a job manually. Just uncheck all conditions in the "build triggers" part of the job configuration.

Then, you can create multiple job. For exemple, the first one runs tests. The second deploy to dev, and run functionnal test / test database schemas evolutions. The third, deploy to QA...

Any job can be trigerred by another job, so Jenkins can automatically run the second job only if the first succeded.