This rule provides basic release management capabilities. It allows to create builds automatically and link work items (user stories and bugs) to them based on the activity in the git repository. This rule requires DevOps integration and checked to work
Trusted by Agile teams at
show more
USER STORIES:
This rule provides basic release management capabilities. It allows to create builds automatically and link work items (user stories and bugs) to them based on the activity in the git repository. This rule requires DevOps integration and checked to work with GitHub. This rule is largely inspired by GitFlow.
The following scenarios are supported:
- For each repository's integration branch (master, by default. Can be customized in the rule's body.) a new build with name "{repo-name} {some-id} - Next" (from now on, next build) will be created automatically. All work that is pushed to the integration branch will be linked to the next build.
- Push commit to the repository integration branch (master by default). Commit message should contain Targetprocess entity id. Good commit messages: "US#1235 description", "#716 description", "123 description" are good samples". Commit message pattern can be customized in the rule's body.
- Merge pull request to the repository integration branch. Pull request's name should contain Targetprocess entity id. The pattern is the same as for commit messages (see above).
- When new release branch is created next build will be renamed according to the release branch name, e.g. release branch name is "release/1.0.0", then "next" will become "{repo-name} {some-id} - 1.0.0". All the work attached to the build will remain intact. New new build for the integration branch will be created. Release branch name should look like "release/{version}" or "hotfix/{version}".
- Push commit to the release branch will link the entity which id is specified in the commit message to the release build.
Known limitations:
- Only release and hotfix branches created based on the latest integration branch commit is supported for now. To avoid wrong linking of work items to release/hotfix branches based on past commits make sure to create a build for them manually. Pushes to such integration branch will be handled correctly and work items will be assigned to the release/hotfix build in the proper way.
Integrations
See how Targetprocess aligns and empowers business and IT with the help of powerful integrations.
Targetprocess facilitates enterprise agility at all levels by enabling both Business and IT to work in one holistic solution. To help ensure value flow visibility and collaboration across the entire enterprise, Targetprocess allows a powerful set of integrations covering use cases for different levels and roles within organization.
For Transparency above the Team Level
EXPAND 2 INTEGRATIONS
For Transparency above the Team Level
EXPAND 2 INTEGRATIONS
For Continuous Integration and Continuous Delivery
EXPAND 6 INTEGRATIONS
For Continuous Integration and Continuous Delivery
EXPAND 6 INTEGRATIONS
For Product Management, ITSM, Sales and Marketing to Stay on the Same Page
EXPAND 5 INTEGRATIONS
For Product Management, ITSM, Sales and Marketing to Stay on the Same Page
EXPAND 5 INTEGRATIONS