The handler is restarting nexus with no_block: true. Waiting for a healthy completed restart is done by the handler a little bit later in the handler by searching for string "Wait for Nexus to start" in the nexus log (here).
This is not ideal in upgrade scenarios where nexus has been restarted recently (the log may already contain the Started Sonatype Nexus) and Wait for Nexus port to be available can be reached before the restart has actually taken place.
Would it be ok to make the no_block configurable so that it can be disabled when there is a risk ?
The handler is restarting nexus with no_block: true. Waiting for a healthy completed restart is done by the handler a little bit later in the handler by searching for string "Wait for Nexus to start" in the nexus log (here).
This is not ideal in upgrade scenarios where nexus has been restarted recently (the log may already contain the
Started Sonatype Nexus) and Wait for Nexus port to be available can be reached before the restart has actually taken place.Would it be ok to make the no_block configurable so that it can be disabled when there is a risk ?