Enabling CI by default problems when using other CI services
Somewhat related to gitlab-org/gitlab-ce!1827
We enable GitLab CI by default on new projects now. If a user then configures an external CI service such as Jenkins/TeamCity it leads to a bad experience. When the user does not notice that GitLab CI is already enabled all merge requests will show the build as being skipped because no .gitlab-ci.yml
file exists. Users don't expect this, they expect to see their other CI service build status.
I recall something where we were going to enable GitLab CI automatically if we see a .gitlab-ci.yml
file in the repository. Are we still planning that? If we had this feature and didn't enable GitLab CI right at creation, this would resolve the experience. Otherwise users must remember to intentionally disable GitLab CI when using any external CI service.