actions/gradle-build-action
1
0
Fork 0
mirror of https://github.com/gradle/gradle-build-action.git synced 2024-11-24 17:21:04 -05:00
Code Issues Projects Releases Packages Wiki Activity
gradle-build-action/.github/workflows/ci-quick-check.yml

92 lines
2.4 KiB
YAML
Raw Normal View History

Capitalize to improve ordering
2022-05-29 16:59:36 -04:00
name: CI-quick-check
Combine all integTest workflows into 2 workflow runs - Workflow to run all integTest workflows, allowing use of prior cache entries - Workflow that starts with empty cache Both of these use workflow_call to combine the existing workflows.
2022-05-28 10:55:58 -04:00
on:
Allow manual trigger of CI pipelines
2022-06-14 13:34:09 -04:00
workflow_dispatch:
Combine all integTest workflows into 2 workflow runs - Workflow to run all integTest workflows, allowing use of prior cache entries - Workflow that starts with empty cache Both of these use workflow_call to combine the existing workflows.
2022-05-28 10:55:58 -04:00
push:
Do full checks on release branches
2024-01-23 17:05:57 -05:00
branches-ignore:
- main
- release/**
Combine all integTest workflows into 2 workflow runs - Workflow to run all integTest workflows, allowing use of prior cache entries - Workflow that starts with empty cache Both of these use workflow_call to combine the existing workflows.
2022-05-28 10:55:58 -04:00
jobs:
action-inputs:
uses: ./.github/workflows/integ-test-action-inputs.yml
Build distribution when running quick-check workflow The action requires the generated distribution to committed to the 'dist' directory. During regular development this step causes a number of problems: - It's easy to forget to add/commit these generated files. - It's very difficult/impossible to merge/rebase commits that involve generated files - These file add unnecessary bulk to the git history With this change, the quick-check workflow will first build the distribution and then use the generated output for testing. Building and committing these files will only be required when merging into the 'main' branch.
2022-05-29 15:47:45 -04:00
with:
runner-os: '["ubuntu-latest"]'
Add integration test for cache cleanup
2022-06-14 13:04:48 -04:00
Combine all integTest workflows into 2 workflow runs - Workflow to run all integTest workflows, allowing use of prior cache entries - Workflow that starts with empty cache Both of these use workflow_call to combine the existing workflows.
2022-05-28 10:55:58 -04:00
caching-config:
Update integ test for config-cache caching - Rename test for clarity - Use cache-encryption-key in config-cache test
2023-12-20 12:58:56 -05:00
uses: ./.github/workflows/integ-test-caching-config.yml
Build distribution when running quick-check workflow The action requires the generated distribution to committed to the 'dist' directory. During regular development this step causes a number of problems: - It's easy to forget to add/commit these generated files. - It's very difficult/impossible to merge/rebase commits that involve generated files - These file add unnecessary bulk to the git history With this change, the quick-check workflow will first build the distribution and then use the generated output for testing. Building and committing these files will only be required when merging into the 'main' branch.
2022-05-29 15:47:45 -04:00
with:
runner-os: '["ubuntu-latest"]'
Combine all integTest workflows into 2 workflow runs - Workflow to run all integTest workflows, allowing use of prior cache entries - Workflow that starts with empty cache Both of these use workflow_call to combine the existing workflows.
2022-05-28 10:55:58 -04:00
Add basic test coverage for dependency graph - Test workflow with dependency graph enabled - Gradle test for init-script functionality
2023-07-05 18:43:29 -04:00
dependency-graph:
uses: ./.github/workflows/integ-test-dependency-graph.yml
Set workflow permissions where required
2024-01-01 19:13:16 -05:00
permissions:
contents: write
Add basic test coverage for dependency graph - Test workflow with dependency graph enabled - Gradle test for init-script functionality
2023-07-05 18:43:29 -04:00
with:
runner-os: '["ubuntu-latest"]'
Add tests for dependency graph failures
2024-01-12 12:11:42 -05:00
dependency-graph-failures:
uses: ./.github/workflows/integ-test-dependency-graph-failures.yml
with:
runner-os: '["ubuntu-latest"]'
Combine all integTest workflows into 2 workflow runs - Workflow to run all integTest workflows, allowing use of prior cache entries - Workflow that starts with empty cache Both of these use workflow_call to combine the existing workflows.
2022-05-28 10:55:58 -04:00
execution-with-caching:
uses: ./.github/workflows/integ-test-execution-with-caching.yml
Build distribution when running quick-check workflow The action requires the generated distribution to committed to the 'dist' directory. During regular development this step causes a number of problems: - It's easy to forget to add/commit these generated files. - It's very difficult/impossible to merge/rebase commits that involve generated files - These file add unnecessary bulk to the git history With this change, the quick-check workflow will first build the distribution and then use the generated output for testing. Building and committing these files will only be required when merging into the 'main' branch.
2022-05-29 15:47:45 -04:00
with:
runner-os: '["ubuntu-latest"]'
Combine all integTest workflows into 2 workflow runs - Workflow to run all integTest workflows, allowing use of prior cache entries - Workflow that starts with empty cache Both of these use workflow_call to combine the existing workflows.
2022-05-28 10:55:58 -04:00
execution:
uses: ./.github/workflows/integ-test-execution.yml
Build distribution when running quick-check workflow The action requires the generated distribution to committed to the 'dist' directory. During regular development this step causes a number of problems: - It's easy to forget to add/commit these generated files. - It's very difficult/impossible to merge/rebase commits that involve generated files - These file add unnecessary bulk to the git history With this change, the quick-check workflow will first build the distribution and then use the generated output for testing. Building and committing these files will only be required when merging into the 'main' branch.
2022-05-29 15:47:45 -04:00
with:
runner-os: '["ubuntu-latest"]'
Combine all integTest workflows into 2 workflow runs - Workflow to run all integTest workflows, allowing use of prior cache entries - Workflow that starts with empty cache Both of these use workflow_call to combine the existing workflows.
2022-05-28 10:55:58 -04:00
Update GE injection script for Develocity rename - Rename all env vars expected by init-script: `s/GRADLE_ENTERPRISE/DEVELOCITY` - Update README for changes - Use `Develocity` consistently in tests
2024-01-10 22:30:40 -05:00
develocity-injection:
uses: ./.github/workflows/integ-test-inject-develocity.yml
Add integ-test for GE injection
2023-08-20 16:56:16 -04:00
with:
runner-os: '["ubuntu-latest"]'
Simplify GE-inject config params (#863)
2023-08-28 13:59:09 -04:00
secrets:
Update GE injection script for Develocity rename - Rename all env vars expected by init-script: `s/GRADLE_ENTERPRISE/DEVELOCITY` - Update README for changes - Use `Develocity` consistently in tests
2024-01-10 22:30:40 -05:00
DEVELOCITY_ACCESS_KEY: ${{ secrets.GE_SOLUTIONS_ACCESS_TOKEN }}
Add integ-test for GE injection
2023-08-20 16:56:16 -04:00
More consistent names for workflow jobs
2022-05-29 16:58:14 -04:00
provision-gradle-versions:
uses: ./.github/workflows/integ-test-provision-gradle-versions.yml
Build distribution when running quick-check workflow The action requires the generated distribution to committed to the 'dist' directory. During regular development this step causes a number of problems: - It's easy to forget to add/commit these generated files. - It's very difficult/impossible to merge/rebase commits that involve generated files - These file add unnecessary bulk to the git history With this change, the quick-check workflow will first build the distribution and then use the generated output for testing. Building and committing these files will only be required when merging into the 'main' branch.
2022-05-29 15:47:45 -04:00
with:
runner-os: '["ubuntu-latest"]'
Combine all integTest workflows into 2 workflow runs - Workflow to run all integTest workflows, allowing use of prior cache entries - Workflow that starts with empty cache Both of these use workflow_call to combine the existing workflows.
2022-05-28 10:55:58 -04:00
Reinstate configuration-cache save/restore capability
2023-12-13 14:45:03 -05:00
restore-configuration-cache:
uses: ./.github/workflows/integ-test-restore-configuration-cache.yml
with:
runner-os: '["ubuntu-latest"]'
Enable config-cache tests - Enable in full-build - Pass encryption key secret to test workflow
2024-01-01 21:36:40 -05:00
secrets:
GRADLE_ENCRYPTION_KEY: ${{ secrets.GRADLE_ENCRYPTION_KEY }}
Combine all integTest workflows into 2 workflow runs - Workflow to run all integTest workflows, allowing use of prior cache entries - Workflow that starts with empty cache Both of these use workflow_call to combine the existing workflows.
2022-05-28 10:55:58 -04:00
Add test for action in containerized runner
2022-06-05 23:11:24 -04:00
restore-containerized-gradle-home:
uses: ./.github/workflows/integ-test-restore-containerized-gradle-home.yml
Combine all integTest workflows into 2 workflow runs - Workflow to run all integTest workflows, allowing use of prior cache entries - Workflow that starts with empty cache Both of these use workflow_call to combine the existing workflows.
2022-05-28 10:55:58 -04:00
restore-custom-gradle-home:
uses: ./.github/workflows/integ-test-restore-custom-gradle-home.yml
restore-gradle-home:
uses: ./.github/workflows/integ-test-restore-gradle-home.yml
Build distribution when running quick-check workflow The action requires the generated distribution to committed to the 'dist' directory. During regular development this step causes a number of problems: - It's easy to forget to add/commit these generated files. - It's very difficult/impossible to merge/rebase commits that involve generated files - These file add unnecessary bulk to the git history With this change, the quick-check workflow will first build the distribution and then use the generated output for testing. Building and committing these files will only be required when merging into the 'main' branch.
2022-05-29 15:47:45 -04:00
with:
runner-os: '["ubuntu-latest"]'
Combine all integTest workflows into 2 workflow runs - Workflow to run all integTest workflows, allowing use of prior cache entries - Workflow that starts with empty cache Both of these use workflow_call to combine the existing workflows.
2022-05-28 10:55:58 -04:00
restore-java-toolchain:
uses: ./.github/workflows/integ-test-restore-java-toolchain.yml
Build distribution when running quick-check workflow The action requires the generated distribution to committed to the 'dist' directory. During regular development this step causes a number of problems: - It's easy to forget to add/commit these generated files. - It's very difficult/impossible to merge/rebase commits that involve generated files - These file add unnecessary bulk to the git history With this change, the quick-check workflow will first build the distribution and then use the generated output for testing. Building and committing these files will only be required when merging into the 'main' branch.
2022-05-29 15:47:45 -04:00
with:
runner-os: '["ubuntu-latest"]'
Combine all integTest workflows into 2 workflow runs - Workflow to run all integTest workflows, allowing use of prior cache entries - Workflow that starts with empty cache Both of these use workflow_call to combine the existing workflows.
2022-05-28 10:55:58 -04:00
sample-kotlin-dsl:
uses: ./.github/workflows/integ-test-sample-kotlin-dsl.yml
Build distribution when running quick-check workflow The action requires the generated distribution to committed to the 'dist' directory. During regular development this step causes a number of problems: - It's easy to forget to add/commit these generated files. - It's very difficult/impossible to merge/rebase commits that involve generated files - These file add unnecessary bulk to the git history With this change, the quick-check workflow will first build the distribution and then use the generated output for testing. Building and committing these files will only be required when merging into the 'main' branch.
2022-05-29 15:47:45 -04:00
with:
runner-os: '["ubuntu-latest"]'
Combine all integTest workflows into 2 workflow runs - Workflow to run all integTest workflows, allowing use of prior cache entries - Workflow that starts with empty cache Both of these use workflow_call to combine the existing workflows.
2022-05-28 10:55:58 -04:00
sample-gradle-plugin:
uses: ./.github/workflows/integ-test-sample-gradle-plugin.yml
Build distribution when running quick-check workflow The action requires the generated distribution to committed to the 'dist' directory. During regular development this step causes a number of problems: - It's easy to forget to add/commit these generated files. - It's very difficult/impossible to merge/rebase commits that involve generated files - These file add unnecessary bulk to the git history With this change, the quick-check workflow will first build the distribution and then use the generated output for testing. Building and committing these files will only be required when merging into the 'main' branch.
2022-05-29 15:47:45 -04:00
with:
runner-os: '["ubuntu-latest"]'
Add test for detection of java toolchains
2023-08-19 19:26:13 -04:00
toolchain-detection:
uses: ./.github/workflows/integ-test-detect-java-toolchains.yml
with:
runner-os: '["ubuntu-latest"]'
Reference in a new issue Copy permalink