Search for a command to run...
Articles tagged with #ci-cd
Continuous Integration (CI) and Continuous Deployment (CD) pipelines are amazing — they automate building, testing, and deploying your applications. But if you run the same workflow repeatedly, some steps like installing dependencies or downloading t...
CI/CD is all about automation. We want our code to be built, tested, and deployed without manual intervention. But what if we want this automation to run at a specific time every day, every week, or even every minute? That’s where cron jobs come in. ...
GitHub Actions is a powerful tool that lets you automate your software development tasks, like building, testing, and deploying your code. But sometimes, you don’t want these tasks to run automatically on every push. What if you want to run a workflo...
Objective: This guide walks you through deploying Docker containers to AWS EC2 running Ubuntu using GitHub Actions. Prerequisites: GitHub Account: Your code should be hosted in a GitHub repository. AWS Account: You need an AWS account with access ...
Issue: "npm install" Failing with Exit Code 137 If your build pipeline is encountering issues during the npm install step, resulting in the following error: Error: Process completed with exit code 137. Cause of the Error This error typically occurs ...
This document provides a comprehensive explanation of the GitHub Actions CI pipeline, detailing each command and step used in the workflow configuration file. The pipeline is designed to run tests across multiple operating systems when code is pushed...