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: Henrik Holst via curl-library <curl-library_at_lists.haxx.se>
Date: Wed, 9 Feb 2022 18:11:04 +0100
Completely unaware how all this works so take this with a huge grain of
salt but it seems like there is much resources wasted on CI when real
errors in patches/pull requests happen. So would it be possible to do
nested CI checks?
With that I mean that if eg "make checksrc" fails then no other CI jobs
should be executed. And then define a default build for Linux, macOS and
Windows where further CI jobs for e.g Linux would only be run if the
default CI job for Linux was successful and so on.
/HH
Den ons 9 feb. 2022 kl 16:00 skrev Daniel Stenberg via curl-library <
curl-library_at_lists.haxx.se>:
> On Wed, 9 Feb 2022, Timothe Litt via curl-library wrote:
>
> > A DB server doesn't have to be high tech; would be pretty simple to
> write a
> > Perl script that acts as a stand-alone network server;
>
> The basics seem easy to describe:
>
> 1. Setup a stats-collecting server with some sort of db backend
> 2. Make CI jobs submit stats to the server using curl
> 3. Write "reporters" to help us analyze the stats and the CI jobs
>
> Bonus:
> 4. Provide the analysis/info with a web UI
>
> I am certain that I'm not the ideal person to do (1) as I'm a general db
> rookie so I would likely end up spending a lot of time accomplishing very
> little and doing plenty of mistakes.
>
> (4) is also something I *can* do but I'm generally bad at.
>
> Anyone interested in helping out with this?
>
> --
>
> / 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.html
>
Date: Wed, 9 Feb 2022 18:11:04 +0100
Completely unaware how all this works so take this with a huge grain of
salt but it seems like there is much resources wasted on CI when real
errors in patches/pull requests happen. So would it be possible to do
nested CI checks?
With that I mean that if eg "make checksrc" fails then no other CI jobs
should be executed. And then define a default build for Linux, macOS and
Windows where further CI jobs for e.g Linux would only be run if the
default CI job for Linux was successful and so on.
/HH
Den ons 9 feb. 2022 kl 16:00 skrev Daniel Stenberg via curl-library <
curl-library_at_lists.haxx.se>:
> On Wed, 9 Feb 2022, Timothe Litt via curl-library wrote:
>
> > A DB server doesn't have to be high tech; would be pretty simple to
> write a
> > Perl script that acts as a stand-alone network server;
>
> The basics seem easy to describe:
>
> 1. Setup a stats-collecting server with some sort of db backend
> 2. Make CI jobs submit stats to the server using curl
> 3. Write "reporters" to help us analyze the stats and the CI jobs
>
> Bonus:
> 4. Provide the analysis/info with a web UI
>
> I am certain that I'm not the ideal person to do (1) as I'm a general db
> rookie so I would likely end up spending a lot of time accomplishing very
> little and doing plenty of mistakes.
>
> (4) is also something I *can* do but I'm generally bad at.
>
> Anyone interested in helping out with this?
>
> --
>
> / 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.html
>
-- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2022-02-09