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

Default revision #5610

Draft
wants to merge 10 commits into
base: master
Choose a base branch
from

Conversation

edmundmiller
Copy link
Contributor

Closes #4427

Need to clean up this PR a bit, and test it out in a real-world, not just in tests.

Copy link

netlify bot commented Dec 13, 2024

Deploy Preview for nextflow-docs-staging failed. Why did it fail? →

Name Link
🔨 Latest commit d1ebdcc
🔍 Latest deploy log https://app.netlify.com/sites/nextflow-docs-staging/deploys/6762d01fa509ae00089d8654

edmundmiller and others added 10 commits December 13, 2024 10:59
- Implemented `getDefaultRevision()` method in `Manifest.groovy` to retrieve the default revision.
- Updated `AssetManager.groovy` to compare the current revision against the default revision instead of the default branch during checkout.
…efaultRevision scenarios

- Added tests to verify behavior of AssetManager when handling defaultBranch and defaultRevision configurations.
- Implemented scenarios for defaultBranch set to 'master', defaultRevision specified, and version as defaultRevision.
- Included tests for cases with no defaultBranch and fallback mechanisms to ensure correct defaults are applied.
- Ensured that commit hashes can be used as defaultRevision and validated the handling of version tags in absence of defaultBranch.
- Marked several tests as PendingFeature for future implementation.

refactor: Remove PendingFeature annotations from AssetManagerTest

- Removed @PendingFeature annotations from multiple test cases in AssetManagerTest.groovy.
- This change indicates that the tests are now fully implemented and ready for execution.
- The tests cover scenarios for defaultBranch and defaultRevision configurations, ensuring comprehensive validation of AssetManager behavior.
- Removed @PendingFeature annotations from multiple test cases, indicating they are fully implemented.
- Added comprehensive tests for AssetManager's handling of defaultBranch and defaultRevision configurations.
- Implemented scenarios for various configurations, including defaultBranch set to 'master', specific defaultRevision, and version as defaultRevision.
- Validated behavior for cases with no defaultBranch and ensured correct fallback mechanisms.
- Enhanced tests for resolving script names and managing repository providers across different platforms.
…onsolidating configurations

- Removed several test cases that were redundant or overly complex, focusing on essential scenarios for AssetManager's behavior.
- Consolidated Git configuration tests into static final strings for better readability and maintainability.
- Streamlined the setup process for tests, ensuring clarity in the initialization of AssetManager instances.
- Enhanced the clarity of the remaining tests by improving comments and structure, making it easier to understand the purpose of each test case.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Set a default revision
2 participants