-
Bug
-
Resolution: Duplicate
-
Minor
-
jenkins-2.7.4
blueocean - Built at 27th September 2016 03:05 AM (no branch) 57f7758
Safari Version 9.1.3 (& FireFox 49.0.1)
Summary: if there is no master branch, if you try to favourite a MB pipeline (vs a specific branch) it does incorrect things. It should work out what the default branch is (or ask user) or at least tell them to pick a branch... (latter is easiest).
If a user has favourited a MB pipeline folder in classic, blue ocean should ignore that.
Steps:
- Click "New Item" and Create "Multibranch Pipeline" without branch "master".
- Open Dashboard Jenkins. Check "Favorite" button for Multibranch Pipeline.
- Open Jenkins Blue Ocean.
Actual Result: New line for this job has been created in "Favorites" (grey colour). "Run" button hasn't worked. - Open Dashboard Jenkins -> this Multibranch Pipeline. Check "Favorite" button for any branch.
E.R. = A.R.: No error. Favorites Job have displayed correctly in Jenkins Blue Ocean. - Disable "Favorite" for this job.
- Open Jenkins Blue Ocean.
- Click "Favorite" button for Multibranch Pipeline.
Expected Result: Favorite label has been added. New line for this job has been created in "Favorites".
Actual Result: Failed to load resource: the server responded with a status of 400 (Bad Request){ "message" : "no master branch to favorite", "code" : 400, "errors" : [ ] } - Disable "Favorite" for this job.
Expected Result: Favorite label has been deleted.
Actual Result: TypeError: undefined is not an object (evaluating 'favoriteToRemove._links')
- duplicates
-
JENKINS-38718 Add an extension point so github et al can expose their default branches via scm api
-
- Resolved
-
- is blocked by
-
JENKINS-39082 Record the "default branch" of the Github repository
-
- Closed
-
-
-
- Closed
-
- relates to
-
JENKINS-39087 Add ability to mark a multibranch pipeline as a favourite - NOT a branch
-
- Resolved
-
[JENKINS-38601] Cannot mark Multibranch Pipeline as Favorite in Blue Ocean when no master branch
I think at the very least we can make this fail without an error in the console and pop up a toast to say that we couldn't favorite the pipeline as master branch does not exist?
Updated the reproduction steps.
Repositories without master branch are not so uncommon, hence this issues is pretty important. GitHub also allows specifying different branch as a main one. Blue Ocean should not hardcode the branch IMHO.
Error output to the console (console only) - is a bad idea. I can offer two options:
1 - In the absence of branches "master" appoint another main branch (default / on the last commit, etc.)
2 - Show a message stating that the branch "master" is not found, and offer the user to choose your favorite branch in Jenkins Dashboard (branch, not MB project). If user selected the project, then the project in the Blue Ocean will be displayed in the favorites, with empty branches, and "run" button will not be worked (please see steps 2-4).
Thanks ks_nenasheva - well spotted.
Currently if you favourite it from blue ocean it should search for a suitable branch (but it won't look for the default as setup in github/bitbucket, as that information isn't currently available yet). However, from your steps, it looks like favouriting it from Jenkins itself is a problem? (this may be a related bug, but not quite the same). Blue ocean can only show favourites for a branch (hence it tries to pick a default) - it can't show a favourite of what is effectively a folder.
The logic should be (for blue ocean): Favourite a MB pipeline -> choose default branch as per SCM provider -> (if none available) look for master/production/default named branch -> (if none found) -> pick the first one alphabetically so there is at least one branch.
What I am curious about is what is the behavior if people don't want a favourite on a branch (I need to investigate that a bit)
ok, I think I see what is happening.
When you fav a branch in classic, it is just marking the Item (a folder) as favourite. Blue Ocean incorrectly shows this up IF you have a master branch. It ideally would not.
It may be a while before the github/bitbuckets can report their default branches (which is clearly what should happen here in either case) so I think this is what should happen to remedy this:
- When favouriting a pipeline (not a branch) from blue ocean, if there is no master branch, ask the user to navigate and pick a branch (or, disable the favouriting feature for now, only on the branch) with a polite message
- If the user has favourited the multibranch folder in "classic", this should not show up as a fav. of the master branch in blue ocean (as it is now, if there is a master branch, you can end up with duplicate favourites) – this is what this bug is initially showing up.
- If the favourite is for a branch that doesn't exist (is it possible to know this?) - don't show it up as a fav.
I'm having the same problem with multibranch pipelines, for example in a folder where the default branch is develop (and that's the only branch I have listed in "Include branches").
In some other multibranch pipelines, I'm not building any branches at all — only pull requests. I can't favourite those folders either.
orrc oh interesting. That is a case I didn't think of - when you filter. Would it bug you if you went to fav a pipeline and it told you to pick a branch? As in your case, it won't know that "develop" if the default branch even if all the stars aligned and there was a default branch (as that isn't the default branch necessarily, its just how filtered).
I think simplest thing we can do is for MB that don't have master branch - we ask user to pick which branch if they try (or remove the star icon). Blue ocean has no concept of fav'ing a folder (the fact that a MB pipeline is actually a folder is a leaky implementation detail), as fav's apply to branches that do work only.
There may be other strategies...
cliffmeyers we should talk about this some time.
Perhaps a better solution is JENKINS-39087. If there is no master branch, you fav the MB folder and show no branch details (essentially just a shortcut, as requested)....
michaelneale vivek as there was some discussion about the current Favorite plugin having some bugs or other issues, I just thought I'd call one out:
- Favorite a branch in a multi-branch pipeline
- Favorite displays in dashboard as expected
- Go to classic UI. Move the MBP inside of a folder
- Reload BOUI: note that favorite is missing
Not sure if this is applicable to all job types or just multi-branch.
Eventually we want the default branch name to be whatever the upstreams "default branch" is (both Github and Bitbucket share a default branch concept).
I didn't understand what your expected behavior should be in this case - did you mean we should disable the favoriting button if the master branch does not exist?