Re: Blue Ocean Status Update

[Jeremy Hartley]

Though, I no longer product manage Jenkins, having left CloudBees, I also 
agree with Oleg's recommendations. 

On Monday, October 18, 2021 at 11:23:32 PM UTC+2 ullrich...@gmail.com wrote:

> Am 18.10.2021 um 10:43 schrieb Oleg Nenashev :
>
> Hi all,
>
> To whomever sees this thread, please see Bringing Blue Ocean into the 
> future of Jenkins 
> <https://cd.foundation/blog/2021/09/02/bringing-blue-ocean-into-the-future-of-jenkins/>
>  by 
> Tim Jacomb. Taking the state of BlueOcean that has not changed much over 
> the past two years, I suggest making the Pipeline Graph View Plugin an 
> official path for Jenkins.
>
> Under that, I mean:
>
>- Add "Pipeline Graph View Plugin" to the Jenkins Roadmap, in the 
>preview or released status
>- Add "Pipeline Graph View Plugin" to the list of the recommended 
>Jenkins plugins in the plugin installation manager
>
> +1
>
>
>- Remove Blue Ocean from the list of recommended plugins in Jenkins
>- TBD: Announce the future plan to double down on consolidating Blue 
>Ocean features in Jenkins and then deprecating Blue Ocean
>
> Since we have nobody working on UI improvements anymore it does not make 
> sense for me to announce a future plan. We already have a plan on our web 
> page (which is as obsolete as the Blue Ocean plan). In my opinion Jenkins 
> UI Development is at a dead end in the moment (Except Cliffs’ and Tims' 
> tremendous work in getting the pipeline view ported back to classic Jenkins 
> UI).
>
>
>- TBD: Create tasks for replacing Jenkins newcomer user documentation 
>that related on Blue Ocean
>
> Note that there are still gaps in Jenkins features, e.g. Visual 
> Declarative Pipeline Editor is available only in Blue Ocean. Probably it is 
> too early to announce deprecation of Blue Ocean, but we need to make a 
> decision at some point.
>
>
> Hmm, for me Blue Ocean is deprecated since 2 years. I wonder why we still 
> use it as the default view in ci.jenkins.io even though we know that it 
> is dead since two years now. 
>
>
> Opinions?
>
> Best regards,
> Oleg
>
> On Thursday, November 28, 2019 at 8:21:34 AM UTC+1 Jeremy Hartley wrote:
>
>> Thank you Peter for your feedback. I don't expect subversion support to 
>> be added to Blue Ocean, but once you switch to Git it will hopefully be a 
>> useful addition to you
>>
>>
>> On Thursday, November 28, 2019 at 3:54:44 AM UTC+1, Peter wrote:
>>>
>>> Followed the blue ocean attempt for some time, but missing support for 
>>> subversion makes it impossible to integrate in our environment (until we'll 
>>> switch to git). Cool stuff, anyways.
>>>
>>>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/cabb4d45-be58-468a-9291-8d3bdf4bfcdbn%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/cabb4d45-be58-468a-9291-8d3bdf4bfcdbn%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3bd183ce-edc9-4f5d-97cf-de486747e6fen%40googlegroups.com.

Re: Join us for Jenkins Online UI/UX Hackfest on May 25-29!

[Jeremy Hartley]

Thanks Oleg!

Also if people can help spread the word via Twitter or any other means
that would be greatly appreciated!

On Thu, May 14, 2020 at 6:15 PM Oleg Nenashev 
wrote:

