How Can I Make A Jenkins Build For A Github Repository Be Triggered By A Push To A Different Repository?
Solution 1:
I think this is a pretty standard approach to implementing a simple build-test-posttest pipeline. Job 1 is name-commit-stage, job 2 is name-test-stage or name-integration-stage and a third job for your pip-wheel.
You can see a more complex pipeline in the build pipeline jenkins plugin.
Check if your third job should be using job 1's artifacts instead of repository X. This will bring atomicity to your pipeline as someone could push something to your repository X while a job has already started. The Copy Artifact Plugin is useful for that, or you can just reference the local job 1 workspace as a source of your job 3 (as a parameter in a build step).
You also need to make sure that changes to repository X-Tests should be pushed before changes to repository X, as job 2 may use code in repository X-Tests that is not in sync with repository X, leading to test failures.
Post a Comment for "How Can I Make A Jenkins Build For A Github Repository Be Triggered By A Push To A Different Repository?"