-
Notifications
You must be signed in to change notification settings - Fork 626
build: fix Jenkinsfile #33
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
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
9bab3dc
to
d19bd73
Compare
looks wierd. I cannot really trigger CI?
|
jenkins cannot detect any change: while it can for #14 |
b667c30
to
5750eac
Compare
3b2905b
to
90b6b49
Compare
ed8081a
to
8b1d241
Compare
8b1d241
to
766e4b7
Compare
mask-pp
approved these changes
Oct 20, 2022
colinlyguo
approved these changes
Oct 20, 2022
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.
i remove
latest
because we should only tag/publishlatest
when merging intomain
branchwill think about a way of how to deal with it later