Skip to content

Add CHAINED_STEP_START and CHAINED_STEP_END events (was "Avoid a build being marked as failed if deploy is chained with --request-deploy and it fails")

Alberto Silva requested to merge chained_step_events into 1.1.x

This PR adds two new special events that appear repeated across several modules:

  1. CHAINED_STEP_START
  2. CHAINED_STEP_END

You can find them in static_export, static_build and static_deploy.

Those three modules work in a chained mode, where each one is executed in an order to provide the main functionality of Static Suite. Each one represents a step in that chain of processes. Inside every step there is a set of events, specific to that step, and they are usually grouped inside a try/catch to be able to handle any situation that could arise when exporting, building or deploying.

On the contrary, CHAINED_STEP_START and CHAINED_STEP_END are triggered outside that try/catch, and they express that one of those chaining steps is finished so the next one could start. They are intentionally outside that try/catch so they can handle they exceptions in isolation; otherwise, a failed deploy triggered by a build would erroneously appear as a build error.

Merge request reports