I created a Docker image for QA use of building and testing the pointing component.  The Dockerfile may be found at https://github.com/lsst-ts/ts_Dockerfiles currently in the pointing_qa folder on the u/rbovill/robot branch.  The pull request for this is at https://github.com/lsst-ts/ts_Dockerfiles/pull/4

The Docker image was pushed to lsstts org on DockerHub, https://cloud.docker.com/u/lsstts/repository/docker/lsstts/pointing

The Jenkins build is now configured and running.  It is successfully building the PtgControllers.

https://ts-ci.lsst.codes/job/ts_pointing_common/

Functional testing of the CSC is still needed.  Work for this is tracked by https://jira.lsstcorp.org/browse/DM-17649

Ready for review.

Reviewed over the Jenkins builds to confirm runs were being made. 

So, I was kind intrigued by the fact that this build successfully whereas it fails when I tried to build the exact same version of the software (I checked the commit hash to make sure).

Looking at the output of the build, I see an error right at the beginning of the build:

In file included from ../src/SAL_Environment.cpp:6:0:

../src/SAL_Environment.h:20:20: fatal error: Python.h: No such file or directory

 #include "Python.h"

So maybe that explains why it does not get to the point of the build where it reaches the bug in the code. 

https://github.com/lsst-ts/ts_pointing_common/blob/3991d040c546ea382b96c7f46e8ecf6404a41d7d/src/c%2B%2B/kernel/point_file.cpp#L70-L72

Also, is the idea of this task to actually run the tests provided by the vendor?  

 Did not have time to get the tests running, but was able to get the code to build in Jenkins.  The work to get the tests running is tracked by DM-17660.