Presumedly this is only of interest for those running Kubernetes?
Jenkins X: a CI/CD solution for cloud applications on Kubernetes
31–40 of 106 posts
Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes
#32I find this solution compared to the gitlab Auto Devops, frankly, underwhelming. We recently deployed AD in our self hosted gitlab instance and combined the SAST container checks with our production policies, it’s been rock solid. Add to this the fact we are able to manage all the production policies via the pipeline API’s and AD templates, the whole Jenkinsfiles deal seems far less scalable and difficult. I have no…
Sorry to hear you're underwhelmed! Did you check out the GitOps features for versioning all changes to all Environments in git with human approval? http://jenkins-x.io/about/features/#promotion Or the automated feedback on releases to all your issues as they move through Environments: http://jenkins-x.io/about/features/#feedback Or the automatic publishing of Helm charts to the bundled Monocular for all versions of y…
[deleted]
Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes
#33Just remember the name XKCD is already taken.
Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes
#34This 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 complained about in the channels that I had at the time and the response was, it's going to be unsupported from now on.
It's a super squechy thing to have such a useful feature bundled with a bunch of support and useless stuff that I don't care, and then charge me per node. I am migrating away from Jenkins into GoCD after close to 10 years using it, and don't get me wrong I don't feel happy doing this, but it's hard to justify it.
Fortunately the future looks bright, there are several interesting solutions available, Argo is super interesting to me, looking forward for Argo CD!
Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes
#35This 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…
They've changed their mind because of the community backlash: https://issues.jenkins-ci.org/browse/JENKINS-45455
Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes
#36This 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…
They've changed their mind because of the community backlash: https://issues.jenkins-ci.org/browse/JENKINS-45455
Thank you I did not know about that. Last time I checked with the sales guy it was not going to happen.
I hope they improve their ways, it's a nice tool and I invested a lot of my time into it, but right now GoCD is my default option from now on.
Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes
#37This solves part of a real problem. There are a lot of tools out there but end to end integration is left as an exercise to the reader. I'd love some out of the box sanity when it comes to devops, CI/CD, and cloudhosting. Instead I'm stuck building nw architectures, deployment scripting, dealing with archaic broken by default configs of misc bits and pieces, host configurations, build servers & CI/CD pipelines, etc. from scratch. Add log aggregation, security auditing, and other nice to haves that are actually not optional these days (what are you running blind and ignoring failed ssh attempts?) and you have a full explanation why so many companies make a mess of all of the above.
IMHO a lot of stuff in this space are either focusing on making life harder through added complexity to up-sell support or more services or on solving a narrow problem in such a way that you have to still take care of a lot of other stuff.
Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes
#38Earlier quoted context omitted.
They've changed their mind because of the community backlash: https://issues.jenkins-ci.org/browse/JENKINS-45455
Thank you I did not know about that. Last time I checked with the sales guy it was not going to happen. I hope they improve their ways, it's a nice tool and I invested a lot of my time into it, but right now GoCD is my default option from now on.
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 :)
Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes
#39Does 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…
We use it in all of our environments and it is extremely flexible, mostly reliable, but still feels like a hodgepodge of plugins and various components. Once you throw in a variety of build tools and deployment options etc, it can get rather unwieldy. Still, we use it for almost everything now (no forgotten cron jobs running on random servers) and it gets the job done. I often think we should investigate other options, but we have made such an investment at this point it would be a massive undertaking to move to something else.
Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes
#40So we already have a very custom Jenkins setup that builds containers, runs tests and creates test environments out of our pull requests in a k8s namespace. This seems to come with so many things that we already have. We have a few issues with it, like Jenkins suddenly deciding to build & test all branches/PRs in all repos, killing the server. • What is Jenkins X exactly, and how does it relate to Jenkins? Is it just…
The things you gain from switching to Jenkins X: * automated CI/CD for your kubernetes based applications using Helm Charts & GitOps to manage promotions (manual or automated) * a single command to create a kubernetes cluster, install Jenkins X and all the associated software all configured for you OOTB (including Jenkins, Nexus, Monocular etc): http://jenkins-x.io/getting-started/create-cluster/ - ditto for upgradin…
Does this work on DigitalOcean as well?