copr-be-dev: allocate powerful EC2 machines in @copr/powerful-test
This commit is contained in:
parent
ffd83e76cd
commit
2448fc14d9
1 changed files with 12 additions and 0 deletions
|
@ -162,3 +162,15 @@ FAS_SIGNUP_URL = "https://accounts.fedoraproject.org"
|
||||||
{% else %}
|
{% else %}
|
||||||
FAS_SIGNUP_URL = "https://accounts.stg.fedoraproject.org"
|
FAS_SIGNUP_URL = "https://accounts.stg.fedoraproject.org"
|
||||||
{% endif %}
|
{% endif %}
|
||||||
|
|
||||||
|
{% if env == 'devel' %}
|
||||||
|
# On stage we only ever start powerful builders in this project. Note that we
|
||||||
|
# also start s390x instances in IBM Cloud on-demand , even without the extra
|
||||||
|
# BuildChroot tags here! The reason is that the `arch_s390x` tag is named in
|
||||||
|
# the `tags_on_demand` section in resalloc's pools.yaml file. But the
|
||||||
|
# difference is that `s390x` can be started by anyone.
|
||||||
|
EXTRA_BUILDCHROOT_TAGS = [{
|
||||||
|
"pattern": "@copr/powerful-test/fedora-rawhide-(x86_64|aarch64)/.*",
|
||||||
|
"tags": ["on_demand_powerful"],
|
||||||
|
}]
|
||||||
|
{% endif %}
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue