-
Notifications
You must be signed in to change notification settings - Fork 316
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
refactor(IDX): update CI env vars #1703
base: master
Are you sure you want to change the base?
Conversation
.github/workflows-source/ci-main.yml
Outdated
mkdir -p "/cache/job/${CI_JOB_ID}/${ROOT_PIPELINE_ID}/artifacts" | ||
ln -s "/cache/job/${CI_JOB_ID}/${ROOT_PIPELINE_ID}/artifacts" /__w/$REPO_NAME/$REPO_NAME/artifacts | ||
buildevents cmd "$ROOT_PIPELINE_ID" "$CI_JOB_ID" build-command -- \ | ||
rm -rf "/cache/job/${CI_JOB_NAME}/${ROOT_PIPELINE_ID}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should use github.run_id
. What we have now is actually not safe and we're prone to issues if two jobs are in the same machine and overlap.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We already use that for ROOT_PIPELINE_ID
ic/.github/workflows-source/ci-main.yml
Line 30 in a95f743
ROOT_PIPELINE_ID: ${{ github.run_id }} |
CI_JOB_ID
with ROOT_PIPELINE_ID
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. We can do that. Probably as well rename ROOT_PIPELINE_ID
.
Github Actions does not expose job_id, so we were using job_id and job_name interchangeably. To simplify, we replace
CI_JOB_ID
with what was previouslyROOT_PIPELINE_ID
and removeROOT_PIPELINE_ID
.