Adam Bloom08/09/2022, 12:12 AM
prha08/09/2022, 5:51 PM
this is no longer true. We used to show runs of identically named jobs, independent of repository, but as of
we only show runs that were created by jobs for that specific repository. Ideally we’d have some run migration CLI tools, but I can walk you through how to do those run migrations by running a data migration against your DB if you’re interested.
Adam Bloom08/09/2022, 5:52 PM
prha08/09/2022, 5:58 PM
table with key
and value of the form
… We use this value to filter by the job’s current repository. If you move the job to a differently named repository, it won’t be able to find the historic runs unless you run an update to the new repository name. If you’re splitting the mega-repo into smaller repos, you may have to join the
table to filter by job name to get the appropriate new repository name.
Adam Bloom08/09/2022, 7:03 PM