-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Polish Azure Pipelines build #1810
Comments
I can't find the "Advanced settings..." described here https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/pipeline-options-for-git?view=azure-devops to activate the "Shallow fetch" option. |
This commit will be reverted when credentials are stored in the Azure Pipeline account. Addresses #1810
Sorry for the confusion - we have two independent ways to configure CI, either the visual designer or the YAML. It's pretty much all or nothing (all visual designer or all YAML) and those instructions guide you to the visual designer path. We're using YAML which is right and true, so I opened #1812 to add the shallow clone rules to the YAML. |
Understood. We are trying to insert our secret credentials via UI right now. Looking forward to merge #1812 and proceed with the switch. |
Should be something like:
@sormuras I can send a PR unless you're in the middle of this. |
About to push it in a second... ;-) |
- "Linux (OpenJDK 11)" published its test results - "Publish Snapshot Artifacts" is longer allowed to fail - "Publish Snapshot Artifacts" depends on "Linux (OpenJDK 11)" - "Update Snapshot Documentation" depends on "Linux (OpenJDK 11)" Addresses #1810
See 6706691 ... chose |
@ethomson ... those two publish/update jobs (and the coverage job as well) are good candidates for a dedicated "Release Pipeline", aren't they? |
@sormuras - I actually would not in this case. There's a couple of reasons:
So, to be honest, I would keep this as-is for now, it's simpler and gets the job done. If you want to scale things up or increase the complexity then it makes sense to reconsider. |
Keeping things as-is. Thanks for the details. |
Blocked by gradle/gradle#8681 Issue #1810
Updated deliverables with "clean up" entries. |
Performance comparison
But
|
Caching is not yet supported at Azure Pipelines: https://devblogs.microsoft.com/devops/adding-caching-to-azure-pipelines/ |
I guess we could build our own Docker image with a "pre-warmed" cache but it's probably not worth the complexity. |
Let's wait for ... "SOON". |
"Publish" jobs were executed although "Build+Test" jobs failed? https://dev.azure.com/junit-team/junit5/_build/results?buildId=59 |
Sorry, that's my fault. I thought it was an accurate translation of the Travis but I may be wrong. Either way I didn't think through the logic very well. 😝 We should just need a |
This commit will be reverted when credentials are stored in the Azure Pipeline account. Addresses #1810
- "Linux (OpenJDK 11)" published its test results - "Publish Snapshot Artifacts" is longer allowed to fail - "Publish Snapshot Artifacts" depends on "Linux (OpenJDK 11)" - "Update Snapshot Documentation" depends on "Linux (OpenJDK 11)" Addresses #1810
Blocked by gradle/gradle#8681 Issue #1810
We'll look into caching dependencies in #1826. |
After-math for #1807 and closes #1795.
Deliverables
Configure dependency cache on Azure Pipelineswill be done in Configure dependency cache on GitHub Actions #1826The text was updated successfully, but these errors were encountered: