Hi all,
I also favour Travis.
But I kindly ask you all to bear with me with - first moving all our services and - bring them up to some extent and - only _after_ that, selectively retiring those services.
That would mean here, please lets move jenkins over, machine with enough space is already provisioned. Also, please lets get it running for now. I know there are some services out there that depend on some deep links into jenkins. No, this is not nice, and I really want to get rid of that, but please _after_ the move :D
Best regards -Tobias
On 29.09.2016, at 19:29, Frank Shearar frank.shearar@gmail.com wrote:
I think using TravisCI instead of our solution is a fabulous idea, and wholeheartedly support the move to same.
frank
On 29 September 2016 at 05:20, David T. Lewis lewis@mail.msen.com wrote: CC to Frank because he may not be following these discussions.
On Wed, Sep 28, 2016 at 10:03:41AM +0000, Fabio Niephaus wrote:
On Wed, Sep 28, 2016 at 11:31 AM Tobias Pape Das.Linux@gmx.de wrote:
Dear all
[ACTIONS AT END]
with retroactive blessing of Levente, I have now prepared eight VMs on Rackspace. Here's the overview:
<snip>
- Do we need Jenkins anymore?
We moved Squeak-Trunk to TravisCI, so if there isn't anything else important still running there, I'd say no.
I have still been using a couple of test projects on build.squeak.org but overall it is not maintained, and I do not think that we should continue to make it publicly visible (links from squeak.org) in that condition.
My suggestion is that we should copy /var/lib/jenkins directory to Rackspace if space permits, so that we do not lose it in the move. Aside from that, I don't think it is something we need to spend time on for the move. If we want to put it back on line, we can do that later if and when a volunteer steps forward.
If the real CI work is happening on TravisCI now, then we should see if we can point build.squeak.org at that system.
Dave