bazelbuild / bazelbuild/rules_apple
Include all values referenced by `resources` attribute in Bazel cache key
- Dominant language
- Starlark
- Stars
- 593
- Forks
- 334
- Avg merge
- 16h 48m
- Merged PRs (30d)
- 9
Description
[Related Slack thread](https://bazelbuild.slack.com/archives/CD3QY5C2X/p1688239583333879)
I renamed some directories referenced by a `glob`, which populates an iOS application’s `resources`. I failed to update the corresponding `Content.json` file. My local build did not fail. My CI build did fail. Based upon [a conversation on Slack](https://bazelbuild.slack.com/archives/CD3QY5C2X/p1688239583333879), it sounds like the `resources` are not always included when creating the Bazel cache key.
Contributor guide
Research direction
No file, test, or entry point is named. Start by reproducing the difference between the local and CI builds, then trace how the Bazel cache key is assembled for an iOS application’s resources; done means renaming a glob-referenced resource or changing its Content.json reliably changes the relevant cache key.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100