NethServer 6

Davide Principi wrote:

To completely replace and obsolete the old tools, we must

• complete the RPM workflow with the upload part

I added two shell functions to my ~/.bashrc.

This is a simple shell function that uploads RPMs:

function upload-rpms() {
    dest=$1
    shift   
    scp ${*} ${dest}
    host=${dest/%:*/}
    path=${dest##${host}:}
    ssh ${host} "pushd ${path} && make dispatch-rpm && make clean && make && popd" 
}

And this is another function that cleans up the git directory and executes the complete workflow:

function pbuild-rpms() {
    git clean -x -f && make-rpms *.spec && sign-rpms -k MYKEYID -f ~/.secret *.rpm && upload-rpms "$1" *.rpm
}

• runs into the project directory
• cleans up any non-tracked file
• the project must have only one .spec file
• any RPM will be uploaded
• remote repo make will be invoked

Sample invocation:

  pbuild-rpms host:/path/nethserver/6.6/testing

hi all

I have tried nethserver-mock, it is quite good, but it build by default in the repository where it is used, so if you use it in your git repository you can do a mess.
Indeed you can use it outside of your git repository but it is a command line more for changing your place of work.
Could it be possible to add an 'exchange' folder where rpms will be saved, this will be more convenient rather to play with cd command all the time. Of course if you do so, you must give the path where rpms are, so the buildder can copy and pasted with a convenient way to move his rpm.

here the script i use https://github.com/stephdl/git_mockbuild/blob/master/git_mockbuild

stephane de Labrusse wrote:

here the script i use https://github.com/stephdl/git_mockbuild/blob/master/git_mockbuild

Thanks for sharing your script Stephane! I think I'll take the CHANGELOG.git idea on loan ;)

nethserver-mock is different from nethserver-devbox: bare bone vs over-engineered :) The first is somehow process-agnostic (good), the latter is tailored on my personal build infrastructure (no good).

So I think the most important thing in nethserver-mock are the mock config files: I hope they could be useful for other scripts.

Also, to ease package testing, I'd like to set up a public CI environment to automatize package builds in the near future, but this is another thread.

No Problem Davidep, I'm glad to help...

The idea to have a main central build server, is the thing to do.....please go on.

Can we open another bug to get the rpm/srpm in another folder than the git folder ?

stephane de Labrusse wrote:

No Problem Davidep, I'm glad to help...

The idea to have a main central build server, is the thing to do.....please go on.

Sure! I'd like travis-ci or similar.

Can we open another bug to get the rpm/srpm in another folder than the git folder ?

Yep! Why not? Maybe a customizable --resultdir argument to mock is enough...

Indeed or in a folder called exchange in the user home.