CI Pipeline for publishing releases with builds#1
Draft
salotz wants to merge 24 commits intoScopesCommunity:mainfrom
Draft
CI Pipeline for publishing releases with builds#1salotz wants to merge 24 commits intoScopesCommunity:mainfrom
salotz wants to merge 24 commits intoScopesCommunity:mainfrom
Conversation
- switch to new actions method of setting outputs - adding cache of eo downloads - generating build version - separate dep build and app compile - allow manual runs of workflow - make release - cache revision
radgeRayden
force-pushed
the
main
branch
6 times, most recently
from
72e4b8c to
beb2003
Compare
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.
In addition to some refactoring I have implemented a pipeline that publishes Github releases with the build artifacts. This will create a standard URL for downloads rather than the CI artifact downloads.
Currently upstream Scopes has the next version in the source code
config.h, so I pull this in, parse it, and create a prerelease version based on the pipeline number. Its not perfect and their could be something better but it will work.TODOs include reintroducing windows builds and cleaning up some stuff, but I wanted to get feedback.
I would also like to try and get it to trigger via web hooks or something rather than a schedule as many spurious builds and releases will be made.