gitpod-io / gitpod-io/leeway

Packages build because they're deps of a script don't get uploaded to the remote cache

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

Nobody has claimed this yet.

bug
Dominant language
Go
Stars
183
Forks
27
PR merge metrics
No merged PRs in 30d

Description

Bug description

deps packages that are being built as part of leeway run don't get uploaded to the remote cachce

Steps to reproduce

Modify previewctl so that you get a new hash

printf "\n// $(date)\n" >> /workspace/gitpod/dev/preview/previewctl/main.go

Run dev/preview/previewctl:install, remove the caches, and run dev/preview/previewctl:install again.

leeway run dev/preview/previewctl:install
rm -rf /tmp/build /tmp/cache
leeway run dev/preview/previewctl:install
Expected behavior

I would have expected the 2nd invocation to download the dev/preview/previewctl:cli package from the remote cache.

It does re-use the cache if it exists. E.g. if you use leeway build, then delete the local caches, and then leeway run it does indeed use the remote cache.

rm -rf /tmp/build /tmp/cache
leeway build dev/preview/previewctl:cli
rm -rf /tmp/build /tmp/cache
leeway run dev/preview/previewctl:install
Example repository

No response

Anything else?

No response

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.

Research direction

Start by reproducing the issue with leeway run dev/preview/previewctl:install after editing dev/preview/previewctl/main.go and removing /tmp/build and /tmp/cache. Compare this with the leeway build dev/preview/previewctl:cli sequence; done means the second leeway run downloads the cli package from the remote cache.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.