iwarapter
iwarapter
@racodond this is why i originally had the info level rule to mark these for manual review, checking to see if its top level scope i.e site.pp should enough however...
@manicminer this is a useful change to merge in if it can make the next release 🙏
hey @jglick, wondering if you had a chance to look at this?
hey @jglick i'd be happy to have a look at this if you could give any pointers on how to go about implementing this.
hi @jglick, thanks for getting back, I have two problems ultimately around multi-branch projects: 1 - Given say I have 3 branches `master`, `example1`, `example2`. With a `sub` claim defined...
> What I am not following is what sub (or set of possible subs) you want to have instead. I'd like to be able to access the actual multibranch folder...
> That seems like something that should be added to branch-api. (Almost. In some corner cases I think the MultiBranchProject.name might not match the GitHub repository name, which is what...
hey @jglick had a quick go at what this might look like, its rough currently but does the basics of allowing precedence based on environment variables.
hey @jglick if you get a chance could you take a look at the supporting PR https://github.com/jenkinsci/branch-api-plugin/pull/344 many thanks!