ci: fix variable null chek on GitLab CI/CD #565
Merged
Conversation
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
huxuan
force-pushed
the
xuan.hu/gitlab-ci-fix
branch
from
da321bb to
e8fa2ba
Compare
huxuan
force-pushed
the
xuan.hu/gitlab-ci-fix
branch
from
1ea4a7a to
45e0f45
Compare
msclock
approved these changes
May 20, 2024
|
🎉 This PR is included in version 0.0.52 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
The varialbe check on GitLab CI/CD is quite strange:
When assign
$PATto$GITLAB_TOKENand$PATis NEVER configured:$GITLAB_TOKEN != null: the job will be triggered.$GITALB_TOKEN != "": the job will be triggered.$PAT != null, the job will NOT be triggered.$PAT != "", the job will be triggered.In conclusion, we have to
$PAT != nullto avoid unexpected job run.Some related reference: