Is there a good resource with screenshots that show these new features? For a 2.0 that was in the making for years, the page is pretty light on screenshots.
The only thing I really wanted out of it was the checkpoint plugin, and that's still enterprise only.
it was not in making for years. 2.0 started only 4-5 months ago.
> This is why in 2.0 we’ve added the pipeline capability. This 2 year old effort allows you to describe your chain of automation in a textual form.
It seems that they have been working on some 2.0 features for two years.
That's not to poo-poo the hard work that obviously went into this release. Big, shiny new stuff there, and the next Jenkins box I setup will be running 2.0. But for my particular situation at this point in time, it'll be 1.6 for a while.
That being said, I updated a few instances to 2.0, immediately applied all plugin updates and things kept working as before. That was a surprise. I was already prepared to spend hours trying to find why our jobs were failing. That was nice.
demo: http://ci.concourse.ci
FD: I work at Pivotal (but not on Concourse), the makers of concourse.
Yes we know there are alternatives to jenkins.
- You can backup / restore / version your entire CI config to a file = move fast and break stuff because it's easy to revert
- Build chains (pipelines in Jenkins) are built in, they're smarter than the average bear too
- Plugins not required, everything just works out the box, from report publishing to maven builds to connectivity with obscure VCS's - it's all just built in and there's no faffing about looking for combinations of plugins which play well together
To get started is as easy as any other CI server, however, because it's quite a bit more powerful than any other CI i've used, i'd say it takes a minute or two to fully appreciate what's on offer.
Also very easy to define build pipelines in the UI.
See 'CraigJPerry answer also.
Scripting languages like Apache Groovy don't scale, instead bring technical debt, complexity that must be fixed up by someone else in the future.
I hope to see Jenkins, and the team behind them, stay strong within the industry for a long time :-)
Does anyone actually prefer to use plugins for project types rather than a hand written build script? (i.e. using Jenkins to just kick off a shell script)
You likely want debian-stable instead: http://pkg.jenkins-ci.org/debian-stable/
It also explicitly mentions backwards compatibility:
> Jenkins 2 is a drop-in replacement of the Jenkins 1.x series of releases and fully backward compatible. There is practically no reason not to upgrade!
