Code changed in jenkins
User: Tom Fennelly
Path:
src/main/js/custom_assertions/urlEndsWith.js
src/main/js/custom_commands/addOpenBlueOceanLinkToFooter.js
src/main/js/custom_commands/openBlueOcean.js
src/main/js/globals.js
src/main/js/page_objects/blueocean/bluePipelineActivity.js
src/main/js/page_objects/classic_jenkins/classicRun.js
src/main/nightwatch.json
src/test/js/edgeCases/folder.js
src/test/js/smoke.js
http://jenkins-ci.org/commit/blueocean-acceptance-test/cdf8d0d9c1e5db06951f9de01bf7498a84c7d254
Log:
[FIX JENKINS-39339] contextual try Blue Ocean button (#65)

• Add "Open Blue Ocean" link to footer

need it because we removed the header

• Added a few custom assertions

• Added some pipeline activity page empty state assertions

• Added openBlueOcean custom command

• Add smoke test for the "Open Blue Ocean" button

• remove urlMatches - unused

• Fix url encoding in urlEndsWith

• Make pipeline activity basic layout testing less fragile

• A test for "Open Blue Ocean" on a freestyle down in a folder

• Fix urlEndsWith assertion to handle weird characters in a more human way

• A test for "Open Blue Ocean" on a multibranch run down in a folder

PRs:

• https://github.com/jenkinsci/blueocean-plugin/pull/582
• https://github.com/jenkinsci/blueocean-acceptance-test/pull/65

yeah not sure why that other one was closed (doesn't have a reason). Not deliberately related. Great minds think alike.

Hey Vivek Pandey or Ivan Meredith, do we have any magic on the Blue Ocean backend that accurately maps a blue ocean URL to it's equivalent classic Jenkins URL? I appreciate that this might not always be possible, but then we can just go to the Blue Ocean home page (as today).

In the meantime, I will see if I can implement some @Extension points that get rendered on classic Jenkins pages (Job page and then Run page) and at least be able to redirect when on these pages (to the active pipeline or run details page in BO). This might be enough (as in the description above).

Tom FENNELLY could you please pick this one up next? This was identified in the CD survey feedback and mentioned on a few email threads as a pain point for adoption.