creating sub-categories for build definitions
Is there a way to creating sub-categories for build definitions, so there doesn't have to be one long list of build def's displayed?
The list ca get pretty cluttered and confusing. A way to categorize them under separate folders/categories in the builds view would allow for ease of use, and clarification on where to look for specific types of required builds
Kind regards,
The list ca get pretty cluttered and confusing. A way to categorize them under separate folders/categories in the builds view would allow for ease of use, and clarification on where to look for specific types of required builds
Kind regards,
3 answers
That capability will be in the 2.0 release.
Is there a way to creating sub-categories for build definitions, so there doesn't have to be one long list of build def's displayed?
The list ca get pretty cluttered and confusing. A way to categorize them under separate folders/categories in the builds view would allow for ease of use, and clarification on where to look for specific types of required builds
Kind regards,
How does one create sub-categories for build definitions in 2.0?
Cheers,
Geoff
topgun wrote:
Cheers,
Geoff
topgun wrote:
That capability will be in the 2.0 release.
tolliemwrote:
Is there a way to creating sub-categories for build definitions, so
there doesn't have to be one long list of build def's displayed?
The list ca get pretty cluttered and confusing. A way to categorize
them under separate folders/categories in the builds view would allow
for ease of use, and clarification on where to look for specific types
of required builds
Kind regards,
There is no way to categorize build definitions in RTC 1.0 or 2.0.
Tollie filed an enhancement request for this:
86093: Ability to create sub-categories for Build Definitions
As a workaround, you can add a prefix to the build definition id, e.g.:
build.foo
deploy.foo
test.foo
Tollie filed an enhancement request for this:
86093: Ability to create sub-categories for Build Definitions
As a workaround, you can add a prefix to the build definition id, e.g.:
build.foo
deploy.foo
test.foo