December 13th, 2021 by inflectra
As we start preparing for 2022, we will be providing some information on our plans for 2022, including some previews of planned functionality in our Spira and Rapise platforms. One of the key plans for 2022 is a closer integration of our Spira platform with GitLab. We already have source code repository and issue tracking integration, but the planned enhancements for 2022 include support for GitLab CI Pipelines.
SpiraTeam and SpiraPlan provide multiple levels of integration with GitLab, including the following three use cases:
The new integration with GitLab CI pipelines will allow you to execute a GitLab CI pipeline directly from the Spira user interface. In addition, the GitLab pipelines may be automatically triggered by source code commits or other events from within GitLab itself.
Whenever a GitLab pipeline executes (either from Spira or via normal source code commit events), the new GitLab pipeline event will be recorded in Spira as a new build:
These GitLab pipeline events will show up in Spira as a new Build under the Release artifact:
When you click on the Build in Spira you can see the build details (including the console log) as well as the associated source code commits, incidents and other associated artifacts.
This functionality is similar to what is already available for tools like Jenkins and TeamCity as well as Azure DevOps Pipelines.
Spira includes powerful integration with Git code repositories, including the code repositories hosted in GitLab. From within Spira, you can view the list of folders and files in a branch as well as view the commits in specific branches.
This is the same code repository that is available also inside GitLab:
Spira includes the ability to quickly and easily drill down onto a specific commit and see the files that have changed, with inline code difference viewing. The Associations tab lets you have traceability from every code change made in the application to the relevant requirement, incident, or task that necessitated the change.
The third aspect of the GitLab integration is the ability to synchronize the Spira incident tracker with the issue tracking module of GitLab projects:
You can log new incidents, bugs, and defects in Spira, either during testing or just ad-hoc, and have them synchronize seamlessly over to GitLab (and vice-versa):
Within GitLab you can see the incidents and make changes, including assigning developers, adding comments, and making changes to the issue priority, status or description. Those changes are then automatically reflected back in Spira.
gitlab devops continuous delivery pipelines continuous integration builds
And if you have any questions, please email or call us at +1 (202) 558-6885
Are you looking for a platform that helps you deliver better software, faster?