bundles xcswift-frontent to the .zip (incl. the swift-frontend -> xcswift-frontend and swiftc -> xcswiftc symbolic links). Symlinks are added because Xcode's driver integration requires that the SWIFT_EXEC has swiftc filename, placed next to the swift-frontent
Duplicate all E2E tests in 2 modes: with and without enable_swift_driver_integration. That makes the E2E testing longer (~x2), but in the near future (when Xcode 14 support will be deprecated) we will be able to delete the legacy testing. Until we stabilize Swift Driver Integration, E2E tests will take more time. In a single CI, it seems the test pipeline takes 22min (vs 14m previously).
For the standalone E2E tests, build&generate artifacts for the M1/M2 machines (arm64). As M1 machines are already more popular than Intel machines, it is better to cover that architecture in tests.
Bumps the CocoaPods plugin, as there was a change in the implementation (0.0.17)
The last part of the Swift integration support
xcswift-frontentto the .zip (incl. theswift-frontend->xcswift-frontendandswiftc->xcswiftcsymbolic links). Symlinks are added because Xcode's driver integration requires that theSWIFT_EXEChasswiftcfilename, placed next to theswift-frontentenable_swift_driver_integration: truein the CocoaPods plugin (the automatic integration already support that, added https://github.com/spotify/XCRemoteCache/pull/208)enable_swift_driver_integration. That makes the E2E testing longer (~x2), but in the near future (when Xcode 14 support will be deprecated) we will be able to delete the legacy testing. Until we stabilize Swift Driver Integration, E2E tests will take more time. In a single CI, it seems the test pipeline takes 22min (vs 14m previously).arm64). As M1 machines are already more popular than Intel machines, it is better to cover that architecture in tests.Previous PRs: https://github.com/spotify/XCRemoteCache/pull/208, https://github.com/spotify/XCRemoteCache/pull/209, https://github.com/spotify/XCRemoteCache/pull/210