[Bug] Workflow fails due to hub download issues

Open
#70 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd

Research direction

Start by reviewing the linked GitHub Actions runs and the workflow step that installs hub. Compare whether caching, retry logic, or replacing hub with gh best addresses the intermittent 504 failure, then verify the workflow completes reliably without the reported installation error.

Written by the indexing model from the issue text.

Description

Current Behaviour

The workflow occasionally fails due to hub installation issues.
This does not happen very frequently -- roughly once a month -- and is considered low priority.
e.g.

'USE_EXTERNAL_7ZIP' has been set to 'True'
Installing 'hub' (2.14.2) [64bit] from 'main' bucket
The remote server returned an error: (504) Gateway Time-out.
URL https://github.com/github/hub/releases/download/v2.14.2/hub-windows-amd64-2.14.2.zip is not valid

WARN 'hub' not found, not a scoop shim, or a broken shim.
Please install hub 'scoop install hub'
INFO: Scheduled finished

Possible Solution
  • Add caching and/or retry logic to improve reliability.
  • Use the built-in gh tool in GitHub Actions instead of hub.
Dominant language
PowerShell
Stars
32
Forks
30
Avg merge
6h 43m
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ScoopInstaller/GithubActions

All issues in ScoopInstaller/GithubActions

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.