Call for test Stephdl modules

[giacomo (Giacomo Sanchietti)]

@davidep

I think NethForge admins should be granted write access on NethForge comps. Others should open PR.

I agree, @stephdl the code is here: https://github.com/NethServer/comps-nethforge

@stephdl

Actually it is talking to push rpm, but not srpm, I would be interested to know if it is not more secure with a builder (self hosted or at http://openbuildservice.org/) which fetchs srpm or sources. At least we can be sure that the rpm could be built on the major part of other servers and not only on the developer’s one who did the code.

As Davide said, you can push srpms to the Forge, but the forge itself is only a yum repository, not a build system.
I just played a bit with COPR (Fedora build system), which has Github integration with webhooks.
Take a look: Index of /results/giacomo/letsencrypt.sh/epel-7-x86_64/00164005-letsencrypt.sh/

But we still need a the forge machine to push RPMs to official yum repository.

[davidep (Davide Principi)]

A fully automated build system is a nice to have but not a priority for me. We build a tiny set of noarch RPMs.

I think we have a simple and open development process built on widely adopted dev tools (git, mock, sftp).

@stephdl, are you the “man of NethForge”? I would be happy if you jump in!!

[alefattorini (Alessio Fattorini)]

@stephdl

there is an open(ed) process for pushing rpm to nethforge, but I recall that if you want to see the rpm available in the software panel you must modify something (the ‘comps’ or something else).

For you, is it “mandatory” in order to move existing modules on NethForge?