-
Notifications
You must be signed in to change notification settings - Fork 113
feat: add run configurations to improve developer experience #4087
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
feat: add run configurations to improve developer experience #4087
Conversation
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 adds pre-configured IntelliJ IDEA run configurations to streamline the local development setup. Developers can now launch all backend microservices, the frontend application, and lakeFS directly from IntelliJ's run menu without manually searching for main classes or compose files.
- Adds 8 individual run configurations for backend microservices (AccessControlService, ComputingUnitManagingService, ComputingUnitMaster, ComputingUnitWorker, ConfigService, FileService, TexeraWebApplication, WorkflowCompilingService)
- Adds a compound run configuration to launch all backend services together
- Adds configurations for frontend (npm start) and lakeFS (Docker Compose)
Reviewed changes
Copilot reviewed 11 out of 11 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| .run/AccessControlService.run.xml | Run configuration for the AccessControlService microservice |
| .run/ComputingUnitManagingService.run.xml | Run configuration for the ComputingUnitManagingService microservice |
| .run/ComputingUnitMaster.run.xml | Run configuration for the ComputingUnitMaster component |
| .run/ComputingUnitWorker.run.xml | Run configuration for the ComputingUnitWorker component |
| .run/ConfigService.run.xml | Run configuration for the ConfigService microservice |
| .run/FileService.run.xml | Run configuration for the FileService microservice |
| .run/TexeraWebApplication.run.xml | Run configuration for the main TexeraWebApplication service |
| .run/WorkflowCompilingService.run.xml | Run configuration for the WorkflowCompilingService microservice |
| .run/frontend.run.xml | Run configuration for the frontend application using npm start |
| .run/texera-lakefs.run.xml | Docker Compose run configuration for lakeFS |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
@mengw15 @Xiao-zhen-Liu can you test it? |
I just tested this feature and it works fine on my side. |
|
Also @aglinxinyuan @aicam please test it as well. |
aglinxinyuan
left a comment
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.
LGTM!
|
@chenlica @aglinxinyuan can we merge it? |
### What changes were proposed in this PR? Add a configuration option to automatically shorten file paths for Windows users when the original path exceeds the system’s maximum length. After this PR, Windows users should not see this error anymore. <img width="612" height="157" alt="image" src="https://github.com/user-attachments/assets/73a23ef2-0fad-4f2f-bc99-c7f2e576a4d9" /> ### Any related issues, documentation, discussions? Follow-up of PR #4087 ### How was this PR tested? Tested manually. ### Was this PR authored or co-authored using generative AI tooling? No
What changes were proposed in this PR?
This PR adds pre-configured IntelliJ run configurations for:
With these changes, developers can now launch the backend services, lakeFS, and frontend directly from IntelliJ’s run menu, eliminating the need to manually locate and configure each relevant class or compose file. This leverages IntelliJ’s built-in Compound and individual run configurations, so no additional plugins are required.
2025-11-26.13-46-11.mp4
Any related issues, documentation, discussions?
Fixes #4045
How was this PR tested?
Verified on a local IntelliJ IDEA environment. The Compound run config cleanly launches all backend microservices in parallel.
Was this PR authored or co-authored using generative AI tooling?
No