> Am 16.12.2022 um 16:10 schrieb ooRexx <oor...@jonases.se>: > > I have updated all jobs on Jenkins and appended the info to > release-steps.txt. > > There are more things to do in relation to Jenkins: > > 1: should we keep two versions of the documentation? We build pdf and html > versions of all files. If so we need two folders. Wouldn‘t it be possible to generate the pdf and html files and place them in the same directory as was done in prior versions of ooRexx?
> 2: The documentation folder will only begin to fill up when there are amended > documents. The check of the amended documents is done locally so until there > are changes the (amended) documentation will not be rebuilt. > > 2B Optionally I can delete the version info locally at which time all > documents will be rebuilt. Well, it would be worth a try such that in the end the creation of the builds get tested by this. As we have a release cut off the trunk there are no new changes to be expected, unless we need to change something in each documentation document. > 3. I amended the uploading script to upload to the new folder. Unfortunately > this was not sufficient, there are more things to modify apparently. Since I > did not write the script I have asked Erich to have a look. +1 > 4. With the help of Mark Hessling I could revive the building and testing of > M1/ARM macOS. Surprisingly this caused some errors in the testing that we did > not see in the past. The building works flawlessly so I assume there is > something wrong with the setting for the testing. I will report the outcome. Interesting! Best regards —-rony Rony G. Flatscher (mobil/e) _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
