[ https://issues.jboss.org/browse/JBIDE-26760?page=com.atlassian.jira.plugi... ] 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?pag...] * [Execution Scripts|https://docs.engineering.redhat.com/display/QEARCH/Execution+Scripts] * [Jenkins Job generation|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job...] * [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-MJB6vP1oZXXFr2qscopkEo...] * [Job Parameters|https://docs.engineering.redhat.com/display/QEARCH/Job+Parameters] * [Data Usage and Retention|https://docs.engineering.redhat.com/display/QEARCH/Data+Usage+a...] 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]. * Create a PR and notify your component backup to get +1 on the PR or Let your backup to verify sub-task jira [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?pag...] * [Execution Scripts|https://docs.engineering.redhat.com/display/QEARCH/Execution+Scripts] * [Jenkins Job generation|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job...] * [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-MJB6vP1oZXXFr2qscopkEo...] * [Job Parameters|https://docs.engineering.redhat.com/display/QEARCH/Job+Parameters] * [Data Usage and Retention|https://docs.engineering.redhat.com/display/QEARCH/Data+Usage+a...] 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]. * Create a PR and notify your component backup to get +1 on the PR or Let your backup to verify sub-task jira [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)