sharkcz reported a new issue against the project: `releng` that you are following: `` * Describe the issue Right now we have only last 14 days of the nightly composes. Which makes it impossible to compare current compose with an old one to see what changed (mainly functionally). The polocy could be time based (like keep 1 compose per week for 4 weeks preceding the 14 days, then keep 1 per month, until previous GA). Or it can be based on the openqa testing and keep composes "nominated for further testing". Or something else.
One of the reason for this request is https://bugzilla.redhat.com/show_bug.cgi?id=1623547 where I'm almost sure I had a F-29 nightly compose behaving sanely on s390x in the past, but have nothing I could compare with the current state.
* When do you need this? (YYYY/MM/DD) soon
* When is this no longer needed or useful? (YYYY/MM/DD) never
* If we cannot complete your request, what is the impact? Difficult to find out what changed (functionally) in the composes as the previous compose is the GA compose of the last release. AFAIK it's almost impossible to recreate an old compose from a given date on demand. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7763
mohanboddu added a new comment to an issue you are following: `` I was thinking of koji inheritance, so that it wont occupy any space and we can go back to what ever date we want to and create a compose out of it.
This doesn't mean that we will have the compose ready, whenever someone wants to have a compose from a certain date, we can re-create it. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7763
sharkcz added a new comment to an issue you are following: `` I think simply adding a "nightly" tag (like f29-20180904.n.0) might work, following a policy suggested above. AFAIK pungi returns event id for the state of the tag it run on, then we would add a tag to all builds matching this event. At the end one could ask "please, re-create a $arch / $variant compose from $nightly_tag". ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7763
sharkcz added a new comment to an issue you are following: `` maybe `koji clone-tag --event <pungi_event>` is what we need ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7763
lsedlar added a new comment to an issue you are following: `` The event is available in `work/global/koji_event` in each compose. It's a JSON file with id and timestamp. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7763
The issue: `define and implement retention policy for nightly composes` of project: `releng` has been assigned to `mohanboddu` by syeghiay.
mohanboddu added a new comment to an issue you are following: `` From RelEng meeting on May 29 2019:
``` #info We will not change the policy but we will keep track of the koji event id (probably in fpdc) from which we can clone a koji tag and run a compose from it if and when its really needed. ``` ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7763
The status of the issue: `define and implement retention policy for nightly composes` of project: `releng` has been updated to: Closed as It's all good by mohanboddu.
rel-eng@lists.fedoraproject.org
-
Dan Horák -
Lubomír Sedlář
-
Mohan Boddu
-
Suzanne Yeghiayan