Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: A CI job inventory
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_lists.haxx.se>
Date: Tue, 8 Feb 2022 00:23:47 +0100 (CET)
On Mon, 7 Feb 2022, Dan Fandrich via curl-library wrote:
> I would rather treat the CI files as the sources of truth and derive a
> dashboard by parsing those instead, to show the jobs that are *actually*
> being run. The down side to that, of course, is that you'd need to write
> code to parse 6 different CI configuration file formats, but the significant
> benefit is that you could always trust the dashboard.
Thanks for talking sense. I should rather go that direction: to generate that
"inventory" file from the sources we already have and maintain.
> Maybe a hybrid approach is the best; read and parse as much job data as
> practical from the job name and "env" section of each CI configuration file
> (which should be pretty simple and stable to retrieve), and supplement that
> with additional data from a structured comment (or magic "env" variable),
> where necessary.
Sounds sensible. I'll reroute and try something along this line. It'll be a
bit more scripting, but it should also ideally become more reliable.
Date: Tue, 8 Feb 2022 00:23:47 +0100 (CET)
On Mon, 7 Feb 2022, Dan Fandrich via curl-library wrote:
> I would rather treat the CI files as the sources of truth and derive a
> dashboard by parsing those instead, to show the jobs that are *actually*
> being run. The down side to that, of course, is that you'd need to write
> code to parse 6 different CI configuration file formats, but the significant
> benefit is that you could always trust the dashboard.
Thanks for talking sense. I should rather go that direction: to generate that
"inventory" file from the sources we already have and maintain.
> Maybe a hybrid approach is the best; read and parse as much job data as
> practical from the job name and "env" section of each CI configuration file
> (which should be pretty simple and stable to retrieve), and supplement that
> with additional data from a structured comment (or magic "env" variable),
> where necessary.
Sounds sensible. I'll reroute and try something along this line. It'll be a
bit more scripting, but it should also ideally become more reliable.
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://curl.se/support.html -- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2022-02-08