Details
-
Bug
-
Resolution: Done
-
P2: Important
-
None
-
None
-
30bafc748e32f6ccaa3aec137fda343349fc6603
Description
First integration: http://10.212.3.36:8080/coin/integration/qt/qt5/tasks/1582110795
Build artifacts have been created including changes Provisioning: Update jinja2 to 2.10.3, Fix openssl build in SLES-15, Install QEMU from .deb package from internal cache. Because webengine test was failed it wasn't merged in.
Second integration: http://10.212.3.36:8080/coin/integration/qt/qt5/tasks/1582175615
Integration with changes Fix openssl build in SLES-15, Install QEMU from .deb package from internal cache got merged.
Third integration: http://10.212.3.36:8080/coin/integration/qt/qt5/tasks/1582183815
Integration started with change Provisioning: Update jinja2 to 2.10.3 (see picrute below)
Coin is running provisioning, but won't rebuild artifacts because those already exists for that sha. This is risky because tier2 images aren't complete reproducible (libraries version might change) and if provisioning error handling isn't bullet proof then errors won't be catch during build or in test phase.