Jenkins X: a CI/CD solution for cloud applications on Kubernetes
71–80 of 106 posts
Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes
#72It's not completely clear to me from reading the site - does this run a non-dockerized app build in kubernetes, or does it also work for building and deploying my app as a docker container itself? This usually requires things like being able to spin up a cluster of containers per build - one with my app, one with a database to run against, maybe one with memcached or elasticsearch for integration tests, etc. And does…
Offloading build queue outside Jenkins to another service, auto-scaling of build servers, configuring Jenkins with your configuration management tools are all something we are thinking about / looking into / actively working on. Some of them haven't gotten to the point of proper write-up yet, but see
- https://github.com/jenkinsci/jep/tree/master/jep/201
Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes
#73This looks like an improvement over what Jenkins 2.0 provides and I wish you guys good luck. I have used and vouched for Jenkins in several companies and some decent sized licenses were bought mainly because of my input. But to me, Cloudbees has done a major dick move making the stages not restartable in Jenkins 2.0, among other things. E.g: Dropping stage view out of nowhere and focusing only in Blue Ocean. I compla…
How are you liking GoCD? I've been looking for an alternative to GitLab for a while.
Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes
#74This looks like an improvement over what Jenkins 2.0 provides and I wish you guys good luck. I have used and vouched for Jenkins in several companies and some decent sized licenses were bought mainly because of my input. But to me, Cloudbees has done a major dick move making the stages not restartable in Jenkins 2.0, among other things. E.g: Dropping stage view out of nowhere and focusing only in Blue Ocean. I compla…
Creator of Jenkins & CTO of CloudBees here. Thanks for using Jenkins for close to 10 years and sorry to see you move on, but I just want to correct the record here because I don't think the time line of events and your description are accurate. First, pipeline stages have never been restartable in Jenkins from the beginning of Jenkins Pipeline. It wasn't as if we started with restartable stage and decided to close-so…
Feel free to correct me, here is my take on it.
You are right the restarting in the declarative was not open, then closed. But I didn't say that, I said not having it was a dick move.
My point is a Stage is just an alias for a Job (or multiple) for the regular Joe who doesn't work on Jenkins code. That was always restartable at any time in my pipelines (Delivery Pipeline Plugin, Build Pipeline plugin, etc...). So when we started writing the old and new pipelines as code we assumed the feature would be the same, while learning the new DSL at the time it was not clear that it was not, at least to us. Lot's of people thought the same the link below is an example of it. This was 2016 if I am not mistaken, it's now open source and congratulations for changing that as I said when it was pointed out to me, but I am not following the topic anymore.
I have no problem with the business, as I said I vouched for it, and in the end they brought the licenses. My problem was, the main reason to buy it was not support or something juicy like Cloudbees cluster management features, It was that we wanted restarts.
Is it bad? Absolutely not. But it's not something that made me feel happy. I just think it was not a thing I could easily communicate with the people making the decisions, was like punishing engineers for a problem that they can't solve, give managers a reason to buy it, Cluster management is a nice one, Automatic backups another, having miserable engineers is a terrible one.
About Stage view, I was frustrated from training support and others to use it on a complex pipeline just to see a new tool take over and from what I remember it was a very fast switch. There was no gain in changing to Blue Ocean at the time, as our restarts where not working on it. So we had one UI that worked without support and another that didn't with it. Again I am not following it the topic anymore, so this might be fixed by now.
Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes
#75This looks like an improvement over what Jenkins 2.0 provides and I wish you guys good luck. I have used and vouched for Jenkins in several companies and some decent sized licenses were bought mainly because of my input. But to me, Cloudbees has done a major dick move making the stages not restartable in Jenkins 2.0, among other things. E.g: Dropping stage view out of nowhere and focusing only in Blue Ocean. I compla…
How are you liking GoCD? I've been looking for an alternative to GitLab for a while.
GoCD is a super simple CD platform (from user/developer point of view), easy to learn and with little possibility to snowflake it, with a Fan in dependency resolution that works nice.
The UI is not awesome but does the tricky for support teams and others.
BTW I have no association to any of the CD/CI companies I just like to work on this topic.
Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes
#76I use Jenkins and k8s and the objective is generally Spring services, so it sounds like this is for me.
Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes
#77Earlier quoted context omitted.
If you have more feedback, I'm happy to connect with one of the PMs or somebody from the Jenkins OSS team. I'm the founder/CEO of Codeship and we got acquired by CloudBees earlier this year. And I want to make sure that Jenkins + all CloudBees products get better :)
If you're interested I could provide UX blockers and annoyances from someone who has worked with Jenkins for close to 10 years now. Most of them would be about the UX around declarative pipelines and the frustrations around Configuration as Code with Jenkins.
Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes
#78Does anyone have Jenkins in production and found it to be reliable and pleasant to use? I had to do lots of Jenkins integrations some time ago, and even though I tried to minimize the number of plugins and make things as simple as possible, things would randomly break from time to time or exhibit weird behaviour etc. I had the impression that Jenkins is deeply conceptually confused about some of its concepts, e.g. ho…
Thanks for your feedback. We are trying to make things simpler with Jenkins X by using best of breed tools (git providers, issue trackers, cloud services, service meshes, security & code quality tools etc) with best of breed OSS tools like kubernetes, helm & skaffold to automate CI/CD on the cloud & kubernetes. One of the big changes to traditional Jenkins is we don’t expect folks to have to configure Jenkins, add/re…
Having a good set of plugins that integrate well should limit the complexity explosion and the number of edge cases users run into. So that's an improvement. It won't fix the Jenkins Heisenbugs though, of course :)
Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes
#79Earlier quoted context omitted.
How are you liking GoCD? I've been looking for an alternative to GitLab for a while.
What can we improve in GitLab that would make you stay?
Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes
#80Earlier quoted context omitted.
If you're interested I could provide UX blockers and annoyances from someone who has worked with Jenkins for close to 10 years now. Most of them would be about the UX around declarative pipelines and the frustrations around Configuration as Code with Jenkins.
Thanks, is it available in any repo? I would like to take a look of course.