PoC: for integrating check-platform.py

Authored by apol on Dec 21 2017, 3:50 PM.



Includes it in SuseQt5.9 builds and adds TODOs of the things I don't know
how to do.

Resolves T7572.

Test Plan

No idea how to test it ¯\_(ツ)_/¯

Diff Detail

R857 CI System Tooling
Automatic diff as part of commit; lint not applicable.
Automatic diff as part of commit; unit tests not applicable.
apol requested review of this revision.Dec 21 2017, 3:50 PM
apol created this revision.
apol edited the summary of this revision. (Show Details)Dec 21 2017, 3:50 PM
apol added a task: Restricted Maniphest Task.
This revision was automatically updated to reflect the committed changes.
bcooksley reopened this revision.Dec 22 2017, 4:37 AM
bcooksley added inline comments.Dec 22 2017, 4:45 AM
129 ↗(On Diff #24260)

The current working directory for a given 'sh' command here is the source directory.
In terms of where ci-tooling lives, that's checked out into a subdirectory of the workspace.

In terms of making a build unstable (yellow) - given we manipulate the build status from the Groovy code already (see the top line of this) that is probably the easier way to do this.

See https://jenkins.io/doc/pipeline/steps/workflow-basic-steps/#code-readfile-code-read-file-from-workspace for how we'd check the file contents.

Note that due to how Pipelines work, regular Groovy code for interacting with files should not be used as Pipeline code itself may be executed on the master rather than on the build node.

Any updates on this Aleix?

This revision was not accepted when it landed; it landed in state Needs Review.Dec 29 2017, 6:41 PM
This revision was automatically updated to reflect the committed changes.