Overview
Gearset now supports pre and post-deployment steps in Pipelines. This allows you to add manual steps to a PR when you create it or while the PR is in progress. When adding pre- or post-deployment steps to a PR, you can associate those steps with any environment where they are needed.
Pre-deployment steps must be marked as complete before the PR can be merged in the Pipelines UI, while post-deployment steps will be highlighted for completion after the PR is merged and propagated to the next environment.
Adding pre/post deployment steps to your PR
You can add your deployment steps to your PR when creating it in the Pipelines UI or in any environment where the PR is awaiting promotion.
You will be able to enter the title of the step, additional details in the provided fields, and specify the environments where the steps should be applied.
Note: The Description input will accept content formatted in Markdown.
Markdown can be used to add formatting to your description with headers, lists, sections, or embed more "rich" content like links and code blocks. If you're unfamiliar with it, see our "cheat sheet" of commonly used syntax below.
All the steps will then appear in the specified environments when the PR is created.
You can also add your pre-/post-deployment steps to your PR directly in the Pipeline. Clicking Add step (highlighted in the image above) will bring up the same modal where you can add the step title, description and select the environments where the steps will appear with that PR.
Managing your pre-/post-deployment steps
Your pre- and post-deployment steps are now attached to the PR. You will only be able to promote the PR once the linked pre-deployment steps have been completed.
Gearset will also append the name of the team member who marked the steps as complete to each step.
You can undo a completed step, edit the steps, or reorder a list of steps in any environment where they are located.
Once the PR is promoted, any pending post-deployment steps will appear in the Pending completion tab of your pipeline.
Gearset will also highlight any environment with uncompleted post-deployment steps in the UI by displaying a notification: "Some post-deployment steps haven't been completed".
The pending post-deployment steps will remain open in this tab until they have been marked as complete. The Pending completion tab will only appear when there are pending post-deployment steps in that environment.
Completed pre-deployment steps and pending or completed post-deployment steps can also be found on the promotion history page for each environment.
Releases
When a pull request (PR) is included in a release, its deployment steps are automatically added to the release.
These steps will appear in the release sidebar, organized by feature. You can edit them just like you would for an individual PR, and you can also add deployment steps directly to the release.
If any pre-deployment steps are incomplete, the release cannot be deployed until they are all finished.
After deployment, post-deployment steps for each PR will appear separately in the Pending completion tab.
Scheduled releases
You can schedule a release that has incomplete pre-deployment steps, but these must be completed before the scheduled deployment date, otherwise the release will not be deployed.
When you're scheduling a release deployment, but some pre- or post- deployment steps haven't been completed yet, you will see below message that serves as a reminder:
"You still have [number] pre-deployment step(s) to finish. If they're not marked completed before the scheduled release time, the release won't happen."
Back propagation and developer sandbox updates
Pre- and post-deployment steps will also show up on back propagation PRs, with post-deployment steps showing up in the Pending completion tab.
Note: In regards to back propagation PRs, Gearset's default behavior is that all of the pre- and post-deployment steps show on these type of PRs.
Developer sandbox updates
Deployment steps will also be displayed for dev-sandbox updates when bringing the latest changes back into your developer box.
This works slightly differently from how the steps appear on a PR, as you just need to check a single 'Mark all steps as complete' checkbox in order to proceed.
Similarly, the post-deployment steps will be shown in a 'pending completion' tab and again, you can select many PRs and mark their post steps as complete in one go.
Markdown Cheat Sheet
The deployment step description field will accept text formatted using markdown. Here are some commonly used formatting options for markdown:
Headers are inserted by adding a number of
#characters before the header text. You can add between 1 and 6i.e.
# Header 1will format the text as anh1
Text can be made bold by adding
**before and after the text, and italicised by adding a_before and after iti.e.
**bold**,_italics_
To add a strike through text, add
~~before and after iti.e.
~~strike through~~
To add an inline piece of code, wrap it with backticks
i.e.
`code`
To add a multiline block of code, wrap the block with three backticks (
```), you can also specify the language of the code next to the opening backticks for syntax highlighting codei.e.
```json
{
"firstName": "Joe",
"lastName": "Bloggs"
}
```
Links can be embedded in your description using the following syntax
[Link text](url), replacing theLink textandurlappropriatelyi.e.
[Gearset docs](https://docs.gearset.com/)Alternatively, you can just paste the URL into your description and it will be embedded as a link
Bulleted and numbered lists are created by adding a
-or1.in front of your list items, respectively.i.e.
- Bulleted list item 1
- Bulleted list item 2
- It also supports adding sub-bullets
1. Numbered list item 1
2. Numbered list item 2
Lastly, tables can be embedded using Markdown's table syntax - with
|chars to separate columns and 3 or more hyphens (---) to create a headeri.e
| Header 1 | Header 2 |
| -------- | -------- |
| Value 1 | Value 2 |