1. 25 8月, 2020 1 次提交
  2. 13 8月, 2020 1 次提交
  3. 01 8月, 2020 2 次提交
  4. 15 7月, 2020 1 次提交
  5. 22 6月, 2020 1 次提交
  6. 15 6月, 2020 1 次提交
  7. 03 6月, 2020 1 次提交
  8. 27 5月, 2020 1 次提交
  9. 22 5月, 2020 1 次提交
  10. 21 5月, 2020 1 次提交
  11. 14 5月, 2020 1 次提交
  12. 23 4月, 2020 1 次提交
  13. 03 4月, 2020 1 次提交
  14. 25 3月, 2020 1 次提交
  15. 14 2月, 2020 1 次提交
  16. 30 1月, 2020 1 次提交
  17. 17 1月, 2020 1 次提交
  18. 11 1月, 2020 1 次提交
  19. 24 12月, 2019 1 次提交
  20. 18 12月, 2019 1 次提交
  21. 21 11月, 2019 1 次提交
  22. 01 10月, 2019 1 次提交
  23. 13 9月, 2019 1 次提交
  24. 14 8月, 2019 1 次提交
  25. 03 8月, 2019 2 次提交
  26. 01 8月, 2019 1 次提交
    • K
      Add support for DAG · e7ee84aa
      Kamil Trzciński 提交于
      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
  27. 30 4月, 2019 1 次提交
  28. 29 3月, 2019 1 次提交
  29. 20 3月, 2019 2 次提交
    • T
      Create framework for build prerequisites · 00f0d356
      Tiger 提交于
      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
    • T
      Add :preparing status to HasStatus · 42ca9c6f
      Tiger 提交于
      Introduces a new status for builds between :created and :pending
      that will be used when builds require one or more prerequisite
      actions to be completed before being picked up by a runner
      (such as creating Kubernetes resources before deploying).
      
      The existing :created > :pending transition is unchanged, so
      only builds that require preparation will use the :preparing
      status.
      42ca9c6f
  30. 25 1月, 2019 1 次提交
  31. 16 11月, 2018 1 次提交
    • Y
      Refactor how a few ActiveRecord enums are defined · 590ff80f
      Yorick Peterse 提交于
      In a few models we define ActiveRecord enums that are redefined in EE
      using the following pattern:
      
          enum :some_enum, {
            ...
          }.merge(EE_ENUM_VALUES)
      
      This particular approach is problematic to deal with, because it
      requires that we `prepend` and EE module _before_ defining the enum.
      This typically translates to the `prepend` being the first line in the
      model in EE, but this can easily lead to merge conflicts when developers
      add more `include` and/or `prepend` lines.
      
      As part of https://gitlab.com/gitlab-org/gitlab-ee/issues/8244 and
      https://gitlab.com/gitlab-org/gitlab-ee/issues/8241 we are moving
      `prepend` to the last line in a file, reducing the chances of running
      into merge conflicts. This poses a bit of a problem with the pattern
      above, because this pattern does not allow us to move the `prepend`
      further down a file.
      
      To resolve this problem, we simply move the Hash value of the enum to a
      separate class method. This method is defined in a separate module where
      necessary, allowing us to use it like so:
      
          enum :failure_reasons, ::SomeModelEnums.failure_reasons
      
      The method in turn is defined in a very straightforward manner:
      
          module SomeModelEnums
            def self.failure_reasons
              {
                ...
              }
            end
          end
      
      This makes it easy for EE to add values without requiring the `prepend`
      to be placed before the `enum` is defined.
      
      For more information, see the following issues and merge requests:
      
      * https://gitlab.com/gitlab-org/gitlab-ee/issues/8244
      * https://gitlab.com/gitlab-org/gitlab-ee/issues/8241
      * https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8424
      590ff80f
  32. 05 11月, 2018 1 次提交
  33. 01 11月, 2018 1 次提交
  34. 29 10月, 2018 1 次提交
  35. 26 10月, 2018 1 次提交
  36. 02 10月, 2018 2 次提交