In our docker tools experiments we saw how clearly tied were github and dockerhub. The latter orchestrates the building of a docker image and the updating of the repository. The former is a repository for the “source”” code of the image build process, issuing an event to dockerhub when a change was performed (that implies the need for a new build). Between the two, an OAUTH connect enables dockerhub to use the githubAPI, when pulling code and updating activities. We blogged at http://wp.me/p1fcz8-5TC .
Now lets take this a step further and ask how well such as github are supporting code builds (vs assembly builds).
For no particular reason, we install unity – a source code and project maintenance system that has little or nothing to do with our normal work. But, it does have its own cloud build service and integration with visual studio. So how do all the cloud, and source repo, and IDE tools all cooperate?
not having created a real project, our build fails: