Skip to content

Releases: agilepathway/gauge-confluence

Gauge Confluence v0.14.1

07 Sep 13:59
4506709
Compare
Choose a tag to compare
Improve no create space permission error message (#52)

* Add test for create space permissions error

NB this test cannot run on the Confluence Cloud environment that we use
for our tests [as Cloud's free tier does not provide configurable
permissions][1].  We use a [Gauge tag][2] to exclude the test from the
CI Confluence Cloud tests.

[1]: https://support.atlassian.com/confluence-cloud/docs/manage-permissions-in-the-free-edition-of-confluence-cloud/
[2]: https://docs.gauge.org/writing-specifications.html#tags

* Improve no create space permission error message

* Bump plugin patch version

Gauge Confluence v0.14.0

06 Sep 13:51
38ab7ab
Compare
Choose a tag to compare
  • #49 - Create space if it does not already exist

Gauge Confluence v0.13.4

28 Aug 09:05
ae31297
Compare
Choose a tag to compare
  • #44 - Remove need for space in dry run mode

Gauge Confluence v0.13.3

26 Aug 18:32
91ca3b8
Compare
Choose a tag to compare
  • #43 - Fix bug: nested empty dirs are no longer published

Gauge Confluence v0.13.2

25 Aug 19:32
00cd056
Compare
Choose a tag to compare
Exit with non-zero code if plugin errors (#41)

* Allow "exit" as first word of git commit messages

* Exit with non-zero code if plugin errors

This commit causes the Gauge Confluence plugin to exit with a non-zero
exit code if the plugin finds that any specs are not in a valid state
for publishing.  This is true both for dry run mode and "normal" mode.

It is useful for CI/CD as it means that the CI/CD pipeline can use the
exit code (0 for success, not 0 for fail) to pass or fail the build.

So a typical workflow would be to have the plugin run in dry run mode on
feature branches, and to fail the build if the plugin exits with a
non-zero exit code.  Then (once the dry run has succeeded and the change
has been successfully merged to the trunk branch) the pipeline can run
the plugin in normal mode and again pass or fail the build depending on
the exit code.  As the plugin has already passed in dry run mode on the
feature branch, it should in theory always pass on the trunk
branch, which is what we want.

NB Gauge only exits with a non-zero exit code for documentation plugins
which return an error since [v.1.4.1][1].

[1]: https://github.com/getgauge/gauge/releases/tag/v1.4.1

* Bump plugin patch version

Gauge Confluence v0.13.1

16 Aug 09:54
f808f4f
Compare
Choose a tag to compare
  • #39 - Improve dry run documentation

Gauge Confluence v0.13.0

16 Aug 09:20
15020c4
Compare
Choose a tag to compare
  • #38 - Add dry run mode

Gauge Confluence v0.12.0

15 Aug 18:16
2414803
Compare
Choose a tag to compare
  • #37 - Move duplicate title checks to before publishing

Gauge Confluence v0.11.1

11 Aug 19:48
f38bacf
Compare
Choose a tag to compare
  • #36 - Fix error message when Space homepage is missing

Gauge Confluence v0.11.0

10 Aug 14:28
811caf0
Compare
Choose a tag to compare
Add informative console output during publishing (#35)

* Add informative console output during publishing

This commit adds two simple messages output on the console (and also in
the logs) during publishing, to provide reassurance when running the
plugin that the plugin is working as expected.

Fixes #26

* Bump plugin minor version