Skip to:

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

Gradually remove jobs from master publisher

Description

We saw how destructive using the current publishers can be during 4.1 cycle,
Problems we encountered:

1. It hides missing RPMs from experimental flows
2. It hides projects that needs to branch or using previous version released
3. It creates confusion of which RPMs are really tested in OST and give different results than experimental instead of having a single source of RPMs for oVirt.

We should aim to drop it for 4.2 and use only experimental deployment.
However, since we have errors on deploy to experimental flow, we can't progress with this until they will be solved.

Activity

Show:

Eyal Edri February 27, 2017 at 3:10 PM

We won't drop the nightly publishers.
Instead we'll just stop publishing RPMs from it and it will only be used to sync tested RPMs each night to the snapshot repos, that way we'll have static nightly updated oVirt repos.

The code to support it for master is already merged and part of the master publisher.

We need to remove all the YAML code from the publisher job gradually until all is left is the code that sync the test repo.

fyi

Eyal Edri January 24, 2017 at 8:56 AM

Waiting for deploy to experimental to stop failing

Fixed

Details

Assignee

Reporter

Blocked By

Priority

Parent

Created January 24, 2017 at 8:54 AM
Updated June 1, 2017 at 11:32 AM
Resolved May 1, 2017 at 8:36 AM