ci: more automation #213
Merged
ci: more automation #213
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
JonasVautherin
force-pushed
the
ci-automate-release
branch
from
048ac4e to
e1be6ed
Compare
JonasVautherin
force-pushed
the
ci-automate-release
branch
from
e1be6ed to
0c35e90
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.
The idea here is to have the CI automatically build and deploy MAVSDK-Java based on the release tag. E.g. if we tag a release
3.7.0-SNAPSHOT, the CI can extract the "3.7.0" part and update the proto submodule to match MAVSDK-C++'s v3.7.0 proto submodule. Then it can run the build and publish the artifacts as "3.7.0-SNAPSHOT".The goal is to make it easier to update MAVSDK-Java when the only change needed is to compile the new proto files and pull the new mavsdk_server binary.