Re: Fixing pot holes in Blue Ocean UI?

[Craig Rodrigues]

I have resolved JENKINS-52825.  The fix for this is visible at
https://ci.blueocean.io/blue

--
Craig

On Tue, Feb 26, 2019 at 3:38 PM Michael Neale 
wrote:

> So just checking in on this excellent list as of this week:
>
>- https://issues.jenkins-ci.org/browse/JENKINS-52825 Cannot see
>executors in Blue Ocean UI - Craig can this be closed? as your changes
>merged in (once released) should resolve this
>
>

-- 
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%3DrPVc3Yzt5ThDbbzzpKxwjLrSYZb%3DrCkAe-5hpX4fQfVNf%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fixing pot holes in Blue Ocean UI?

[Jennifer Briden]

Hello! Yes, we have prioritized those issues and a few minor UI
improvements.

Craig, I'd like to set up some time with you to introduce myself and
establish a way to more quickly and directly get your input. I will reach
out to you in email via my CloudBees address, if that works for you.

Jenn

On Tue, Feb 26, 2019, 15:32 Michael Neale  wrote:

> So just checking in on this excellent list as of this week:
>
>- https://issues.jenkins-ci.org/browse/JENKINS-53022 Cannot disable a
>job in Blue Ocean - Looks like Gavin is starting this (sounded like some
>good progress).
>- https://issues.jenkins-ci.org/browse/JENKINS-53019 Changes tab does
>not group changes for multiple SCM providers by SCM - Nicu has started on
>that (shouldn't be major hopefully)
>- https://issues.jenkins-ci.org/browse/JENKINS-52825 Cannot see
>executors in Blue Ocean UI - Craig can this be closed? as your changes
>merged in (once released) should resolve this
>- https://issues.jenkins-ci.org/browse/JENKINS-55691 Cannot edit build
>information in Blue ocean UI - This one will be probably the biggest one,
>and I am not sure how it can be tackled given build config can be highly
>dynamic based on plugins installed. If there is a way to scope this a bit
>better may make it easier to start.
>
>
>
>
> On Sunday, February 3, 2019 at 10:38:02 AM UTC+11, Craig Rodrigues 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/46600b1b-9853-4648-abfc-3f9869ef27be%40googlegroups.com
> 
> .
> 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/CAGuTKx%2BJJFKa9Tp%3DjNunEy%2Bz09degQXUZXTVkX%3D1mAqC4dRnmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fixing pot holes in Blue Ocean UI?

[Michael Neale]

So just checking in on this excellent list as of this week:

   - https://issues.jenkins-ci.org/browse/JENKINS-53022 Cannot disable a 
   job in Blue Ocean - Looks like Gavin is starting this (sounded like some 
   good progress). 
   - https://issues.jenkins-ci.org/browse/JENKINS-53019 Changes tab does 
   not group changes for multiple SCM providers by SCM - Nicu has started on 
   that (shouldn't be major hopefully)
   - https://issues.jenkins-ci.org/browse/JENKINS-52825 Cannot see 
   executors in Blue Ocean UI - Craig can this be closed? as your changes 
   merged in (once released) should resolve this
   - https://issues.jenkins-ci.org/browse/JENKINS-55691 Cannot edit build 
   information in Blue ocean UI - This one will be probably the biggest one, 
   and I am not sure how it can be tackled given build config can be highly 
   dynamic based on plugins installed. If there is a way to scope this a bit 
   better may make it easier to start. 




On Sunday, February 3, 2019 at 10:38:02 AM UTC+11, Craig Rodrigues 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/46600b1b-9853-4648-abfc-3f9869ef27be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fixing pot holes in Blue Ocean UI?

[Gavin Mogan]

Okay, ci.blueocean.io has now been updated to 2.150.3, and updated all the
plugins.

It seems the CI urls now work properly, and I don't see any issues.

So go us! no need to deep dive into things.

I'll delete the backup in a couple days if nothing else comes up.

Gavin

On Thu, Feb 21, 2019 at 9:55 PM Gavin Mogan  wrote:

> Hey Craig,
>
> The short version is no, don't know where to fix it.
>
> In some spare time I did a bunch of investigation, which I don't have
> access to my notes right now, but it essentially should be somewhere in
> https://github.com/jenkinsci/github-oauth-plugin/blob/master/src/main/java/org/jenkinsci/plugins/GithubRequireOrganizationMembershipACL.java#L82
> (or at least that plugin) and some interaction with the
> https://github.com/jenkinsci/display-url-api-plugin plugin.
>
> It hasn't been a priority for me (since there's a work around, and I've
> been focusing on BO specific items) to try to reproduce on my own instance
> where i can enable the debugger and walk through things.
>
> I will say it bugs me enough that I *will* look into it, just not right
> now.
>
> Work around
> 1) Login to ci.blueocean.io -
> https://ci.blueocean.io/securityRealm/commenceLogin?from=%2F
> 2) Click on redirect link
>
> On Thu, Feb 21, 2019 at 9:40 PM Craig Rodrigues 
> wrote:
>
>> Gavin,
>>
>> In this pull request:
>> https://github.com/jenkinsci/blueocean-plugin/pull/1918
>>
>> One of the automatically generated links is this:
>>
>> https://ci.blueocean.io/job/blueocean/job/bug%252FJENKINS-38339-fix/2/display/redirect
>>
>> which is broken.
>>
>> Do you know where in the config we can fix this?
>>
>> --
>> Craig
>>
>> On Thu, Feb 7, 2019 at 2:47 PM 'Gavin Mogan' via Jenkins Developers <
>> jenkinsci-dev@googlegroups.com> wrote:
>>
>>> I've been poking at that link for a few weeks now. I'm pretty sure it's
>>> a side effect of the github-oauth-plugin configuration/plugin that is
>>> installed but I have to setup a dev instance to confirm.
>>>
>>> For now if you login to the instance, the link will work.
>>>
>>> --
>>> 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/18c46df5-66e7-4da9-8363-f3be8def86ad%40googlegroups.com
>>> .
>>> 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%3DrPVfHd_9DzOSG0Msecvwxk5-U7O61jz7F-2RTZEnd1%2BXHag%40mail.gmail.com
>> 
>> .
>> 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/CAAgr96L7b_aWyLJawqmZqc3TYeJKnbbmbvPQXE5uOO1Oi6dbYA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fixing pot holes in Blue Ocean UI?

