[#427] Fix version fetching for backend and frontend on CI/CD pipeline #428
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ages tagging This commit modifies the build-and-deploy workflow file to include fetching the full history of the repository during deployment. This change is essential for accurately calculating the Docker image tags for both backend and frontend components in the CI/CD pipeline. By setting the `fetch-depth` to 0 in the step that checks out the code, the workflow now ensures that all historical commits are available, enabling precise version information retrieval for tagging the Docker images. Changes made: - Modified: .github/workflows/build-and-deploy.yml to add `fetch-depth: 0` parameter in the step that checks out the code, ensuring full repository history is fetched during deployment.
This commit adds logging of target indicators during the deployment process to improve visibility and tracking of deployment steps. Changed the deployment workflow in .github/workflows/build-and-deploy.yml to include target indicators logging when performing certain actions, such as destroying the Cardano Node and DB sync, deploying the application, and reprovisioning Grafana. The changes involve adding the '--debug=w' flag to the 'make' commands for destroying Cardano Node and DB sync, deploying the application, and reloading Grafana, allowing for more detailed logging during these actions.
4 tasks
MSzalowski
approved these changes
Mar 7, 2024
placek
deleted the
fix/427-fix-version-fetching-for-backend-and-frontend-on-cicd-pipeline
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR make significant improvements to the deployment workflow, primarily focusing on enhancing Docker image tagging accuracy and increasing visibility during the deployment process.
It ensures that all historical commits are accessible during deployment, facilitating precise Docker image tagging based on version information for both backend and frontend components.
It also refines the deployment process by incorporating logging of target indicators. This addition aims to improve the monitoring and tracking of the deployment steps, offering clearer insight into the deployment activities.