CI misconfiguration are preventing releases or updates to the list of gateways used by the frontend.

[2color]

Problem

• the test & maybe release workflow (source) does not run the release job

Background

• We have two workflows that run concurrently: "test & maybe release" and "Gateway Conformance Dashboard"
• Both workflows commit to the master branch
  • "test & maybe release": creates a release commit with the changelog
  • "Gateway Conformance Dashboard": creates a commit in the aggregate job which updates the conformance results example.
• A race condition between the two running causes the aggregate job to fail example example because other job already committed to the repo.
• https://github.com/ipfs/public-gateway-checker/pull/529 made the test & maybe release workflow run once the conformance one is completed.
• However, this has likely changed the event that triggers the test & maybe release workflow and causes the release-check job to prevent a release (source)

Possible solutions

• Update the conditions for the test & maybe release workflow ( a bit annoying because it's in a different repo https://github.com/ipfs/public-gateway-checker/blob/master/.github/workflows/js-test-and-release.yml#L22)
• Something else I haven't thought of because I'm not so familiar with the CI setup here and all the intentions behind it

[2color]

@lidel @SgtPooki Any thoughts on how to proceed? I think I'm missing some context from how this repo was set up.

[2color]

Following discussion with @lidel

• As it currently stands, we are not using the results from the gateway conformance tests.
• A quick look at the current results (report.json), shows that the results don't seem to even be correct

Some improvements we could handle:

• Decouple the gateway conformance tests from the frontend's source of truth (gateway.txt)
• Use the gateways.txt in the frontend
• Clean up the current list of gateways by removing gateways that don't answer to http HEAD https://ipfs.io/ipfs/bafkqaaa

[SgtPooki]

Yea we have some followup actions from the gateway conformance updates that were made. I haven't had a chance to focus on changes here for a while

[2color]

Closing this as it's not longer a problem. The conformance tests rely on the same source of truth (gateways.json) but aren't blocking releases.