We detect you are using an unsupported browser. For the best experience, please visit the site using Chrome, Firefox, Safari, or Edge. X
0
$0.00
Item Qty
Your cart is empty.

MPLAB® X IDE CI/CD Wizard

Live Chat

Need Help?

Privacy Policy

Continuous Integration and Continuous Deployment (CI/CD) System

By using a Continuous Integration and Continuous Deployment (CI/CD) system, you can receive feedback quickly in your software development. Quick feedback can help improve the quality and reliability of your code by automating much of the building and testing process.

Our MPLAB X IDE CI/CD wizard gets you started by setting up a CI/CD system using an MPLAB X IDE project. The CI/CD system works to give you immediate feedback by testing early and often, which can alleviate potential issues before merging code into the main line.

Our CI/CD wizard uses two programs to set up the CI/CD system: Jenkins and Docker. Jenkins is a commonly used continuous integration system that creates an automation workflow or pipeline in your infrastructure. Docker helps to containerize your system and provides a lightweight, scalable and maintainable build-and-test environment.

Set Up CI/CD Now

Key Features and Benefits of the CI/CD Wizard

  • Helps create the infrastructure to help your team get started in CI/CD
  • Accessible via command line to automate new CI/CD build environments and workflows
  • Container customized to your particular build tool chain
  • Integrates MPLAB X IDE tools and popular third-party tools and supporting files into the Jenkins pipeline
  • Includes an easy-to-use GUI that gets your CI/CD system up and running quickly with a push of a button
Download the MPLAB X IDE CI/CD Wizard User's Guide

The MPLAB® X IDE CI/CD Wizard

This video featues an MPLAB X IDE tool that helps you create the files needed to implement a Continuous Integration/Continuous Delivery (CI/CD) pipeline for the rapid delivery of reliable products. The tool generates a Jenkinsfile, which defines the build and test steps that can be carried out by a Jenkins automation server, as well as a Dockerfile, allowing the pipeline to be run within the consistent environment of a Docker virtual container, populated with all the tools needed to build and test your product.