Overview
QuantSA has some level of continuous integration. This currently run in two different places:
- https://travis-ci.org/JamesLTaylor/QuantSA
- https://jameslatimertaylor.visualstudio.com/QuantSA/_build
Both of which need private log on details and can’t be changed by other developers. Please contact me if you would like to be involved in the building process.
Travis
- Build the markdown docs using Jekyll
- Checks that there are no dead links
- Upload all output to <www.quantsa.org/latest>.
This was easier to set up on Travis than installing Ruby into Visual Studio Team Servives.
Visual Studio
Core library:
- Build QuantSACore.sln
- Run tests
Excel parts:
* Build QuantSACommon.sln
* Build GenerateXLCode.sln
* Build QuantSAExcelAddin.sln (includes excel code generation via GenerateXLCode.exe)
* Zip the dlls (only required because the visual studio AfterBuild task does not appear to run properly, see issue #34 )
* Build QuantSAInstaller.sln
* Zip the whole addin directory
* Upload to Azure the addin directory as QuantSA_build_latest.zip and QuantSA_build_[BuildID].zip.
* Upload to Azure the QuantSA Installer as QuantSAInstaller_Latest.exe and QuantSAInstaller_[BuildID].zip
Deploy
The deploy steps are manual, for a version X.Y.Z:
- Copy http://www.QuantSA.org/latest to http://www.QuantSA.org/[vX.Y.Z] and http://www.QuantSA.org
- Make a github release
- Copy latest zip and installer to github release, rename to include version.
- Add link to help menu in github release.
- Add help links to an index page on QuantSA.org.
Further work
- None of the excel functionality is currently tested. This needs to be added somewhere rather than relying on developer’s good behaviour.
- It would be nice to change the QuantSACore solution projects to be able to run on mono and hence on the travis build. This could be useful in the futire for distributing calculations.
- Should add python testing to one of the builds.