Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Get rid of old 'create_rpms' jobs

Description

'create_rpms' jobs are the old kind of jobs that we used to have before STD-CI. We still have many of those laying around.

Here is the list for the time of writing these lines:

  1. vdsm_any_create-rpms_manual

  2. mom_any_create-rpms_manual_old

  3. qemu_4.1_create-rpms-el7-x86_64_merged

  4. qemu_4.1_create-rpms-el7-ppc64le_merged

  5. qemu_4.1_create-rpms-el7-x86_64_created

  6. qemu_4.1_create-rpms-el7-ppc64le_created

  7. qemu_master_create-rpms-el7-x86_64_created

  8. slf4j_master_create-rpms-el6-x86_64_merged

  9. qemu_master_create-rpms-el7-ppc64le_created

  10. slf4j_master_create-rpms-el6-x86_64_created

  11. ioprocess_0.15_create-rpms-el7-x86_64_merged

  12. ovirt-wgt_4.1_create-rpms-fc24-x86_64_merged

  13. ioprocess_0.15_create-rpms-el7-x86_64_created

  14. ovirt-wgt_4.1_create-rpms-fc24-x86_64_created

  15. ovirt-reports_3.6_create-rpms-el6-x86_64_merged

  16. ovirt-reports_3.6_create-rpms-el7-x86_64_merged

  17. ovirt-wgt_master_create-rpms-fc25-x86_64_merged

  18. py2exe-py2.7_4.1_create-rpms-fc24-x86_64_merged

  19. pywin32-py2.7_4.1_create-rpms-el7-x86_64_merged

  20. vcredist-x86_4.1_create-rpms-fc24-x86_64_merged

  21. ovirt-reports_3.6_create-rpms-el6-x86_64_created

  22. ovirt-reports_3.6_create-rpms-el7-x86_64_created

  23. ovirt-wgt_master_create-rpms-fc25-x86_64_created

  24. py2exe-py2.7_4.1_create-rpms-fc24-x86_64_created

  25. python-windows_4.1_create-rpms-el7-x86_64_merged

  26. pywin32-py2.7_4.1_create-rpms-el7-x86_64_created

  27. pywin32-py2.7_4.1_create-rpms-fc24-x86_64_merged

  28. vcredist-x86_4.1_create-rpms-fc24-x86_64_created

  29. ovirt-hosted-engine-ha_any_create-rpms_manual_old

  30. ovirt-vmconsole_3.6_create-rpms-el6-x86_64_merged

  31. ovirt-vmconsole_3.6_create-rpms-el7-x86_64_merged

  32. python-windows_4.1_create-rpms-el7-x86_64_created

  33. python-windows_4.1_create-rpms-fc24-x86_64_merged

  34. pywin32-py2.7_4.1_create-rpms-fc24-x86_64_created

  35. ovirt-vmconsole_3.6_create-rpms-el6-x86_64_created

  36. ovirt-vmconsole_3.6_create-rpms-el7-x86_64_created

  37. py2exe-py2.7_master_create-rpms-fc25-x86_64_merged

  38. python-windows_4.1_create-rpms-fc24-x86_64_created

  39. pywin32-py2.7_master_create-rpms-el7-x86_64_merged

  40. vcredist-x86_master_create-rpms-fc25-x86_64_merged

  41. vcredist-x86_master_create-rpms-fc26-x86_64_merged

  42. ovirt-host-deploy_3.6_create-rpms-el6-x86_64_merged

  43. ovirt-host-deploy_3.6_create-rpms-el7-x86_64_merged

  44. py2exe-py2.7_master_create-rpms-fc25-x86_64_created

  45. python-windows_master_create-rpms-el7-x86_64_merged

  46. pywin32-py2.7_master_create-rpms-el7-x86_64_created

  47. pywin32-py2.7_master_create-rpms-fc25-x86_64_merged

  48. pywin32-py2.7_master_create-rpms-fc26-x86_64_merged

  49. vcredist-x86_master_create-rpms-fc25-x86_64_created

  50. vcredist-x86_master_create-rpms-fc26-x86_64_created

  51. ovirt-host-deploy_3.6_create-rpms-el6-x86_64_created

  52. ovirt-host-deploy_3.6_create-rpms-el7-x86_64_created

  53. python-windows_master_create-rpms-el7-x86_64_created

  54. python-windows_master_create-rpms-fc25-x86_64_merged

  55. python-windows_master_create-rpms-fc26-x86_64_merged

  56. pywin32-py2.7_master_create-rpms-fc25-x86_64_created

  57. pywin32-py2.7_master_create-rpms-fc26-x86_64_created

  58. ovirt-log-collector_3.6_create-rpms-el6-x86_64_merged

  59. ovirt-log-collector_3.6_create-rpms-el7-x86_64_merged

  60. python-windows_master_create-rpms-fc25-x86_64_created

  61. python-windows_master_create-rpms-fc26-x86_64_created

  62. ovirt-log-collector_3.6_create-rpms-el6-x86_64_created

  63. ovirt-log-collector_3.6_create-rpms-el7-x86_64_created

  64. ovirt-engine-sdk-java_3.6_create-rpms-el6-x86_64_merged

  65. ovirt-engine-sdk-java_3.6_create-rpms-el7-x86_64_merged

  66. ovirt-engine-sdk-java_3.6_create-rpms-fc24-x86_64_merged

  67. ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_merged

  68. ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_merged

  69. jasperreports-server_master_create-rpms-el6-x86_64_merged

  70. jasperreports-server_master_create-rpms-el7-x86_64_merged

  71. ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_created

  72. ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_merged

  73. ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_created

  74. jasperreports-server_master_create-rpms-el6-x86_64_created

  75. jasperreports-server_master_create-rpms-el7-x86_64_created

  76. ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_created

  77. ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_merged

  78. ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_created

  79. ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_merged

  80. ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_merged

  81. nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_merged

  82. ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_created

  83. ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_created

  84. nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_created

  85. tmp_ovirt-hosted-engine-ha_master_create-rpms-el7-x86_64_tagged

  86. nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_merged

  87. ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_merged

  88. ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_merged

  89. nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_created

  90. ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_created

  91. ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_created

  92. ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_merged

  93. ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_created

  94. ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_merged

  95. ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_merged

  96. ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_created

  97. ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_created

  98. ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_merged

  99. ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_created

