perlbot / canary-builder

This is a new recreation of my old daily build system for blead I'm rewriting it to take advantage of things I've learned and some changes in the setup for everything to be more robust and nicer to work on. The original is at ... and was mostly written as some bash scripts. This version will be almost entirely in perl and directly depend on App::EvalServerAdvanced to be running to perform the testing and fuzzing functionality. This will enable the tests to run in parallel and also better handle some patholigical timeout cases that I've run into issues with. I'll also be doing the builds via Perl::Build instead of perlbrew, to enable more fine grained control over things, and enable testing the unthreaded version of perl while the threaded is being built. This will also enable me to do better reporting than just a dump from cron.

Tasks:

1. Move Perl::Build code into library utilizing Future
2. Use IO::Async::Function or ::Routine to enable doing tasks in parallel
3. Use Email::Stuffer to report failures to mailing list
4. Report on CPAN module installs and failures individually
5. Run filesystem shrinking script after all is said and done
6. Keep logs in compressed form (zstd) available on webserver
7. Automatic cleanup of logs after 30 days
8. Automatic cleanup of perls, keep last 5 successful builds of threaded and unthreaded
9. Use secondary evalserver, configured for batch mode scheduling so that it can't overload the system
10. Allow for specific commits/tags/branches of perl to be built and tested

canary-builder's Issues

Support final symlinks when tests complete successfully

Support creating simpler symlinks when build is complete

ln -nsf blead-2020-07-27-ASDF-threads blead-threads

This gets used by the evalserver to easily point at the latest build

Support log compression

It'd be good to support something for compressing log files to tiny sizes. I think zstd with a dictionary trained on a build should be perfect. This then needs a mojo app to send them off

Need a configuration file

A base configuration file of some kind to go along with the command line options. This way I can setup a few regular builds to handle

Sequencing issue with perl builds

Right now it won't do cpanm and other testing concurrently.

It should be able to build each perl in sequence and then do cpanm and testing while building other perls

Logs are broken

They need to be rewritten and written for each cpan and perl build. This way they are archived in a way that lets me report failures to cpanreporters

Support saving build state to SQLite database

This should support how each build and install went so that it can be queried. This should be consumable by the mojo log app

Needs command line options

Needs command line options for branch name, source directory, and a few other things. All TBD

Flexible build option handling

Right now I hard code threaded and unthreaded builds, this needs to be flexible and support a few other options.

Likely an option for usemymalloc and maybe something for cflags.

Much further into the future, support resuming an incomplete run from the SQLite database

This is more for when I get it ready to do a complete cpan run from a perl version. It's going to be expected that things will break and need to be restarted from the previous state.

This will require being able to resume each section of things, mostly the cpanm installs.

Log perl -V after each build

Need to make a log file for perl -V so that constructing a cpanreport is easy to do after the fact