fix: remedy Swift Package Index build failures & timeouts #731
Conversation
.spi.yml
Outdated
| @@ -0,0 +1,22 @@ | |||
| version: 1 | |||
| external_links: | |||
| documentation: 'https://aws.amazon.com/sdk-for-swift' | |||
There was a problem hiding this comment.
Given our current documentation is so out of date, should we remove this for now. We can add it back in after we update our docs.
There was a problem hiding this comment.
Link removed. Our page currently has no docs linked (since we don't specify a link and SPI is not building docs for us.). I guess people can get to docs by going to our Github & starting at the README.
| builder: | ||
| configs: | ||
| - platform: macosXcodebuild | ||
| target: AWSSTS |
There was a problem hiding this comment.
Thoughts on AWSS3 or AWSEC2 instead of STS? Just thinking of something a bit more popular
There was a problem hiding this comment.
Those were the two I was trying to avoid because they're so big, lol. They take a very long time to compile, especially the Models.swift in each of those.
I don't think it shows anywhere except in the config file and in the build logs which specific target we build, so it makes no difference to someone looking at our listing.
2 participants
Issue #
Fixes #708
Description of changes
Our builds on Swift Package Index (SPI) either fail or timeout, resulting in the appearance that our package isn't compatible with any platform or Swift version. I discussed how to fix with the SPI maintainers here.
This PR adds a
.spi.ymlconfig file for SPI that does the following:AWSSTStarget for all platforms, which is a small, representative service client that should build quickly and provide adequate proof of compatibility.openssl-devpre-installed.I have validated this config file per the instructions here.
New/existing dependencies impact assessment, if applicable
No new dependencies were added to this change.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.