We currently use Appveyor (good) and TeamCity (okish) and feed into Octopus Deploy. We have ~50ish projects (web, backend systems, embedded firmware) that all go through these systems. Works really well!
Jenkins Is Getting Old
151–160 of 340 posts
Re: Jenkins Is Getting Old
#152I receive vulnerability notifications for Jenkins, pretty much regularly... mostly XSS and RCE. https://www.cvedetails.com/vulnerability-list/vendor_id-1586... I'm just waiting for Apache to adopt it, and then it'll sit and fester like everything else in the Apache graveyard, full of vulnerabilities and slowly decaying. Those are just Jenkins core exploits too... there are so many many more for Jenkins plugins.... ht…
[deleted]
Re: Jenkins Is Getting Old
#153Earlier quoted context omitted.
Last I checked, there were a lot of little things that made it not possible to move to GitLab CI. E.g.: - Can't customize your git checkout process (e.g. shallow clone with depth, or merging source branch with target branch with certain strategy) - Can't make job run/not run based on filter on source branch/target branch/etc. of a merge request - Can't dynamically make certain jobs only run on certain agent machines…
You can definitely do all of your requirements, but likely as a result of recent features 1) you can customise the git checkout depth and style: https://docs.gitlab.com/ee/ci/yaml/#shallow-cloning https://docs.gitlab.com/ee/ci/yaml/#git-strategy 2) https://docs.gitlab.com/ee/ci/yaml/#onlyexcept-basic 3) https://docs.gitlab.com/ee/ci/yaml/#tags I'm not associated with gitlab at all but happy to give pointers if anyone…
2) was released in October, about six months ago [0]. I'd also like to add: as a user of GitLab for about a year now, their steady rate of feature releases has bene pretty pleasant, even if I can't take advantage of some right away.
[0] https://about.gitlab.com/2018/10/22/gitlab-11-4-released/#ru...
Re: Jenkins Is Getting Old
#154Jenkins is to CI, as Nagios is to monitoring.
Both work ?
No, the key difference is that Nagios has perfectly viable alternatives (Zabbix admin here and it's not the only one). Jenkins however has no alternatives.
Bamboo or whatever it is called now is typical Atlassian crapware. Expensive as fuck, eats more resources than the stuff it builds, and did I mention it is yet another half assed product that got shoddily integrated into the usual Atlassian lineup?
Gitlab CI is great for anything that is code (think build, test, deploy), but it is not suited for abstracting "non-development" jobs which can perfectly be automated in Jenkins (e.g. creation of a dev environment with fresh data from production). Plus it is Docker and the runners are polling - which means at minimum 10s startup time compared to milliseconds for a Jenkins shellscript job running on a ssh connected slave!
Github and friends are cloud which is a big no-no. We're placing too much power in the hands of AWS, GCE and Azure already, no way in hell it is a good idea to put private source code to a cloud provider.
Re: Jenkins Is Getting Old
#155I have been with jenkins since about 2010. At its peak I had to shepherd ~50 masters of varying ages, plugins and levels of customisations. Yes, it allowed repeatable builds, and it can be, in certain circumstances a very good replacement for cron jobs where you need to administer >5000 machines. However, it has an offensive UI, the plugin system appears to be designed to deliberately cause things to break, versionin…
We’re currently replacing Jenkins with EKS, and if it goes well, will consider doing the same with Circle. External partners have costs. And really the kind of things we need these things for here are pretty easy to configure in a Docker container. What we expect we’ll end up with after the Jenkins switch is Cloudformation templates we can hack into a Circle CI replacement. And we’d use GitLab if we could start over…
> replacing Jenkins with EKS
This doesn't make sense to me. Jenkins is a CI tool - that means it can build, test, and deploy your code.
EKS is a managed Kubernetes instance. That means it can run a collection of Docker containers.
I don't see how EKS can accomplish building or testing.
Re: Jenkins Is Getting Old
#156I receive vulnerability notifications for Jenkins, pretty much regularly... mostly XSS and RCE. https://www.cvedetails.com/vulnerability-list/vendor_id-1586... I'm just waiting for Apache to adopt it, and then it'll sit and fester like everything else in the Apache graveyard, full of vulnerabilities and slowly decaying. Those are just Jenkins core exploits too... there are so many many more for Jenkins plugins.... ht…
Last place I was at had their unmanaged Jenkins servers get compromised and used to run crypto miners.
Were they using an older version of Jenkins on the public internet? There's been a randomized GUID applied to the initial Jenkins admin password, which you can only access if you have direct access to the Jenkins install. I think this was added in 2016.
Re: Jenkins Is Getting Old
#157Hello, I see a lot of great feedback in this post. I am a product manager working at CloudBees, the primary corporate sponsor of Jenkins. Jenkins is now in the Continuous Delivery Foundation as well. While it is easy to bash on an inanimate object, there are some very dedicated and empathetic people who care deeply about the project. Some of those people do this work in their off-hours and some to this work as part o…
Jenkins configuration as code. It's hard to configure without going to all the files and options. You have several things to take care of: server config files, plugins, credentials, projects, etc. Going through xml files is not fun.
Also, having predetermine pipeline plugin configuration based on runner types would be nice. For example, if k8s I would expect k8s plugin + credentials + organization plugin. In many cases, the only thing I want is a pipeline which I can deliver code.
Do something with jenkins declarative and get rid of groovy script. The latter makes a mess in your files, the former is very limited. At the end you have to write groovy if you want things more bespoken. It would be nice to just use any language in a container as drone does for your plugins.
Re: Jenkins Is Getting Old
#158Earlier quoted context omitted.
I wish I could bring you here to see you do better. Or do you mean systemic corporate problems? In that case, I agree. It still doesn't change the fact that Jenkins does not make my job any easier. I'll spend a day worrying about Jenkins idiosyncrasies ("why can't I use a pipe in sh", "why did my bash escaping disappear completely", "why 'dir' doesn't work with a container build agent?! (JENKINS-33510)", "why this in…
I feel you, but why are your jenkins pipelines so complicated? I feel like your workplace's deployable artifacts should follow a familiar pattern and there should not be much guessing/re-inventing the wheel with jenkins scripts. I feel like complicated builds are usually the result of an application that is not very well thought out in the first place.
> I feel like complicated builds are usually the result of an application that is not very well thought out in the first place.
Welcome to the world of enterprise Java or .net programming. Loads upon loads of crap. Best served with multiple frontends (e.g. web + mobile) which need different npm versions to compile and all of it out of a single fucking pom.xml which is a nightmare in itself!
Re: Jenkins Is Getting Old
#159I have been with jenkins since about 2010. At its peak I had to shepherd ~50 masters of varying ages, plugins and levels of customisations. Yes, it allowed repeatable builds, and it can be, in certain circumstances a very good replacement for cron jobs where you need to administer >5000 machines. However, it has an offensive UI, the plugin system appears to be designed to deliberately cause things to break, versionin…
Agree in all cases. Bamboo was actually ok for a little while; but then they got rid of the cloud version which made it a bit more niche. I also like to plug VSTS in these conversations. It’s really nice to be able to drill down from feature roadmap to build status in a single tool without a lot of config. I haven’t built anything complex in it personally, but hear nothing but good things from the teams I work with w…
We’re running it on our own cloud provider. Do you not consider that self-hosting?
Re: Jenkins Is Getting Old
#160I have been with jenkins since about 2010. At its peak I had to shepherd ~50 masters of varying ages, plugins and levels of customisations. Yes, it allowed repeatable builds, and it can be, in certain circumstances a very good replacement for cron jobs where you need to administer >5000 machines. However, it has an offensive UI, the plugin system appears to be designed to deliberately cause things to break, versionin…
> " ... has an offensive UI... " > " ... suck massive genitals... " I cannot believe that this is the top-voted comment.
Yeah, almost like ideas are more important than the specific way they're expressed. Or are you one of those people who is always commenting on the web page chrome instead of what the article says?