Support for Multibranch Pipelines [$15]

[CbeckDrive]

Hi!

If you have a project that was created as a multibranch pipeline adding it to the view doesn't actually work. You can enable it, but it won't show up anywhere on the monitor. I assume this is because it's essentially a folder containing a different build for each branch, but it is impossible to select individual branches as well!

Thanks!

---

There is a $15 open bounty on this issue. Add to the bounty at Bountysource.

[jan-molak]

Hi @CbeckDrive!

You're right, support for Cloudbees Folders is still very basic I'm afraid :-(
I'll have a closer look into this at some point if there's interest in the community.
I am happy to help with pull requests if anyone would like to pick this up?

[groie]

Just bumping up the issue, as we'd be very interested in this functionality as well.

[reftel]

Something like #263?

[Multiply]

We're also quite interested in this. Jobs are added and removed automatically when PRs are made, and merged. Would be nice to show all active PRs on one monitor.

[foutoucour]

Hello,

Do you have any eta on this feature?

Best,
Jordi

[hoall]

Just an idea, but it would be nice to throw some money in the bounty, don't you think? Probably has more success like saying you want it too without doing anything

[edit] it's a rainy day over here, so please don't take me too serious

[pzelnip]

Bumping as yeah, it'd be awesome to have this feature as all our build projects are based on mulitbranch pipelines. As it stands we have to manually add each branch as a separate build to the wallboard, which works, but is a bit cumbersome.

Would would be really ideal is to be able to mark a number of "always interested in" branches", and specify a number of other branches to track. Ie say my multibranch job is called MyProject, I'd always want the master and test branches of MyProject to be visible on the board, and then maybe a grid of the 5 most recently updated other branches in the MyProject project, regardless of name. Failed builds should always show up (regardless of branch).

[gothrek22]

It's quite simple with the current regex and job filter support:

1. In Status Filter, choose "Enabled jobs only"
2. Mark recurse in subfolders
3. Mark "Use a regular expression to include jobs into the view"
4. Use regex like .(MULTIBRANCH_PROJECT_NAME.).*
5. ....
6. PROFIT!

[dwarcake]

@gothrek22 Thanks for the tip!
This actually seems to work :)

[ennisa-ire]

Thanks for supporting MB :)

[coachnate]

For whatever reason I couldn't get the regex to work, but just checking the recurse subfolders box made the pipelines available to check that were part of a multipipe config for me.

[seanfisk]

I was able to get both @gothrek22's and @coachnate's solutions working. The regex solution is preferable when you want to see all of the branches for a multi-branch pipeline, whereas checking individual branches allows you to see just those.

Overall, the regex solution seems a little hacky but it does work well — thank you to all involved!

[dcendents]

Actually I would recommend to use the View Job Filters plugin, it is much more powerful than a regex: https://wiki.jenkins.io/display/JENKINS/View+Job+Filters

I'm actually able to display only the branches I care about.

For example:

• Include all builds in the last 4 hours
• Exclude all builds triggered only by timer
• Keep only develop branches (at this point I have only develop branches that were built because of an actual commit/merge, they will disappear after 4 hours to declutter the board )
• Add all unstable and failed jobs (now if the develop build was not green, it will be added back)
• Add all my feature branches
• Remove all feature branches after they've been merged (regex on the job description, which I modify after the branch is merged)

This works well for us, and as you can see you can pretty much control exactly what you need to see for your team.

[RabiaShaik]

It's quite simple with the current regex and job filter support:

1. In Status Filter, choose "Enabled jobs only"
2. Mark recurse in subfolders
3. Mark "Use a regular expression to include jobs into the view"
4. Use regex like .(MULTIBRANCH_PROJECT_NAME.).*
5. ....
6. PROFIT!

Hi I tried the above and it doesnot work for me. I am running on Build Monitor version 1.12+build.201809061734. Kindly help