-
-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow the pipeline config to be generated dynamically #53
Comments
Feels like the Drone configuration plugin idea is a variation of your proposal. What do you think? harness/harness#1021 (comment) |
No not exactly, that is globally on the drone installation. I want the drone file to be allowed to be fetched with curl from a remote place, or generate with a docker container, or generated with bash. Imagine being able to add another deploy target to all drone files when you are doing a Kubernetes deployment? Or having a script that generate steps for reviewapps: # .drone.yaml
generate: docker run generate-woodpecker-file --features reviewapps,lint,nodejs,ruby,deploy That file is then shown in the UI so you know where the steps where coming from. |
will be covered by #1400 |
It would be really cool if the drone.yml could be generated dynamically.
It could be a step that executes a docker image and then drone uses that output to run the pipeline.
This would allow users and companies to easier share templates. Like automatically setting up reviewapps without having to have a long yaml file.
This is not like jsonette as that is not dynamic either.
The text was updated successfully, but these errors were encountered: