Shaman should contain (and sort by) a 'created' field

[zmc]

Currently, if a build is "updated", the modified field is updated, breaking the sort order.

[alfredodeza]

Would created be something you would expect after a successful completed repository? or when the repository is being worked on? I ask the latter because in DEB repos for example, even in the middle of adding more packages to the repo it is correct to say that the repo has been "created" because it is just adding more packages.

We are currently working on the build status (closely related to repositories) and we are working with these fields for that model: started, completed, which are also utc datetime fields. Would those be something that you could consume here (for the repo model)?

[andrewschoen]

I think the issue that you ran into here won't be an issue once we get past the stabilization period for all these systems. In normal usage if a repo is 'updated' it will be because that exact same ref and sha1 was rebuilt in jenkins, in that scenario the modified date should be updated and the repo pushed up in the sort order.

If we switch to sorting by a 'created' date then these valid repo rebuilds will be missed.