- 
                Notifications
    
You must be signed in to change notification settings  - Fork 53
 
MLE-24733 Merging the two test ml-gradle projects #1026
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
Conversation
Needs two separate invocations to handle data/modules going to different locations.
| 
           Copyright Validation Results ⏭️ Skipped (Excluded) Files
 ✅ All files have valid copyright headers!  | 
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR consolidates two separate ml-gradle test projects by merging test-complete-app-mlDeploy into test-app. The changes eliminate the duplicate deployment project and configure test-app to handle both standard and e2e test deployments through separate invocations with different property configurations.
- Removed the standalone 
test-complete-app-mlDeployproject directory and all its files - Enhanced 
test-appto support e2e test data/module deployment via a newgradle-e2e.propertiesconfiguration - Updated CI/CD and documentation to reflect the consolidated approach
 
Reviewed Changes
Copilot reviewed 25 out of 77 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description | 
|---|---|
| test-complete-app-mlDeploy/* | Entire directory removed including security configs, gradle wrapper, and build files | 
| test-app/gradle-e2e.properties | New properties file defining e2e-specific data/module paths and database configuration | 
| test-app/gradle.properties | Added properties plugin configuration for environment-based property loading | 
| test-app/build.gradle | Added properties plugin version update and curl tasks previously in mlDeploy project | 
| test-app/src/main/ml-config/servers/node-client-api-ssl-server.json | Updated SSL certificate template reference | 
| Jenkinsfile | Streamlined e2e test setup by removing separate mlDeploy project deployment | 
| CONTRIBUTING.md | Updated deployment instructions to include e2e data/module loading step | 
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "authentication": "digestbasic", | ||
| "ssl-certificate-template": "ssl-project-template" | ||
| } | ||
| "ssl-certificate-template": "node-client-ssl-template" | 
    
      
    
      Copilot
AI
    
    
    
      Oct 29, 2025 
    
  
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The SSL certificate template reference has been changed from 'ssl-project-template' to 'node-client-ssl-template', but this new template is not included in the visible configuration files. Ensure this template is defined elsewhere in the project or deployed separately.
Needs two separate invocations to handle data/modules going to different locations.