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

Introduce Buildkite pipeline config #40

Merged
merged 15 commits into from
Jan 25, 2024
Merged

Introduce Buildkite pipeline config #40

merged 15 commits into from
Jan 25, 2024

Conversation

wzieba
Copy link
Member

@wzieba wzieba commented Jan 25, 2024

Description

This PR introduces Buildkite pipeline for the project that executes the same Gradle tasks as the GitHub Actions workflow: https://github.com/gravatar/Gravatar-SDK-Android/blob/trunk/.github/workflows/android.yml

@wzieba wzieba changed the title [Draft] Introduce Buildkite pipeline config Introduce Buildkite pipeline config Jan 25, 2024
Actually I think those reports are not useful. The static code analysis tools reports issues directly to the log and browsing them there is faster and more convient than downloading artifacts.
Copy link
Contributor

@hamorillo hamorillo left a comment

Choose a reason for hiding this comment

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

❤️ Looks great! Thanks!

- label: "Build"
command: |
echo "--- ⚒️ Building"
./gradlew assemble
Copy link
Member Author

Choose a reason for hiding this comment

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

This changed from build to assemble because build task in Android Gradle Plugin also performs tests (which we do in a separate job)

Copy link

@AliSoftware AliSoftware Jan 25, 2024

Choose a reason for hiding this comment

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

This changed from build to assemble because build task in Android Gradle Plugin also performs tests (which we do in a separate job)

Worth an inline # comment to keep that info for future readers of the file? 🤔

@wzieba
Copy link
Member Author

wzieba commented Jan 25, 2024

Thanks @hamorillo for the review! I'll also ask Apps Infra member to verify if it's all good.

hi @AliSoftware ! Are you fine with reviewing this PR? 🙂

@wzieba wzieba requested a review from AliSoftware January 25, 2024 14:21
@wzieba wzieba requested a review from AliSoftware January 25, 2024 15:45
Add a comment that helps to understand origin of variables
@wzieba wzieba requested a review from AliSoftware January 25, 2024 15:56
Copy link

@AliSoftware AliSoftware left a comment

Choose a reason for hiding this comment

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

Setup looks good to me now 👍

PS: Side note that you might want to create the .tf terraform setup for this pipeline soon-ish in buildkite-ci PR, because our doc about this in buildkite-ci mentions that the preferred way is usually to create the Buildkite project from the .tf (Option 1), and while importing an existing pipeline/project after the fact (Option 2) is not impossible, it might lead to trickier cases. So you might end up wanting to delete the pipeline/project in Buildkite, then recreate it via terraform, and then check again that the setup still works as expected with your pipeline.yml after that.

- label: "Build"
command: |
echo "--- ⚒️ Building"
./gradlew assemble
Copy link

@AliSoftware AliSoftware Jan 25, 2024

Choose a reason for hiding this comment

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

This changed from build to assemble because build task in Android Gradle Plugin also performs tests (which we do in a separate job)

Worth an inline # comment to keep that info for future readers of the file? 🤔

@wzieba wzieba merged commit 9c625a2 into trunk Jan 25, 2024
1 check passed
@wzieba wzieba deleted the migrate_to_buildkite branch January 25, 2024 17:03
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