ci: separate GHCR image publish from SSH deploy into distinct jobs#110
Merged
abigaildotnet merged 1 commit intomasterfrom Apr 19, 2026
Merged
ci: separate GHCR image publish from SSH deploy into distinct jobs#110abigaildotnet merged 1 commit intomasterfrom
abigaildotnet merged 1 commit intomasterfrom
Conversation
Agent-Logs-Url: https://github.com/EspacoGeek-Teams/SpringAPI_EspacoGeek/sessions/907808c6-ac83-4609-9c51-9d10d4a363af Co-authored-by: AbigailGeovana <142514517+AbigailGeovana@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
abigaildotnet
April 19, 2026 18:40
View session
This file contains hidden or 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
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.
Summary
Separates the "publish image to ghcr.io" step from the "deploy to server via SSH" step in
cicd.yml.Motivation
Previously, both publishing the Docker image and deploying it via SSH lived in the same job (
build_and_publish/build_native_and_publish). If the SSH connection to Hostinger failed, the entire job had to be re-run — including the expensive image build and push. By splitting them into independent jobs, a failed deploy can be re-run without rebuilding the image.Changes
build_and_publish— SSH deploy step removed; image build + push only.build_native_and_publish— SSH deploy step removed; native compile, validation container, and image push only.deploy_jvm(new) — depends onbuild_and_publish; runs only the SSH deploy for the JVM image.deploy_native(new) — depends onbuild_native_and_publish; runs only the SSH deploy for the native image.Both new deploy jobs compute
GHCR_OWNER_LCfromGITHUB_REPOSITORY_OWNER(same logic as their parent jobs) and run only onpush/workflow_dispatchevents to master.