1. 18 Jan, 2019 1 commit
  2. 15 Jan, 2019 2 commits
  3. 14 Jan, 2019 3 commits
  4. 09 Jan, 2019 1 commit
    • Tristan Van Berkom's avatar
      Support running test environments in parallel with `detox` · f29a0995
      Tristan Van Berkom authored
      This patch namespaces the test temp directory and the output
      coverage report file with the name of the environment under test,
      such that separately run tests do not access the same files.
      
      When running tests without tox, directly through setup.py,
      then the tmp directory will still be `./tmp`.
      
        * .gitignore: Added new .coverage-reports/ directory
      
        * .gitlab-ci.yml: Rely on tox to combine and report coverage, only
          tell tox about the COVERAGE_PREFIX so that results can be namespaced
          by CI job name.
      
          This change also publishes the sources and final combined `.coverage`
          file in an output gitlab artifact for inspection, and lists some missing
          dependencies to the `coverage` job.
      
        * tox.ini: Add comments and refactor main [testenv] section so that
          other environments dont inherit too much unrelated cruft.
      
          Generate the coverate reports in the respective {envtmpdir} so that
          all per-process coverage files are prefixed with a full path, ensuring
          that concurrent runs don't mix reports and addressing concerns
          raised in #844.
      
          Also implemented new `tox -e coverage` environment to combine
          any found coverage and print a report.
      
        * .coveragerc: Omit .tox/ directory from coverage stats
      
      Fixes issue #844
      f29a0995
  5. 04 Jan, 2019 2 commits
    • Chandan Singh's avatar
      .gitlab-ci.yml: Remove prepare stage · f42dcb54
      Chandan Singh authored
      As we now run tests using `tox`, we don't need to worry about manually
      packing and unpacking BuildStream. So, we can remove the preapre stage
      entirely.
      
      Update `coverage` and nightly jobs to appropriately cope with this
      change. Both these jobs now install all runtime dependencies from
      requirements files.
      f42dcb54
    • Chandan Singh's avatar
      Rename "tools" directory to "requirements" · ebd965fe
      Chandan Singh authored
      This seems like a better name for the directory, as it more closely
      describes the purpose of its contents.
      ebd965fe
  6. 03 Jan, 2019 3 commits
  7. 02 Jan, 2019 1 commit
  8. 29 Nov, 2018 1 commit
  9. 22 Nov, 2018 1 commit
  10. 20 Nov, 2018 7 commits
  11. 14 Nov, 2018 2 commits
  12. 05 Nov, 2018 1 commit
  13. 25 Oct, 2018 2 commits
  14. 02 Oct, 2018 1 commit
    • Phillip Smyth's avatar
      Forcing CI to install Sphinx 1.7.9 · d5b396e0
      Phillip Smyth authored
      .gitlab-ci.yml: forced pip3 install Sphinx 1.7.9
      The theme we use in our docs "sphinx_rtd_theme"
      Does not support the latest version of Sphinx (>1.8)
      This results in search functionality failing
      d5b396e0
  15. 01 Oct, 2018 2 commits
  16. 26 Sep, 2018 3 commits
  17. 25 Sep, 2018 1 commit
  18. 29 Aug, 2018 1 commit
  19. 27 Aug, 2018 2 commits
  20. 26 Aug, 2018 1 commit
  21. 24 Aug, 2018 1 commit
    • Chandan Singh's avatar
      .gitlab-ci.yml: Verify that source tarball installs correctly · 56096b60
      Chandan Singh authored
      Add a check to verify that the source distribution tarball that we
      generate installs corrctly. It is useful to do this check as this is the
      same tarball will be used when installing BuildStream via PyPI.
      
      This check also happens indirectly in the coverage job where we install
      BuildStream but this check makes it more explicit and will also cause
      the CI to fail early if the tarball is not correct.
      56096b60
  22. 23 Aug, 2018 1 commit