Generates the latest/greatest Maven-based artifacts for the Openfire project, every night.

Build: #1548 was successful Scheduled with changes by 3 people

Stages & jobs

  1. Build and Package

  2. Deploy

  3. copy nightlies to website

Build result summary


Queue duration
2 minutes
9 minutes
Total tests
First to pass since
#1547 (Scheduled with changes by 5 people)


Code commits

Author Commit Message Commit date
Guus der Kinderen Guus der Kinderen b2d34016cf99be3a37a2d292d195e5708277257d Add warm-up connection to connectivity tests
For reasons beyond me, one connection (out of many) for the BOSH connectivity test seems to fail - but only on the infrastructure for Github Actions.

From the output, it appears to be the _first_ connection that fails. I suspect that this is triggered by a weird scheduling/timing/eventing thingy that is specific to that environment.

This commit adds an additional connection attempt, for which the outcome will be ignored. Hopefully by 'warming up' the system under test, we get more stable results.
daryl herzmann <> daryl herzmann <> 5e6e69e552e066364098a93cb600b20fac5668de Merge pull request #1850 from guusdk/ci-docker-publish-changes
CI Docker publish changes
Guus der Kinderen Guus der Kinderen 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.
daryl herzmann <> daryl herzmann <> 49dd35d69ca195576e2d719a1eda5b81239f0a16 Merge pull request #1849 from guusdk/ci-codeql-remove-checkout
Simplyfiy CI CodeQL workflow
Guus der Kinderen Guus der Kinderen 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?


Fixed tests 1
Status Test Failing since View job Duration
Successful LoginLimitManagerTest lockoutsWillBeAudited
Failing since build #1547 (Scheduled with changes by 5 people) Run Maven < 1 sec

Jira issues

Unknown Issue TypeOF-2190Could not obtain issue details from Jira
Unknown Issue TypeOF-2266Could not obtain issue details from Jira