Hi Gil, Indeed this might be happening and anyone doing a commit should keep this in mind and amend the documentation BEFORE committing the actual code changes. In the normal case the build of a single document takes only a couple of minutes (with the exception of the ooDialog docs).
For a potential release the entire documentation would need to be rebuilt, with new copyright messages, changes entered etc BEFORE any builds are run. I have already considered this and will turn off all building platforms leaving only the documentation build running. Only when that is finished will I let some build platforms run. I am not quite there yet with the automatization but I do think we should try to strive towards a release before the Symposium. Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 17.02.2025 um 16:05 schrieb Gilbert Barmwater <gi...@bellsouth.net>: > > +1 > > Just one (slightly) negative note however. The Windows builds include the > documentation (PDFs) which is retrieved from the most recently built > versions. If one updates the documentation AFTER committing the code > changes, the documents will be rebuilt AFTER the new builds are made and, > hence, will NOT be included. So it seems that, at least for Windows, the > docs are (almost) always out of date. I don't see a way for the build system > to fix this problem as it can't know that a document update is "pending" but > I suppose it could trigger a code rebuild after a document rebuild. Of > course, if the developer were to commit the doc updates FIRST and then the > code updates (waiting for the docs to be rebuilt), the problem goes away. > But we all know that the documentation is the last to be done <sigh>. > > Gil > > On 2/17/2025 8:05 AM, Rony G. Flatscher wrote: >> Hi P.O., >> >> On 11.02.2025 17:19, ooRexx wrote: >>> This is just to say that Jenkins is up&running again, all platforms (with >>> the exception of ams-02 (René) and ubuntu16 (Erich)) are connected and all >>> builds are ok. Some tests are not ok but these are minor issues. >>> >>> It is fine to commit again >> it seems that all works out judging from the automatic production of ooRexx >> (full installation package and portable version) and running the tests after >> yesterday's commits. It is great as it is also always reassuring when one >> can see that after changes the tests run through in full. >> >> This is a *real* boon, thank you for your hard work for the community! >> >> How about offering a talk about the infrastructure you set up and maintain, >> what it (automatically) allows for, the current state and future plans? I >> think this would be very interesting for others, unacquainted about how >> ooRexx gets compiled to multiple platforms and tested on them! >> >> Kudos! >> >> ---rony >> >> >> >>>> Am 07.02.2025 um 17:32 schrieb ooRexx <oor...@jonases.se> >>>> <mailto:oor...@jonases.se>: >>>> >>>> Dear all, >>>> >>>> Beginning of this month I was “upgraded” by my internet provider. This >>>> caused a lot of local problems and I still have not solved the problems >>>> with Jenkins. For this reason the build platform will be unavailable for >>>> some time, I will report back when I have a solution. >>>> >>>> Hälsningar/Regards/Grüsse, >>>> ooRexx >>>> oor...@jonases.se <mailto:oor...@jonases.se> >>>> >>>> >> -- >> -- >> __________________________________________________________________________________ >> >> Prof. Dr. Rony G. Flatscher, iR >> Department Wirtschaftsinformatik und Operations Management >> WU Wien >> Welthandelsplatz 1 >> A-1020 Wien/Vienna, Austria/Europe >> >> http://www.wu.ac.at <http://www.wu.ac.at/> >> __________________________________________________________________________________ >> >> >> >> >> >> >> >> >> _______________________________________________ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> <mailto:Oorexx-devel@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- > Gil Barmwater > _______________________________________________ > 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
