Hey, First of all, I'm really happy with and thankful for gitlab and how you guys open sourced it. Having said that, I have some problems understand gitlab CI.
More specifically about why does the .gitlab-ci.yml file has to be versioned. There are a couple of problems I can think because of this: 1) Suppose you have a repo which has two forks. Since you want to avoid having git conflicts with the ci file, you need to have the exact same file accross these repos. But suppose you want to run a different job for each repo. The only way of doing this I thought of is having all of the jobs in the same .gitlab-ci.yml file, and just disabling the runner that run the jobs I don't want to run in X repo. So, maybe that could be done if you could specifiy the repo owner in the `only` keyword like `repo:branch`, but you would still jobs have jobs in the yml file that other repositories don't care about in a single file. 2) Suppose I have this really old commit that I want to run a job. This commit was done way before the .gitlab-ci.yml was added to the project. So, I don't have any CI build now because it's in an newer commit. So why wouldn't the CI yml file be configured as a project setting. Configuring it as a project setting is the right way, IMHO. I hope I don't come as disrespectful because it sure took time do add the CI. I really like gitlab, and I would like to help if someone showed me how. Cheers. -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/aff98f75-8647-4788-a1ea-de401abb503b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
