With the adoption of RFC-332 devtoolset-6 is to become the new baseline on both CentOS6 and CentOS7. This requires the CI build nodes to be upgraded to use devtoolset-6.
Switch to C++14
Update lsst-dev shared stacks to use devtoolset-6
Update boost to 1.66
Stack demo failure with devtoolset-6
allow multiple compiler strings and/or wildcard matching in LSST_COMPILER
update job workspace paths to allow compiler changes without cleanup
add a job to flush all workspaces
shapelet test failures
run-rebuild always attempting to push docs
Investigate building stack on CentOS7 with devtoolset-6
add gcc5 to CI matrix
If the Mac builds are done with MACOSX_DEPLOYMENT_TARGET set then you should get binaries that will work on multiple OS versions.
Yes and that is already the case but semantics of LSST_COMPILER still need to be changed as described above. I don't want to make it an optional env var as protection against misconfiguration of either the CI systems or the VMDK image, such as getting gcc from brew.
(the same logic is used for tarball production – cleaning up mixed compiler object code in the same eups distrib repo would be painful.)
Ugh, I found an unmerged branch with changes to the python setup in jenkins_wrapper.sh that was used for testing but not deployed to production. This probably resulted in the stack-os-matrix + "clean builds" always defaulting to python 3, including the centos-6.py2 configuration. Fortunately, the tarball builds shouldn't have been affected. I've merged the stray branch and started a cleanup off all the jenkins workspaces to make sure.
The validate drp run was successful and metrics have appeared in squash.