Go to the releases as described here. Then edit a release. You should see something like what you see in the image below. The items in the connected line below are part of an automatic deployment upon a successful merge to the master code branch while the disconnected item must be manually deployed to from within either Octopus, assuming you are using Octopus, or the shown UI. The "Clone" option here allows you to copy an environment. Across the top where is reads Pipeline, Tasks, Variables, Retention, Options, and History you may pick Tasks and then pick a particular task to set the "Deploy To Environments" setting to, yes, an environment to deploy to and you may also get to the Tasks by clicking the blue links shown here:
The icon of a person with a lightning bolt raining down on him opens a pane where you may pick between options for After release, After stage, and Manual only to determine if a push to this environment is automatically kicked off by something else somewhere in a chain as shown or must be done manually in isolation. (Maybe we should only push dev to test infrequently when requested to keep test from being polluted by dev's ongoing wackiness and midstream steps in between demonstratable stories in complete.) Clicking in the greater rectangle opens a pane where you may name your step.
No comments:
Post a Comment