1. 07 May, 2018 1 commit
  2. 25 Apr, 2018 4 commits
  3. 16 Apr, 2018 2 commits
  4. 13 Apr, 2018 1 commit
  5. 12 Apr, 2018 4 commits
  6. 28 Mar, 2018 1 commit
  7. 22 Mar, 2018 1 commit
  8. 21 Mar, 2018 1 commit
  9. 20 Mar, 2018 1 commit
  10. 19 Mar, 2018 2 commits
  11. 16 Mar, 2018 1 commit
  12. 14 Mar, 2018 1 commit
  13. 28 Feb, 2018 1 commit
  14. 13 Feb, 2018 1 commit
  15. 12 Feb, 2018 1 commit
  16. 07 Feb, 2018 1 commit
  17. 05 Feb, 2018 1 commit
  18. 02 Jan, 2018 1 commit
  19. 22 Dec, 2017 1 commit
  20. 21 Dec, 2017 1 commit
  21. 28 Nov, 2017 1 commit
    • Tristan Van Berkom's avatar
      .gitlab-ci.yml: Use source distribution tarballs in all tests · 3934ce81
      Tristan Van Berkom authored
      This commit adds an initial stage to the pipeline to build a distribution
      tarball and generate some helper scripts for later CI to use to unpack it
      and install it.
      
      Then, it makes sure that all pytest and integration test runs work from
      the dist tarball instead of directly from the git repo, also the docs are
      built from the dist tarball.
      
      This ensures that everything continues to work with a dist tarball at all times.
      3934ce81
  22. 27 Nov, 2017 1 commit
    • Sam Thursfield's avatar
      .gitlab-ci.yml: Use specific version of buildstream-fedora Docker image · 5c37208c
      Sam Thursfield authored
      The image is rebuilt nightly which means it could change under our
      feet and cause confusing breakages. The reason for these nightly
      rebuilds is so that the `bst-here` script offers a reasonably fresh
      version of BuildStream to users. But it also means that dependencies
      could change in broken ways.
      
      You can see the list of tags here, ordered by newness:
      https://hub.docker.com/r/buildstream/buildstream-fedora/tags/
      
      The number in one of these tag names is the "version" of the image
      (which is really the number of commits in the buildstream-docker-images
      repo), while the hex string identifies the commit of BuildStream that
      the image contains.
      
      When changing the Docker image (to add new dependencies, or whatever)
      you will need to wait until the new tag is pushed, then modify
      .gitlab-ci.yml so that it pulls the new tag.
      5c37208c
  23. 20 Oct, 2017 2 commits
  24. 18 Oct, 2017 2 commits
  25. 14 Oct, 2017 1 commit
  26. 10 Oct, 2017 1 commit
    • Sam Thursfield's avatar
      .gitlab-ci.yml: Follow latest BuildStream Docker image · 7704f581
      Sam Thursfield authored
      This allows us to remove env vars that are now set in the image,
      and some packages which are already installed in the image.
      
      I've left Sphinx (which is needed for the documentation task) out of the
      image as it pulls in a bunch of Python 2 dependencies that would bloat
      the image. Although note that Python 2 is already present in the image
      because Bazaar depends on it.
      7704f581
  27. 02 Oct, 2017 1 commit
  28. 28 Sep, 2017 2 commits
  29. 09 Sep, 2017 1 commit