AWS DevOps Build and Test Code

AllCode follows DevOps best practices based on “Infrastructure as Code” using tools like Ansible and AWS Cloud Development Kit (CDK) to automatically compile, test, and deploy software components. Our core Continuous Integration and Continuous Delivery (CI/CD) processes are automated to build new developments whenever code is merged into the source control repository. The automation scripts (Jenkins pipelines, Ansible, CDK) are versioned and stored in Git.

This process includes quality assurance steps such as static code reviews, security code reviews, unit tests, and other testing practices to ensure we deliver the best possible customer experience for their DevOps workloads. Additionally, we have processes in place to provision, manage, and scale servers according to needs, leveraging AWS CodeBuild or equivalent tools.

Below is our standard process for building and testing code.

1. We create a CodeBuild Project for each project.
2. We ensure source code is hosted and supported in a repository, e.g. GitHub, BitBucket, etc, and then we connect that repository with CodeBuild.
3. We create build specifications by creating a root file in our project’s directory. This build file defines the build steps, environment variables and artifacts. We will customize the build steps according to the project requirements.
4. Triggering Builds can be done automatically by CodeBuild or by setting up a webhook.
5. Scaling Builds –  Scaling can occur automatically with CodeBuild and allows monitoring of builds and adjustment of project settings.
6. Production of artifacts occurs after successful builds and we can further deploy these artifacts in conjunction with customer needs toward desired environments.