Search Feedback

29
votes

Wild Cards for branches

Cloud Build

-

-

If you are using Git with Git Flow, you usually use branches in this way:
- having a develop branch which should contain stable versions of the project
- having feature branches branched from develop (or a release branch) and merged back to it when finished. They are usually located at "feature/"
- having a master branch containing released versions of the product
- having release candidate branches which are branched from develop and are merged back to develop as well as to master at a certain point. Usually located at "release/"

For the release branches you usually want to setup a build agent. Since unity projects rarely need to maintain older versions, only one build agent is required for all the release branches.

It is possible right now but you have to go into the build agent settings and change the branch whenever you branch a new release.

Feature request:
Support wild cards which are checking for changes in branches containing a certain string rather then specify the exact branch.

For the example with the release branches a wild card would look like this:
"release/*"

Your opinion counts

Help us make things better. Share your great idea for improving Unity or vote for other people’s.

Log in to post a new idea

Categories

All

(10750)

2D

(281)

Ads

(54)

AI & Navigation

(81)

Analytics

(130)

Animation

(395)

Asset Store

(355)

Asset Store Publisher

(15)

Assets

(543)

Audio

(184)

Cloud Build

(144)

Collaborate

(63)

Docs & Tutorials

(239)

Editor

(2507)

Everyplay

(17)

Game Performance Reporting

(21)

General

(978)

Graphics

(869)

GUI

(430)

Input

(172)

Licensing

(90)

Networking

(188)

Physics

(383)

Platforms

(440)

Profiling & Optimization

(84)

Runtime

(181)

Scripting

(1168)

Terrain

(170)

WebGL

(142)