https://github.com/rajat-03/kaiburr-task5

Creating CI/CD pipeline using Github Actions.
https://github.com/rajat-03/kaiburr-task5

Last synced: 7 days ago
JSON representation

Creating CI/CD pipeline using Github Actions.

• Host: GitHub
• URL: https://github.com/rajat-03/kaiburr-task5
• Owner: rajat-03
• Created: 2024-03-08T19:47:47.000Z (8 months ago)
• Default Branch: main
• Last Pushed: 2024-03-08T20:03:28.000Z (8 months ago)
• Last Synced: 2024-03-31T19:25:29.414Z (8 months ago)
• Language: JavaScript
• Size: 230 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
## Kaiburr Task 5: CI-CD Pipeline

![Alt text](public/Screenshot.png)

### Workflow Configuration

The CI/CD pipeline is defined using GitHub Actions workflows. The workflow file is located at `.github/workflows/code&docker_build.yaml`. This file contains the configuration for the pipeline stages and steps.

The workflow is triggered automatically on every push to the main branch of the repository. It includes the following stages:

1. **Build**: Checks out the repository, sets up Node.js, installs dependencies, and builds the application.

2. **Build Docker Image**: Builds a Docker image for the application using the Dockerfile.

### Workflow Steps

Each stage in the workflow consists of multiple steps, which are executed sequentially. These steps perform various tasks such as:

- Checking out the source code from the repository.

- Setting up Node.js environment and installing dependencies.

- Building the application using npm scripts.

- Building a Docker image for the application using `docker build` command.

### Viewing CI/CD Pipeline Results

To view the results of the CI/CD pipeline execution, follow these steps:

1. Navigate to the **Actions** tab of the GitHub repository.

2. Here you will see a list of workflow runs triggered by recent pushes or manual dispatches.

3. Click on the workflow run you want to inspect to view detailed information, including logs for each step, execution status, and any associated artifacts.