> Dear all,
>
> On behalf of the Jenkins User Experience, Documentation and
> Advocacy special interest groups, we are happy to announce the Online
> UI/UX Hackfest <https://www.jenkins.io/events/online-hackfest/2020-uiux/>
> on May 25-29! Everyone is welcome to participate, regardless of their
> Jenkins development experience. Newcomers are also to join the event and
> start contributing to the project.
>
> The goal is to get together and improve the Jenkins user experience,
> including but not limited to user interface and user documentation. We also
> invite you to share experiences about Jenkins and to participate in UX
> testing, non-code contributions also count. The event follows the Jenkins
> is the Way <https://www.jenkins.io/blog/2020/04/30/jenkins-is-the-way/>
> theme and the most active contributors will get special edition swag and
> prizes!
>
> [image: register button]  (Direct URL
> <https://forms.gle/zLTZwfH7Au1obs9R7>)
>
> There will be 3 main tracks
> <https://www.jenkins.io/events/online-hackfest/2020-uiux/#tracks-and-project-ideas>
> :
>
>-
>
>*User Interface *- Improve look and accessibility for Jenkins
>users, work on new read-only interface for instances managed with
>configuration as code, create and update Jenkins themes, and many other
>topics. Also, UX testing for the listed projects. This track is coordinated
>by the UX SIG <https://www.jenkins.io/sigs/ux/>.
>-
>
>*User Documentation* - Verify, improve and create new user
>documentation <https://www.jenkins.io/doc/book/>, tutorials
><https://www.jenkins.io/doc/tutorials/> and solution pages
><https://www.jenkins.io/solutions/>. Also, there is ongoing
>documentation migration from Wiki to jenkins.io and plugin
>repositories. This track is coordinated by the Documentation SIG
><https://www.jenkins.io/sigs/docs/>.
>-
>
>*Spread the word* - Write user stories for Jenkins Is The Way
><https://jenkinsistheway.io/> site and the Jenkins blog
><https://www.jenkins.io/blog>, post about your Jenkins user experience
>and new features, record overview and HOWTO videos, etc. This track is
>coordinated by the Advocacy and Outreach SIG
><https://www.jenkins.io/sigs/advocacy-and-outreach/>.
>
> You can find more information about the event on its landing page
> <https://www.jenkins.io/events/online-hackfest/2020-uiux/>: tracks and
> project ideas, contribution guidelines, etc. We will also host the kick-off
> online meetup
> <https://www.meetup.com/Jenkins-online-meetup/events/270644129> on May 25
> to kick-off the hackfest.
>
> Have a great event!
> Jenkins Advocacy SIG
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins User Experience" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-ux+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-ux/CAPfivLA_Nz6nFauW4U_AdKnpOoL8KUkEvh%3DD4EepzcXYTLBcUA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-ux/CAPfivLA_Nz6nFauW4U_AdKnpOoL8KUkEvh%3DD4EepzcXYTLBcUA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>


-- 

Jeremy Hartley

Senior Product Manager

CloudBees, Inc.




P: +31610526836
E: jhart...@cloudbees.com
 <https://twitter.com/CrossGenevieve>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CALkOT4r2iOmQsGuv%2BiU%3D-Zrb2E_AzfuJCPO8bruUknGgDxMU3A%40mail.gmail.com.

Updates about Jenkins User Experience SIG moving to Jenkins User Experience Mailing List

[Jeremy Hartley]

Hi,

At the first Jenkins User Experience SIG meeting it was agreed that the 
conversation and updates about this SIG would be done in the Jenkins User 
Experience mailing list 
<https://groups.google.com/forum/#!forum/jenkinsci-ux>  . So if you are 
interested in reading the minutes of the first meeting or finding out when 
the next meeting is scheduled please head over there. This is to avoid 
having multiple threads about the same. Everybody is welcome!

Thanks

Jeremy Hartley

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ce3ac49c-fb92-4b64-9f4f-e5ee7345720f%40googlegroups.com.

Re: Blue Ocean Status Update

[Jeremy Hartley]

Thank you Peter for your feedback. I don't expect subversion support to be 
added to Blue Ocean, but once you switch to Git it will hopefully be a 
useful addition to you

On Thursday, November 28, 2019 at 3:54:44 AM UTC+1, Peter wrote:
>
> Followed the blue ocean attempt for some time, but missing support for 
> subversion makes it impossible to integrate in our environment (until we'll 
> switch to git). Cool stuff, anyways.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/cac606c4-38d5-4b3c-b8bb-9990a5eacfd0%40googlegroups.com.

Blue Ocean Status Update

[Jeremy Hartley]

There has been some confusion for a while about the status of Blue Ocean. 
As the product manager for Jenkins at CloudBees I would like to provide an 
update on CloudBees point of view with regards to the status of Blue Ocean.


CloudBees Point of View

Jenkins is not going anywhere and it needs a modern, up-to-date, UX for the 
next ten years of the projects’ life. CloudBees is investing in 
transformatively improving the Jenkins UI/UX. We have started a project to 
revamp the Jenkins User Experience and launched a new User Experience 
Special Interest Group (SIG) to involve the open source community in this 
process. 

CloudBees does not believe that Blue Ocean is the most appropriate vehicle 
with which to make these changes. As such, we will focus on alternative 
approaches and we will not be working on any major new functionality within 
Blue Ocean.

As we implement improvements to the Jenkins UI and UX, the Blue Ocean 
pipeline experience will remain relevant to users for quite some time. The 
work on the new UX will be prioritised and due to the relative modernity of 
the Blue Ocean pipeline UX, it is not a candidate to be replaced early on 
in the process. During this time we will selectively address significant 
security issues and functional defects.

As a part of the Jenkins OSS project, we encourage community contributions 
that resolve functional issues and add small enhancements to Blue Ocean. We 
intend to merge worthy community PRs and release these at a regular 
cadence. 


Any questions are of course welcome


Thanks 


Jeremy Hartley

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/992bc58e-75ef-4d43-bc1d-8ac6a5d50253%40googlegroups.com.

Re: ANN: Time Change for new Jenkins User Experience SIG

[Jeremy Hartley]

Hi, 

Just a reminder that the inaugural session of the Jenkins User Experience 
SIG will take place today at 15:00 UTC. Everybody that has an interest in 
the Future of the Jenkins UX is welcome to participate and you can join 
via: https://cloudbees.zoom.us/j/621503564 
<https://www.google.com/url?q=https://cloudbees.zoom.us/j/621503564=D=1574778164667000=AOvVaw1njRWWTYWvs7uhdgPxCg2N>.
 
The recording will post on YouTube. If you are there please remember to 
remind me to hit record!.

Thanks

Jeremy Hartley

On Thursday, November 21, 2019 at 3:25:09 PM UTC+1, Jeremy Hartley wrote:
>
> Description:
>
> I need to let you know that due to unforeseen circumstances the time of 
> the first meeting of Jenkins User Experience SIG has to change to one hour 
> earlier than previously planned. 
>
> It will now take place at Tuesday, November 26th, 2019 at 15:00 UTC. 
>
>
> The proposed meeting agenda is available at 
> https://docs.google.com/document/d/1xA6UN7ORv3OFYBC3Kw6y4mtqDekAjwYVNhsrH4PBwBk/edit?usp=sharing
>  
> <https://www.google.com/url?q=https://docs.google.com/document/d/1xA6UN7ORv3OFYBC3Kw6y4mtqDekAjwYVNhsrH4PBwBk/edit?usp%3Dsharing=D=1574778164667000=AOvVaw2vzGG8TNB_VXZtVNXjBlEN>
>  . 
> We'll be using Zoom to host the meetings and record them 
> https://cloudbees.zoom.us/j/621503564 
> <https://www.google.com/url?q=https://cloudbees.zoom.us/j/621503564=D=1574778164667000=AOvVaw1njRWWTYWvs7uhdgPxCg2N>.
>  
> The videos will be published to YouTube.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e832880e-9425-4bd2-9ab8-4e9a300372ed%40googlegroups.com.

ANN: Time Change for new Jenkins User Experience SIG

[Jeremy Hartley]

Description:

I need to let you know that due to unforeseen circumstances the time of the 
first meeting of Jenkins User Experience SIG has to change to one hour 
earlier than previously planned. 

It will now take place at Tuesday, November 26th, 2019 at 15:00 UTC. 


The proposed meeting agenda is available at 
https://docs.google.com/document/d/1xA6UN7ORv3OFYBC3Kw6y4mtqDekAjwYVNhsrH4PBwBk/edit?usp=sharing
 

 . 
We'll be using Zoom to host the meetings and record them 
https://cloudbees.zoom.us/j/621503564 
.
 
The videos will be published to YouTube.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ea9906c4-c3ff-42b7-b906-c468bcb238ec%40googlegroups.com.

Re: Git Commit Message as an Environment Variable

[Jeremy Hartley]

Thanks Mark and Eric. I'll give this suggestion a try

On Thursday, November 21, 2019 at 12:37:44 AM UTC+1, Mark Waite wrote:
>
> If it helps, I have an example that iterates over the changeset 
> <https://github.com/MarkEWaite/jenkins-bugs/blob/873e78402ca3cc2fc2330020cba8794274b2077a/Jenkinsfile#L56>
>  
> provided for a Pipeline job when running on a branch within a multibranch 
> pipeline.
>
> I believe it is limited to multibranch pipelines, but have not checked to 
> be sure.
>
> On Wed, Nov 20, 2019 at 3:44 PM 'Eric Boehm' via Jenkins Users <
> jenkins...@googlegroups.com > wrote:
>
>> You could use groovy to collect the commit message from the ChangeSet and 
>> then put it in an environment variable.
>>
>> On Tuesday, November 19, 2019 at 9:53:52 AM UTC-5, Jeremy Hartley wrote:
>>>
>>> Hi,
>>>
>>> I'm playing around a bit with Git environment variables to send to slack 
>>> and would like to include the Git commit message. I don't see it available 
>>> in the list here: 
>>> https://wiki.jenkins.io/display/JENKINS/Git+Plugin#GitPlugin-Environmentvariables
>>>
>>> Is there any way to send the Git commit message to slackSend as an 
>>> environment variable in my pipeline?
>>>
>>> Thanks
>>>
>>> Jeremy
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkins...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/a0b485ff-8f48-4432-be5b-8a2d6af600a4%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/a0b485ff-8f48-4432-be5b-8a2d6af600a4%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>
>
> -- 
> Thanks!
> Mark Waite
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/04714215-d3de-4b2b-84a4-8aefdedd2ddc%40googlegroups.com.

Git Commit Message as an Environment Variable

[Jeremy Hartley]

Hi,

I'm playing around a bit with Git environment variables to send to slack 
and would like to include the Git commit message. I don't see it available 
in the list here: 
https://wiki.jenkins.io/display/JENKINS/Git+Plugin#GitPlugin-Environmentvariables

Is there any way to send the Git commit message to slackSend as an 
environment variable in my pipeline?

Thanks

Jeremy

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/65afed35-7011-4f3c-84e0-41b196b3a5a3%40googlegroups.com.

ANN: Proposal for a new User Experience SIG

[Jeremy Hartley]

In keeping with JEP-4 <https://github.com/jenkinsci/jep/tree/master/jep/4>, 
I'm posting to the user mailing list my plan to create and lead the Jenkins 
User Experience  special interest group.

I'll submit a pull request to jenkins.io with the structure described in 
JEP-4 <https://github.com/jenkinsci/jep/tree/master/jep/4>.

The first UX special interest group meeting is scheduled for Tuesday, 
November 26th, 2019 at 16:00 UTC. The proposed meeting agenda is at 
<https://docs.google.com/document/d/1uNNo0QJKPHnNp8PGr_jLI8p3K_94ZYD-M0evZOEZ93c/edit#>
https://docs.google.com/document/d/1xA6UN7ORv3OFYBC3Kw6y4mtqDekAjwYVNhsrH4PBwBk/edit?usp=sharing
 
. We'll be using Zoom to host the meetings and record them 
https://cloudbees.zoom.us/j/621503564. The videos will be published to 
YouTube.

Draft mission statement:

The User Experience SIG focuses on improving Jenkins user interface and 
user experience. The SIG will seek feedback from the community on the 
current UI and UX and new designs proposed by SIG members and others and 
will discuss alternatives, identify compromises, and test implementations 
to improve the Jenkins UI / UX.

Thanks,

Jeremy Hartley

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b6d61a2a-8881-453f-b7d2-1a57d65dcc4c%40googlegroups.com.

Re: Updates to the Blue Ocean plugin and a new Pipeline sub-project

[Jeremy Hartley]

Hi Ulrich,

Thanks for your suggestion. I'll definitely cross post it to the Developers 
List.

In terms of your question about the UX overhaul. What you suggest makes a 
lot of sense. We are planning to start with a few small changes to improve 
the First TIme Wizard experience and then make some limited (mostly 
CSS-based) improvements to the the Jenkins UX while we gradually plan the 
larger UX overhaul. Our goal is to learn from Blue Ocean and not be in a 
position where we find that though good for Pipelines it is difficult to 
extend out to cover/replace the rest of the UX.

If you have any more comments or follow up I would be really happy to hear.

Thanks

Jeremy Hartley

On Tuesday, June 18, 2019 at 12:02:56 PM UTC+2, Ullrich Hafner wrote:
>
>
> Am 17.06.2019 um 13:17 schrieb Jeremy Hartley  >:
>
> Hello fellow Jenkins users and developers,
>
> I am a product manager at CloudBees and have taken over responsibility for 
> the Jenkins Blue Ocean sub-project. Over the last year, the teams working 
> on Jenkins at CloudBees have looked at the initiative of overhauling the 
> Jenkins user experience. This analysis led us to conclude that Blue Ocean 
> is a great way to work with Jenkins Pipelines but that it’s not the best 
> way to achieve the larger goal of overhauling the entire Jenkins user 
> experience. <https://www.cloudbees.com/blog/cloudbees-and-jenkins-update>
>
>
> Does this mean that blue ocean is dead and a new - even bigger - project 
> will come? Wouldn’t it make more sense to start with smaller UI refactoring 
> steps in the current UI rather than another large overall approach that may 
> fail in the end? There is so much potential in the current UI that could be 
> leveraged with small effort. (An overall approach still can be started in 
> parallel. But now we have the problem that almost nobody is improving the 
> classic UI side anymore because of the announcement of blue ocean.)
>
> Christina Noren's blog post on CloudBees and Jenkins 
> <https://www.cloudbees.com/blog/cloudbees-and-jenkins-update> gives a 
> good update of the work we are doing at CloudBees on Jenkins overall. The 
> CloudBees teams working on Jenkins are currently engaged in a discovery 
> process to start a large project to modernize the overall user experience 
> in Jenkins. This research goes beyond simple user interface updates and 
> focuses on usability in addition to  modern aesthetics. 
>
>
>
> Maybe it would also make sense if you could run such a discussions in 
> public (dev list?) so that non-Cloudbees contributors can participate? At 
> least during the initialization of blue ocean we had a lot of discussions 
> with plugin authors about requirements for a new UI.
>
>
> I believe that Pipeline is THE way that continuous integration and 
> continuous delivery are best done in Jenkins. Therefore, I am proposing 
> that we raise Pipeline to become a top-level sub-project within Jenkins.
>
> Making Pipeline a top-level sub-project will:
>
>- Clearly tie Jenkins to CI/CD for new and existing Jenkins users
>- Make it easier for everyone to find documentation for using CI/CD 
>Pipelines in Jenkins
>- Help the community and CloudBees to continue to improve and build 
>out new features for Pipeline and to improve documentation and examples
>- Help clarify that Blue Ocean is a feature of Jenkins Pipeline
>
>
> I look forward to getting your feedback. Thank you for your time.
>
> Regards
>
> Jeremy Hartley
> Senior Product Manager
> CloudBees, Inc.
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkins...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/264C1702-896E-485B-8630-8B4616607AE3%40cloudbees.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/264C1702-896E-485B-8630-8B4616607AE3%40cloudbees.com?utm_medium=email_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 Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/416d7df6-2027-41d9-acd9-d46be75c5271%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Updates to the Blue Ocean plugin and a new Pipeline sub-project

[Jeremy Hartley]

Hello fellow Jenkins users and developers,

I am a product manager at CloudBees and have taken over responsibility for the 
Jenkins Blue Ocean sub-project. Over the last year, the teams working on 
Jenkins at CloudBees have looked at the initiative of overhauling the Jenkins 
user experience. This analysis led us to conclude that Blue Ocean is a great 
way to work with Jenkins Pipelines but that it’s not the best way to achieve 
the larger goal of overhauling the entire Jenkins user experience. Christina 
Noren's blog post on CloudBees and Jenkins 
<https://www.cloudbees.com/blog/cloudbees-and-jenkins-update> gives a good 
update of the work we are doing at CloudBees on Jenkins overall. The CloudBees 
teams working on Jenkins are currently engaged in a discovery process to start 
a large project to modernize the overall user experience in Jenkins. This 
research goes beyond simple user interface updates and focuses on usability in 
addition to  modern aesthetics. 

I believe that Pipeline is THE way that continuous integration and continuous 
delivery are best done in Jenkins. Therefore, I am proposing that we raise 
Pipeline to become a top-level sub-project within Jenkins.

Making Pipeline a top-level sub-project will:
Clearly tie Jenkins to CI/CD for new and existing Jenkins users
Make it easier for everyone to find documentation for using CI/CD Pipelines in 
Jenkins
Help the community and CloudBees to continue to improve and build out new 
features for Pipeline and to improve documentation and examples
Help clarify that Blue Ocean is a feature of Jenkins Pipeline

I look forward to getting your feedback. Thank you for your time.

Regards

Jeremy Hartley
Senior Product Manager
CloudBees, Inc.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/264C1702-896E-485B-8630-8B4616607AE3%40cloudbees.com.
For more options, visit https://groups.google.com/d/optout.