Skip to content

Commit d961d1a

Browse files
committed
Add Buildkite annotation about validate_podspec bypass
1 parent f8f8214 commit d961d1a

File tree

2 files changed

+14
-7
lines changed

2 files changed

+14
-7
lines changed

.buildkite/pipeline.yml

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -29,13 +29,10 @@ steps:
2929
command: |
3030
# validate_podspec
3131
echo '+++ ⚠️ validate_podspec was bypassed ⚠️'
32-
echo 'As of Xcode 14.3, libraries with deployment target below iOS 11 (iOS 12 in Xcode 15) fail to build out of the box'
33-
echo 'The reason is a missing file, /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/arc/libarclite_iphonesimulator.a'
34-
echo 'Client apps can work around this with a post install hook that updates the dependency deployment target, but libraries do not have this option.'
35-
echo ''
36-
echo 'Our old Alamofire dependency targets iOS 8.0, making the validation build fail.'
37-
echo ''
38-
echo 'In the interest of using up to date CI (i.e. not waste time downloading old images) we bypass validation until either we are able to drop or upgraed Alamofire, or find a workaround.'
32+
# post a message in the logs
33+
cat .buildkite/validate_podspec_annotation.md
34+
# and also as an annotation
35+
cat .buildkite/validate_podspec_annotation.md | buildkite-agent annotate --style 'warning'
3936
key: "validate"
4037
env: *common_env
4138
plugins: *common_plugins
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
**`validate_podspec` was bypassed!**
2+
3+
As of Xcode 14.3, libraries with deployment target below iOS 11 (iOS 12 in Xcode 15) fail to build out of the box.
4+
The reason is a missing file, `/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/arc/libarclite_iphonesimulator.a`, more info [here](https://stackoverflow.com/questions/75574268/missing-file-libarclite-iphoneos-a-xcode-14-3).
5+
6+
Client apps can work around this with a post install hook that updates the dependency deployment target, but libraries do not have this option.
7+
8+
Our old Alamofire dependency targets iOS 8.0, making the validation build fail.
9+
10+
In the interest of using up to date CI (i.e. not waste time downloading old images) we bypass validation until either we are able to drop or upgraed Alamofire, or find a workaround.

0 commit comments

Comments
 (0)