Back in March there was an email thread "COE builds using docker system" about this which never went anywhere AFAIK...
https://git.opendaylight.org/gerrit/#/c/68911/ (not saying we'll use that, just for reference)
In last week's TSC, zxiiro said that whenever we (CoE folks) were ready and really wanted this, to open a helpdesk ticket and he/someone would assist from the infra side.
dfarrell07 in today's #opendaylight-integration IRC weekly meeting expressed interested in helping with this and/or COE-33 ? He pointed to INTPAK-12.
It's not something for tomorrow morning as I haven't even got to being able to build that image locally, and I first need to progress on where I actually use that image - but I'll get back.
Note that the goal of this issue is to build and push a container image of some Go code, not an ODL distribution (and same for another container in COE-32; but not COE-33 which is an ODL image).
OK, changed comment to right ticket 
I'll see how hard it is to get the POC container with odlovs-cni from COE-22 (which BTW I'm not really even sure works yet) deployed on Quay.io ... I wonder if Go is available there, or if we need to do something like https://git.opendaylight.org/gerrit/#/c/78105/6/odlCNIPlugin/odlovs-cni/Dockerfile ...
watch (WIP) https://quay.io/repository/vorburger/test-opendaylight-coe-cni/ (FYI https://quay.io/organization/opendaylight reserved for future use...)
> I wonder if Go is available there, or if we need to do something like https://git.opendaylight.org/gerrit/#/c/78105/6/odlCNIPlugin/odlovs-cni/Dockerfile ...
yeah, it builds (only) off a Dockerfile and can't launch a "native" (non-containerized) Go build from a Makefile or build.sh ...
With my first 3-4 related changes required for this just merged, I've now set up a build trigger on https://quay.io/repository/opendaylight/opendaylight-coe-cni/ :
- Please enter the HTTP or SSH style URL used to clone your git repository : https://git.opendaylight.org/gerrit/coe.git
- Please select the location of the Dockerfile to build when this trigger is invoked : /odlCNIPlugin/odlovs-cni/Dockerfile
- Please select the context for the Docker build : /odlCNIPlugin/odlovs-cni
which then gave me this information:
Please note: If the trigger continuously fails to build, it will be automatically disabled. It can be re-enabled from the build trigger list. In order to use this trigger, the following first requires action:
1. You must give the following public key read access to the git repository:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC0gURKttJAy2B1Ohm56hLfGk9dQLcdYzjpq1xcNNot41aJF2m2NBw8Prn//TGCBGOsjLFO/T5pQFkd8Q85dhRKq8ZRHGPVxEEVvvZUv0mjG9LyLIZeY4CWTBoH38V+pJDoyDRtQKzlIBS4TeYkUdyB54k4LFLDCm0s7WEOFoY4rLigMqVcsWRSnEhBP5hi1I3u0LUbvLCv06TCi8p2ufxrWqY6m+w3sOa4MZgG5GmtMVjTAdmjCrGv3lMMO9RxTdxO1IyUTgqhP7+3kYLpMD/1ePwmOm/R9gjNH9A+Zx8sTNlIoELOoKVq2Xo3ycGv78bfzNEzoJHFh/2cVHDQ96mX
2. You must set your repository to POST to the following URL to trigger a build: (For more information, refer to the Custom Git Triggers documentation.)
https://$token:D...R@quay.io/webhooks/push/trigger/9...e
The ... are perhaps best not posted here, I'll send them by private email to anyone who asks for it, for COE-56.
I've deleted https://quay.io/repository/vorburger/test-opendaylight-coe-cni again to avoid future confusion.
Considering this done, but follow-up required in COE-56 (by others than me).
Because zxiiro in COE-56