> On 20. Apr 2024, at 13:34, Rony G. Flatscher <[email protected]> wrote:
>
> Hi P.O.,
>
> thank you for your information and efforts!
>
> How about targeting an initiative to create a new release (5.1.0) at the
> beginning of June then?
>
>
I am fine with that Rony, if there is a decision to go ahead at that time, I
will iron out the last bits& pieces then. To make a meaningful test I would
need to work on a 5.1.0 release candidate, but that can wait until we are
closer to a release. I will remove the staged directories today,
I noticed that there had been some commits just now before I had the
opportunity to revert back to 5.1.0Beta, Jenkins did not respond since it
monitored 5.0.0 release brach. When switching back to 5.1.0Beta again it picked
up the commits and is now building as expected. On some platforms there will be
a conflict since we use -upgrade install (to really test the installer) but I
will relaunch those items manually once everything has calmed down. This was a
good test I think. As you can see from this snipped the 5.1.0 artifact was
created but failed the upgrade because of a 5.0.0 being installed.
CPack: Create package
CPackRPM: Will use GENERATED spec file:
/home/osboxes/workspace/ooRexx-CentOS9-build/oorexxBuild/_CPack_Packages/Linux/RPM/SPECS/oorexx.spec
CPack: - package:
/home/osboxes/workspace/ooRexx-CentOS9-build/oorexxBuild/oorexx-5.1.0-12831.centos9.x86_64.rpm
generated.
+ pkill rxapi
+ sudo rpm --upgrade oorexx-5.1.0-12831.centos9.x86_64.rpm
file /usr/local/bin/csvStream.cls from install of
oorexx-5.1.0-12831.x86_64 conflicts with file from package
ooRexx-5.0.0-12830.x86_64
file /usr/local/bin/json.cls from install of oorexx-5.1.0-12831.x86_64
conflicts with file from package ooRexx-5.0.0-12830.x86_64
file /usr/local/bin/rexx from install of oorexx-5.1.0-12831.x86_64
conflicts with file from package ooRexx-5.0.0-12830.x86_64
> Cheers
> ---rony
>
>
>
> On 19.04.2024 19:01, ooRexx wrote:
>> A progress report on my activites today.
>>
>> The test was partially successful, if you look at Sourceforge you will find
>> two folders 5.0.0test under /files/oorexx and /files/oorexx-doc. They are
>> staged so only visible if you are logged on to sourceforge.
>>
>> For the understanding of how Jenkins works: Each job is defined in an xml
>> file and each setting in the GUI correspond to a line in the xml.
>>
>> The test showed that it is possible to parse and modify all those xml files
>> and thereby modify all build jobs in one go, replacing "needles" with
>> "newneedles", i.e. switching from 5.1.0beta to 5.0.0test or whatever.
>>
>> I have also modified the uploading script so that it can be redirected by an
>> input parameter. This worked with the sideeffect that all the 5.1.0 files
>> were uploaded as well. They can be removed manually or deleted in the work
>> folder so not a big problem
>>
>> The zip uploader did not work as expected, not yet sure why.
>>
>> The documentation build should also accept input parameters to redirect the
>> builds, unfortunately this did not work as expected, I will look into that
>> later.
>>
>> Finally, since I reproduced the 5.0.0 I got all the mistakes coming back
>> (referring to a missing document; wrong case for the built entities etc)
>>
>> Have a look on sourceforge and on Jenkins, I will restore everything
>> tomorrow 20.4. to 5.1.0beta again.
>>
>> In my view this will be a doable way to save manual work during the next
>> release, unfortunately I will be away from home for the most of April and
>> May and can only help at the beginning of june.
>>
>>
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> [email protected] <mailto:[email protected]>
>>
>
> _______________________________________________
> Oorexx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
