upload nightly to deken, manual upload setting for release #118
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
this removes the deken upload logic for
releaseruns and just expects the checkbox in the manually dispatched run (seems more elegant and logical anyway):besides that (and more importantly),
nightlybuilds are also uploaded to deken - as suggested in #111 (comment). the version is derived the same way as for releases, but an additional-nightlysuffix is added. the result looks like this (these were my test runs and i removed the packages again):this works pretty well; the only issue that i see is that users will probably install the nightly version by default - the deken app has preference toggles to only display the latest version and only for the system architecture. with these set, the result looks like this (but it's obviously exactly the same for Gem snapshots):
to properly run, this requires flucoma/actions#8 and a
v6tag on the actions side.