Skip to content
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

CI: Create Continuous Prerelease #11929

Merged
merged 1 commit into from
Oct 16, 2024
Merged

Conversation

HTRamsey
Copy link
Collaborator

This should upload commits to master to a continuous release making it easy for people to download daily builds

@HTRamsey HTRamsey requested a review from mrpollo September 28, 2024 21:01
@HTRamsey
Copy link
Collaborator Author

@mrpollo Thoughts on this?

@mrpollo
Copy link
Member

mrpollo commented Oct 3, 2024

This should work, but we must test it as soon as possible. Unfortunately, we can't test until we merge.

By the way, I'm also using the same action package for PX4 here: PX4/PX4-Autopilot#23703.

@@ -43,3 +43,11 @@ runs:
working-directory: ${{ runner.temp }}/shadow_build_dir/${{ inputs.source }}
run: aws s3 cp ${{ inputs.artifact_name }} s3://qgroundcontrol/latest/${{ inputs.artifact_name }} --acl public-read
shell: bash

- name: Create Continuous Release
if: ${{ github.event_name != 'pull_request' && github.ref_name == 'master' && !github.event.pull_request.head.repo.fork }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you test github.ref_name = 'master'? sometimes ref_name isn't what we want

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would skip the fork conditional, I don't its needed

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you creating a release every time you push to master? Is this the desired behavior?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rather than every commit, should it be every night/week?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Daily builds upload to S3 on every merge so seems like it should match that.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also seems like this is way ore important on automating Stables. This just kinda duplicates the S3 thing which is referenced by the docs. I guess some people go here to get releases though.

@HTRamsey HTRamsey requested a review from DonLakeFlyer October 9, 2024 19:23
@HTRamsey HTRamsey marked this pull request as ready for review October 16, 2024 08:47
@HTRamsey HTRamsey merged commit 45eeaac into mavlink:master Oct 16, 2024
7 checks passed
@HTRamsey HTRamsey deleted the dev-ci-continuous branch October 16, 2024 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants