Re: [GNUnet-developers] Discussion, and Help Wanted: Moving to Gitlab for Git, CI, and Issues

[ng0]

Christian Grothoff transcribed 4.5K bytes:
> On 4/5/19 9:20 PM, Devan C. dvn wrote:
> > - wldhx has kindly offered two "Gitlab Runners" for running CI jobs.
> >   These will be added as shared runners, to be used by any projects on
> >   the instance. This may be changed later to only be shared by projects
> >   under the GNUnet namespace.
> 
> Eh, what is required here? It's not like we don't have enough CPU or RAM
> on gnunet.org itself, right?
> 
> > - Daily remote backups. Perhaps 'firefly.gnunet.org' could be the backup
> >   site, hmm?
> 
> I plan to re-install firefly "soon", after that it should ideally become
> the primary site in the future.
> 
> > Exporting:
> > - Mantis can export to CSV and "Excell" XML
> >   - These do not contain comments (bugnotes). It looks like there might
> >     be a possibility to enable them via a configuration option[2]. Not
> >     sure who all has admin access, whom I could coordinate with. Maybe
> >     easier if I can get admin rights? Grothoff, what do you think?
> 
> I've checked the configuration option, and it can only give you the #
> bug notes, not the bug notes as far as I can tell.  I think you will
> need to do a *proper* DB export->import.  Also, the CSV will hardly give
> you the file attachments either.

I think losing the file-attachments would be okay if that means we get
the migration done for the rest.
 
> > I suppose this means that we will continue to use Mantis, and disable
> > issues in Gitlab for now. Any protests or ideas?
> 
> Neither ideas nor protest from me at this time ;-).
> 
> >  4. Manually replicate permissions. Will need a Gitolite admin's help
> >  on this.
> 
> dvn: you're now gitolite admin, please help yourself ;-).

Unless you require general orientation what all of these permissions
and special permissions in gitolite grammar mean. Feel free to ask
if you need to.
 
> > - As we build out a matrix of pipelines, we will need more resources.
> > 'firefly.gnunet.org' is a logical option. In the past I've seen it
> > utilized heavily by experiments. As long as we are okay with dedicating
> > some CPU and RAM to runners, then I will begin setting them up.
> 
> How much crazy resources are you expecting to need here? You have ~20
> idle cores and 40 GB free RAM on gnunet.org --- and that's with the
> existing buildbot CI running. If gitlab is _that_ resource hungry, maybe
> it's not a viable option?
> 
> > - Setup Gitlab Container Registry [7] for storing our CI artifacts.
> 
> That's more worrisome, we're short-ish on disk space on _both_ systems.
> So please be careful there!

How much space for additional harddrives do they have? As a group or
as association we could certainly pay for more disks if possible.
 
> 
> Happy hacking!
> 
> Christian
> 




> _______________________________________________
> GNUnet-developers mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/gnunet-developers

signature.asc
Description: PGP signature