Implementing a pipeline script command as an equivalent to the post build step "HPE Octane Cucumber test reporter" would enable us to use only a pipeline script without the need to trigger a separate build job to play our cucumber test reports and implemented tests back to octane.

Currently we publish junit results as an workaround. That ensures that we have the test runs from jenkins visible in octane, but with that we don't get the E2E reference. Octane (Gherkin Test) -> GIT (Gherkin test implementation & extension) -> Jenkins (Build & Test) -> Octane (Results & Reference to initial Gherkin test and updated test specification based on GIT)