mirror of
https://github.com/woodpecker-ci/woodpecker.git
synced 2024-11-25 19:31:05 +00:00
547f5dea35
When triggering a deployment event on an existing pipeline, there is no way to get the tag used to trigger the parent pipeline, even if this parent was a tag event. In our company CI/CD current setup with drone, we use the tag event to trigger a kaniko image build step, using the git tag as an image tag, and the deployment/promotion step to effectively deploy this image using the tag reference in our cluster. This is the only point blocking us to completely switch to woodpecker and get rid of drone... What's done: - changed the metadata environ() method to populate CI_COMMIT_TAG env var if commit ref starts with /refs/tags (like it's done in drone), independently of event type EventTag. Please let me know if I'm wrong, I will happily contribute in this nice project. --------- Co-authored-by: Christian Gapany <christian.gapany@netplus.pro> Co-authored-by: Lauris BH <lauris@nix.lv> |
||
|---|---|---|
| .. | ||
| backend | ||
| errors | ||
| frontend | ||
| multipart | ||
| rpc | ||
| samples | ||
| shared | ||
| error.go | ||
| error_test.go | ||
| logger.go | ||
| option.go | ||
| pipeline.go | ||
| stepBuilder.go | ||
| stepBuilder_test.go | ||
| tracer.go | ||