Differential D14259
Allow "Repository Automation" to be configured for repositories Authored by epriestley on Oct 12 2015, 10:48 PM. Tags None Referenced Files
Subscribers
Details
Ref T182. This allows you to assign blueprints that a repository can use to perform working copy operations. Eventually, this will support "merge this" in Differential, etc. This is just UI for now, with no material effects. Most of this diff is just taking logic that was in the existing "Blueprints" CustomField and putting it in more general places so Diffusion (which does not use CustomFields) can also access it.
Diff Detail
Event TimelineComment Actions I anticipate this section eventually having more configuration (policies, merge strategies, which branches can be targets?). The phrase "repository automation" isn't a perfect fit for "stuff to make a 'land button' work", but I think it will make more sense after release and deployment hooks become available (roughly, the stuff in T9530) and some of these processes really are more along the lines of automation. I wouldn't mind finding a better term for this, but wasn't able to come up with one. The only problem I really have with it is that it isn't very self-explanatory: when you read it for the first time, you probably can't guess what it means. But the size of the idea seems about right (big enough to accommodate future changes, small enough that it can be explained in one sentence without requiring you to understand Drydock first), and the term doesn't seem confusing or misleading or overloaded to me. |