Skip to content

fix: cases when GIT_PREVIOUS_SUCCESSFUL_COMMIT fails #19

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 18, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions Jenkinsfile
Original file line number Diff line number Diff line change
Expand Up @@ -121,11 +121,14 @@ pipeline {
// change only affects metadata files but not only with
// previous commit, but with previos successful commit
// See https://github.com/ai4os/ai4os-hub-qa/issues/16
// If there is no GIT_PREVIOUS_SUCCESSFUL_COMMIT (e.g. First time build),
// we fall back to last commit
if (env.GIT_PREVIOUS_SUCCESSFUL_COMMIT) {
// If GIT_PREVIOUS_SUCCESSFUL_COMMIT fails
// (e.g. First time build, commits were rewritten by user),
// we fallback to last commit
try {
changed_files = sh (returnStdout: true, script: "git diff --name-only HEAD ${env.GIT_PREVIOUS_SUCCESSFUL_COMMIT}").trim()
} else {
} catch (err) {
println("[WARNING] Exception: ${err}")
println("[INFO] Considering changes only in the last commit.."
changed_files = sh (returnStdout: true, script: "git diff --name-only HEAD^ HEAD").trim()
}

Expand Down