[
https://ovirt-jira.atlassian.net/browse/OVIRT-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barak Korren reassigned OVIRT-1219:
-----------------------------------
Assignee: Barak Korren (was: infra)
> Pupulate staging jenkins
> ------------------------
>
> Key: OVIRT-1219
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1219
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: oVirt CI
> Reporter: Barak Korren
> Assignee: Barak Korren
> Priority: Low
> Labels: jenkins, staging
>
> The staging Jenkins instance currently contains only a few jobs that were
> created manually. These jobs do not resemble production jobs at all, nor is
> there any activity going on on that instance that simulates production work.
> We can populate the staging Jenkins instance with the following steps:
> # Setup the Gerrit plugin in the staging Jenkins to also listen to events
> from the production Gerrit.
> # Create a '{{staging-projects}}' directory on the '{{/jobs/confs}}'
> directory of the '{{jenkins}}' repo. This way the production YAML job
> templates can be used to create jobs in the staging Jenkins.
> # Create a '{{jenkins_master_deploy-configs_merged}}' job for the staging
> Jenkins that will deploy jobs from the directory mentioned above. The job
> template should probably be changed so that the name of the dorectory it will
> take jobs from will come from a global variable defined in the Jenkins server.
> # Create some Standard-CI dummy projects in the staging Gerrit. Setup jobs to
> occasionally submit random patches to these projects.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100068)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
