131:be85d5073342
Anton Shestakov <av6@dwimlabs.net>, Thu, 11 Aug 2016 18:21:31 +0800
pipelines: make the second run quiet and check that nothing's changed Using exit within current shell (i.e. `{}` instead of `()`) is an experiment.
next change 132:926bee60cea5
previous change 130:aa9bf9c90aac

bitbucket-pipelines.yml

Permissions: -rw-r--r--

File Latest Revisions Annotate Diff Comparison
Other formats:
JSON Raw
Feeds:
Atom RSS 
image: python:2
pipelines:
  default:
    - step:
        script:
          - pip install -r REQUIREMENTS
          - ./test.py
          - pip install ansible
          - ansible --version
          - echo localhost > inventory
          - ansible-playbook provision/playbook.yml
              -i inventory --syntax-check
          - ansible-playbook provision/playbook.yml
              -i inventory --list-tasks
          - apt-get update && apt-get install -y sudo supervisor
          - service supervisor restart
          - ansible-playbook provision/playbook.yml
              -i inventory --connection=local --skip-tags=ufw --verbose
          - pgrep -f 'fruitbar/venv/bin/gunicorn'
          - ansible-playbook provision/playbook.yml
              -i inventory --connection=local --skip-tags=ufw
              | grep -q 'changed=0.*failed=0'
              && { echo 'Idempotence test: pass'; exit 0; }
              || { echo 'Idempotence test: fail'; exit 1; }