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 t
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?
tir. 6. aug. 2019 kl. 14:03 skrev Baptiste Mathus :
> IIUC what is team-folder inside bitbucket, then yes I believe you've got
> it right
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
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 appr
