Skip to content
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

Closed
kevinsimper opened this issue Jul 19, 2019 · 3 comments
Closed

Allow the pipeline config to be generated dynamically #53

kevinsimper opened this issue Jul 19, 2019 · 3 comments

Comments

@kevinsimper
Copy link

kevinsimper commented Jul 19, 2019

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.

@laszlocph
Copy link
Member

Feels like the Drone configuration plugin idea is a variation of your proposal. What do you think? harness/harness#1021 (comment)

@kevinsimper
Copy link
Author

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.

@anbraten anbraten changed the title Allow the drone yaml to be generated dynamicly Allow the pipeline config to be generated dynamically Feb 3, 2022
This was referenced Nov 26, 2022
@6543
Copy link
Member

6543 commented Dec 23, 2022

will be covered by #1400

@6543 6543 closed this as completed Dec 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants