realm / realm/SwiftLint

SwiftLint 0.52.2 Cache Access Permission Causes Builds To Fail

Open
#5,045 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

integration
Dominant language
Swift
Stars
19.7k
Forks
2.3k
Avg merge
1d 1h
Merged PRs (30d)
11

Description

New Issue Checklist
Describe the bug

After updating to SwiftLint 0.52.2 from 0.48.0, all builds (local + Jenkins) started failing.

When building locally seeing the following errors:

Error while creating cache: You don’t have permission to save the file “9030F0EF-F3AB-3361-A5B2-BC9D54BAEAA1” in the folder “0.52.2”.

Error: The folder “71affc6a6424d4096940b766378714e44ba2e54e7d55796ff09b8e40b8fe9d6d.plist” doesn’t exist.

No other changes were made.

The projects is running on company machines were users (including on Jenkins) do not have admin access.

We are using SwiftLint via a SPM Package and an SPM Build Plug-in.

Passing - --cache-path - does not help or seem to change where the cache is being written to.

Passing - --no-cache - resolved the issue, but disabled SwiftLint cache logic.

Environment
  • SwiftLint version (run swiftlint version to be sure)?

  • 0.52.2

  • Installation method used (Homebrew, CocoaPods, building from source, etc)?

  • SPM package via SwiftLintBinary-macos.artifactbundle

  • Which Xcode version are you using (check xcodebuild -version)?

  • Xcode 14.3/14.2

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 SwiftLint 0.52.2 SPM package and build-plugin setup on a machine without admin access, with caching enabled, and compare it with --no-cache and --cache-path. Done means local and Jenkins builds succeed without disabling the cache or requiring elevated permissions.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.