Overall Satisfaction with Jenkins
[It is being used to] automate deployments while verifying code quality. Several jenkins jobs were defined to cover individual deployment to environments. Jenkins' pipeline makes the process more user-friendly. Jenkins supported several different software technologies from node to Java. We frequently utilise the wide variety of hooks jenkins can handle, and automatically trigger a build once the source code has changed.
- jenkins pipeline: useful to visualise the dependent job hierarchy and easy to start/stop each step manually
- Source code management (SCM): supports different types of repositories from SVN to Git and you can set different triggers after each code change.
- Plugins: jenkins can work well with lots of plugins, for instance it can render test results or run scheduled scripts seamlessly. Artifacts can be easily deployed with docker.
- UI might need a bit of improvement. I can point to material design, it' sso easy to visualise on a smart phone as well.
- Too much configuration on one page, I suggest separating out the config sections in a cleaner manner.
- Mainly just positive for instance thanks to the easy setup and install process. Easy to understand configurations and migrate to a newer version.
- The only part that needs to be improved is the UI which is far beyond the recent admin dashboard style material designs.
Jenkins is very flexible to define your custom dashboards and organise your jobs in groups. If you need a simple build pipeline it is highly recommend to use jenkins. On the other hand if you need lots of custom steps or long scripts to run to deploy your code Jenkins is not the best choice.