We'll need Blubber installed on contint1001 so that we can build us some container images. To package or not to package...
|Resolved||None||T170453 FY2017/18 Program 6: Streamlined Service delivery|
|Invalid||None||T170480 FY2017/18 Program 6 - Outcome 2: Developers are able to develop and test their applications through a unified pipeline towards production deployment.|
|Invalid||None||T170481 FY2017/18 Program 6 - Outcome 2 - Objective 2: Set up a continuous integration and deployment pipeline|
|Resolved||None||T157469 Mathoid CI Container Build|
|Resolved||dduvall||T175297 Define new Jenkins pipeline for container build phase|
|Resolved||dduvall||T175296 Install Blubber on contint1001|
|Resolved||dduvall||T175609 Package Blubber|
We do have the new thirdparty/ci component in the repository, but I suppose blubber isn't a thirdparty tool. Also, it doesn't have any conflicts in main and is relatively small (surprisingly so for a statically built golang binary) and standalone.
I guess I have no strong opinions on where this goes, feedback from opsen needed :)
It should be built on boron (or copper) and added to the main component IMO.
I reviewed the packaging and it seems ok, although I think we might want to add a default config file to it at a later stage, and so on.
I'll work on this.
blubber is on contint1001 and contint2001 (installed via role::ci:slave so that is on all production slaves). We might consider adding contint2001 as a Jenkins slave and have the blubber based jobs to roam on them (via the Jenkins label productionSlaves).