[jbosstools-issues] [JBoss JIRA] (JBIDE-26760) Migrate QE integration tests jobs into job DSL under dev-platform/cci-config repo

[Ondrej Dockal (Jira)]

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

Ondrej Dockal updated JBIDE-26760:
----------------------------------
    Description: 
As a part of QE - CI initiative and its out coming best practices, we need to move our QE and Infra jobs into job DSL. New repository that will be used to store jobs as a code ( job DSL) is here [1]. Migrate according to the QE - CI initiative best practices that can be found here:
* [Authentication & Credentials|https://docs.engineering.redhat.com/pages/viewpage.action?pageId=103418313]
* [Execution Scripts|https://docs.engineering.redhat.com/display/QEARCH/Execution+Scripts]
* [Jenkins Job generation|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job+generation]
* [Jenkins Job Types|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job+Types]
* [Job Triggers|https://docs.engineering.redhat.com/display/QEARCH/Job+Triggers]
* [Resource Ready|https://docs.engineering.redhat.com/display/QEARCH/Resource+Ready]
* [SCM|https://docs.engineering.redhat.com/display/QEARCH/SCM]

Some other are still in doing: 

* [Provisioning|https://docs.google.com/document/d/1p-MJB6vP1oZXXFr2qscopkEoMwb13s1TH5v9p6lCyT8/edit]
* [Job Parameters|https://docs.engineering.redhat.com/display/QEARCH/Job+Parameters]
* [Data Usage and Retention|https://docs.engineering.redhat.com/display/QEARCH/Data+Usage+and+Retention]

*Job migration workflow:*
* Check on best practices and migrate job according to them, use existing examples, already migrated jobs
* Verify that migration is successful by running it locally using jcasc [2]. And share the test results in your sub-tasks jira.
* Create a PR and notify your component backup to get +1 on the PR.

[1]: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/cci-config
[2]: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/jcasc

  was:
As a part of QE - CI initiative and its out coming best practices, we need to move our QE and Infra jobs into job DSL. New repository that will be used to store jobs as a code ( job DSL) is here [1]. Migrate according to the QE - CI initiative best practices that can be found here:
* [Authentication & Credentials|https://docs.engineering.redhat.com/pages/viewpage.action?pageId=103418313]
* [Execution Scripts|https://docs.engineering.redhat.com/display/QEARCH/Execution+Scripts]
* [Jenkins Job generation|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job+generation]
* [Jenkins Job Types|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job+Types]
* [Job Triggers|https://docs.engineering.redhat.com/display/QEARCH/Job+Triggers]
* [Resource Ready|https://docs.engineering.redhat.com/display/QEARCH/Resource+Ready]
* [SCM|https://docs.engineering.redhat.com/display/QEARCH/SCM]

Some other are still in doing: 

* [Provisioning|https://docs.google.com/document/d/1p-MJB6vP1oZXXFr2qscopkEoMwb13s1TH5v9p6lCyT8/edit]
* [Job Parameters|https://docs.engineering.redhat.com/display/QEARCH/Job+Parameters]
* [Data Usage and Retention|https://docs.engineering.redhat.com/display/QEARCH/Data+Usage+and+Retention]

job migration workflow:
* Check on best practices and migrate job according to them, use existing examples, already migrated jobs
* Verify that migration is successful by running it locally using jcasc [2]. And share the test results in your sub-tasks jira.
* Create a PR and notify your component backup to get +1 on the PR.

[1]: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/cci-config
[2]: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/jcasc



> Migrate QE integration tests jobs into job DSL under dev-platform/cci-config repo
> ---------------------------------------------------------------------------------
>
>                 Key: JBIDE-26760
>                 URL: https://issues.jboss.org/browse/JBIDE-26760
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: integration-tests, qa
>    Affects Versions: 4.13.0.Final
>            Reporter: Ondrej Dockal
>            Assignee: Ondrej Dockal
>            Priority: Critical
>              Labels: integration_tests, jenkins, jenkins_pipeline
>             Fix For: 4.13.0.Final
>
>
> As a part of QE - CI initiative and its out coming best practices, we need to move our QE and Infra jobs into job DSL. New repository that will be used to store jobs as a code ( job DSL) is here [1]. Migrate according to the QE - CI initiative best practices that can be found here:
> * [Authentication & Credentials|https://docs.engineering.redhat.com/pages/viewpage.action?pageId=103418313]
> * [Execution Scripts|https://docs.engineering.redhat.com/display/QEARCH/Execution+Scripts]
> * [Jenkins Job generation|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job+generation]
> * [Jenkins Job Types|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job+Types]
> * [Job Triggers|https://docs.engineering.redhat.com/display/QEARCH/Job+Triggers]
> * [Resource Ready|https://docs.engineering.redhat.com/display/QEARCH/Resource+Ready]
> * [SCM|https://docs.engineering.redhat.com/display/QEARCH/SCM]
> Some other are still in doing: 
> * [Provisioning|https://docs.google.com/document/d/1p-MJB6vP1oZXXFr2qscopkEoMwb13s1TH5v9p6lCyT8/edit]
> * [Job Parameters|https://docs.engineering.redhat.com/display/QEARCH/Job+Parameters]
> * [Data Usage and Retention|https://docs.engineering.redhat.com/display/QEARCH/Data+Usage+and+Retention]
> *Job migration workflow:*
> * Check on best practices and migrate job according to them, use existing examples, already migrated jobs
> * Verify that migration is successful by running it locally using jcasc [2]. And share the test results in your sub-tasks jira.
> * Create a PR and notify your component backup to get +1 on the PR.
> [1]: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/cci-config
> [2]: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/jcasc



--
This message was sent by Atlassian Jira
(v7.13.5#713005)