Change Details

I've asked @marmoute and @Alphare on irc. This requires a new lister instance. There are 3 types of repositories: - git - hg: native mercurial - hg-git: those should be converted in a few months so we should ignore them for now. In practice, that means: - Adapt gitlab lister's current implementation to deal with other types than git (e.g. we need mercurial for this instance). - add a new gitlab instance in the scheduler once ^ is packaged and deployed.

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, so we should just ignore them for now. In practice, that means: - Adapt lister's current implementation to deal with other types - add a new gitlab instance in the scheduler once ^ is packaged and deployed. - The name should be different than "gitlab" to avoid having the coverage under gitlab as well, something like "heptapod" would do.

I've asked @marmoute and @Alphare on irc. This requires a new listerIt'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, so we should just ignore them for now. In practice, that means: - Adapt gitlab lister's current implementation to deal with other types than git (e.g. we need mercurial for this instance). - add a new gitlab instance in the scheduler once ^ is packaged and deployed. - The name should be different than "gitlab" to avoid having the coverage under gitlab as well, something like "heptapod" would do.