-
-
Notifications
You must be signed in to change notification settings - Fork 155
Move Azure pipelines to Github Actions #567
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
55d8c0a to
5ec84f0
Compare
|
Pushed a change to add an empty line to the end of files, and mark the nightly as prerelease. |
5ec84f0 to
3ff4358
Compare
|
SonarCloud Quality Gate failed.
|
|
Removed the prerelease tag... |
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week. |
|
Go out, stale bot... |
|
AUTOMERGE: (FAIL)
|
|
Please don't merge yet. Need to solve sonar duplication warnings (otherwise we have this issue on each subsequent change). |
|
@McGiverGim please rebase (if needed) and push again so we are able to analyze the build (as it's not available anymore) |
|
I can do it tomorrow, but I see the build and the artifacts available. |
728b108
3ff4358 to
728b108
Compare
|
Rebased against master... |
d002a6e to
e6a13c0
Compare
|
I don't know why it detects the code duplication. My PR does not touch the files that complains. Maybe SonarCloud has modified the way to detect duplications and for this reason now it appears in this PR. |
e6a13c0 to
803cc55
Compare
|
SonarCloud Quality Gate failed.
|
|
Rebased, the false positive of code duplication continues there... |
|
@blckmn it seems some permission is missing for the nightly release. Did you add it as requested on the first message? |
Yep - missed that step. Have now added the repo_token. |









This moves the CI system from Azure pipelines to Github Actions, like it has been done in the Configurator.
Thanks to @mathiasvr for the original code, this only modifies it slightly.
@blckmn this will need the same changes done in the Configurator before merging:
This has been tested in the Configurator, so I think is safe to merge. I have tested it in my repo too before doing the PR.