beremiz: bitbucket-pipelines.yml@1fdc32be71b8

author	Edouard Tisserant
	Thu, 19 Apr 2018 12:22:40 +0200
changeset 1994	1fdc32be71b8
parent 1880	e5ddbaf756cb
child 2295	dda34e671700
permissions	-rw-r--r--

Rework of runtime non-real-time threading, and shared object dynamic loading :
- All exposed operations on PLCObject are now serialized through main thread
(@RunInMain). Only one exception : python trace thread calling _GetDebugData
- Re-loading of same shared object is prevented. dlclose/delte/rewrite/dlopen
don't happen in that case. This is a workaround for some xenomai copperplate
bug triggering segfault, inbetween delete and rewrite.
- Trace thread now waits for data, dies if no data, and dies instead of
suspending as before when no data consumed after 3 seconds.
- Disabled threading in Pyro client
- Enforced auxiliary threads starting sequence : Pyro -> [UI] ->
PLCWorker.RunLoop

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