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

Automate Deployment Process/Set up Continuous Delivery #9

Open
ProfessorTom opened this issue Jun 20, 2020 · 0 comments
Open

Automate Deployment Process/Set up Continuous Delivery #9

ProfessorTom opened this issue Jun 20, 2020 · 0 comments

Comments

@ProfessorTom
Copy link
Collaborator

This may need to be two tickets with the line of demarcation being the / in the ticket name.

The deployment first needs to be automated, that is to say that deployment can happen by running a single script/command. Of course that script can call other scripts.

Once such a script/command exists, it should then be added as a step or pipeline in the Continuous Integration tool. Once this step is accomplished, then so-called “push button” deployments should exist; that is to say, pushing one single button should be all it takes to deploy code from a branch, presumably master.

At that point, the opportunity will exist for merges to master to be automatically pushed into production; however, that may only make sense if a Blue/Green environment is first set up.

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

1 participant