1. 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.
  2. 27 Nov, 2017 2 commits
    • Valentin David's avatar
      Remove all deleted paths from manifest after integration commands in · 02cc8d03
      Valentin David authored
      compose plugin including paths still reachable through following of
      symbolic links.
      Keeping reachable paths through following of symbolic links in
      manifest. Can lead to ENOENT error when copying the file if target
      directory of a symbolic link is not yet created. The file is anyway
      copied since the real path of the file is also in the manifest.
    • 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:
      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.
  3. 25 Nov, 2017 2 commits
  4. 23 Nov, 2017 2 commits
    • Sam Thursfield's avatar
      Only initialize remote artifact cache connections if needed · f17ef1e4
      Sam Thursfield authored
      This fixes a regression from the canonical-pull-urls branch that was
      just merged. The `OSTreeCache.__init__()` function was connecting to
      the cache, which is bad because execution would randomly freeze for
      several seconds when the connection was slow.
      We now only initialize remote connections where needed; this was
      already introduced in 5c2ef6d0 but
      had regressed. I renamed the keyword arg from `fetch_remote_refs`
      to `use_remote_cache` because it needs to be set for any interaction
      with the remote cache, doesn't matter if they are fetches or pushes.
      The initialization stage is also moved later so that we print a message
      telling the user what we are up to before trying the network access.
    • Tristan Van Berkom's avatar
  5. 22 Nov, 2017 5 commits
  6. 20 Nov, 2017 9 commits
  7. 19 Nov, 2017 1 commit
  8. 18 Nov, 2017 8 commits
  9. 17 Nov, 2017 5 commits
  10. 16 Nov, 2017 1 commit
  11. 14 Nov, 2017 4 commits