Update distribution-scripts and publish nightly packages to bintray #9663
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
* crystal-lang/distribution-scripts#72 Bintray publishing scripts * crystal-lang/distribution-scripts#73 Update shards v0.12.0
nightlies .tar.gz .deb .rpm will be branded as x.y.z-dev
waj
approved these changes
Aug 6, 2020
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.
Includes the following changes from distribution-scripts:
It publishes nightly packages to bintray deb and rpm repos. A sample run was made at https://circleci.com/workflow-run/56b17888-c9bd-493a-83a1-d5e1fcb74aa8. The names for the files are changed from
nightly-YYYYMMDDtox.y.x-dev(or whatever is stated in thesrc/VERSIONfile).https://bintray.com/beta/#/crystal/deb/crystal/1.0.0-dev?tab=overview
I'm also including some branch rules to run only the package steps (without test), I've been using this multiple times already to avoid running the whole maintenance workflow in some situations.