Builds, how to link requirements into builds?

The link is done implicitly via commits:

• The CI build (from the CI tool such as Jenkins, GitLab, etc.) contains code commits (Git) or revisions (SVN)
• The code commits have artifact tags such [TK:45] or [RQ:23]
• the code commits are then linked to the requirements and tasks
• The builds are linked via. the commits to the requirements and tasks

David, Thanks for your answer!

Could you provide step by step examples as we would like to synthetically reproduce that logic using Spira's APIs? We are using Amazon code commit that you are not supporting yet.

So, I need to know step by step what entities should I create with what associations, etc. Better with names of API calls that I should use.

Hi Ilya

OK, for AWS CodeCommit (which is on our list now that we have done GitLab, GitHub and CircleCI). You need to call this Build API:

https://api.inflectra.com/Spira/Services/v6_0/RestServiceOperation.aspx?uri=projects%2f%7bproject_id%7d%2freleases%2f%7brelease_id%7d%2fbuilds&method=POST

The list of commits is very important, basically this JSON:

"Revisions": [
{
 "RevisionKey": "44bf09d0a2c36585aed1c34ba2e5d958a9379718"
},
{
 "RevisionKey": "44bf09d0a2c36585aed1c34ba2e5d958a9379718"
}
]

And forgot to mention, the commits inside Git need to have their message include the appropriate Spira token [IN:5], [RQ:2] etc.

Great! I am glad to hear that AWS CodeCommit will be supported by Inflectra. We will wait for it.

You're welcome.!