You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use github action instead of curl method to trigger jenkins
Improves the way we trigger next-machine-image job using a dedicated github action instead of using curl.
Fixes: #659
(cherry picked from commit aa2866a)
if ! curl -X POST "$JENKINS_URL/job/$JOB_NAME/buildWithParameters" --fail --user "$JENKINS_USER:$JENKINS_API_TOKEN" -i -v; then
35
-
echo "Error: Jenkins job trigger failed"
36
-
37
-
# Send Slack message
38
-
curl -X POST -H 'Content-type: application/json' \
39
-
-H "Authorization: Bearer $SLACK_BOT_TOKEN" \
40
-
--data '{
41
-
"channel": "#releng-team",
42
-
"text": "🚨 @here '$JOB_NAME' failed to be triggered, please check https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }} for more details"
"text": "🚨 @here '${{ env.JOB_NAME }}' failed to be triggered, please check https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }} for more details."
0 commit comments