4 ms·

My team and I designed Blue Ocean. We are really excited to get your feedback and suggestions. Ask me anything :)

by i386 10y ago

badlogic 10y ago
First, let me say this looks amazing. Thanks for your work! My biggest issue with Jenkins so far has been configuring complex jobs. The single configuration page just gets unwiedly fast, and important settings are often hidden by default. Is there any work being done to make this easier as well?
- i386 10y ago
  Wow thanks for the complement - I'm chuffed! There's a trend to move job configuration to a Jenkinsfile that's stored in a Git repository using Jenkins Pipeline. What used to be several jobs is now one Pipeline job config defined using this DSL https://jenkins.io/solutions/pipeline/ https://jenkins.io/solutions/pipeline/ Today the pipeline visualization only works with this way of making jobs. Now we realize this isn't for everyone and we are thinking about how to let users create Jenkins Pipelines through the UI without having to know the DSL (just like freestyle). We are also looking at making Pipeline easier for beginners too.
  - agentgt 10y ago
    It probably doesn't need reiterating but not having Travis like config is my biggest issue with Jenkins as well. While Pipeline looks awesome for sophisticated entities that have complex workflow it seems overly powerful for most I think that just have a lot of projects and configuration drift. Pipeline unlike Travis Yaml is also not a declarative language. One of the advantages of using a declarative markup language that respects comments and spaces (cough XML) would be for the Web UI editor to intelligently edit the configuration files while respecting order, formatting and comments (right now I believe Jenkins XStreams so its just naive serialization).
    - christop 10y ago
      Well you don't have to use the sophisticated features for a simple build. Something like "node { sh './build.sh' }" will work fine. But you can also build your own simplified syntax on top of Pipeline, e.g. I believe there is a prototype out there that will run Travis .yml scripts in a Pipeline job, and there are already plugins that simplify the Pipeline syntax, e.g. https://wiki.jenkins-ci.org/display/JENKINS/Simple+Build+For+Pipeline+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Simple+Build+For...
    - jacques_chester 10y ago
      GoCD has XML configuration, if that's your kind of thing. However, it turns out that tree-structured documents struggle to describe build graphs.
    - i386 10y ago
      Good news is that there is a RFC in the Dev list proposing what you are asking for. I'm personally a big supporter of it http://jenkins-ci.361315.n4.nabble.com/RFC-Plumber-a-declarative-layer-on-top-of-Pipeline-td4814898.html http://jenkins-ci.361315.n4.nabble.com/RFC-Plumber-a-declara...
- quicksilver03 10y ago
  I wrote a Greasemonkey user script to always show any advanced, hidden settings in Jenkins. I haven't tested it with the newer Jenkins 2.x versions, but you may want to try it to see if it helps. https://www.opsfordevelopers.com/2015/03/jenkins-show-advanced-settings/ https://www.opsfordevelopers.com/2015/03/jenkins-show-advanc...
boucher 10y ago
Having some trouble getting it running: https://gist.github.com/boucher/1a9beb22ac3cbadf858a82f4db05c0f2 https://gist.github.com/boucher/1a9beb22ac3cbadf858a82f4db05...
- i386 10y ago
  Might be best to post to the Jenkins Dev mailing list - it's pretty alpha at the moment and there are bound to be rough edges. When it's more ready we will be pushing the plugin continuously to be update center :)
- dominotw 10y ago
  cd .. && mvn install try that to build missing artifacts. It worked for me.
jancborchardt 10y ago
Great stuff! Working as designer on ownCloud where we use Jenkins it always felt outdated in the design department. Really good to see the improvements! I also added the main contributors of the repository to the Open Source Design collective at https://github.com/opensourcedesign https://github.com/opensourcedesign, more info at http://opensourcedesign.net http://opensourcedesign.net – welcome! :)
- i386 10y ago
  Thank you! This is my first attempt at designing in open source and would love to chat about your experience if you've got some time - jdumay@cloudbees.com
code_research 10y ago
I would like to ask you to please establish a new standard of NOT expecting all kind of config files in a project root directory - this is an annoying pestilence that has to stop and the Jenkins team could really help with that. Please instead establish any kind of directory that is expected where all that project and tooling related meta files are kept, I would like to suggest a top level folder called "config" - but I really do not care, how this is called, as long as that top level config file annoyance will disappear forever. I believe it might be acceptable to expect exactly one optional top level config file that might be called "configrc" that would contain only the path of that actual config path if this is not in a default place. Thank you very much for your attention!
- stephenconnolly 10y ago
  Well my original plan was that the default build instructions would be in a README.md file in the root of the source control as a verbatim block in the highest level heading containing the word "build" If you needed any additional configuration for Jenkins specific instructions then that would be in a folder called ".jenkins" Sadly, people did not embrace that project type... perhaps because it was given the nerdy name "literate" by a colleague of mine (who's name rhymes with Nichale Meale)
  - i386 10y ago
    So dry, Stephen :)
tbrock 10y ago
Wow, thank you! Jenkins' appearance has been a major deterrent for me in the past.
- i386 10y ago
  It's not just an appearance change - we hope it's the way you use it too :)