[Gavin Mogan]

Hey Craig,

The short version is no, don't know where to fix it.

In some spare time I did a bunch of investigation, which I don't have
access to my notes right now, but it essentially should be somewhere in
https://github.com/jenkinsci/github-oauth-plugin/blob/master/src/main/java/org/jenkinsci/plugins/GithubRequireOrganizationMembershipACL.java#L82
(or at least that plugin) and some interaction with the
https://github.com/jenkinsci/display-url-api-plugin plugin.

It hasn't been a priority for me (since there's a work around, and I've
been focusing on BO specific items) to try to reproduce on my own instance
where i can enable the debugger and walk through things.

I will say it bugs me enough that I *will* look into it, just not right now.

Work around
1) Login to ci.blueocean.io -
https://ci.blueocean.io/securityRealm/commenceLogin?from=%2F
2) Click on redirect link

On Thu, Feb 21, 2019 at 9:40 PM Craig Rodrigues  wrote:

> Gavin,
>
> In this pull request:
> https://github.com/jenkinsci/blueocean-plugin/pull/1918
>
> One of the automatically generated links is this:
>
> https://ci.blueocean.io/job/blueocean/job/bug%252FJENKINS-38339-fix/2/display/redirect
>
> which is broken.
>
> Do you know where in the config we can fix this?
>
> --
> Craig
>
> On Thu, Feb 7, 2019 at 2:47 PM 'Gavin Mogan' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>> I've been poking at that link for a few weeks now. I'm pretty sure it's a
>> side effect of the github-oauth-plugin configuration/plugin that is
>> installed but I have to setup a dev instance to confirm.
>>
>> For now if you login to the instance, the link will work.
>>
>> --
>> 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/18c46df5-66e7-4da9-8363-f3be8def86ad%40googlegroups.com
>> .
>> 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%3DrPVfHd_9DzOSG0Msecvwxk5-U7O61jz7F-2RTZEnd1%2BXHag%40mail.gmail.com
> 
> .
> 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/CAAgr96JO2c%2Bsb762kf-w_5kSXJ%2BFEaN1Y5toyop62eLAUup%2BQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fixing pot holes in Blue Ocean UI?

