well, that explains a number of things. Indeed it builds on your machine now; rather quickly compared to the much slower docker build on my machine. Also, I took the zip from my local machine so it really is no miracle that it ran on the same image on which it was built on.
I switched to ubuntu16 thinking it was an alias for P.O.’s build machine, that was also just moved to ubuntu. This was because it did not build on master - so black to the blueprints. It appears we need at least one slave that runs docker. René. > On 26 Dec 2018, at 15:48, René Jansen <rvjan...@xs4all.nl> wrote: > > well, that certainly is amazing! I am going to see what happened here. Just > before I stopped this activity last week I made a zip from the last build > that it did, and that ran perfect on Arch Linux - but I see that might have > been a ubuntu build. I checked this with a local jenkins and that went also > fine - and I put uname -a and gcc —version in there to make sure it ran in > the docker image. So, I’ll put in some debug of the build process and will > let you know. > > René. > >> On 26 Dec 2018, at 15:26, Erich Steinböck <erich.steinbo...@gmail.com >> <mailto:erich.steinbo...@gmail.com>> wrote: >> >> The label ‘ubuntu16’ tells it to build on the master machine because I know >> that to have a docker system running >> Well, ubuntu16 is my Ubuntu VM, and I'm pretty sure it has no docker running >> It's seems a bit amazing that the pipeline doesn't notice that. >> >> _______________________________________________ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> <mailto:Oorexx-devel@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
