Ok, my mistake, I assumed that Windows being the most used ooRexx item would be automatically updated. I assume that I could copy it from the slave to my own machine?
In the meantime I have set up & built myself today ooRexx on Windows, several times with various settings. Building is slow and I did not manage to speed it up although I run the build on a i7 machine :-( I have also set up & run (almost) all tests but I get several errors that I do not know how to handle. Can I come back to U later on that? Finally I have now amended fileutil.cls to work also for macOS and I have copied over and run one new sample test case. Before I convert the rest (I have done test cases for all sample files) I need your feedback on how it was done so that I can correct anything once before the bulk of the work. I will provide a Diff file in a separate posting. I tried to run tests for samples also on Windows but none of the samples (including the ones already in) work for me on Windows. Can you confirm that you can run say month.testGroup and get any output? Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 08.02.2019 um 12:24 schrieb Erich Steinböck <erich.steinbo...@gmail.com>: > > ooRexx-5.0.0-11724.windows.x86_64.exe, but this file is not to be seen at the > sourceforge download site. > > Hi P.O., > unfortunately there's no connection between the slaves or the build server > and the sourceforge files section, except for two slaves, where I managed to > set up an automatic upload. All Windows builds that show up on sourceforge > have been manually uploaded by me. > > Automatic upload is difficult due the required public key/private key setup > for each slave. > This is why I decided to try to transfer all built installers to the Jenkins > master (most slaves do that now using "Archive build artefacts") and the plan > is to set up public/private keys so that the master can then upload to > sourceforge files. That would involve a bit of scripting, including some > logic to also remove older builds from sourceforge again, but I haven't come > round to doing that. > > There may be better solutions for this, but I'm not aware of any. > > _______________________________________________ > 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
