Verifies the integrety of the projects, as builds are executed immediately after a code change was detected. This plan provides no artifiacts (use a nightly build instead).

Build: #2150 was successful Changes by daryl herzmann <akrherz@iastate.edu>

Build result summary

Details

Completed
Duration
1 minute
Labels
None
Agent
Default Agent
Revision
5e6e69e552e066364098a93cb600b20fac5668de 5e6e69e552e066364098a93cb600b20fac5668de
Total tests
452
Successful since
#2137 ()

Tests

Code commits

Author Commit Message Commit date
daryl herzmann <akrherz@iastate.edu> daryl herzmann <akrherz@iastate.edu> 5e6e69e552e066364098a93cb600b20fac5668de 5e6e69e552e066364098a93cb600b20fac5668de Merge pull request #1850 from guusdk/ci-docker-publish-changes
CI Docker publish changes
Guus der Kinderen Guus der Kinderen 15473d28841ca330e6d57d7956da4957e9c03ed4 m 15473d28841ca330e6d57d7956da4957e9c03ed4 Identify docker hub pushes for non-released code as 'alpha'
Openfire builds that are not a release typically identify themselves as 'alpha'. The corresponding Docker images could do the same, which would reduce confusion.
Guus der Kinderen Guus der Kinderen 6e53bc6c271776ecf6cb11c590de9fd4be73b556 m 6e53bc6c271776ecf6cb11c590de9fd4be73b556 Docker publishing only after all tests succeed.
Previously, only the Smack test outcome was taken into account (as the others were not stable). Smack's output was not very stable either, which made this seemingly an arbitrary choice. The resulting flow diagram might have added more confusion than worked around actual issues?