README.md

lilypond musical typesetting

why another lilypond image

I needed some more packages to use this image for a gitlab CI runner. It is possible to use this image to build lilypond files from a gitlab repository fully automated.

gitlab CI configuration

.gitlab-ci.yml

image: iskaron/lilypond

stages:
  - build
  - deploy

lilyfy:
  stage: build
  script:
    - mkdir -p /pdfs
    - 'git diff-tree --no-commit-id --name-only -r "$CI_BUILD_REF" | grep ".ly$" | grep -v setup.ly | xargs -I % find "%" -name \*.ly -execdir lilypond "--output=/pdfs/{}" "{}" \;'
  artifacts:
    expire_in: 31d
    paths:
    - pdfs/*.pdf
    - pdfs/*.mid*

deploy:
  dependencies:
    - lilyfy
  stage: deploy
  only:
    - master
  script:
    - eval $(ssh-agent -s)
    - echo "$DEPLOY_KEY" | ssh-add -
    - mkdir -p ~/.ssh
    - echo -e "Host *\n\tStrictHostKeyChecking no\n\n" > ~/.ssh/config'
    - mkdir -p /pdfs
    - scp -r /pdfs/* $SCP_TARGET_PATH

The script will deploy via SSH. The required private key has to be stored in the gitlab CI variable "DEPLOY_KEY", the scp target path in SCP_TARGET_PATH (something like '@:'.

standalone usage

    docker run --rm -v $(pwd):/app -w /app iskaron/lilypond lilypond FILE