I have triggered a forced build. The last three scheduled builds detected no new package changes, and aborted the build without producing anything. This is a bit of a problem if the prior container build build produced new docker images that need to be included in helm charts. I'm looking at options to address this going forward. Scott On 2020-07-31 8:39 a.m., Jascanu, Nicolae wrote:
Hi All,
The sanity and metrics tests were NOT executed today because there is no proper image available:
http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/202007...
http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/202007...
http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/202007...
Regards,
Nicolae Jascanu, Ph.D.
*TSD Software Engineer*
intel-logo
*Internet Of Things Group*
*Galati, Romania*
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
