Display the workflow progress logs in Jenkins's console output
If possible, the Jenkins plugin's logging system should be harmonized with that of openf-ctl described here (section 'Optional parameters'): https://opentestfactory.gitlab.io/orchestrator/tools/running-commands/
The implementation must firstly provide for the possibility of adding to the runOTFWorkflow method of a pipeline an optional stepDepth parameter allowing the display of the nested steps logs of each steps:
node {
stage 'Stage 1 : sanity check'
echo 'OK pipelines work in the test instance'
stage 'Stage 2 : steps check'
configFileProvider([configFile(fileId: 'a9b08830-42de-44f0-87ef-45a6db7fff0c',targetLocation: 'workflow.json')]) {
def workflow_id = runOTFWorkflow(
workflowPathName:'workflow.json',
workflowTimeout: '2000S',
serverName:'defaultServer',
stepDepth: 2
)
}
}
2021-10-13T17:18:33] [job 9ea3be45-ee90-4135-b47f-e66e4f793383] Requesting execution environment providing ['windows', 'robotframework'] for job keyword-driven
[2021-10-13T17:18:33] [job 9ea3be45-ee90-4135-b47f-e66e4f793383] Running actionscheckoutv2
[2021-10-13T17:18:33] [job 9ea3be45-ee90-4135-b47f-e66e4f793383] Running ['git clone https://github.com/robotframework/RobotDemo.git']
[2021-10-13T17:18:37] [job 9ea3be45-ee90-4135-b47f-e66e4f793383] Running ['dir']
Workflow completed successfully.
Second, the implementation must allow the passing of an optional dumpOnError parameter which, in the case of an failed workflow, restarts the display of all the workflow logs with a maximum depth.
In the event of an error during the execution of the Workflow, a log must warn the user of the possibility of using the two parameters described previously and/or opentf-ctl in order to be able to understand the reason for the failure of the Workflow.