We heavily use a build pipeline where the first job is a CI job that pulls code from repository, pushes it to a cloud platform, compiles and unit tests the code. Downstream jobs in the pipeline deploy code in a promoted fashion through a series of target environment ... ending in "Production".
We want to add functional testing into the mix and have a HP too and test cases that allow us to run tests against the deployed code. In Jenkins, this steps runs as a "Build" step. We have a series of virtual servers configured to run these tests and were planning on running this "step" on a slave. It does not appears that I can run an actual build step on a slave, but how can I configure my jobs to run the deployment, then run the test build "step" and only have the downstream job in the pipeline be able to be manually triggered in the tests pass? Current pipeline jobs are CI -> TEST-> UAT->Production In the test scenario, the CI,TEST. and UAT jobs would have build "Steps" to run functional testing. The only thing I can think of is to adjust the pipeline so 1) The CI job kicks off from a change in the SCM repository 2) a "CI functional test" job is a downstream job, that is automatically kicked off is the CI job succeeds 3) The TEST job is a manually executed downstream job of the "CI Functional Test" 4) a "TEST functional test" job is a downstream job, that is automatically kicked off is the TEST job succeeds 5) and so on down the pipeline. This seems overly complicated and I was not sure if there was a cleaner way to execute this process. Thanks for any insight, Eric -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
