5 ms·

Fair enough to advocate for your project, which I btw find it very nice. However, xml configuration is really a weak argument. It is very rare that anyone need

by mpermar 13y ago

Fair enough to advocate for your project, which I btw find it very nice. However, xml configuration is really a weak argument. It is very rare that anyone needs to touch the XML files. In fact, when someone touches those files is normally due to either a very extreme case or more commonly lack of interest in learning how the admin UI works. Jenkins lets you manage absolutely everything from the UI, from the very beginning, which is pretty convention-over-configurationish. Also Jenkins' changes control system lets you track and diff every change very quickly.

pbiggar 13y ago
Fair. My real gripe with jenkins is the UI configuration - the XML is a bit of a sideshow. I'll restructure my post slightly, thanks.
echohack 13y ago
You can track changes in Jenkins configurations?
- mpermar 13y ago
  Actually I was wrong on that one. I took for granted that you could track changes because we have a nice "Job Config History" menu option. But that is actually the job config history plugin ( https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory... ) So, I step back on saying Jenkins lets you track main changes history. That has to be done manually I guess.
  - echohack 13y ago
    This plugin is actually really nice. Thanks, this will help. :)
drunkenfly 13y ago
I find Jenkins UI too cluttered with a lot of stuff being hidden by default behind the "Advanced" buttons. So I stopped using Jenkins UI and migrate all my job definitions to YAML file in my source code repo. I use OpenStack Jenkins-job-builder to generate job. Here is the list of different tools, that can be used to automate Jenkins: https://gist.github.com/lechat/6666099 https://gist.github.com/lechat/6666099
icambron 13y ago
> or more commonly lack of interest in learning how the admin UI works. If this is even possible, the admin UI is not usable enough. "Man, I wouldn't have to use this ridiculous XML configuration system, if only I had the patience to slog through this UI. Alas..."

by mpermar 13y ago

pbiggar 13y ago

Fair. My real gripe with jenkins is the UI configuration - the XML is a bit of a sideshow. I'll restructure my post slightly, thanks.

echohack 13y ago

You can track changes in Jenkins configurations?

mpermar 13y ago
Actually I was wrong on that one. I took for granted that you could track changes because we have a nice "Job Config History" menu option. But that is actually the job config history plugin ( https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory... ) So, I step back on saying Jenkins lets you track main changes history. That has to be done manually I guess.
- echohack 13y ago
  This plugin is actually really nice. Thanks, this will help. :)

drunkenfly 13y ago

I find Jenkins UI too cluttered with a lot of stuff being hidden by default behind the "Advanced" buttons. So I stopped using Jenkins UI and migrate all my job definitions to YAML file in my source code repo. I use OpenStack Jenkins-job-builder to generate job. Here is the list of different tools, that can be used to automate Jenkins: https://gist.github.com/lechat/6666099 https://gist.github.com/lechat/6666099

icambron 13y ago

> or more commonly lack of interest in learning how the admin UI works. If this is even possible, the admin UI is not usable enough. "Man, I wouldn't have to use this ridiculous XML configuration system, if only I had the patience to slog through this UI. Alas..."