The issues are in Redmine, the source code is in GitLab or GitHub. Whoever wants to know what actually changed for an issue searches the repository. Whoever wants to know why it changed searches the issue.
The DevOps plugin connects the two. The commit appears on the issue, the issue points to the commit.
How it works day to day
- Connect the repository. GitLab or GitHub is linked to the project. A webhook reports changes to Redmine.
- Name the issue in the commit. Developers write the issue number into the commit message, as they usually do anyway.
- Follow along on the issue. The commit appears on the issue, with author, time and message. The jump into the repository stays one click away.
- Track deployments. The overview shows which version sits on which environment.
What changes
- The question “what belongs to this issue” is answered by the issue itself.
- A release can be traced without putting two systems side by side.
- Project management and development see the same status without anyone assembling it.
If you run Redmine and GitLab with us, both systems sit with the same provider, with one contact and one server location.
Which functions the Redmine DevOps plugin brings along and what it costs is described on the product page.