-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xcode 15 Beta 8 + Xcode Cloud Error #5205
Comments
We are seeing the same issue with Xcode 15 RC (15A240d) and macOS Sonoma 14 RC (23A339) on Xcode Cloud. |
Facing the same issue. Doesn't matter if we use different macOS versions so must be something in Xcode 15. |
I'm also facing the same issue. I have Swiftlint installed via SPM.
|
Same issue here |
Same issue here |
Ran into this as well. The only way I could get it to work was to hack swiftlint so isLikelyXcodeCloudEnvironment always returned true (and jump through the hoops to host my own binary of it). I couldn't figure out how to get logs out of it when running on Xcode Cloud so I'm not sure why that function isn't returning true when it should. As far as I can tell all the right things are in the environment. Edited to add: I thought I had tried this before but I guess it failed for a different reason. But changing SwiftLintPlugin to pass "--no-cache" as an argument also is sufficient to fix the problem, further evidence, I think, that isLikelyXcodeCloudEnvironment is no longer able to correctly detect Xcode Cloud builds. |
@honus This made me think about and look at the docs for Xcode Cloud environment variables, at which point I noticed this entry that I don't think I've seen before:
Still haven't looked at why |
Could be. I haven't figured out how to get logs out of swiftlint running in Xcode Cloud so it is hard to diagnose. |
Having this problem as well, and I'm guessing the reason that isLikelyXcodeCloudEnvironment is no longer working has something to do with the It doesn't quite make sense why |
Same issue here, is there any easy workaround for this? |
I've switched to using the binary by committing it into the project repository and running it as part of a build phase script. It works fine as long as |
…e Cloud In Xcode Cloud environment, SwiftLint’s cache cannot be written. When using the SwiftLinkPlugin, there is no way to disable the cache. Previously, a solution was made for the SwiftLint CLI itself where it looks at a set of environment variables (realm#4485). This solution offers a cleaner approach where the plugin itself decides whether it needs to enable or disable the cache based on the `CI_XCODE_CLOUD` environment variable.
I have same issue on Xcode Cloud.
|
Any news about this issue? |
Watching this issue to re-enable SwiftLint realm/SwiftLint#5205
Fixed by #5287. |
This issue does not appear to have been fully resolved by #5287. I'm encountering the following error today:
BugI'm seeing SwiftLint 0.54 attempt to write to the file system despite the fact that the tool is running in Xcode Cloud. This causes an unrecoverable error preventing the rest of the build process. Setup:
Xcode Cloud EnvironmentThe Xcode Cloud environment variables during Xcode Cloud's "Set environment variables" build step are:
|
I filed the above as a new issue (#5448) because I believe the package plugin variant of using SwiftLint may have been overlooked during the earlier fixes for Xcode Cloud. |
#5287 has only been done for package plugins. |
New Issue Checklist
Describe the bug
Hello. We are utilizing the SwiftLint plugin as a build phase in our project containing:
When building with Xcode Cloud using Xcode Beta (8 in this case) a build error is encountered related to SwiftLint.
Additionally, our
ci_post_clone
script containsdefaults write com.apple.dt.Xcode IDESkipPackagePluginFingerprintValidatation -bool YES
Xcode Cloud Environment is set to:
Complete output when running SwiftLint, including the stack trace and command used
Environment
swiftlint version
to be sure)?# insert yaml contents here
If so, paste their relative paths and respective contents.
xcodebuild -version
)?echo "[string here]" | swiftlint lint --no-cache --use-stdin --enable-all-rules
to quickly test if your example is really demonstrating the issue. If your example is more
complex, you can use
swiftlint lint --path [file here] --no-cache --enable-all-rules
.The text was updated successfully, but these errors were encountered: