That raises an interesting subject. The script in question is a jenkins script. Part of a larger build job, which in turn is a part of a family of jobs that do various sub-tasks. The editing is through the jenkins web-gui, and that will not be made accessible to the public. I'm troubled that Jenkins doesn't seem to keep an edit history of 'config' changes out of the box, and I've yet to spot a plugin that adds this feature.

I've been pondering making the jenkins home directory one big git, with a lot of excludes for all the build history, logs, workspaces and such. Has anyone solved this? A git could readily be published.

In the mean time, the script content can be inferred from the various build logs. A successful build would be more informative. e.g. http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190121T060000Z/logs/

Accepting feedback/revisions would be another matter entirely. We'll probably stick with e-mail to myself, and build.starlingx@gmail.com, for the near term.

Scott

On 2019-01-22 11:20 a.m., Victor Rodriguez wrote:

Thanks, Scott

Please also send the link of the script so we can send patches to imrpove it

Regards