COMPILING SEMAPHOR C FULL
COMPILING SEMAPHOR C SOFTWARE
COMPILING SEMAPHOR C SERIES

This service is worth a look for other teams that have relatively lengthy test build processes.

COMPILING SEMAPHOR C SOFTWARE

Conclusionīased upon these findings and those from similar analyses in our Python software repositories, we are transitioning to Semaphore CI for most of our continuous integration testing across our Go, Python, and UFO typeface source projects. The documentation for the built-in Semaphore CI dependency caching that he referred to can be found here. “We also recommend using the built-in caching mechanism to avoid re-building external dependencies that don’t change between builds.” Marko also had the following recommendation for additional potential gains in projects like ours: As a result the hardware capacity that comes in one CI worker (we call it a Box) is 2x comparing to other services.” “At Semaphore we take performance very seriously and our CI/CD platform is based on dedicated hardware with desktop-class performance. I reached out to the co-founder of Semaphore CI, Marko Anastasov, to see if he could explain these differences and here is what he had to say: Nearly two minutes were shaved off of our builds on average with the default Semaphore test settings! That’s pretty impressive by any standard. The mean build times were 208.6 seconds (+/- 16.7s) on Semaphore and 319.4 seconds (+/- 33.6s ) on Travis. There was a statistically significant (p<0.05) decrease in build time across these five recent commits that amounted to a mean 110.8 seconds saved on the Semaphore CI service. Mean (+/- SD) for build times across five commits to the Hack typeface repository for Semaphore (blue) and Travis (red). The git commits are labeled with git commit SHA1 short hash strings on the y-axis. The following figure demonstrates the raw build time in seconds by git commit to the Hack typeface repository. The builds were run on both testing services simultaneously via GitHub git commit hooks. These data exclude queue time and represent the software build testing execution time only. Here are the data on the build execution times required for five recent sequential commits in our repository. The Python versions were 2.7.13 on Travis and 3.6.x on Semaphore. The gcc versions were 4.8.4 on Travis and 4.9 on Semaphore. The git versions were 2.13.0 on Travis and 2.14.2 on Semaphore. The Travis and Semaphore tests were both performed on Ubuntu 14.04 LTS systems. The time-intensive tests for us are those shown in the list above. We perform parallel shell script linting tests that are not considered in this analysis as they are brief relative to our compile tests and do not impact the total time to test completion. This build process has historically required approximately 4–5 minutes on the Travis platform. Post-compile modification writes to the font binaries with other OpenType table fixes including DSIG table mocking, fstype permission modification.Post-compile modification writes to the font binaries with instruction sets (i.e., hints).Compile of four character subset font variants in web font (*.woff, *.woff2) formats from UFO version 2 typeface source files.

COMPILING SEMAPHOR C FULL

Compile of four full character set font variants (regular, italic, bold, and bold italic) in desktop (*.ttf) and web font ( *.woff, *.woff2) formats from UFO version 2 typeface source files.Compile of the FreeType & Harfbuzz libraries and the ttfautohint executable from C/C++ source with a make-based compile workflow.Installation of Python typeface compile and post-compile font modification software with pip.

COMPILING SEMAPHOR C SERIES

The build process involves the following series of steps: The following analysis compares the two testing services with the same git commits that were pushed to the Hack typeface repository and built simultaneously on both CI testing platforms via GitHub git commit hooks.

Intriguing! As a long time user of Travis CI, I decided to put the test services to the test and find out if these benefits apply to our software testing needs.

Compiling semaphor c