this change adds support for parallel gcp builds for the following windows build configurations: - win32 - opt - debug - pgo - win64 - opt - debug - pgo gcp builds are triggered with a treeherder tier 3 flag so that they are only displayed in the treeherder ui when the user has a tier 3 flag set. gcp builds use a th build symbol of "Bg" to make them easy to differentiate from ec2 builds in the treeherder ui. gcp builds use a perfherder "gcp" flag to make them easier to differentiate from ec2 builds in the perfherder ui.
Bug 1536555 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
this change adds support for parallel gcp builds for the following windows build configurations: - win32 - opt - debug - pgo - win64 - opt - debug - pgo gcp builds are triggered with a treeherder tier 3 flag so that they are only displayed in the treeherder ui when the user has a tier 3 flag set. gcp builds use a th build symbol of "Bg" to make them easy to differentiate from ec2 builds in the treeherder ui. gcp builds use a perfherder "gcp" flag to make them easier to differentiate from ec2 builds in the perfherder ui.
this change adds support for parallel gcp builds for the following windows build configurations: - win32 - opt - debug - pgo - win64 - opt - debug - pgo gcp builds are triggered with a treeherder tier 3 flag so that they are only displayed in the treeherder ui when the user has a tier 3 flag set. gcp builds use a th build symbol of "Bg" to make them easy to differentiate from ec2 builds in the treeherder ui. gcp builds use a perfherder "gcp" flag to make them easier to differentiate from ec2 builds in the perfherder ui.
this change adds support for parallel gcp builds for the following windows build configurations: - win32 - opt - debug - pgo - win64 - opt - debug - pgo notes: - gcp builds are triggered with a treeherder tier 3 flag so that they are only displayed in the treeherder ui when the user has a tier 3 flag set. - gcp builds use a th build symbol of "Bg" to make them easy to differentiate from ec2 builds in the treeherder ui. - gcp builds use a perfherder "gcp" flag to make them easier to differentiate from ec2 builds in the perfherder ui.
this change adds support for parallel gcp builds for the following windows build configurations: - win32 - opt - debug - pgo - win64 - opt - debug - pgo notes: - gcp builds are triggered with a treeherder tier 3 flag so that they are only displayed in the treeherder ui when the user has a tier 3 flag set. - gcp builds use a th build symbol of "Bg" to make them easy to differentiate from ec2 builds in the treeherder ui. - gcp builds use a perfherder "gcp" flag to make them easier to differentiate from ec2 builds in the perfherder ui.
this change adds support for parallel gcp builds for the following windows build configurations: - win32 - opt - debug - ~~pgo~~ - shippable - win64 - opt - debug - ~~pgo~~ - shippable notes: - gcp builds are triggered with a treeherder tier 3 flag so that they are only displayed in the treeherder ui when the user has a tier 3 flag set. - gcp builds use a th build symbol of "Bg" to make them easy to differentiate from ec2 builds in the treeherder ui. - gcp builds use a perfherder "gcp" flag to make them easier to differentiate from ec2 builds in the perfherder ui.