[sakai-pmc] Decommission Collab server?

[Matthew Jones]

We have to continue to run Jenkins though at least the support period for
the 2.9 release so I'd say for another year. If Jenkins stopped building
artifacts for 2.9 then because of the indies and core deploy, various local
builds would (and do) fail once sonatype removes the snapshots (usually
after a few weeks).

Once 11 is out and we are no longer supporting 2.9 we could safely retire
both Jenkins and Mailman, if Google groups provides a good option for
mailman. All of the archives are available as flat html files, and are also
indexed in nabble and gmane anyway.

I'd say get it for one more year and plan to end these services in summer
2015.

I think there is still value in having Jenkins do periodic compiles of the
full Sakai tree, but I think whenever we get new nightlies setup (probably
on EC2 or digitalocean), that a new process that is tied into that will
exist.


On Tue, Jun 10, 2014 at 8:04 AM, Neal Caidin <neal.caidin at apereo.org> wrote:

> Hi Sakai PMC,
>
> What do you think about moving all of our Collab lists to the Apereo
> Google Groups?
>
> My understanding is that the Collab system and the Jenkins system are on
> the same physical box. If there is an opportunity to move the Jenkins
> system then potentially we could decommission the use of that server.
>
> I'm not sure how (and where) we would move Collab archives off the server
> and keep them searchable, which I presume we would want to do? It seems to
> me like if we make this change we would want to figure that out now.
> Otherwise we risk not having the knowledge, energy and resources to make
> the move (I'm kind of assuming that Anthony would help, which may or may
> not be a good assumption).
>
> I'm asking now because we need to renew the security certificate for the
> Collab server and I was thinking maybe we would just do a one year
> extension while we make the move. We haven't kept up with Collab software
> upgrades. With Google Groups we wouldn't have to worry about such things.
>
> Btw, I have been hearing that the real cost of moving the Jenkins server
> is the labor involved. So it may be that there is not a compelling enough
> reason to change that for now.
>
> Cheers,
> Neal
>
>
> _______________________________________________
> sakai-pmc mailing list
> sakai-pmc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20140610/b327942c/attachment.html