1. 03 Dec, 2018 1 commit
    • Pekka Paalanen's avatar
      CI: build customized Debian docker image · 3b590cf9
      Pekka Paalanen authored
      Build a custom image that contains everything installed as part
      of each CI run in the before_script.
      
      The Dockerfile contains instructions on how to submit changes to the
      image in upstream without causing temporary CI failures.
      
      The image needs to be identified per build, because it pulls things from
      internet that will change over time. That means that an image built from
      the same Weston commit may be different if built again. Hence the
      unique image tag contains also the build id.
      
      To avoid cluttering forks with unnecessary images, the automatic image
      build will happen only on a master branch in the upstream repository and
      only if Dockerfile is changed. Contributors can trigger an image build
      in their own branches by launching a pipeline from the Web UI with
      FORCE_DOCKER variable.
      Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <pq@iki.fi>
      3b590cf9
  2. 20 Nov, 2018 5 commits
  3. 15 Nov, 2018 1 commit
    • Dima Ryazanov's avatar
      Don't look for weston.ini in the current working directory · ad0d83bd
      Dima Ryazanov authored
      It's a bit surprising that Weston looks different when launched from the root
      of the git repo vs from elsewhere.
      
      But it's also technically a security vulnerability: if I launch it from
      a directory like /tmp, it might pick up a weston.ini created by another user,
      which could then load modules with arbitrary code. Basically, it's the same
      problem as including "." in $PATH.
      Signed-off-by: Dima Ryazanov's avatarDima Ryazanov <dima@gmail.com>
      ad0d83bd
  4. 05 Nov, 2018 4 commits
  5. 03 Nov, 2018 1 commit
  6. 02 Nov, 2018 8 commits
  7. 30 Oct, 2018 6 commits
  8. 18 Oct, 2018 2 commits
  9. 12 Oct, 2018 1 commit
  10. 23 Sep, 2018 5 commits
  11. 18 Sep, 2018 6 commits