Skip to content

Moving To A New Version Of The Swift Binaries

Jump to bottom Edit New page
Daniel Firsht edited this page Jun 9, 2016 · 17 revisions

This page document the steps the Kitura development team should follow when moving to a new version of the Swift binaries:

  1. Install the latest binaries (Swift) on OS X and (Swift + libdispatch) on Ubuntu v15.10 on your test systems.

  2. Test the develop branch to determine if it builds on both operating systems using the latest binaries. This includes compilation of the Kitura modules and also the test modules. If Kitura and test modules build and execute just fine, then we can proceed to update the Docker image used for CI builds (i.e. notify a developer that can update the Docker image and test the Travis CI builds).

  3. If the Kitura modules and/or the test modules in the develop branch do not compile with the latest Swift binaries, then let's create a separate branch from develop to test further and make any necessary changes to have a successful. Please note that the main purpose for having a separate branch is to avoid breaking the develop branch and current Travis CI build while we figure things out. Note that having a separate branch will not address the tagging requirements imposed by SPM. If you find yourself having to make changes across multiple Kitura Swift Packages to build the modules and test classes with the latest Swift binaries, then the following approach is recommended:

  • Navigate to the Packages folder and make any necessary changes in the corresponding Swift Package folders.
  • You can then push those changes to a separate branch.
  • Your changes are now saved and can be pulled down to different VMs or systems.

  1. Update the binary version in Kitura-Build in build_kitura_package.sh on the develop branch.

  2. Once we can compile and execute the Kitura modules and test modules using the Swift binaries, then we can proceed to update the Docker image used for Travis CI builds (i.e. notify a developer that can update the Docker image and test the Travis CI builds).

  3. In addition, update the vagrantfile in Kitura.

  4. Update the statement regarding version in README.md.

Add a custom footer
Add a custom sidebar
Clone this wiki locally