Includes it in SuseQt5.9 builds and adds TODOs of the things I don't know
how to do.
Resolves T7572.
bcooksley |
Sysadmin |
Includes it in SuseQt5.9 builds and adds TODOs of the things I don't know
how to do.
Resolves T7572.
No idea how to test it ¯\_(ツ)_/¯
Automatic diff as part of commit; lint not applicable. |
Automatic diff as part of commit; unit tests not applicable. |
pipeline-templates/SUSEQt5.9.template | ||
---|---|---|
129 ↗ | (On Diff #24260) | The current working directory for a given 'sh' command here is the source directory. 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. |