| [ << Administrative policies ] | [Top][Contents][Index][ ? ] | [ LilyPond grammar >> ] | ||
| [ < Configuring Patchy ] | [ Up : Managing Staging and Master branches with Patchy ] | [ Automating Patchy > ] | ||
14.4.5 Running the script
lilypond-patchy-staging.py is run without any arguments.
It then checks to see if remote/origin/staging is
“further ahead” than remote/origin/master.
If there are no new differences between the two branches since the last run check, the script will report something like this:
(UTC) Begin LilyPond compile, previous commit at 4726764cb591f622e7893407db0e7d42bcde90d9 Success: No new commits in staging |
If there are any differences between the two branches since the last run check, (or if the script cannot for any reason, locate the last instance of a commit that it checked) it will report something like this:
(UTC) Begin LilyPond compile, previous commit at 4726764cb591f622e7893407db0e7d42bcde90d9 Merged staging, now at: 79e98a773b6570cfa28a15775a9dea3d3e54d6b5 Success: ./autogen.sh --noconfigure Success: /tmp/lilypond-autobuild/configure --disable-optimising ... |
and proceed with running make, make test and a
make doc. Unlike test-patches.py if all the tests pass,
the script then pushes the changes to remote/origin/master.
... Success: nice make clean Success: nice make -j7 CPU_COUNT=7 Success: nice make test -j7 CPU_COUNT=7 Success: nice make doc -j7 CPU_COUNT=7 To ssh://joe@git.sv.gnu.org/srv/git/lilypond.git 79e98a7..4726764 test-staging -> master Success: pushed to master |
Note: In the case where any of the lilypond-patchy-staging.py
tests fail, do not try to push your own fixes but report the failures to
the Developers List <lilypond-devel@gnu.org> for advice.
| [ << Administrative policies ] | [Top][Contents][Index][ ? ] | [ LilyPond grammar >> ] | ||
| [ < Configuring Patchy ] | [ Up : Managing Staging and Master branches with Patchy ] | [ Automating Patchy > ] | ||