[Starlingx-discuss] [build-report] STX_build_docker_images - Build # 29 - Still Failing!

[Scott Little]

OK, those build steps need to be serialized.  Another script fix, 
restaring job with same parameters.   Sorry for the noise folks.

The fun part is that one error generate three build failure e-mails due 
to the nested jobs.

Scott


On 2019-01-22 2:37 p.m., build.starlingx at gmail.com wrote:
> Project: STX_build_docker_images
> Build #: 29
> Status: Still Failing
> Timestamp: 20190122T191315Z
>
> Check logs at:
> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190122T145945Z/logs
> --------------------------------------------------------------------------------
> Parameters
>
> BRANCH: master
> MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190122T145945Z
> OS: centos
> MUNGED_BRANCH: master
> MY_REPO: /localdisk/designer/jenkins/master/cgcs-root
> PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190122T145945Z/logs
> PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190122T145945Z/logs
> MY_REPO_ROOT: /localdisk/designer/jenkins/master
> PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos
> DOCKER_BUILD_ID: jenkins-master-20190122T145945Z-builder
> OPENSTACK_RELEASE: pike
> TIMESTAMP: 20190122T145945Z
> OS_VERSION: 7.5.1804
> PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/20190122T145945Z/inputs
> PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20190122T145945Z/outputs
>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190122/ff471127/attachment.html>