An error occurred fetching the project authors.
  1. 21 Oct, 2019 1 commit
  2. 18 Oct, 2019 2 commits
  3. 17 Oct, 2019 1 commit
  4. 16 Oct, 2019 2 commits
  5. 15 Oct, 2019 1 commit
  6. 10 Oct, 2019 1 commit
  7. 27 Sep, 2019 1 commit
  8. 13 Sep, 2019 1 commit
  9. 22 Aug, 2019 1 commit
  10. 08 Aug, 2019 1 commit
  11. 02 Aug, 2019 3 commits
  12. 01 Aug, 2019 1 commit
    • Kamil Trzciński's avatar
      Add support for DAG · e7ee84aa
      Kamil Trzciński authored
      This implements the support for `needs:` keyword
      as part of GitLab CI. That makes some of the jobs
      to be run out of order.
      e7ee84aa
  13. 29 Jul, 2019 1 commit
  14. 23 Jul, 2019 1 commit
  15. 10 Jul, 2019 1 commit
  16. 05 Jun, 2019 1 commit
  17. 31 May, 2019 1 commit
    • Shinya Maeda's avatar
      Remove legacy artifact related code · 387a4f4b
      Shinya Maeda authored
      We've already migrated all the legacy artifacts to the new realm,
      which is ci_job_artifacts table.
      It's time to remove the old code base that is no longer used.
      387a4f4b
  18. 28 May, 2019 1 commit
  19. 24 May, 2019 1 commit
  20. 17 May, 2019 1 commit
  21. 06 May, 2019 1 commit
  22. 29 Apr, 2019 1 commit
    • Shinya Maeda's avatar
      Fix CI_COMMIT_REF_NAME and SLUG variable · ed3a2fc8
      Shinya Maeda authored
      With Pipelines for Merge Requests feature, users cannout keep using
      $CI_COMMIT_REF_NAME and _SLUG predefined variables for dynamic
      environments. We fix this problem by explicitly looking at the source
      ref.
      ed3a2fc8
  23. 26 Apr, 2019 1 commit
  24. 19 Apr, 2019 2 commits
  25. 18 Apr, 2019 1 commit
  26. 16 Apr, 2019 1 commit
  27. 10 Apr, 2019 2 commits
  28. 05 Apr, 2019 2 commits
  29. 04 Apr, 2019 1 commit
    • Shinya Maeda's avatar
      Drop legacy artifacts usage · 8e51439e
      Shinya Maeda authored
      Legacy artifacts have been correctly migrated to new place -
      ci_job_artifacts. Now it's time to remove the related code, but before
      that we should ensure it doesn't break anything by using feature flag.
      8e51439e
  30. 01 Apr, 2019 1 commit
  31. 29 Mar, 2019 1 commit
  32. 20 Mar, 2019 2 commits
    • Tiger's avatar
      Add feature flag for build preparing state · 759dab5b
      Tiger authored
      The flag is on by default, but allows us to revert back
      to the old behaviour if we encounter any problems.
      759dab5b
    • Tiger's avatar
      Create framework for build prerequisites · 00f0d356
      Tiger authored
      Introduces the concept of Prerequisites for a CI build.
      If a build has unmet prerequisites it will go through the
      :preparing state before being made available to a runner.
      
      There are no actual prerequisites yet, so current
      behaviour is unchanged.
      00f0d356