bitbucket-pipelines.yml
author Edouard Tisserant <edouard.tisserant@gmail.com>
Fri, 16 Feb 2018 18:38:30 +0100
changeset 1941 cde74a39df51
parent 1880 e5ddbaf756cb
child 2295 dda34e671700
permissions -rw-r--r--
Fixed Exception dialog disapearing after a view second when exception occurs during app startup.
Problem was caused by splashscreen timeout, wx closing averything else if there is no more main frame.
Changes:
- no more timeout for splashscreen
- use wx.App OnInit method to give first operation to mainloop, object are then now created in mainloop
- main loop is then created _before_ showing splash screen
- no more wxyield or wx processevent tricks needed to display splash screen
- exception handler not blocking anymore on dialog (callafter)
- because of mainloop being there before everything, exit must be called explicitely if exception caught during startup -> exit parameter in handle_exception + try/except around startup calls

UNTESTED ON WINDOWS
image: skvorl/beremiz-requirements

pipelines:
  custom: # Pipelines that are triggered manually
    checks: # The name that is displayed in the list in the Bitbucket Cloud GUI
        - step:
            script: # Modify the commands below to build your repository.
              - ln -s /CanFestival-3 $BITBUCKET_CLONE_DIR/../CanFestival-3
              - /usr/bin/python --version
              - ./tests/tools/check_source.sh
              - ./tests/tools/run_python_tests.sh


  default:
    - step:
        script: # Modify the commands below to build your repository.
          - ln -s /CanFestival-3 $BITBUCKET_CLONE_DIR/../CanFestival-3
          - /usr/bin/python --version
          - ./tests/tools/check_source.sh
          - ./tests/tools/run_python_tests.sh