Thanks, Michael! By the way, if I go to https://github.com/jenkinsci/blueocean-plugin/pull/1909 and click on the Details link next to *continuous-integration/blueocean/pr-head* that takes me to a broken link. It looks like there is a misconfiguration in the settings for ci.blueocean.io and github integration.
Can someone fix that? -- Craig On Sun, Feb 3, 2019 at 2:07 PM Michael Neale <mne...@cloudbees.com> wrote: > Thanks Craig. > > I think that makes a lot of sense - that was kept separate for historic > reasons that no longer matter. > > I think there may be some more work to do to get it clean (as it was part > of some acceptance test in the past) but can continue that on the PR. > > On Sunday, February 3, 2019 at 10:45:38 AM UTC+11, Craig Rodrigues wrote: >> >> Michael, >> >> I submitted this PR to import the blueocean-executor-info-plugin into the >> blueocean-plugin >> via a git subtree merge, to preserve history: >> >> https://github.com/jenkinsci/blueocean-plugin/pull/1909 >> >> blueocean-executor-info-plugin is not perfect, but having it inside the >> blueocean-plugin core is >> better than not having it. >> >> -- >> Craig >> >> >> On Mon, Jan 21, 2019 at 9:01 PM Michael Neale <mne...@cloudbees.com> >> wrote: >> >>> >>> To Craig's point - that is a great and fairly reasonable hitlist to make >>> something end to end useful. On the first one I put a comment (not sure if >>> pipeline jobs can be disabled at all...) but it is valid. The others are >>> doable (the hard one is editing build info - as that is where extensible >>> GUIs of plugins can kick in - but likely the scope can be contained here to >>> be reasonable to make something useful end to end). That would be great! >>> >>> For the executors one - we could resurrect the old executor >>> visualisation plugin (this was mostly done as a demo of extensibility, but >>> perhaps it is time to fold it in) - there is some code here: >>> https://github.com/jenkinsci/blueocean-executor-info-plugin which may >>> be useful for that (doesn't need to be its own plugin, really...) >>> >>> >> >> On Sat, Feb 2, 2019 at 3:37 PM Craig Rodrigues <rod...@freebsd.org> >> wrote: >> >>> Hi, >>> >>> I like the Blue Ocean UI a lot! I am trying to use Blue Ocean >>> as my "daily driver" when interacting with Jenkins. >>> I spend a lot of my day starting/stopping jobs, examining logs, >>> editing build descriptions, and disabling/enabling builds. >>> >>> However, there are some gaps in the Blue Ocean UI. >>> >>> The gaps are small, but annoying enough that I need to keep switching >>> back to the classic UI. This is annoying. >>> >>> I mentioned this in this other discussion thread: >>> https://groups.google.com/d/msg/jenkinsci-dev/zNukeuLK4Og/DGwWnJyGCAAJ >>> , but wanted to pull out this list to a separate discussion. >>> >>> Here are my top pet peeves, which I classify as "pot holes": >>> >>> >>> - https://issues.jenkins-ci.org/browse/JENKINS-53022 Cannot disable >>> a job in Blue Ocean >>> - https://issues.jenkins-ci.org/browse/JENKINS-53019 Changes tab >>> does not group changes for multiple SCM providers by SCM >>> - https://issues.jenkins-ci.org/browse/JENKINS-52825 Cannot see >>> executors in Blue Ocean UI >>> - https://issues.jenkins-ci.org/browse/JENKINS-55691 Cannot edit >>> build information in Blue ocean UI >>> >>> >>> If anyone wants to collaborate on fixing these bugs, please communicate >>> on the Gitter channel: https://gitter.im/jenkinsci/blueocean-plugin >>> >>> -- >>> Craig >>> >>> >>> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/23c9fe25-f2f0-470f-a50b-73e36ecc0301%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/23c9fe25-f2f0-470f-a50b-73e36ecc0301%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3DrPVeUUqqv-4SN9juOubjwW5qb0giUaWEdxBjmw0uANMgFOA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
