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
Update pipeline #265
Merged
Merged
Update pipeline #265
Conversation
This file contains 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
Which should distribute with updated icons and translations
amolenaar
force-pushed
the
update-pipeline
branch
from
February 12, 2020 14:49
a084eb5
to
251011f
Compare
should also deal with versions like 1.2.0rc1
Windows-specific dependencies seem to be not picked up.
amolenaar
force-pushed
the
update-pipeline
branch
from
February 14, 2020 19:44
2051899
to
dc009cf
Compare
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.
Make the release builds work again
The general idea is that there should be as few steps not executed. Now the release builds are big jobs that run separate from the test jobs. Ideally one would use the artifacts created by the build process and just release those. No idea if it's possible, though.