To upload the test results from AWS code pipelines, you need to use allurectl.
The aim of this chapter is to explain how AWS code pipelines could be integrated with Allure TestOps' workflows.
This chapter won't cover the peculiarities of AWS Code pipelines, and detailed description of AWS pipelines configuration as we believe AWS created high quality documentation covering their product.
When you create a new project, a new form will appear. In this window you need to set-up your new project:
API token will be used by allurectl running in a pipeline to authenticate / authorize your pipeline to upload the test results to Allure TestOps server.
Allure will randomly generate the token and show you in modal window.
Next you need to specify the path to the AWS yaml specification.
Then click on the CodeBuild button, the window will close and we'll be back at the Pipeline Creation page.
Choose what type of build you need, check that everything is in place and click Next.
Depending on your process you can either skip creating of the Deploy stage or set it up if a Deploy is needed, this is out of the scope of the integration with Allure TestOps.
From the main page open IAM section and proceed to Roles tab.
Search for the service role you are using in CodeBuild and select it for the editing.
You need to add the following 3 roles:
then specify for which resources these rules apply:
Depending on your security policies the settings could be more granular.
allurectl is to be used to upload the test results to Allure TestOps.
allurectl is to be somehow added to the pipeline or can be downloaded to pipeline on some stage of a pipeline execution.