Rationale for this is that in a large organisation with many repositories whose specs are being published to Confluence, we want to make the process as smooth, easy and consistent as possible.
So rather than requiring users of this plugin to specify a Confluence Space key, we instead want the plugin to set up the space key if it is not provided.
Business rules and examples:
Rule:
The link to the newly created Space is provided to the user
Examples:
The user sees the link in the console output
Rule:
The space key is derived from the git remote url of the repo
Examples:
Rule:
If there is no space key provided and the space does not exist, the space will be created
Rule:
If there is no space key provided and the space with the default space name already exists, the existing space will be published to
Rule:
The space key should be unique for each repository
Examples:
Two repos with the same path but a different domain name have different space keys
johnboyes
commented
3 years ago
Rationale for this is that in a large organisation with many repositories whose specs are being published to Confluence, we want to make the process as smooth, easy and consistent as possible.
So rather than requiring users of this plugin to specify a Confluence Space key, we instead want the plugin to set up the space key if it is not provided.
Business rules and examples:
Rule: The link to the newly created Space is provided to the user Examples:
Rule: The space key is derived from the git remote url of the repo Examples:
Rule: If there is no space key provided and the space does not exist, the space will be created
Rule: If there is no space key provided and the space with the default space name already exists, the existing space will be published to
Rule: The space key should be unique for each repository
Examples: Two repos with the same path but a different domain name have different space keys