Gosh - this would be a great talk at a conference⦠;) Maybe at Esug someone can show me some of what is going on⦠I donât really understand how you are building things, but it should be possible to come up with some pragmatic things that maybe we can help with. Certainly self halt. should be a simple one to detect and get in place. In my Esug, talk I was going to show my simple (and naive) script that builds the OU image and regexâs the transcript that I pump out to the file system. It sounds like the Pharo build is much more clever - but maybe that technique might work too? Tim On 14 Aug 2014, at 15:19, Marcus Denker <marcus.denker@inria.fr> wrote:
On 08 Aug 2014, at 17:29, Tim Mackinnon <tim@testit.works> wrote:
Maybe this is a good moment to review what checks are run on every build and ensure that they are working?
Itâs easy to leave in something like self halt - it would be nice to have the CI system do its stuff and send you an email that you forget (this is where CI is awesome).
Yes⦠but nothing happens by itself.
Iâm also assuming in the CI process we check logs for âundefinedâ and âerrorâ msgs that would appear in the transcript right?
no, it does not. It fails on Error, though. And Undeclareds are checked by the test #testUndeclared of the ReleaseTest class that is run on the final result of the build.
Marcus