[jboss-jira] [JBoss JIRA] (SWSQE-499) Configure automation jobs to start using clusters from pool

[Filip Brychta (Jira)]

     [ https://issues.jboss.org/browse/SWSQE-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Filip Brychta resolved SWSQE-499.
---------------------------------
    Resolution: Done


I updated the main pipeline configuration following way:
- can be triggered concurrently
- when OS_HOSTNAME parameter is empty, it will pick one free cluster from automation pool (b06, b12 clusters) and run there. It automatically blocks/releases the lock on the picked cluster.
- when OS_HOSTNAME parameter is not empty, it will run on specified cluster, but it will not BLOCK the cluster!!!. IMPORTANT: do not use clusters from automation pool to invoke this job manually because it will not block it so it's open for conflicts

Currently all jobs which are triggered automatically (kiali-core-pr-e2e-test, kiali-ui-pr-UI-test, python-ui-test-pr and Istio-and-Kiali-on-Openshift which is scheduled nightly) have empty OS_HOSTNAME parameter so they will run in automation pool.

> Configure automation jobs to start using clusters from pool
> -----------------------------------------------------------
>
>                 Key: SWSQE-499
>                 URL: https://issues.jboss.org/browse/SWSQE-499
>             Project: Kiali QE
>          Issue Type: Sub-task
>            Reporter: Filip Brychta
>            Assignee: Filip Brychta
>            Priority: Major
>
> We can use https://jenkins.io/doc/pipeline/steps/lockable-resources/ plugin to define cluster of OS clusters and then configure jobs to pick and lock free one.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)