### Motivation:
This will allow us to decommission the old CI hooks.
### Modifications:
* Migrate the existing tests to use the package-benchmark framework.
* Delete the obsolete integration tests
* Remove allocations test references from the docker files.
### Result:
Allocation counts are checked using GitHub Actions.
Migrate CI to use GitHub Actions.
### Motivation:
To migrate to GitHub actions and centralised infrastructure.
### Modifications:
Changes of note:
* Disable warnings-as-errors until issues with recent NIO changes are
resolved
* Adopt swift-format using rules from SwiftNIO
* Remove scripts which are no longer needed
### Result:
Feature parity with old CI minus allocation tests which remain on the
old CI.
Motivation:
Now that Swift 5.9 is GM we should update the supported versions and
remove 5.6
Modifications:
* Update `Package.swift`
* Remove `#if swift(>=5.7)` guards
* Delete the 5.6 docker compose file and make a 5.10 one
* Update docs
Result:
Remove support for Swift 5.6, add 5.10
* Drop Swift 5.5
This patch drops Swift 5.5 support. It removes docker-compose files and
deletes any conditional compilation guards that are no longer necessary.
* Remove test generation script
Motivation:
Docs are generated by and hosted on the Swift Package Index. We no
longer need the script to generate docs via Jazzy.
Modifications:
- Remove the generate_docs script
- Remove Jazzy from the Dockerfile but keep Ruby; it's used for
generating test manifests.
- Remove SwiftFormat from the Dockerfile; we don't use it.
Result:
Fewer unused things.
Motivation:
SwiftNIO periodically drops support for older Swift versions. Now that
5.7 has been released, 5.4 will be dropped.
Modifications:
- Remove 5.4 specific Package.swift and docker-compose
- Update the 5.7 docker-compose to use the released 5.7 and move from
focal (2004) to jammy (2204)
- Fix the tools version in Package@swift-5.5.swift
- Update docs
Results:
Minimum Swift version is 5.5
Motivation
Documentation is nice, and we can help support users by providing useful
clear docs.
Modifications
Add Docc to 5.6 and later builds
Make sure symbol references work
Add overview docs
Result
Nice rendering docs
As outlined in a [Swift forums post in November ’21](https://forums.swift.org/t/swiftnio-swift-version-support/53232), SwiftNIO will only support the latest non-patch Swift release and the 2 immediately prior non-patch versions.
- drop support for Swift 5.2 and 5.3
- update CI for Swift 5.4 to run on bionic instead of focal to ensure that we still test bionic
From: https://github.com/apple/swift-nio-extras/pull/141
Motivation:
The combination of Ruby and Jazzy are throwing up issues in CI on older
Ubuntu versions.
Modifications:
- Only install Jazzy on focal
- Fix doc generation script to use more recent source-kitten syntax
Results:
- CI doesn't complain
- Docs get built
Changes made:
Removed CI config for 5.0 ad 5.1
Changed 5.2 to be based on 16.04 so we have some coverage there
Converted Package.swift to the latest syntax
Added a description to supported Swift versions in the README
Motivation:
Ruby on Xenial is too old for the cocoapods downloader which jazzy uses.
Modifications:
Change Dockerfile to not install Jazzy on xenial.
Result:
Dockerfile will build again, but bionic or later is required for docs.
motivation: more secured ci setup
changes:
* enable :z selinux flag on bind mounts so we can enable selinux on ci
* drop potentially exploitable capabilities from docker-compose
Motivation:
We missed these out, which means we failed to detect the massive
allocation win in #159.
Modifications:
Correctly add allocation limits.
Result:
We'll know if we regress.
motivation: run performance tests 🎉
changes: add performance-test task in docker-compose setup, add script to analyze performance results to be used in CI
Motivation:
We want the CI to make sure we don't accidentally regress the executable
stack property of the binary.
Modifications:
Run execstack against our build output in the integration tests.
Result:
We shouldn't regress the executable stacks.
motivation: test for api breakage on PR
changes:
* add script to detect api breakage
* amend docker setup to include jq
* amend docker-compose setup to include a shell utility task
* swift 5.1 docker setup
motivation: support swift 5.1
changes:
* use formal swift docker images
* refactor docker-compose to seperate unit tests, integration tests and full test suites
* add docker compose file for swift 5.1, will add CI job once merged
* update swiftformat version to 0.40.12
Motivation:
We have a static library target that is used as part of the BoringSSL
vendoring setup to generate a list of hidden symbols. This works nicely,
but building it fires out a bunch of warnings due to files with no symbols
in them. That's fine during the build phase, but most developers should
never need to see it.
Modifications:
- Hide the static archive product most of the time.
- Update vendor script to un-hide the static archive product on vendoring.
- Enable warnings-as-errors.
Result:
Fewer warnings.
Motivation:
The older Swift 5 we're using in CI breaks on our Package.swift. This
rather limits the utility of our CI.
Modifications:
Use a newer Swift 5 snapshot.
Result:
CI will actually work.
motivation: easier testing on different architectures and swift versions
changes:
* update dockerfile to match more closely what we do in swift-nio, including support for extenral versions of ubuntu and swift
* add docker-compose files representing different permutations of ubuntu and swift versions
Motivation:
set up continuous integration
Modifications:
add docker file to include all dependencies required for build and tests
Result:
able to set up docker based continuous integration