Activity

Show:

Barak Korren August 20, 2017 at 2:51 PM

Is it possible to create a "wrapper" project that will use standard CI, and will still monitor the upstream project (run CI per each push/merge there)?

We recently added the "upstream polling" capability to Standard-CI which is precisely targeted at this kind of scenario.

The general idea is that you put a YAML file in "automation/" that specifies the upstream project and the SHA1 of the commit you want to base further work on and then:
1. All jobs check out that commit to there place your own source is going to be and then override it with files from your project.
2. You can setup a polling job that will monitor the upstream repo and automatically create Gerrit patches with suggestions for updates to the SHA1. Since those are just Gerrit patches, you get automated check-patch runs on them.

For more details about this please nag because apparently he did not yet document this properly.

Eyal Edri August 20, 2017 at 2:22 PM

What I suggest is to create 'automation/*' dir and the 'check-patch','build-artifacts' scripts there to do the build instead of the obselete 'create rpms' jobs,
which are not being tested by OST and also not deployed automatically to tested repos.

Not sure what was asked in the past or why it was refused, but we can assist in the move if needed, as we did for the wildfly project:

removing from rel-eng tools:
https://gerrit.ovirt.org/#/c/80651/
https://gerrit.ovirt.org/#/c/80630/

adding new Jenkins jobs:
https://gerrit.ovirt.org/#/c/80650/
https://gerrit.ovirt.org/#/c/80629/

adding new wildfly project:
https://gerrit.ovirt.org/#/c/80625/
https://gerrit.ovirt.org/#/c/80624/
https://gerrit.ovirt.org/#/c/80626/

Yedidyah Bar David August 20, 2017 at 2:15 PM

On Sun, Aug 20, 2017 at 5:07 PM, eyal edri (oVirt JIRA)

It is active, although not too much.

Not sure how to "move to a project on its own", or what wildfly did.

It's maintained externally:

https://gitlab.com/spice/spice-nsis

The copy on ovirt gerrit is used for internal review and for CI.
Once we are happy internally with a change, we push it upstream.

We asked in the past to include an "automation/" directory for
standard CI and it was refused. Is it possible to create a "wrapper"
project that will use standard CI, and will still monitor the
upstream project (run CI per each push/merge there)?

Or you suggest some other means?

–
Didi

Eyal Edri August 20, 2017 at 2:07 PM

We can't drop 3.6 yet, some projects still use it to test and build for downstream 3.6, but we can drop 4.0 if there are any left.
I also saw WGT, probably one of the only active projects that should move to standard CI. is the wgt project actively worked on? any chance we can move it to a project on its own like wildfly did recently?

Barak Korren August 20, 2017 at 1:58 PM

I can see many jobs that are related to WGT. I don't think those are obsolete.

Also we should probably drop all the 3.6 jobs, that'll make the list at least 50% shorter.

Eyal Edri August 20, 2017 at 1:19 PM

All the wildfly 'jobs were removed, after the projects moved to std-ci.

As for the rest of the jobs, not sure if its worth the effort to update or remove them, as some of them are already obsolete like reports and qemu ( which is built from centos ).

We can probably keep this as a tracker ticket, in case one of these pkgs will need an update like wildfly did, and we can migrate them when it's needed.

Fixed

Details

Assignee

Reporter

Components

Priority

Created July 26, 2017 at 12:32 PM
Updated August 29, 2019 at 2:12 PM
Resolved July 4, 2019 at 12:04 PM