Skip to content

Forcing Jenkins to actually use the ssh key #3893

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.

Sign up for GitHub

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
dopplershift merged 2 commits into from
Jul 29, 2025
Merged

Forcing Jenkins to actually use the ssh key #3893

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1ffe6f4
Forcing Jenkins to actually use the ssh key
blue-jaye-121 Jul 29, 2025
a76c9a4
Update Jenkinsfile - fixing indentation
blue-jaye-121 Jul 29, 2025
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
3 changes: 2 additions & 1 deletion benchmarks/Jenkinsfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,8 @@ pipeline {
cd ${CLONE_DIR}
git add --all
git commit -m "Jenkins Updating Benchmark Results BUILD-NUMBER:${BUILD_NUMBER}" || echo "-----no changes to commit-----"
git push origin HEAD:main --force
export GIT_SSH_COMMAND="ssh -i ${deploy_key}"
git push origin HEAD:main --force
Comment thread
blue-jaye-121 marked this conversation as resolved.
Outdated
fi
'''
}
Expand Down
Loading