|
|
|
This basically hit us now pretty hard. We really would like to have such option.
We got some test artifacts checked in which consume around a GB of disk space per configuration and are reachable in just one branch within the last 100 commits. When we're able to just have --branch=master this would ease our current situation a lot. I would say that lies in the responsibility of the user to only use the defined config for a specific branch. And I also think as an advanced option with appropriate description this should not be a problem for other users. For us it would ease the situation a lot in regard to disk space as you can see in the table above.
QB has to retrieve all branches to calculate changes reliably (previous build might on a different branch). Also adding this specific option is quite confusing considering all other existing options in git repository definition.
|
QB-3329