Re: automated computing tasks for lilypond

[John Mandereau]

Il giorno gio, 30/08/2012 alle 18.15 +0100, James ha scritto:
> Yes actually that would help. Also what would be useful in a similar
> vein would be what I need to configure where in my 'config' so that
> when I do accept or reject patchy.py I don't have to keep adding my
> user and password to the gmail account.

You need to write gmail account name (full email address) on first line,
and the password on second line, in a file
~/.lilypond-project-hosting-login, then do

chmod 700 ~/.lilypond-project-hosting-login


>  We have two of config files.
> lilypond-patchy-config and .msmtp-patchy (used by patchy staging).

I sent you a sample config file, if the instructions work for you too
I'll add them to the CG.


> > Is the manual running of Patchy/staging twice a day the frequency you
> > aim at in production phase too?
> 
> not especially, I could run it every hour if you wanted? It takes
> about 20 minutes to do a full merge.

It's glad IMO running every two hours is frequent enough, running every
hour wouldn't bring much more and so would not be worth stressing the
hardware more.  Of course, the build is done only when new commits
appear in staging, so in fact you'd have to see whether setting it to
run every hour would not make it run much more frequently in practice.


> I used to run it every 6 hours, but because I didn't have any email
> notifications to watch it from work, I was a bit hesitant to do so.

This is understandable.  More than having email notifications of every
single run, I can recommend you to set build_user in compiling section
to have a bit more security, which is not really needed to
lilypond-patchy-staging, but is good to have for patches tests, see
instructions in the commit message of 
6e5acb57aa83bd9287afe3cbfa9b67a56cf405be:

https://github.com/gperciva/lilypond-extra/commit/6e5acb57aa83bd9287afe3cbfa9b67a56cf405be

The last paragraph is a bit unclear ("lilybuild" should read "builduser"
BTW): even on a non-server setup, you must add "gituser" to the group of
"builduser", which is easily done by appending "gituser" to the group
definition of "builduser" in /etc/group, and you must make sure that the
parent directory BUILD_PARENT of build_dir configuration setting has rwx
permissions for both "gituser" and "builduser", which may be achieved
with

chown builduser:builduser BUILD_PARENT
chmod 775 BUILD_PARENT

Best,
John