An error occurred fetching the project authors.
  1. 22 Mar, 2021 1 commit
  2. 17 Feb, 2021 1 commit
  3. 02 Feb, 2021 1 commit
  4. 27 Jan, 2021 1 commit
  5. 17 Nov, 2020 1 commit
  6. 30 Oct, 2020 1 commit
  7. 16 Oct, 2020 1 commit
    • Amy Troschinetz's avatar
      Support ci_forward_deployment_enabled in edit API · ae6a055d
      Amy Troschinetz authored
      **app/controllers/projects/settings/ci_cd_controller.rb:**
      
      Supports `:forward_deployment_enabled` as part of the nested
      `ci_cd_settings_attributes` property.
      
      **app/models/project.rb:**
      **app/models/deployment.rb:**
      **app/views/projects/settings/ci_cd/_form.html.haml:**
      
      Use a `ci` prefix for the `forward_deployment_enabled` delegate so that
      it is more in-line with the existing conventions.
      
      **doc/api/groups.md:**
      **doc/api/projects.md:**
      
      Document support for `forward_deployment_enabled`.
      
      **lib/api/entities/project.rb:**
      **lib/api/helpers/projects_helpers.rb:**
      
      Add API support for `forward_deployment_enabled`.
      
      **spec/controllers/projects/settings/ci_cd_controller_spec.rb:**
      **spec/features/projects/settings/pipelines_settings_spec.rb:**
      **spec/requests/api/projects_spec.rb:**
      
      Test support for `forward_deployment_enabled`.
      
      **changelogs/unreleased/forward_deployment_enabled-api.yml:**
      
      Changelog entry.
      ae6a055d
  8. 11 Sep, 2020 1 commit
  9. 07 Sep, 2020 1 commit
  10. 29 Jul, 2020 1 commit
  11. 24 Jun, 2020 1 commit
  12. 21 May, 2020 1 commit
    • Jose Vargas's avatar
      Remove prepend-top-0 css rule · 20962b73
      Jose Vargas authored
      This removes the prepend-top-0 rule and
      replaces usage accross GitLab with GitLab-UI
      gl-mt-0 utility class instead
      20962b73
  13. 07 May, 2020 1 commit
    • Zeff Morgan's avatar
      Add basic test for code coverage stats · 09470f6b
      Zeff Morgan authored
      Add simplecov regex to code coverage field in project level CI/CD
      general pipeline settings.
      
      Add qa data selectors to the general pipelines section and to the
      coverage regex field in the form so they can be validated, used
      for selection, and modified.
      
      Create new page object for general pipelines settings and initialize in
      QA module. Verify required elements and add method for modifying
      coverage regex.
      
      Modify ci_cd page object to validate general pipelines element and
      add method to expand the section.
      09470f6b
  14. 20 Mar, 2020 1 commit
  15. 13 Mar, 2020 1 commit
    • briankabiro's avatar
      Doc: Move the settings and index docs to CI folder · 207d9c98
      briankabiro authored
      The pipelines docs are under `user/project` but should be
      with the rest of the CI docs under `/ci`
      
      This change updates the location of `settings.md` and the
      `pipelines.md`
      
      * move `/user/project/settings.md` to `ci/pipelines` folder
      
      * update references to `settings.md` to point to the new location
      
      * move images to the new location and delete the old directory
      
      * move `pipelines.md` to `index.md` in the new ci/pipelines folder
      207d9c98
  16. 03 Mar, 2020 2 commits
  17. 22 Nov, 2019 1 commit
  18. 21 Oct, 2019 2 commits
  19. 17 Oct, 2019 1 commit
  20. 14 Oct, 2019 2 commits
  21. 28 Aug, 2019 2 commits
  22. 22 Jul, 2019 1 commit
  23. 06 Jun, 2019 1 commit
    • Krasimir Angelov's avatar
      Add project level git depth setting · ad9ae16d
      Krasimir Angelov authored
      Introduce default_git_depth in project's CI/CD settings and set it to
      50. Use it if there is no GIT_DEPTH variable specified. Apply this
      default only to newly created projects and keep it nil for old ones
      in order to not break pipelines that rely on non-shallow clones.
      
      default_git_depth can be updated from CI/CD Settings in the UI, must be
      either nil or integer between 0 and 1000 (incl).
      
      Inherit default_git_depth from the origin project when forking projects.
      
      MR pipelines are run on a MR ref (refs/merge-requests/:iid/merge) and it
      contains unique commit (i.e. merge commit) which doesn't exist in the
      other branch/tags refs. We need to add it cause otherwise it may break
      pipelines for old projects that have already enabled Pipelines for merge
      results and have git depth 0.
      
      Document new default_git_depth project CI/CD setting
      ad9ae16d
  24. 28 Mar, 2019 2 commits
  25. 31 Jan, 2019 1 commit
  26. 05 Dec, 2018 1 commit
  27. 06 Nov, 2018 1 commit
    • Fabian Peter Hammerle's avatar
      CI/CD coverage docs: fix pytest-cov regex · 5b8bb3c8
      Fabian Peter Hammerle authored
      adapted regular expression to correctly parse total coverage when using pytest-cov
      
      > ----------- coverage: platform linux, python 3.6.6-final-0 -----------
      > Name                      Stmts   Miss  Cover
      > ---------------------------------------------
      > integrade/__init__.py         0      0   100%
      > integrade/api.py             86      0   100%
      > integrade/config.py          36      1    97%
      > integrade/exceptions.py       3      0   100%
      > integrade/utils.py           11      0   100%
      > tests/test_api.py           153      0   100%
      > tests/test_config.py         46      0   100%
      > tests/test_integrade.py       6      0   100%
      > tests/test_utils.py          12      0   100%
      > ---------------------------------------------
      > TOTAL                       353      1    99%
      
      issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/48613
      5b8bb3c8
  28. 04 Oct, 2018 2 commits
    • Tomasz Maczukin's avatar
      Simplify runner registration token resetting · 0a460523
      Tomasz Maczukin authored
      This icommit adds several changes related to the same topic
      - resetting a Runner registration token:
      
      1. On Project settings page it adds a button for resetting the
         registration token and it removes the Runner token field
         that was confusing all GitLab users.
      
      2. On Group settings page it adds the same button for resetting
         the registration token.
      
      3. On Admin Runners settings page it moves the button to the same
         place as in Project and Group settings and it changes slightly
         the page layout to make it more similar to Group and Project
         setting pages.
      
      4. It refactorizes a little the partial that prints runner
         registration description. Thanks to this Project, Group
         and Admin settings of the Runner are re-using the same
         code to generate the button.
      
      5. Updates the translations of changed text.
      0a460523
    • Tomasz Maczukin's avatar
      Simplify runner registration token resetting · 42af2295
      Tomasz Maczukin authored
      This icommit adds several changes related to the same topic
      - resetting a Runner registration token:
      
      1. On Project settings page it adds a button for resetting the
         registration token and it removes the Runner token field
         that was confusing all GitLab users.
      
      2. On Group settings page it adds the same button for resetting
         the registration token.
      
      3. On Admin Runners settings page it moves the button to the same
         place as in Project and Group settings and it changes slightly
         the page layout to make it more similar to Group and Project
         setting pages.
      
      4. It refactorizes a little the partial that prints runner
         registration description. Thanks to this Project, Group
         and Admin settings of the Runner are re-using the same
         code to generate the button.
      
      5. Updates the translations of changed text.
      42af2295
  29. 19 Sep, 2018 2 commits
  30. 16 Aug, 2018 1 commit
  31. 07 Aug, 2018 1 commit
  32. 20 Jul, 2018 1 commit
  33. 19 Jul, 2018 1 commit