Skip to content

Remove caching of Maven metadata#211

Merged
TheEadie merged 2 commits into
mainfrom
fix/remove-metadata-caching
Feb 4, 2026
Merged

Remove caching of Maven metadata#211
TheEadie merged 2 commits into
mainfrom
fix/remove-metadata-caching

Conversation

@TheEadie
Copy link
Copy Markdown
Contributor

Description

On self-hosted runners the data would be cached on first run and never updated. This leads to setup-flyway never discovering new versions of Flyway to install unless the agent is rebuilt.

There is a risk that this introduces more traffic to download.red-gate.com

Related issue

None

Check list

  • Mark if documentation changes are required.
  • Mark if tests were added or updated to cover the changes.

@TheEadie TheEadie force-pushed the fix/remove-metadata-caching branch from 7a607a1 to d48e05e Compare January 30, 2026 13:58
On self-hosted runners the data would be cached on first run and never
updated. This leads to setup-flyway never discovering new versions of
Flyway to install unless the agent is rebuilt.
@TheEadie TheEadie force-pushed the fix/remove-metadata-caching branch from d48e05e to fff95a7 Compare February 2, 2026 11:42
@DoodleBobBuffPants
Copy link
Copy Markdown
Contributor

If we want to minimize traffic, maybe the flow ought to be:

  • If version is cached, use it
  • If version is in cached metadata file, use that file
  • Otherwise, fetch and cache metadata file

@TheEadie
Copy link
Copy Markdown
Contributor Author

TheEadie commented Feb 4, 2026

I'm not sure the traffic risk is worth the overhead of the code to be honest. In the worst case each job runs on an ephemeral agent and its a cache miss everytime.

@TheEadie TheEadie merged commit a0bcf3e into main Feb 4, 2026
40 checks passed
@TheEadie TheEadie deleted the fix/remove-metadata-caching branch February 4, 2026 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants