<div dir="ltr"><div><div><div>Hi All,<br><br></div><div class="" id="magicdomid31"><span class="">Update on recent work done for the CentOS Container Pipeline.</span></div><div class="" id="magicdomid33"><br></div><div class="" id="magicdomid1056"><span class="">-</span><span class=""> </span><span class="">We
noticed that some test runs would fail due to content not being
available at the right time. We tracked this down to and fixed a race
condition that caused container </span><span class="">test </span><span class="">stages to remove content while it is being used </span><span class="">in delivery stage</span><span class="">. This also fixed a problem where sometimes the notify email was not being sent out.</span></div><div class="" id="magicdomid673"><br></div><div class="" id="magicdomid671"><span class="">-</span><span class=""> </span><span class="">removing
all artifacts on the builder nodes once the built containers are pushed
out (or failed ), without this we were using up a lot of storage for
content that would otherwise never be useful. We will try and come up
with a smart process to catalog these before removing them ( either via
cron or opportunity driven )</span></div><div class="" id="magicdomid672"><br></div><div class="" id="magicdomid1088"><span class="">-</span><span class=""> Refresh the build configurations and templates for each build, so that it builds from scratch for each build.</span><span class=""> This ensures that no previously cached content or state can impact the present build, test and delivery run.</span></div><div class="" id="magicdomid828"><br></div><div class="" id="magicdomid826"><span class="">-</span><span class=""> </span><span class="">Due
to the layers involved with openshift and how we implement the build,
reporting cycle we've had issues with the emails that get sent out to
the user to notify them of a success / fail state along with some details
on what went wrong or where they can download the built images. We've
done some work in this area to both improve the content that gets sent
out and also to help ensure a better delivery rate ( we believe all the
issues causing email delivery failures are now fixed, but we will
continue to monitor )</span></div><div class="" id="magicdomid1089"><br></div><div class="" id="magicdomid1101"><span class="">Our immediate next focus is :</span></div><div class="" id="magicdomid1102"><br></div><div class="" id="magicdomid152"><span class="">-
be able to demo some of the work we've been doing to the various SIGs
in CentOS, to make sure we are doing the best possible work to solve
their problems and support them in the best possible manner.</span></div><div class="" id="magicdomid1103"><br></div><div class="" id="magicdomid1116"><span class="">- continue to work on closing off the minimal feature set allowing us to release / announce the service for the wider audiences.</span></div><div class="" id="magicdomid1118"><br></div><div class="" id="magicdomid1157"><span class="">- develop a comprehensive life-cycle plan to audit and report on existing containers built in the pipeline.</span></div><br></div>Regards<br></div>Bamacharan<br clear="all"><div><div><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Bamacharan Kundu<br>IRC Nick- bamachrn<br><br></div>
</div></div></div>