Skip to:

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

When a component build passes OST, tag its git hash

Description

As a project maintainer, I want to see which changes passed CI gating (aka CQ) so that it will be easy for me to tell if a specific commit was tested in CQ and is available for QA.

Scenario: Project maintainer specifies in stdci.yaml config that he wants STDCI to tag changes of this project by specifying

"standard stage" will add the relevant information to the change object and CQ will handle the tagging.

Need to see if the tags will be pushed by CQ as well or another component should be used (such as pusher.py)

25% Done
Loading...

Activity

Show:

Eyal Edri January 9, 2019 at 1:38 PM

I don't see us implementing it soon or in the near future, given the team resources and priority.

Barak Korren June 24, 2018 at 7:31 AM

Converted this ticket into an epic, since it will take a significant amount of work.

please add detailed work items and acceptance criteria.

Eyal Edri October 29, 2017 at 3:40 PM

This requires keeping a hash/mapping of each project rpm to a source repo, maintaining permissions for a specific user to tag any project ( and keeping track on new projects,etc.. ), and to what purpose?

I'm not sure what is the reason behind this request, but won't it be irrelevant once we move to patch gating? ( which should happen in the near future ), which means any merged patch is basically passing OST and tested?

danken October 29, 2017 at 12:00 PM
Edited

Until this is implemented, I've written a little script to automate what I do to find the latest tested version of a project

Details

Assignee

Reporter

Components

Priority

Epic Name

Created October 24, 2017 at 9:30 AM
Updated June 16, 2021 at 11:51 AM