[jbosstools-issues] [JBoss JIRA] (JBIDE-26893) Create universal template and label that would accommodate different rhel needed by interop testing team

[Ondrej Dockal (Jira)]

    [ https://issues.redhat.com/browse/JBIDE-26893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976519#comment-13976519 ] 

Ondrej Dockal commented on JBIDE-26893:
---------------------------------------

Labels: rhel7-interop and rhel8-interop
We are listening for Rhel compose messages, though these do not follow UMB factory 2.0, see [1].
Example of the listener [2].

[1]: https://projects.engineering.redhat.com/browse/RCM-67442
[2]: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/cci-config/merge_requests/66

> Create universal template and label that would accommodate different rhel needed by interop testing team
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-26893
>                 URL: https://issues.redhat.com/browse/JBIDE-26893
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: integration-tests, qa
>    Affects Versions: 4.13.0.Final
>            Reporter: Ondrej Dockal
>            Assignee: Ondrej Dockal
>            Priority: Major
>              Labels: jenkins
>             Fix For: 4.14.0.Final
>
>
> We would like to use universal label that would cover different rhel versions that are required by interop testing. The idea is that we will keep one/two label for interop testing slave: rhel-interop (and possibly for both stream, so rhel7-interop and rhel8-interop), which would have used image: rhel-interop-7(8)-snapshot that would have actually needed rhel version to test. During provisioning we will replace snapshot with proper rhel. This way we can keep these two labels and do not need to change interop test job label all the time via PR in cci-config repo.
> Reqs:
> * UMB trigger for interop rhel to run provision job with
> * job will be parametrized based on rhel version given by umb message
> * jenkins provisioning job build description needs to be updated to have available info about rhel version
>  
> Pros:
>  * do not need to change code via PR every time there is new bits to test
>  * probably can be fully automated
> Cons: 
>  * only one version to test at a time
>  * complex and possibly unstable?



--
This message was sent by Atlassian Jira
(v7.13.8#713008)