|
|
|
|
|
by henryaj
3266 days ago
|
|
> Build dependencies. Ability to trigger project-B build when project-A build succeeds Within a pipeline, you can 'pass' an output of one step as a triggering input to another. Across pipelines, you can use e.g. an S3 resource to save state; the job to be triggered looks at that S3 resource and triggers when it changes. > Use the same artifact across multiple build stages. Yep - you can pass the output of one job to be used as the input of another. > Ability to combine multiple builds together. Yep - have a look for "fan-in" in the docs. > An option to promote a build to the next step either manually or automatically. You can manually trigger steps from the UI; you could also have a resource that triggers a job automatically on some condition. |
|