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

Enhancement: Introduce back the job to create environments on demand #14

Open
deors opened this issue Apr 16, 2016 · 1 comment
Open

Comments

@deors
Copy link

deors commented Apr 16, 2016

Before the introduction of environment type DEV|PROD, the environment job allowed for creating as many environments as needed on demand, and then the deploy job could be used to deploy any build to any environment as needed.
This has been so far a very useful feature in demos and presentations, and one useful for those cases in which the project is not mature enough to go directly to production, but need to have feature environments to test and validate specific stuff before merging and deploying to production.
Could we bring back the ability to create new environments on demand with any desired name, and then manually control via deployment what features are put in them?

@nickdgriffin
Copy link
Contributor

Yes, it's on my list of random things that need doing - happy for a PR to go in for it too. I think it should be creating just a "NAME" environment for the dev type and "NAME_A" and "NAME_B" environments for the prod type.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants