-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
Add test repository #190
Add test repository #190
Conversation
I think many test repos need to be removed. |
Yes, that was what I was thinking too. |
It may also be possible to run some things in parallel, also trying out circle-ci may also be an option. |
Do you mean running the java-parser and the prettier plugin on the separate jobs or running a job on each test repositories ?
I think we should migrate the CI to Azure Pipelines since the other repositories are migrated here (travis is not going well). Btw, I removed most of repositories to just keep 2 JHipster repositories, Spring-Boot and java design patterns and the build time is now 11-13 minutes. |
We could have 3 parallel jobs each with a different env variable and each doing a different set of repo checks.
We should change it to 8/10/12 and it is needed to ensure our code runs on all modern node.js versions.
That is better, It is actually ~8 mins for the longest job so its perfectly fine. |
I have added some repositories to test and it seems that the plugin can now successfully prettify spring-boot and still be semantically valid.
I also added some fixes.
fix #186