LilyPond Contributor's Guide: 14.4.4 Configuring Patchy

[ << Administrative policies ]	[Top][Contents][Index][ ? ]			[ LilyPond grammar >> ]
[ < Installing Patchy ]		[ Up : Automated testing with Patchy ]	[ Running the scripts > ]

14.4.4 Configuring Patchy

Note: It is recommended to create a new user on your computer specifically to run the Patchy scripts as a security precaution and that this user should not have any administrative privileges. Also do not set password protection for your ssh key else you will not be able to run the scripts unattended.

Make sure the environment variables LILYPOND_GIT and LILYPOND_BUILD_DIR are configured appropriately. See Environment variables.
To save being prompted for your login and password to http://code.google.com/ when testing patches. create a plain-text file in your Patchy user’s $HOME directory called .lilypond-project-hosting-login containing your login and password, each on a separate line.
```
joe_smith123@gmail.com
mYp455w0rd!
```
Manually run either the test-patches.py or lilypond-patchy-staging.py scripts and when prompted:
Warning: using default config; please edit /home/joe/.lilypond-patchy-config Are you sure that you want to continue with the default config? (y/[n])
Answer “n” and press enter.

The next time either of the scripts are run they will use the .lilypond-patchy-config settings copied to your $HOME directory.
Manually edit the ‘.lilypond-patchy-config’ file, located in your $HOME directory to change any of the default settings.

These include:

All make operations are run with;
```
extra_make_options = -j3 CPU_COUNT=3
```
See Saving time with the ‘-j’ option
A complete build of all the LilyPond documentation is not performed;
```
patch_test_build_docs = no
```
Each instance of either a patch test or commit test & push is logged in;
```
auto_compile_results_dir = ~/lilypond-auto-compile-results/
```
Both scripts will perform their build operations in;
```
build_dir = /tmp/lilypond-autobuild/
```

Each completed patch test will also generate its own directory in ‘/tmp/...’ labelled with the tracker issue number prefixed by show-.

\tmp\show-3446

Both the scripts create clones of staging and master branches (prefixed with test-) with a third branch, called test-master-lock used as a check to protect against two or more instances of Patchy being run locally at the same time.

[ << Administrative policies ]	[Top][Contents][Index][ ? ]			[ LilyPond grammar >> ]
[ < Installing Patchy ]		[ Up : Automated testing with Patchy ]	[ Running the scripts > ]

14.4.4 Configuring Patchy

LilyPond — Contributor’s Guide v2.19.24 (development-branch).