Seeing how much people recommend other solutions, I've actually moved from Travis to Jenkins, and never looked back.<p>Yes, Jenkins has its issues (crappy UX, poor/awkward docs), but where it shines is the fact it's self-hosted, so I can SSH onto the instance to debug a failing build or replay it with a modified Jenkinsfile on the fly.<p>I'm quite proud of the current setup we have; We're hosting our app with Google's Container Engine (Kubernetes), so what we're doing is on every build Jenkins creates a slave agent within the same cluster (just different node pool) as the production, so the environment in which test containers are ran is identical to production, and what's more it actually talks to the same Kubernetes master, which means I can, for example, test our Nginx Reverse proxy with real backend endpoints and real certificates (that are mounted through glusterfs).
Hey there,<p>I am the community leader for Jenkins Blue Ocean and Product Manager for the project at CloudBees. It's really great to see Jenkins users getting excited about Blue Ocean!<p>Please let us know if there are any missing features that are blocking your team from adopting Blue Ocean. We know there are some gaps between Jenkins Classic and Blue Ocean and while we have some good ideas, we are relying on your feedback to help us prioritise what to work on next.<p>If you've got any questions feel free to drop a comment here and Ill do my best to answer them or join our Gitter community [1]<p>Thanks,
James<p>[1] <a href="https://gitter.im/jenkinsci/blueocean-plugin" rel="nofollow">https://gitter.im/jenkinsci/blueocean-plugin</a>
Esoteric use case from someone in AI: Jenkins is the only CI we've been able to use even as an open source project due to needing gpus. CI and things like special hardware is a "semi-common" edge case and a big reason to have something self hosted.<p>Referencing other comments here: We've also found periodic builds and arbitrary jobs to be a must as well.<p>A lot of providers out there support most of the basic stuff out of the box, and I understand why they won't go after an edge case like that. It's great to see improvements in the UX on the horizon, that has been our biggest pain point.<p>If anyone's curious, our CI setup involves a multi OS cluster: Mac,windows,linux for power,linux x86 (with cross building for android) with 1 linux master running a gpu for gpu tests.
They should rethink the deployment model instead.<p>You cannot provision jenkins
unattended without 3rd party hacks and undocumented features. Until this is fixed I recommend avoiding it, as you'll get pet servers. This is totally retrograde to the devops mindset. Now why should I not use that mindset if that proves to be productive at other parts of work?
Wow, this looks amazing. I really want to try this out.<p>On my current contract, we've been moving away from Jenkins and towards Gitlab CI. I still work on an opensource project that uses Jenkins to build. The screenshots show a really good pipeline layout. It seems like it's similar in power to Gitlab CI, but also looks like it has way better visual representations and UI.<p>I'm glad the Jenkins team is still moving forward and developing plugins/tools like this.
I just want to mention that I loved the idea of BlueOcean at the begining. It looks sleak an works well with pipeline. However, for us it's unusable in production setting.
I know that it's still in beta, but as one example it doesn't support parameters. When user starts a job through BlueOcean it will fail.(Officialy they don't plan to implement it any time soon as I found out) That means It stays disabled in our jenkins. PS: For now its just a presentation tool for management :)
I love to hate Jenkins. Such a nice (and remarkably simple, for what it accomplishes) piece of software.<p>I've tried to replace it so many times, and so many times come to realize what an asset it is.
We used Jenkinsfiles and pipelines recently. And also introduce Blue Ocean on our jenkins server.<p>It come with a few glitches: Some plugins are not compatible with Blue Ocean, causing a white-page-of-death. However I found there where already issues created for them, i just turned off the plugin.<p>But the biggest downer, is that blue ocean is just a small UI on viewing pipelines. Its not a replacement for jenkins. And you still need the normal jenkins UI. Which doesn't handle pipelines well.<p>I think its still very much a beta project.
I have been using Blue Ocean as the radiator view for our Jenkins projects for a long while now and it does look really nice and sleek. That said, currently that's pretty much the extend it can be used for. I'd say it has about ~5% feature parity with the "old" UI currently, which means that there's not much to do than just look at the pretty progress bars. Can't wait for this to progress though, the old UI of Jenkins is archaic at best.
This news is from September, I gave my first impressions on Hacker News then, here's my blog post including an interview from the team behind Blue Ocean.<p><a href="http://blog.alexellis.io/tag/jenkins/" rel="nofollow">http://blog.alexellis.io/tag/jenkins/</a><p>They are doing a great job at reinventing JenkinsCI (but remember it's still Java)
See also thread from May this year: <a href="https://news.ycombinator.com/item?id=11790900" rel="nofollow">https://news.ycombinator.com/item?id=11790900</a>
I think in the what is AI argument what has actually happened is that there have been two conversations about AI over the years - what AI is and what AI can do by virtue of being AI.<p>In that conversation the assumption has been that AI would be in some ways self-aware and intelligent like 'Data in Star Trek'
and by virtue of being self aware and intelligent it would be able to learn things from its users, it would be able to make aesthetic judgements about music and art, it would be able to create interesting art of its own and so forth.<p>As it turns many of the things that AI will be able to do for us has been done by programs that are 'just math', the question is if in the future more or even all of AI's perceived benefits for humanity can be accomplished by just more and more complex 'math'.<p>In the end perhaps the essence of what AI is will only be beneficial to AI itself.
This is nice! I've been looking for a way to schedule deployments of multiple code bases at the same time, with automatic rollback support. Does this support that?
This looks great. Not because of the aesthetics, but because it finally acknowledges that Groovy is absolutely useless for Pipeline. I want to try out this new workflow.
We've actually built Pipelines [1] for that very reason; Jenkins has always felt over-engineered and unfriendly.<p>I'd be very interested in hearing from folks who are familiar with it what they think of our alternative.<p>[1]: <a href="https://github.com/Wiredcraft/pipelines#readme" rel="nofollow">https://github.com/Wiredcraft/pipelines#readme</a>
This look nice, is there a hosted version of BlueOcean?<p>I've been looking into (preferably hosted) pipeline-based CD options because simple CIs like Travis and CircleCi are not really meant true CD. What does everybody recommend?