change concurrency settings (try to avoid "Error: The operation was canceled.")

[mahibi]

followup of (or maybe should replace?) #5587

Not sure if it helps. Just testing..

Keep in mind also if it solves the "Error: The operation was canceled." issue:

This would change the behavior for builds on master.

Before:

analysis-wrapper-${{ github.head_ref || github.run_id }}

"The following concurrency group cancels in-progress jobs or runs on pull_request events only"

https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-workflow-concurrency#example-using-a-fallback-value

After:

${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}

${{ github.workflow }} is just used for convenience.
The important parts are github.head_ref || github.run_id vs github.event.pull_request.number || github.ref

same as iOS talk uses.
Modified version of https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-workflow-concurrency#example-using-concurrency-and-the-default-behavior

🚧 TODO

• keep an eye on if "Error: The operation was canceled." happens on other branches without these changes
• keep an eye on if "Error: The operation was canceled." still happens in this branch (retrigger builds again..?)
• if it's merged, also do the changes in config repo

🏁 Checklist

• ⛑️ Tests (unit and/or integration) are included or not needed
• 🔖 Capability is checked or not needed
• 🔙 Backport requests are created or not needed: /backport to stable-xx.x
• 📅 Milestone is set
• 🌸 PR title is meaningful (if it should be in the changelog: is it meaningful to users?)

[github-actions]

APK file: https://www.kaminsky.me/nc-dev/android-artifacts/5590.apk



To test this change/fix you can simply download above APK file and install and test it in parallel to your existing Nextcloud app.

[github-actions]

Codacy

Lint

Type	master	PR
Warnings	99	99
Errors	0	0

SpotBugs

Category	Base	New
Bad practice	6	6
Correctness	10	10
Dodgy code	54	54
Internationalization	3	3
Malicious code vulnerability	3	3
Performance	4	4
Security	1	1
Total	81	81

[mahibi]

It also failed with with "Build failed with an exception." in this run (garm3)

FAILURE: Build failed with an exception.

* What went wrong:
Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to generate a Build Scan (powered by Develocity).
> Get more help at https://help.gradle.org.
> Task :app:mergeDexGenericRelease
> Task :app:lintVitalAnalyzeGenericRelease
Error: The operation was canceled.