3 ms·

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 pa

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

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