Summary

put description setter into ftc (remove from Jenkins)

Owner

Tim

Reporter

Tim

Status

open

Priority

medium

Description [edit section]

Our current method of setting the Jenkins description is too complicated, and not flexible enough. Jenkins description-setter plugin is limited, and the strings for the descriptions for pass and fail have to be set at job creation time. It would be preferable to have ftc or fuego_test or the parser set the Jenkins job description (which in Fuego we use to show links to relevant results artifacts), and a per-run basis.

Switch from using Jenkins description-setter to Fuego-specific description-setter.

The Jenkins description-setter is supposed to automatically set the description based on a regular expression, but the feature we really need is just programmatic setting of the description, from fuego_test.sh or from the parser.

Here's an idea: Put the description in the run.json file, and create a mechanism to allow adding that to the build description at build-time (maybe as a post-test step?)

Notes [edit section]

One of the problems is that the links are Jenkins-specific, and we might want to use the artifact links with some other system. Making a generalized link format might be difficult.

backlink

Fuego Issues List