Confluence Hooks for Bitbucket
Link your Bitbucket software development process with your Confluence documentation process
The common issues regarding software documentation
How do we ensure that, for example, a software design document is created, discussed and released before every code change? How can we link software development and documentation not only in theory?
Each rule ensures your documentation strategy
Based on a CQL rule, Confluence pages can be identified for an issue and various attributes of the page can be checked. Currently, “Page likes” and any page properties based on the “page properties macro” can be checked.
Multiple merge and push constrains
There is a merge and push hook in which you can define constraints for special use cases based on one or more rules. As soon as a rule could not be successfully evaluated, the push or merge is prevented.
Documentation of the software is important. Everyone understands the need and yet the documentation is missing, reports are not released or tests are not documented. So how do we ensure that, for example, a software design document is created, discussed and released before every code change? How can we link software development and documentation not only in theory?
The add-on "Confluence for Bitbucket" has the target to map the workflow between Conluence and Bitbucket. Especially from the point of view of development process or also from the point of view of certification bodies, many documents are necessary regarding software development and the quality assurance. It must be ensured that documents are not only available, but also be lived and integrated into the workflow.