Skip to content

Ignore keep_latest_artifact parameter for project creation endpoint

Jerry Seto requested to merge 393502-creating-a-project-with-ci_default_git_depth-within-group-causes-500-when-enabling-group-1 into master

What does this MR do and why?

Similar to !123959 (merged) except with the keep_latest_artifact parameter

How to set up and validate locally

  1. Try creating a project through the API (Something like curl -XPOST 'http://gdk.test:3000/api/v4/projects' --header "PRIVATE-TOKEN: token" --header "Content-Type: application/json" --data '{"name": "test-settings", "namespace_id": 1, "keep_latest_artifact": false}') and see that the project is created and the keep_latest_artifact parameter is ignored
  2. Try to change ci/cd settings for the project (Settings -> CI/CD) that exist on the ci_cd_setting association. For example Keep artifacts from most recent successful jobs or Git shallow clone. There should be no unexpected errors here.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #393502 (closed)

Merge request reports