Currently, we are working on getting the policy setup to be able add new
systems to second Jenkins master and looking into extending @swift-ci
capablelty to support additional platforms. Plan is to have this completed
soon, we are working out few things before we make this available publicly.
> On Sep 19, 2016, at 5:04 AM, Brian Gesiak via swift-dev <firstname.lastname@example.org>
> Oops, forgot to actually CC people. My bad!
> On Mon, Sep 19, 2016 at 8:02 AM, Brian Gesiak <modoca...@gmail.com
> <mailto:modoca...@gmail.com>> wrote:
> Hello all,
> (+cc Ted Kremenek, John Holdsworth, Philippe Hausler)
> Following up on
> I'd like to discuss expanding the range of platforms that are tested by
> Currently, @swift-ci is capable of "test macOS platform" and "test Linux
> platform", among others. It would be awesome if we could ask it to "test
> Android platform", "test Linux ARM platform", and so on.
> Ted Kremenek states that the idea is to add another Jenkins master that
> could be used to add additional machines for different platforms, to enable
> more CI testing on additional platforms the community cares about, including
> I was wondering if there's anything I could do to help here. I have desktops
> capable of building Swift for Android, Android devices to run the tests on,
> and developer time to help get this set up. Would those resources help?
> If the "another Jenkins master" is something that'll happen far off into the
> future, I was considering creating a @swift-android-ci GitHub user that
> would, like the @swift-ci bot, respond to "@swift-android-ci please test".
> Since Android isn't tested on Swift CI, I've been fixing build breakages
> after they land in master, sometimes a few days after they're merged.
> Additional CI would greatly improve the stability of the Android build -- I'm
> looking forward to next steps here! :)
> - Brian Gesiak
> swift-dev mailing list
swift-dev mailing list