There are some very popular continuous integration (CI) tools, such as Jenkins. These tools will help automate your process.
You can trigger your workflow, also known as pipeline, whenever someone checks their code into a version control system.
Containerization is an extremely useful way to capture your build and test environment in a lightweight operating system container. One benefit of the containers being lightweight is how quickly you can bring up the environment.
The container you create can also be duplicated multiple times based on the image that was created. With this you can create and run multiple containers, or parallel tests, while ensuring you have the same development environment across the whole team.
The containers are configured to access MPLAB XC Server Licenses, which are accessible to build your jobs using high-level optimizations, and other MPLAB X tools.
As you run the Jenkins pipeline, you’re able to integrate additional tools such as static analysis tools, simulator tests, code coverage, and third-party tools. You can also run a hardware in-the-loop test to be sure your software is ready for production.
As these tools run and pass your tests, you can then promote your build image in a binary repository from the integration stage all the way to production.
The CI/CD Wizard will help you with the scripts and code needed to create a Jenkins file and a Docker file to get this system set up. As you get familiar with these tools, you can customize the setup files to further enhance your pipeline with thousands of plug-ins that Jenkins supports.
Automating your testing process—from unit testing to build integration to end-to-end testing—will provide you and your test team with fast feedback that is essential to improving the quality of your products.
Hover Over Icons to Learn More