[Starlingx-discuss] [build-report] STX_build_stein_master - Build # 23 - Failure!

[Victor Rodriguez]

On Tue, Jan 22, 2019 at 11:58 AM Ponce Castaneda, Guillermo A
<guillermo.a.ponce.castaneda at intel.com> wrote:
>
> Hello Scott,
>
> Why don’t you put your Jenkins jobs on a git repository?
>
> This can be done by issuing a GET method to the address <JENKINS_URL>/job/<JOB_NAME>/config.xml.
> The GET method will bring you back an xml file that represents the configuration of the job, including any scripts contained inside.
>
> To issue this GET method you may use your USER and PASSWORD or if you have an API_TOKEN you can use it instead of your password.
>
> This is an example on how this can be done.
>
> $ curl https://somejenkinsserver.com/job/some_job/config.xml --user ${USER}:${API_TOKEN}
>
>
>
> It is also possible to modify jobs by issuing a new XML file on a POST method, in case you want to automate changes based on your git repo.
>
>
>
> I also happen to have a script that backups and restore Jenkins Jobs configs, here’s a github gist where you can see it:
>
> https://gist.github.com/gaponcec/8f43635707849feae8555fd4d2572755
>
>
>

Sounds like a great way we all can collaborate, to improve the quality
of the tools/CI-CD we have
 Scott, what do you thing?

>
>
> From: Scott Little <scott.little at windriver.com>
> Date: Tuesday, January 22, 2019 at 11:35 AM
> To: Victor Rodriguez <vm.rod25 at gmail.com>
> Cc: "starlingx-discuss at lists.starlingx.io" <starlingx-discuss at lists.starlingx.io>
> Subject: Re: [Starlingx-discuss] [build-report] STX_build_stein_master - Build # 23 - Failure!
>
>
>
> 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 at 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
>
>