You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: