Change Details

I've asked @marmoute and @Alphare on irc. It's somewhat a gitlab instance. There are 3 types of repositories for that instance currently: - git - hg: native mercurial - hg-git: those should be converted in a few months by upstream, they can be ingested as mercurial repository safely In practice, that means: - [x] Adapt lister's current implementation to deal with other types [1] - [ ] add a new gitlab instance in the scheduler once ^ is packaged and deployed. - [ ] The name [2] should be different than "gitlab" to avoid having the coverage under gitlab as well, something like "heptapod" would do. [1] @anlambert did it in P1168, i iterated over it and packaged D6285 [2] "swh-scheduler" db, "listers" table, "name" column, other gitlab instances have their name "gitlab"

I've asked @marmoute and @Alphare on irc. It's somewhat a gitlab instance. There are 3 types of repositories for that instance currently: - git - hg: native mercurial - hg-git: those should be converted in a few months by upstream, they can be ingested as mercurial repository safely In practice, that means: - [x] D6285: Adapt lister's current implementation to deal with other types [1] - [x] D6286: Allow hg_git origns to be ingested as hg origins - [ ] D6287: Allow lister name to be something else than "gitlab" - [ ] Schedule a new gitlab instance named "heptapod" [3], instance="foss.heptapod.net" once ^ is packaged and deployed. [1] @anlambert did it in P1168, i iterated over it and packaged [2] "swh-scheduler" db, "listers" table, "name" column, other gitlab instances have their name "gitlab" [3] name must be different than "gitlab" to dedicate their coverage stats

I've asked @marmoute and @Alphare on irc. It's somewhat a gitlab instance. There are 3 types of repositories for that instance currently: - git - hg: native mercurial - hg-git: those should be converted in a few months by upstream, they can be ingested as mercurial repository safely In practice, that means: - [x] D6285: Adapt lister's current implementation to deal with other types [1] - [ ] add a new gitlab instance in the scheduler once ^ is packag- [x] D6286: Allow hg_git origns to be ingested and deployed.s hg origins - [ ] The name [2] should be different than "gitlab"D6287: Allow lister name to avoid havbe something the coverage underelse than "gitlab" - [ ] Schedule a new gitlab as wellinstance named "heptapod" [3], something like "instance="foss.heptapod" would do. [1] @anlambert did it in P1168, i iterated over itod.net" once ^ is packaged and packaged D6285deployed. [1] @anlambert did it in P1168, i iterated over it and packaged [2] "swh-scheduler" db, "listers" table, "name" column, other gitlab instances have their name "gitlab" [3] name must be different than "gitlab" to dedicate their coverage stats