#2460 Better tracking of buildroot repo create time
Closed: Fixed by mikem. Opened by tkopecek.

Followup of #2424

Maybe we can add _ts fields to buildroot repo_create_event_time + retire_event_time

I think we should look into something like that, but not for this issue. I wouldn't simply add fields with those names though. For the repos, I think we need to track:

  • the event that the repo is generated from
  • the time the repo was created
  • the time the repo was retired

The first is decidedly an event reference, but the original field name of create_event is inaccurate.

The latter two are timestamps primarily, and could possibly not be events at all (though they could be).

So we could just add two timestamp field as you say, but the naming is confusing. We could rename things a bit to be more accurate, but we'd need to be careful about api_compatibility.

At any rate, this is way outside the scope of this issue. If we want to follow up on this, we should have a separate issue for it.


The on-demand work adds such data. See #4033

  • repo.creation_time -- the ts when the repo was created (not the same as the create_event ts)
  • repo.state_time -- the ts when the repo state was last changed
  • repo.begin_event -- the first event where the tag content is known to match the repo
  • repo.end_event -- the last event where the tag content is known to match the repo

We did not rename the "create_event" field to avoid breaking api, but that is the event that the repo was based on

Metadata Update from @mikem:
- Custom field Size adjusted to None
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/koji/issues/2460

Please continue any further discussion there.

Metadata