Skip to content

Conversation

@StephanDollberg
Copy link
Member

@StephanDollberg StephanDollberg commented Dec 2, 2025

Adds a github actions job to upload the minimal tar.gz to our S3 bucket
such that we can use it in bazel.

@StephanDollberg StephanDollberg requested a review from a team as a code owner December 2, 2025 10:50
@StephanDollberg StephanDollberg requested review from travisdowns and removed request for a team December 2, 2025 10:50
@StephanDollberg StephanDollberg force-pushed the stephan/ga branch 5 times, most recently from c018ab7 to 6230304 Compare December 2, 2025 11:01
branches: [main]
pull_request:
branches:
- main
Copy link
Member

Choose a reason for hiding this comment

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

Is this right? Will this upload the artifact from PRs before they are merged?

Copy link
Member

Choose a reason for hiding this comment

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

(I assume you don't want to do that)

Copy link
Member Author

Choose a reason for hiding this comment

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

No I don't, this is all still WIP testing phase. I need devprod to create some credentials first.

@StephanDollberg StephanDollberg force-pushed the stephan/ga branch 3 times, most recently from b67b098 to 901ad4f Compare December 11, 2025 10:21
Adds a github actions job to build and upload the minimal tar.gz to our
S3 bucket such that we can use it in bazel.

On PRs only build.
branches: [main]
pull_request:
branches:
- main
Copy link
Member

Choose a reason for hiding this comment

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

Trying out all the YAML list variations, huh?

Copy link
Member Author

Choose a reason for hiding this comment

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

LOL I don't understand yaml to this day.

Copy link
Member Author

Choose a reason for hiding this comment

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

Isn't this one the normal one?

Copy link
Member

@travisdowns travisdowns Dec 16, 2025

Choose a reason for hiding this comment

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

This is the most common one I think but right above for identical branches you have the other one.

Copy link
Member

@ivotron ivotron Dec 16, 2025

Choose a reason for hiding this comment

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

just to clarify:

  • push.branches. triggers it whenever a commit gets pushed to the given list of branches. so this would trigger when a PR is merged to the main branch, and also if someone pushed directly to it (though we disallow that via branch protection rules)
  • pull_request.branches. triggers the job when a PR against the main branch is opened, or when new commits to an existing PR's branch are pushed
  • workflow_dispatch. allows the workflow to be triggered by other workflows or manually when a person runs it from the web UI.

so your goal is to have this workflow run in any of the above scenarios?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes the first two is what we want.

The last I don't really mind but is good to have I guess.

on:
push:
branches: [main]
pull_request:
Copy link
Member

Choose a reason for hiding this comment

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

Cool, so we get build on PRs too, nice!

run: mvn clean compile package -DskipTests

- name: Upload to S3 bucket
if: github.event_name == 'push'
Copy link
Member

Choose a reason for hiding this comment

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

So this works on a GH "merge PR" click, right?

Copy link
Member Author

Choose a reason for hiding this comment

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

That's what I expect yes.

Copy link
Member

Choose a reason for hiding this comment

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

so this will ONLY upload when a PR is merged. that's what you want, right?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes exactly.

Copy link
Member

@travisdowns travisdowns left a comment

Choose a reason for hiding this comment

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

Looks good to me, but let's get devprod eyes on it too.

@ivotron
Copy link
Member

ivotron commented Dec 16, 2025

lgtm

@StephanDollberg StephanDollberg merged commit 3b204f6 into main Dec 17, 2025
1 check passed
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