the first thing it does is placing a azure pipelines inside the repo. So how is it supposed to work?
It’s a good question, you could use the pipeline part separating the “critical” yaml in a different repo of the same project, so it’s part of the devops of the project. Or also you could use the “release” part that is more articulate in some part but more limited in others. Anyway I keep the devops “things” anyway in a different repo with different permissions
I think you're mixing up a file lock (the protection I'm looking for as I mentioned) with the capability to centralize and use template. Did I get it right?
Uhm, not sure about that, I don’t try to lock the file in the app code repo, I keep in a locked place
But if you keep it in a locked place, how azure pipelines is supposed to work? Don't you have a chicken egg?
Locked for the developer team, not for devops
Обсуждают сегодня