Hi,
d.ostrovsky@idaia.de wrote on 2013-10-07 14:32:
thanks for fixing that. Buildbot-Log@Jenkins is reachable again.
kudos to Alex then, seems he was fast. :-)
That's because Buildbot-logs deployment on VM4 was a temporary solution.
The plan was to move that Jenkins instance to a new VM.
if that has changed, please notify hostmaster@tdf
Nope it didn't, unless we redefine VM4 as production VM.
Ok, so I keep it as testing. A new instance should be in KVM anyways,
not in LXC as vm4.
If there's anything you need, let me know.
Florian
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.