Modified Jenkinsfile into one-liner format.

[timurh01]

Description

@OPpuolitaival
Jenkinsfile refactoring into one-liner format in order to use improved internal Jenkins scripting.

Pull request type

[ ] Fix
[ x ] Refactor
[ ] Target update
[ ] Feature
[ ] Breaking change

[OPpuolitaival]

Looks good

[cmonr]

@ARMmbed/mbed-os-test I've been wondering. What does this file do, and where is it used?

What does mbed.run_job() call, and is it in the Mbed OS repo, or somewhere else?

[timurh01]

Mbed-OS Jenkins CI runs command from Jenkinsfile, and that triggers Jenkins test jobs to run. Jenkins is used to run tests that cannot be shared publicly. Script framework, that is called by this mbed.run_job(), is located in repo mbed-os-ci/vars (private repo). And this frame is already built that way, that old format Jenkinsfile is actually calling mbed.run_job() command.
More info from @OPpuolitaival

[0xc0170]

While we are doing this update, as @cmonr asked about it. Can we add a description to this file what it does, why it is here.

// This is internal file for internal jenkins (something similar)

[OPpuolitaival]

@0xc0170 good point

[timurh01]

Comment inside Jenkinsfile updated.

[cmonr]

/morph build

[OPpuolitaival]

@cmonr morph build need to retriggering. There was jenkins internal failure

[mbed-ci]

Build : SUCCESS

Build number : 2851
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7772/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build
/morph mbed2-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 2482
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/7772/

[mbed-ci]

Test : SUCCESS

Build number : 2610
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/7772/2610