Setting "Edit Build Information" / "Description" from within the build to store further metadata?

[Jan-Benedict Glaw]

Hi!

This is probably a bit off-topic, but is there a way to communicate
back some internal state from within a build to Jenkins?

I see that there's a "Description" that could be set, though
manually. It would be nice to be able to eg. set some JSON to this
field (or any other similar way?) to be able to return more than just
a SUCCESS / FAILED state.

For example, some test suites expectedly fail, so within the build
script, I'd `|| true` them right now. However, it would be nice to set
some data from the building script to the job, like:

{
'requested_revision': 'master',
'actual_revision': '2c317c75dd97ee98465f307b00384a46628afe85',
'SOURCE_DATE_EPOCH': '1769681199',
...
}

One way could be to just write that as an artifact, but maybe there
are better ways in doing this? (Some heavier jobs would even have
multiple revisions, like doing full builds with glibc's
scripts/build-many-glibcs.py, which could use different compiler
revisions.)

Thanks,
Jan-Benedict
--

[Avi Kessner]

Technically, you can set an environment variable, and then there is a Jenkins API to read the environment variables of a job. However, I think artifacts is a better way.

brought to you by the letters A, V, and I
and the number 47

--
You received this message because you are subscribed to the Google Groups "jenkins-job-builder" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkins-job-bui...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/jenkins-job-builder/20260129105058.GM4689%40lug-owl.de.