Here is the update in for the work done recently, for the CentOS Community Container Pipeline.
There was an issue where the entry point of the container was running, instead of the build / test / delivery scripts specified by the user. We solved this by overriding entry point in all the stages.
Setup a basic framework for running test suits, such as scans against containers. This currently runs a check for updates and reports the same, but the target is to get a scanner to to be fit into the framework.
Solved the problem of some repositories using specific dockerfiles (such as Dockerfile.centos7), by allowing the user to specify a custom dockerfile name as target.
Verified sclo (Software Collections) containers in preparation for adding them to the pipeline. The status of the same can be currently viewed in a document[1].
Had a knowledge sharing session, so as to get the entire team on the same page.
In the coming days, we will be focusing on:
Getting sclo containers through the pipeline.
Coming up with a contribution documentation to instruct new contributors on how to setup an environment and start contributing.
Updating the origin dockerfiles and getting CentOS Dockerfiles, through the pipeline
Getting the test suites planned and setup, especially the scanners