-
Bug
-
Resolution: Not A Defect
-
Major
-
None
-
Browser:
Google Chrome on Linux, Version 59.0.3071.115 (Official Build) (64-bit)
Jenkins:
Core 2.68
Beta builds of the Branch UX Refactor suspects:
cloudbees-bitbucket-branch-source 2.2.0-beta-1
branch-api 2.0.11-beta-1
mercurial 2.0-beta-1
github-branch-source 2.2.0-beta-1
scm-api 2.2.0-beta-1
git 3.4.0-beta-1Browser: Google Chrome on Linux, Version 59.0.3071.115 (Official Build) (64-bit) Jenkins: Core 2.68 Beta builds of the Branch UX Refactor suspects: cloudbees-bitbucket-branch-source 2.2.0-beta-1 branch-api 2.0.11-beta-1 mercurial 2.0-beta-1 github-branch-source 2.2.0-beta-1 scm-api 2.2.0-beta-1 git 3.4.0-beta-1
Summary:
Given a Git multibranch project with many Additional Behaviours options set, after taking the beta-1 upgrades, some of these behaviors are not shown in the revised UI. So far, the job's config.xml file appears to be unaffected - in other words, the settings which don't show up in config.xml do not appear in the UI.
Assumptions:
This issue assumes that project settings which were set in a multibranch job before taking the upgrade, should remain visible to the user after taking the upgrade. Especially those settings which remain present in the job's config.xml file.
Steps to recreate: This is an example job. There are obviously a great many "additional behaviours" which can be set - 23 options are available in the dropdown, and some of those 23 reveal nested settings.
1. Set up a Multibranch job, using Git (not GitHub) as your source. I just pointed mine to a GitHub repo that I use frequently, by supplying the same URL that gets supplied by GitHub's "Clone with HTTPS" button.
2. Under "Additional Behaviours," select "Check out to a specific local branch" and provide an easy to spot branch name. In the examples attached I used FANCY.
3. Also under "Additional Behaviours," select "Check out to a sub-directory," and provide an easy to spot subdirectory name. In the examples attached I used CheckOutToASubdirectory.
4. Finally, select "Strategy for choosing what to build," and pick Ancestry. Under this, set Maximum Age of Commit to 10.
5. Upgrade the plugins to the betas.
6. Note that this information does not appear in the UI anywhere.
The question is...should it appear, or is it by design that this information is hidden from view?
Other notes:
I've attached four files:
- before.xml and after.xml: the job xml files, as returned by the Jenkins CLI, before and after taking the plugin upgrades. The files are identical.
- Git--NOT--GitHubConfigBEFORE.pdf: A PDF of the pre-upgrade config page for the job. (page was too long to screenshot so this was the next best thing)
- Git--NOT--GitHubConfigAFTER.pdf: A PDF of the post-upgrade config page for the same job.