In this PR, we refined several GitHub Actions to optimize the workflow process, preventing unnecessary Docker image builds.
Description
Several enhancements and clean-ups were performed on the existing GitHub Actions. These refinements are aimed at optimizing the CI/CD process, making it more efficient, and reducing unnecessary builds. Specifically, Docker images will now only be built when tags/releases are created. This prevents the system from generating new Docker images on every merge to the main branch, ensuring that only meaningful and versioned builds are triggered. The refined actions now also consider changes in Go files, go.mod, go.sum, and Dockerfile to determine when to trigger the builds.
Related Issue(s)
None
Motivation and Context
The optimizations made to GitHub Actions were motivated by the need to streamline the workflow processes, minimize resource usage, and ensure that only meaningful and necessary builds are triggered. This contributes to overall operational efficiency and resource conservation, particularly important in environments with limited resources or where build costs are a concern.
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:
[x] Optimization (non-breaking change which improves existing functionality)
Checklist:
Go over all the following points, and put an x in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!
[x] My code follows the code style of this project.
Summary
In this PR, we refined several GitHub Actions to optimize the workflow process, preventing unnecessary Docker image builds.
Description
Several enhancements and clean-ups were performed on the existing GitHub Actions. These refinements are aimed at optimizing the CI/CD process, making it more efficient, and reducing unnecessary builds. Specifically, Docker images will now only be built when tags/releases are created. This prevents the system from generating new Docker images on every merge to the main branch, ensuring that only meaningful and versioned builds are triggered. The refined actions now also consider changes in Go files,
go.mod,go.sum, andDockerfileto determine when to trigger the builds.Related Issue(s)
Motivation and Context
The optimizations made to GitHub Actions were motivated by the need to streamline the workflow processes, minimize resource usage, and ensure that only meaningful and necessary builds are triggered. This contributes to overall operational efficiency and resource conservation, particularly important in environments with limited resources or where build costs are a concern.
Types of changes
What types of changes does your code introduce? Put an
xin all the boxes that apply:Checklist:
Go over all the following points, and put an
xin all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!