[Craig Rodrigues]

Gavin,

In this pull request:
https://github.com/jenkinsci/blueocean-plugin/pull/1918

One of the automatically generated links is this:
https://ci.blueocean.io/job/blueocean/job/bug%252FJENKINS-38339-fix/2/display/redirect

which is broken.

Do you know where in the config we can fix this?

--
Craig

On Thu, Feb 7, 2019 at 2:47 PM 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> I've been poking at that link for a few weeks now. I'm pretty sure it's a
> side effect of the github-oauth-plugin configuration/plugin that is
> installed but I have to setup a dev instance to confirm.
>
> For now if you login to the instance, the link will work.
>
> --
> 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/18c46df5-66e7-4da9-8363-f3be8def86ad%40googlegroups.com
> .
> 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%3DrPVfHd_9DzOSG0Msecvwxk5-U7O61jz7F-2RTZEnd1%2BXHag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fixing pot holes in Blue Ocean UI?

[Michael Neale]

On JENKINS-52825  have reopened and can discuss on the PR in place (as a 
bunch of work already there).

On Wednesday, February 13, 2019 at 1:03:00 PM UTC+11, David Lin wrote:
>
> Hi Craig,
>
> I was just pointed to this thread (Thanks @Michael!). We have 
> JENKINS-53022 on our radar already to fix, we were just finalizing some 
> Acceptance Test repairs and releasing a chunk of fixes. So it should be 
> coming up soon.
>
> As for JENKINS-52825, we're not exactly sure if it makes sense to pull it 
> into the root of Blue Ocean since it's already a plugin and was never fully 
> completed. Hopefully it still works for you that way.
>
> JENKINS-53019 and JENKINS-55691 will also be picked up to be completed 
> soon after the next release as well.
>
> Thanks again for your suggestions and contributions. It's very helpful, 
> keep them coming!
>
>  - David
>
>
>
> On Saturday, February 2, 2019 at 3:38:02 PM UTC-8, Craig Rodrigues 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/3ec344c1-6afc-4c10-a1a2-6df8b6dab431%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fixing pot holes in Blue Ocean UI?

[David Lin]

Hi Craig,

I was just pointed to this thread (Thanks @Michael!). We have JENKINS-53022 
on our radar already to fix, we were just finalizing some Acceptance Test 
repairs and releasing a chunk of fixes. So it should be coming up soon.

As for JENKINS-52825, we're not exactly sure if it makes sense to pull it 
into the root of Blue Ocean since it's already a plugin and was never fully 
completed. Hopefully it still works for you that way.

JENKINS-53019 and JENKINS-55691 will also be picked up to be completed soon 
after the next release as well.

Thanks again for your suggestions and contributions. It's very helpful, 
keep them coming!

 - David



On Saturday, February 2, 2019 at 3:38:02 PM UTC-8, Craig Rodrigues 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/31a96508-ede7-4148-9a19-02d4aebe23f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fixing pot holes in Blue Ocean UI?

['Gavin Mogan' via Jenkins Developers]

I've been poking at that link for a few weeks now. I'm pretty sure it's a side 
effect of the github-oauth-plugin configuration/plugin that is installed but I 
have to setup a dev instance to confirm.

For now if you login to the instance, the link will work.

-- 
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/18c46df5-66e7-4da9-8363-f3be8def86ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fixing pot holes in Blue Ocean UI?

[Craig Rodrigues]

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  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 
>> 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 
>> 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
> 
> .
> 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.

Re: Fixing pot holes in Blue Ocean UI?

[Michael Neale]

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  > 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  > 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.
For more options, visit https://groups.google.com/d/optout.

Re: Fixing pot holes in Blue Ocean UI?

[Craig Rodrigues]

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  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  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/CAG%3DrPVf4%3Ds610N2j2rdG-f0StL%3DMDgyGv5TxHDyaO_GvFU0Lug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.