Skip to content
This repository has been archived by the owner on Mar 21, 2021. It is now read-only.

Setting up Jhipster-Core for Azure Pipelines #326

Closed
Shaolans opened this issue May 20, 2019 · 4 comments
Closed

Setting up Jhipster-Core for Azure Pipelines #326

Shaolans opened this issue May 20, 2019 · 4 comments
Assignees

Comments

@Shaolans
Copy link
Member

Shaolans commented May 20, 2019

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)

@pascalgrimaud pascalgrimaud self-assigned this May 20, 2019
@pascalgrimaud
Copy link
Member

The first thing you can do, is to init a very simple azure-pipelines.yml to this repo.
So it will be easier for me to start to configure Azure.

Similar to: jhipster/prettier-java#199

@pascalgrimaud
Copy link
Member

Don't forget to add badge to readme, @Shaolans :)

@Shaolans
Copy link
Member Author

Thanks ! I almost forgot 👍

@Shaolans
Copy link
Member Author

This is not relevant anymore since we migrated to Github Actions

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants