You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 21, 2021. It is now read-only.
Since Travis future is now uncertain, we should progressively migrate our CI to Azure Pipelines like we did for the generator or prettier-java.
Motivation for or Use Case
Travis is not doing well.
Azure Pipelines can have up to 10 parallel jobs (5 for Travis)
The sonar is currently broken 0% coverage, this is due to the sonar addon on travis. (It can be easily fixed)
Related issues or PR
I worked on the ci migration and made it worked here but the pipeline needs to be configured beforehand:
Overview of the feature request
Since Travis future is now uncertain, we should progressively migrate our CI to Azure Pipelines like we did for the generator or prettier-java.
Motivation for or Use Case
Travis is not doing well.
Azure Pipelines can have up to 10 parallel jobs (5 for Travis)
The sonar is currently broken 0% coverage, this is due to the sonar addon on travis. (It can be easily fixed)
Related issues or PR
I worked on the ci migration and made it worked here but the pipeline needs to be configured beforehand:
Install sonarcloud extension
add a service connection for SonarCloud
[ x] Checking this box is mandatory (this is just to show you read everything)
The text was updated successfully, but these errors were encountered: