generated from agilepathway/gauge-jira
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Having a dry run mode is very useful, e.g. in a CI/CD pipeline the dry run mode can be run on feature branches and pull requests to verify that the Gauge specs are in a valid state for publishing. If they are not valid then the CI/CD pipeline build can fail, alerting the submitter of the pull request to amend them on the feature branch. This ensures that the Gauge specs are always in good shape to be automatically published by the CI/CD pipeline upon any push to the trunk branch (e.g. upon a successful pull request merge). The dry run mode is set by setting a `DRY_RUN` environment variable or property (we can't use a command-line flag for this as [Gauge does not propagate command line flags to documentation plugins][1]). [1]: getgauge/spectacle#42 (comment)
- Loading branch information
Showing
6 changed files
with
74 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
# Dry run mode | ||
|
||
Having a dry run mode is very useful, e.g. in a CI/CD pipeline the dry run mode can be run on feature branches and pull | ||
requests to verify that the Gauge specs are in a valid state for publishing. If they are not valid then the CI/CD | ||
pipeline build can fail, alerting the submitter of the pull request to amend them on the feature branch. This ensures | ||
that the Gauge specs are always in good shape to be automatically published by the CI/CD pipeline upon any push to the | ||
trunk branch (e.g. upon a successful pull request merge). | ||
|
||
The dry run mode is set by setting a `DRY_RUN` environment variable or property (we can't use a command-line flag for | ||
this as [Gauge does not propagate command line flags to documentation plugins][1]). | ||
|
||
|
||
|spec 1 heading|spec 2 heading|did publishing occur?|message | | ||
|--------------|--------------|---------------------|-----------------------------------| | ||
|same |same |did not |Please fix the error then try again| | ||
|same |different |did not |Dry run finished successfully | | ||
|
||
|
||
## Dry run mode indicates if specs are in a publishable state or not | ||
|
||
* Activate dry run mode | ||
|
||
* Publish specs to Confluence: | ||
|
||
|heading | | ||
|----------------| | ||
|<spec 1 heading>| | ||
|<spec 2 heading>| | ||
|
||
* Output contains <message> | ||
|
||
* publishing <did publishing occur?> occur | ||
|
||
__________________________________________________________________________________________ | ||
|
||
[1]: https://github.com/getgauge/spectacle/issues/42#issuecomment-813483933 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters