Skip to content
Snippets Groups Projects
  1. Mar 20, 2020
  2. Mar 13, 2020
  3. Mar 12, 2020
  4. Mar 03, 2020
  5. Mar 02, 2020
  6. Feb 25, 2020
  7. Feb 06, 2020
  8. Jan 30, 2020
  9. Jan 24, 2020
  10. Dec 10, 2019
  11. Dec 09, 2019
  12. Dec 05, 2019
  13. Oct 17, 2019
  14. Oct 15, 2019
  15. Oct 08, 2019
  16. Oct 03, 2019
  17. Oct 02, 2019
  18. Sep 27, 2019
  19. Sep 18, 2019
  20. Aug 30, 2019
  21. Aug 05, 2019
  22. Jul 29, 2019
  23. Jul 17, 2019
  24. Jul 15, 2019
  25. Jun 19, 2019
  26. Jun 06, 2019
    • Krasimir Angelov's avatar
      Add project level git depth setting · ad9ae16d
      Krasimir Angelov authored and Fabio Pitino's avatar Fabio Pitino committed
      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
  27. Apr 08, 2019
  28. Feb 25, 2019
  29. Feb 24, 2019
  30. Feb 12, 2019
  31. Jan 21, 2019
  32. Jan 18, 2019
  33. Jan 08, 2019
  34. Sep 07, 2018
  35. Apr 08, 2018
  36. Mar 29, 2018
  37. Mar 28, 2018
  38. Dec 13, 2017
  39. Nov 20, 2017
Loading