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

Migrated from gradle conventions plugin to CCUD plugin #303

Merged
merged 4 commits into from
Aug 2, 2024

Conversation

ribafish
Copy link
Member

Migrated from gradle conventions plugin to CCUD plugin and fixed and updated the Github Actions to enable CI to publish scans and write to remote build cache.

@ribafish ribafish merged commit fbcd658 into main Aug 2, 2024
6 checks passed
@ribafish ribafish deleted the gk/migrateCcud branch August 2, 2024 11:51
Copy link
Contributor

@runningcode runningcode left a comment

Choose a reason for hiding this comment

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

otherwise, LGTM!

- name: "Setup Build Environment"
uses: ./.github/actions/setup-environment

- name: 'Setup Gradle'
uses: gradle/actions/setup-gradle@v3
with:
Copy link
Contributor

Choose a reason for hiding this comment

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

do we need the key for the setup action? or just the build action?

Copy link
Member Author

Choose a reason for hiding this comment

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

In the setup action the key is used to get the access token, which is then actually used. In the build action it's there more for the remote cache push, since this is an OSS project. I can also remove it from the build action and as a check for remote cache push in the settings.gradle.kts.

- uses: gradle/gradle-build-action@v3

- name: 'Setup Gradle'
uses: gradle/actions/setup-gradle@v3
with:
Copy link
Contributor

Choose a reason for hiding this comment

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

same question as above :)

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