"Team-folder" multibranch pipelines for github

[David Karlsen]

Bitbuckets offers "teamfolders" - which are multibranch pipelines around the project scope in bitbucket. One project contains several repos, each repo has branches - they have Jenkinsfile - you get jobs for several repos by doing just one manual configuration.

For github I don't see a similar approach which would be "team-level".

I can find a multibranch option, but then you need to go off and configure it by hand once per repo.

I find https://plugins.jenkins.io/github-branch-source - but this seems to be per gh organization or user ("Scans a GitHub organization (or user account) for all repositories matching some defined markers.").

I find organization too wide (as they can grow very large) - and individuals to narrow - while team-level would be perfect.

Any thoughts?

--

--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen

[Baptiste Mathus]

IIUC what is team-folder inside bitbucket, then yes I believe you've got it right by matching it to organization folders.

The fact seems to me that given this is what GitHub offers, this is what the plugin could propose?

How would you propose, think this should evolve?

For instance starting with a GitHub team and find repos what that team is admin? Other?

On our organization, mixing many different teams, we've solved this by using "marker files", which we then filter the full GitHub organization with.

When such a file is found (say `.our-team`), then it is matched and imported inside a given Jenkins org folder (using ghbs plugin, yes).

Cheers

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAGO7Ob2Dvibh-%3Dsmynv1-Da9DR%2BKHmciMXnhBex8gJMX%2B%3D1upA%40mail.gmail.com.

[David Karlsen]

Hi - yes, list repos via teams, or filter repos based on team-access level - but the marker-file approach should work equally well - where is this configured?

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS51%2BhvJ1wGLHemWJuwfYy0qYo%2BK31GwB1EGO3dcF8qKRw%40mail.gmail.com.

[David Karlsen]

https://github.com/jenkinsci/github-branch-source-plugin/pull/214 seems to implement exactly the feature I am looking for but needs some review-love.

From https://www.cloudbees.com/blog/ensuring-corporate-standards-pipelines-custom-marker-files it seems it is not simply a marker file - but I need to change the actual Jenkinsfile to have some team-custom name - which works - but is a bit quirky.