[ << Administrative policies ]	[Top][Contents][Index][ ? ]			[ LilyPond grammar >> ]
[ < Installing Patchy ]		[  Up : Managing Staging and Master branches with Patchy ]	[ Running the script > ]

14.4.4 Configuring Patchy

1. Make sure the environment variables LILYPOND_GIT and LILYPOND_BUILD_DIR are configured appropriately. See Environment variables.
2. Manually run either the lilypond-patchy-staging.py script 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.

3. 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/
  

The script creates a 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 : Managing Staging and Master branches with Patchy ]	[ Running the script > ]

<< Back to Documentation Index

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