My team and I designed Blue Ocean. We are really excited to get your feedback and suggestions. Ask me anything :)

by i386 10y ago

My team and I designed Blue Ocean. We are really excited to get your feedback and suggestions. Ask me anything :)

First, let me say this looks amazing. Thanks for your work! My biggest issue with Jenkins so far has been configuring complex jobs. The single configuration page just gets unwiedly fast, and important settings are often hidden by default. Is there any work being done to make this easier as well?

i386 10y ago
Wow thanks for the complement - I'm chuffed! There's a trend to move job configuration to a Jenkinsfile that's stored in a Git repository using Jenkins Pipeline. What used to be several jobs is now one Pipeline job config defined using this DSL https://jenkins.io/solutions/pipeline/ https://jenkins.io/solutions/pipeline/ Today the pipeline visualization only works with this way of making jobs. Now we realize this isn't for everyone and we are thinking about how to let users create Jenkins Pipelines through the UI without having to know the DSL (just like freestyle). We are also looking at making Pipeline easier for beginners too.
- agentgt 10y ago
  It probably doesn't need reiterating but not having Travis like config is my biggest issue with Jenkins as well. While Pipeline looks awesome for sophisticated entities that have complex workflow it seems overly powerful for most I think that just have a lot of projects and configuration drift. Pipeline unlike Travis Yaml is also not a declarative language. One of the advantages of using a declarative markup language that respects comments and spaces (cough XML) would be for the Web UI editor to intelligently edit the configuration files while respecting order, formatting and comments (right now I believe Jenkins XStreams so its just naive serialization).
  - christop 10y ago
    Well you don't have to use the sophisticated features for a simple build. Something like "node { sh './build.sh' }" will work fine. But you can also build your own simplified syntax on top of Pipeline, e.g. I believe there is a prototype out there that will run Travis .yml scripts in a Pipeline job, and there are already plugins that simplify the Pipeline syntax, e.g. https://wiki.jenkins-ci.org/display/JENKINS/Simple+Build+For+Pipeline+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Simple+Build+For...
  - jacques_chester 10y ago
    GoCD has XML configuration, if that's your kind of thing. However, it turns out that tree-structured documents struggle to describe build graphs.
  - i386 10y ago
    Good news is that there is a RFC in the Dev list proposing what you are asking for. I'm personally a big supporter of it http://jenkins-ci.361315.n4.nabble.com/RFC-Plumber-a-declarative-layer-on-top-of-Pipeline-td4814898.html http://jenkins-ci.361315.n4.nabble.com/RFC-Plumber-a-declara...
quicksilver03 10y ago
I wrote a Greasemonkey user script to always show any advanced, hidden settings in Jenkins. I haven't tested it with the newer Jenkins 2.x versions, but you may want to try it to see if it helps. https://www.opsfordevelopers.com/2015/03/jenkins-show-advanced-settings/ https://www.opsfordevelopers.com/2015/03/jenkins-show-advanc...

boucher 10y ago

Having some trouble getting it running: https://gist.github.com/boucher/1a9beb22ac3cbadf858a82f4db05c0f2 https://gist.github.com/boucher/1a9beb22ac3cbadf858a82f4db05...

i386 10y ago
Might be best to post to the Jenkins Dev mailing list - it's pretty alpha at the moment and there are bound to be rough edges. When it's more ready we will be pushing the plugin continuously to be update center :)
dominotw 10y ago
cd .. && mvn install try that to build missing artifacts. It worked for me.

jancborchardt 10y ago

Great stuff! Working as designer on ownCloud where we use Jenkins it always felt outdated in the design department. Really good to see the improvements! I also added the main contributors of the repository to the Open Source Design collective at https://github.com/opensourcedesign https://github.com/opensourcedesign, more info at http://opensourcedesign.net http://opensourcedesign.net – welcome! :)

i386 10y ago
Thank you! This is my first attempt at designing in open source and would love to chat about your experience if you've got some time - jdumay@cloudbees.com

code_research 10y ago

I would like to ask you to please establish a new standard of NOT expecting all kind of config files in a project root directory - this is an annoying pestilence that has to stop and the Jenkins team could really help with that. Please instead establish any kind of directory that is expected where all that project and tooling related meta files are kept, I would like to suggest a top level folder called "config" - but I really do not care, how this is called, as long as that top level config file annoyance will disappear forever. I believe it might be acceptable to expect exactly one optional top level config file that might be called "configrc" that would contain only the path of that actual config path if this is not in a default place. Thank you very much for your attention!

stephenconnolly 10y ago
Well my original plan was that the default build instructions would be in a README.md file in the root of the source control as a verbatim block in the highest level heading containing the word "build" If you needed any additional configuration for Jenkins specific instructions then that would be in a folder called ".jenkins" Sadly, people did not embrace that project type... perhaps because it was given the nerdy name "literate" by a colleague of mine (who's name rhymes with Nichale Meale)
- i386 10y ago
  So dry, Stephen :)

tbrock 10y ago

Wow, thank you! Jenkins' appearance has been a major deterrent for me in the past.

i386 10y ago
It's not just an appearance change - we hope it's the way you use it too :)