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>
Woodpecker
Woodpecker is a community fork of the Drone CI system.
🫶 Support
Please consider to donate and become a backer. 🙏 [Become a backer]
📖 Documentation
✨ Contribute
📣 Translate
We use an own Weblate instance at translate.woodpecker-ci.org.
👋 Who uses Woodpecker?
Woodpecker is used by itself multiple well-known companies, organizations like Codeberg, hobbyist and many others.
Leave a comment if you're using it as well.
Also consider using the topic WoodpeckerCI in your repository, so others can learn from your config and use the hashtag #WoodpeckerCI when talking about the project on social media!
Here are some places where people mention Woodpecker:
✨ Stars over time
License
Woodpecker is Apache 2.0 licensed with the source files in this repository having a header indicating which license they are under and what copyrights apply.
Files under the docs/ folder are licensed under Creative Commons Attribution-ShareAlike 4.0 International Public License.