Continuous Verification and Testing are important phases of software delivery. This repo described how logsight.ai can be used to add Quality Gates to a CI/CD pipeline build with GitHub Actions.
We use the Stage Verifier service from logsight.ai since it enables to analyze and compare log files generated by differente versions of an application.
- You are collaborating on changes to a repository using your own branch
- You create a pull request to propose a new feature
- Before merging the changes, the CI/CD triggers a continuous verification gate
- Logsight Stage Verifier analyzes the logs generated by the two applications / branches
- The deployment risk score is
⚠️ 78% - Since the risk is high, the merge is automatically cancelled and a GitHub Issue is created
To try the simplicity and transparency of using Logsight, we recommend you to follow the instructions directly from our Hello Logsight tutorial
- Fork the hello-logsight repository
- Go to Pull Requests and create a New pull request
- In the compare drop-down list, set
compare: candidate
- Create pull request
- The continuous verification gate runs
- If the verification fails:bangbang:, a report is created with the deployment risk. The report is available under GitHub Issues.
The following image gives an example of a report created by the CI/CD Stage Verifier gate:
You can also view a more detailed report of the verification using the online service. You need to have a logsight.ai user account.
To access the report, select the Detailed onine report link shown in the Github Report.
The hello-logsight example ends here. You can get more in-depth knowledge about the actions and how to use them at docs.logsight.ai