| [ << Administrative policies ] | [Top][Contents][Index][ ? ] | [ LilyPond grammar >> ] | ||
| [ < Automated testing with Patchy ] | [ Up : Automated testing with Patchy ] | [ Patchy requirements > ] | ||
14.4.1 Overview of Patchy
Patchy is a set of Python scripts used for testing patches or testing &
pushing new commits added to remote/origin/staging to
remote/origin/master.
No programmatic skill is required to run either of the scripts; although knowledge of compiling LilyPond and its documentation along with understanding how to configure the PATH environment of your computer is required. See Working with source code.
The two scripts that are used for each function are:
-
test-patches.py. This script tests issues labelled as “Patch-New” on the LilyPond issue tracker. Part of the testing process involves running the regression tests, so this script always requires some human intervention in order to visually check for any differences that may be present after a successful test has occurred. -
lilypond-patchy-staging.py. This script checks for any new commits inremote/origin/staging, makes sure that the new HEAD compiles along with all the LilyPond documentation. Then finally pushing toremote/origin/master. This script can be run and left unattended, requiring no human intervention.
Both of the scripts can be run independently of each other and it is not necessary to be able to run both. So if you wanted to contribute to LilyPond development, for example by just testing patches then this would still be a helpful contribution to LilyPond’s development.
Patchy can also be configured to send emails after each successful (or unsuccessful) operation. This is not a requirement and is turned off by default.
| [ << Administrative policies ] | [Top][Contents][Index][ ? ] | [ LilyPond grammar >> ] | ||
| [ < Automated testing with Patchy ] | [ Up : Automated testing with Patchy ] | [ Patchy requirements > ] | ||