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

Test more DV plugin versions #13

Merged
merged 8 commits into from
Nov 9, 2024
Merged

Test more DV plugin versions #13

merged 8 commits into from
Nov 9, 2024

Conversation

bigdaz
Copy link
Member

@bigdaz bigdaz commented Nov 8, 2024

This PR extends coverage of the init-script to include more plugin versions.

These tests exposed an issue when enforcing the DV URL on a project that already
applies the com.gradle.build-scan:[3.17,3.18.1] plugin.
As such, these versions are excluded from testing for now.

We do not test early versions of the GE/BuildScan plugins, since the mock server protocol
appears to have changed. This will require fixing to expand the coverage further.

@bigdaz bigdaz changed the title Test move DV plugin versions Test more DV plugin versions Nov 8, 2024
@bigdaz bigdaz force-pushed the dd/test-plugin-versions branch 2 times, most recently from 0ccb8ab to 17d0033 Compare November 8, 2024 02:54
Copy link
Member

@erichaagdev erichaagdev left a comment

Choose a reason for hiding this comment

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

LGTM, but it will need to be rebased to drop 5494507

Previously, our test coverage for injection of the DV plugin was limited to the latest DV plugin. The only exception was testing v3.16.2, but even then we failed to test setting the DV URL, capture fingerprints, etc.

With this change, we now test running the init-script with different DV versions to inject, ensuring our script continues to support injection of older plugin versions (which may be required if the DV server environment is out of date).
The log messages are used to test init-script functionality.
This change moves the 'Enforce URL' logging so that it is only
emitted when DV URL is actually forced.
The init-script must be able to apply configuration to a Gradle build that already
has the DV plugin applied, and must not error regardless of the DV plugin version applied.

Previously, we only tested against Gradle builds using the latest DV plugin, and GE plugin v3.16.2.
With this change, we now test running the init-script on projects with many different DV versions applied.
- Avoid CCUD tests where plugins are not compatible
- Temporarily ignore tests that demonstrate issue with enforceUrl and GE plugin < 3.2
Several "successful" CCUD scenarios were logging errors from build scan publishing.
We now check that no exceptions are logged when applying the init-script.
@bigdaz bigdaz merged commit 3c5c0f7 into main Nov 9, 2024
1 check passed
@bigdaz bigdaz deleted the dd/test-plugin-versions branch November 9, 2024 16:01
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.

2 participants