Jenkins in new cloud - status update

[Pierre-Yves Chibon]

On Fri, Jul 31, 2015 at 12:24:50AM +0200, Mikolaj Izdebski wrote:
> On 07/30/2015 09:11 PM, Kevin Fenzi wrote:
> >> Deployment details: There are: 1 master and 3 slaves (workers) running
> >> in the new cloud.  All instances are of type "m1.small" (1 CPU, 2 GB
> >> RAM, 20 GB disk).
> > 
> > In the old cloud some of the builders were bigger, should we bump
> > these up some when we move to production? 
> 
> I will check instances on the old cloud, now I should be able to access
> them. I wanted to avoid unnecessary resource consumption, given that
> this is only dev instance.

+1 for a larger disk size. We got bitten by this in the past that some projects
are quite demanding space wise and keeping the results of the builds also
increases the disk usage.

> >> Only members of sysadmin-jenkins group have admin access through web
> >> interface.  Should sysadmin-main be added there too?
> > 
> > We could, but I think all the sysadmin-main folks that are interested
> > are already in sysadmin-jenkins and/or we could add them easily. 
> 
> Ok, I'll leave it as-is (sysadmin-jenkins only).
> 
> >> Subversion plugin is currently disabled due to unresolved problem.
> >> Projects using subversion SCM (if any) won't work until this is fixed.
> > 
> > Do we have any SVN projects in the old cloud?
> 
> I don't know, but there is subversion plugin installed.

As far as I remember there are none, I added the plugin to be complete but I
don't know of any project using it.


Thanks for working on this!

Pierre