1. 09 Dec, 2019 1 commit
  2. 04 Nov, 2019 1 commit
  3. 01 Nov, 2019 1 commit
  4. 28 Oct, 2019 6 commits
  5. 21 Oct, 2019 2 commits
    • Allison Browne's avatar
      c77bb71c
    • Fabio Pitino's avatar
      Expose arbitrary artifacts via MR widget · 5c168885
      Fabio Pitino authored
      * Allow user to specify `artifacts:expose_as` in CI config
      * Save :has_exposed_artifacts in job metadata for queries
      * Find exposed artifacts in build metadata model
      * Expose API endpoint for frontend to fetch data
      
      Fix unlrelated controller specs
      
      Use default has_exposed_artifacts NULL
      
      Avoid using a background migration to change NULL
      to false. It's not needed.
      
      Feedback from review
      
      * add links to issue for follow up refactoring
      * preload job artifacts and metadata associations
      * merge DisallowedRegexInArrayValidator into existing
      ArrayOfStringsValidator
      * other minor changes
      
      Rename params to match frontend code
      
      Feedback from review
      
      Feedback from review
      5c168885
  6. 15 Oct, 2019 3 commits
  7. 20 Aug, 2019 2 commits
    • drew's avatar
      Introducing new Syntax for Ci::Build inclusion rules · ac77bb93
      drew authored
      - Added Gitlab::Ci::Config::Entry::Rules and Gitlab::Ci::Config::Entry::Rules:Rule
        to handle lists of Rule objects to be evalauted for job inclusion
      - Added `if:` and `changes:` as available Rules::Rule::Clause classes
      - Added Rules handling logic to Seed::Build#included? with extra specs
      - Use DisallowedKeysValidator to mutually exclude rules: from only:/except: on job config
      ac77bb93
    • drew's avatar
      Introducing new Syntax for Ci::Build inclusion rules · ac449a8c
      drew authored
      - Added Gitlab::Ci::Config::Entry::Rules and Gitlab::Ci::Config::Entry::Rules:Rule
        to handle lists of Rule objects to be evalauted for job inclusion
      - Added `if:` and `changes:` as available Rules::Rule::Clause classes
      - Added Rules handling logic to Seed::Build#included? with extra specs
      - Use DisallowedKeysValidator to mutually exclude rules: from only:/except: on job config
      ac449a8c
  8. 13 Aug, 2019 1 commit
  9. 18 Jun, 2019 2 commits
    • Kamil Trzciński's avatar
      Introduce default: for gitlab-ci.yml · a014e204
      Kamil Trzciński authored and Grzegorz Bizon's avatar Grzegorz Bizon committed
      This moves all existing `image/services/before_script/variables`
      into `default:`. This allows us to easily add a default and
      top-level entries. `default`: is keep backward compatible: to
      be considered to be job if `default:script:` is specified. This
      behavior should be removed.
      
      All existing `image/services/before_script/variables` are properly
      handled in root context.
      a014e204
    • Kamil Trzciński's avatar
      Introduce default: for gitlab-ci.yml · 505d71ec
      Kamil Trzciński authored and Grzegorz Bizon's avatar Grzegorz Bizon committed
      This moves all existing `image/services/before_script/variables`
      into `default:`. This allows us to easily add a default and
      top-level entries. `default`: is keep backward compatible: to
      be considered to be job if `default:script:` is specified. This
      behavior should be removed.
      
      All existing `image/services/before_script/variables` are properly
      handled in root context.
      505d71ec
  10. 20 May, 2019 1 commit
  11. 05 Apr, 2019 1 commit
    • Paul 🐻's avatar
      fix(gitlab-ci-config): allow strings in the 'include' keyword · 9f36097d
      Paul 🐻 authored and Grzegorz Bizon's avatar Grzegorz Bizon committed
      This fix is a followup to !24098 which introduced a validation of the
      `include:` keyword of a gitlab-ci configuration file when triggered
      from /ci/lint API calls.
      
      However, there was a test case missing: the case of a single string as
      value. I have added a test case for that which shows that the code was
      not validating it correctly.
      
      This commit fixes that to allow all `include:` valid inputs.
      9f36097d
  12. 04 Apr, 2019 2 commits
  13. 03 Apr, 2019 2 commits
  14. 15 Mar, 2019 1 commit
  15. 15 Jan, 2019 2 commits
  16. 14 Jan, 2019 2 commits
  17. 10 Jan, 2019 1 commit
  18. 29 Nov, 2018 1 commit