Hi Gavin,

Am 16.11.21 um 09:37 schrieb Gavin McDonald:
> Hi All.
>
> Ok so I am making progress.
>
> The nightly x64 build is running fine. as are the rat builds.
> I'll get the 41 branch added today - should we also do a 42 branch build?

Thanks!

It would be ideal to have all branches (trunk/AOO42X/AOO41X).

>
> As for the win10 builds I am working on those now.
>
> I am at a stage in the win10 build where it wants dlls and exe files
> (listed below) from an
> 'external' directory located on the machine but outside of the build
> itself. These get copied in
> during a build step.
>
> These files have been previously uploaded manually to the buildbot
> node/agent. I'd like to stop that
> practice; and change the build so that it pulls them in from a repository
> instead. We can create a new
> gitr repo called openoffice-externals and put them in there. This method
> has the added advantage that
> the project can then manage these externals themselves,
> adding/updating/deleting/whatever from the
> repo and the build will pull those in each time.
>
> Thoughts? My only query really was one of whether or not these libraries
> should not be available to the
> public, (I don't see why) in which case I would have to rethink this
> strategy. If I can get replies ASAP on
> this please so that I can continue to migrate the builds.
>
> Thanks
>
> /////////
>
> '/cygdrive/e/slave14/aoo-win7/external/gdiplus/gdiplus.dll'
> '/cygdrive/e/slave14/aoo-win7/external/dbghelp/dbghelp.dll'
> '/cygdrive/e/slave14/aoo-win7/external/msm90/Microsoft_VC90_CRT_x86.msm'
> '/cygdrive/e/slave14/aoo-win7/external/msm90/policy_9_0_Microsoft_VC90_CRT_x86.msm'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp100/msvcr100.dll'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp71'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp71/msvcp71.dll'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp71/msvcr71.dll'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp80'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp80/msvcp80.dll'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp80/msvcr80.dll'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp90/Microsoft.VC90.CRT.manifest'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp90/msvcm90.dll'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp90/msvcp90.dll'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp90/msvcr90.dll'
> '/cygdrive/e/slave14/aoo-win7/external/vcredist/vcredist_x64.exe'
> '/cygdrive/e/slave14/aoo-win7/external/vcredist/vcredist_x86.exe'
> '/cygdrive/e/slave14/aoo-win7/external/vcredist/old'
> '/cygdrive/e/slave14/aoo-win7/external/vcredist/old/vcredist_x64.exe'
> '/cygdrive/e/slave14/aoo-win7/external/vcredist/old/vcredist_x86.exe'

No objection against copying these files from whatever location. They
haven't changed in the last years but it is always good when we can
access them.

If you take the files from the old buildbot everything should be the
correct version.

If you have questions about the Windows builds, feel free to contact me.

Regards,

   Matthias

>
> /////////
>
> As can be seen at:
> https://ci.apache.org/builders/openoffice-win7/builds/737/steps/externals/logs/stdio
>
> On Sun, Nov 14, 2021 at 9:54 PM Carl Marcum <cmar...@apache.org> wrote:
>
>> Hi Gavin,
>>
>> On 11/14/21 2:16 PM, Gavin McDonald wrote:
>>> Hi All,
>>>
>>> As the current Buildbots arent really working, nodes offline etc, I
>> thought
>>> this would be the best time to migrate your builds over to our newer
>>> replacement
>>> buildbot 3.2 over at ci2.apache.org .
>>>
>>> I'll do my best to get them all running as passing as best they can, and
>>> will update this thread with any questions or messages.
>>>
>>> My first query is seeing as we have no more i386 or FreeBSD agents/nodes,
>>> I'll probably just go ahead and remove those from the new config file.
>>>
>>> HTH
>>>
>> I just realized I had somehow missed your original email about migrating
>> andwas discussing getting with you.
>>
>> Thanks for working on this.
>>
>> Let us know if you have any questions.
>>
>> Best regards,
>> Carl
>>
>

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to