orcaLog in

Datasets

mojo.repo_versions

Written by
mojo_versions step versions pipelines/mojo_versions.mojo:39
Read by
mojo_versions step versions pipelines/mojo_versions.mojo:39
gharchive pipelinegharchivepipelinegharchive.candidates datasetgharchive.candidatesdatasetgharchive.events datasetgharchive.eventsdatasetgharchive.releases datasetgharchive.releasesdatasetgharchive.repo_hour datasetgharchive.repo_hourdatasetgharchive_index pipelinegharchive_indexpipelinemojo_activity pipelinemojo_activitypipelinemojo.activity datasetmojo.activitydatasetmojo.activity_repos datasetmojo.activity_reposdatasetmojo.releases datasetmojo.releasesdatasetmojo.repos datasetmojo.reposdatasetmojo_history pipelinemojo_historypipelinemojo.commits datasetmojo.commitsdatasetmojo.migrations datasetmojo.migrationsdatasetmojo.tags datasetmojo.tagsdatasetmojo_repos pipelinemojo_repospipelinemojo.checked datasetmojo.checkeddatasetmojo_stats pipelinemojo_statspipelinemojo.repo_stats datasetmojo.repo_statsdatasetmojo_versions pipelinemojo_versionspipelinemojo.repo_versions datasetmojo.repo_versionsdataset

Rebuild docs

Rebuild reruns everything downstream of this dataset for the partitions you give, in dependency order. Use it after this dataset's data was fixed or reloaded, so the tables built from it catch up.

  1. mojo_versions (reads mojo.repo_versions)

Plans a run of each pipeline above over those partitions; each level is queued once the one before it has succeeded.

Same from the command line (on the control instance today, remotely once #111 lands):

orca rebuild mojo.repo_versions <range>

Snapshots docs

No orca run has committed to it.