Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Jenkins Is Getting Old

itnext.io

Post reply on HN
Print view View original

91–100 of 340 posts

Re: Jenkins Is Getting Old

#91

Post by pilif »

kristianc wrote: post #38
lultimouomo wrote: post #19

Earlier quoted context omitted.

The page is actually a medium post which immediately pops up an annoying modal trying to get you to give them your personal information and phones home who knows what kind of analytics. I'm not sure about the ethics of outline.com, but I can totally see why people are using it.

I'm not sure about the ethics of taking other people's content and putting it behind a paywall.

But it's Medium's content. You gave it away when you posted it here. In exchange, you got exposure[1]

[1]: https://theoatmeal.com/comics/exposure

Re: Jenkins Is Getting Old

#92

Post by bluGill »

rjeli wrote: post #3

I’d never used Jenkins before, a few weeks ago I needed to do some CI that was more complicated than just pytest or whatever. Installed jenkins, put together a dockerfile, connected the github hooks and It Just Works. I’m a happy customer

The problem is people want to do really complex things with Jenkins. A few hundred repos, each with dozens of builds; Multiple operating systems... There is a reason a team of 10 works full time to administer our CI system: it is complex (the CI system is more than Jenkins)

Re: Jenkins Is Getting Old

#93

Post by buzer »

stabbles wrote: post #81

Jenkins's plugin manager is absolutely terrible. If you're stuck on an older version of Jenkins, you better not click the "refresh" button in the plugin management page, cause otherwise the page is just filled with red warnings saying that the latest version of each plugin is incompatible or has dependencies that are incompatible with your current Jenkins version. There is afaik no way to install the last plugin that…

> There is afaik no way to install the last plugin that was compatible with your version of Jenkins.

Probably not directly, but if you know the version, you can download the HPI and install it manually. Jenkin's Docker build also contains install-plugins.sh (https://github.com/jenkinsci/docker/blob/7b4153f20a61d9c579b...) that you can use to install specific version of plugin via command line.

Re: Jenkins Is Getting Old

#94

Post by flowardnut »

evv555 wrote: post #35
FrenchyJiby wrote: post #18

I sincerely wish I could move away from Jenkins for the reasons stated in TFA (GUI-oriented, slow, hard to backup/config, test-in-production mentality and boundless plugins) but I've never found something that fits the bill. The much-touted repo integrations (travis, circle...) all have an exclusive focus on build-test-deploy CI of single repos. But when you have many similar repos (modules) with similar build steps…

>Anyone got a sane alternative to jenkins for us poor souls? I haven't tried this yet myself but AWS CodePipeline lets you have Jenkins as a stage in the pipeline. You use Jenkins only for the bits you need without the extra plugins. The resulting Jenkins box is supposed to be very lean and avoid the problems you describe.

Performance isn't great. We're using codepipeline/codebuild (triggered via jenkins), and it's common to wait 30 seconds while the step is being created

Cloudbuild on the gcp side has had much better performance

Re: Jenkins Is Getting Old

#95

Post by KaiserPro »

I 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, versioning the flows is difficult, unless you rely on plugins (which break) or want to learn groovy.

Automating and making jenkins it's self repeatable is a soul sapping task.

In short, jenkins needs to disappear.

Yes, cirle is crap, bamboo suck massive genitals.

However I have had great success with gitlab runners. Now that gitlab is actually reliable, they are a brilliant first class integration into a git workflow.

Re: Jenkins Is Getting Old

#96

Post by cjbprime »

It's true that Jenkins is old, and has systemic architecture problems which mean that I'm sure we haven't seen the last RCE for it. RCEs in build systems are a nightmare because build systems necessarily end up knowing secret tokens.

But drone.io is no kind of replacement. It only works with Docker containers! Even small Jenkins installs can quickly end up with Windows targets, mobile builds, etc.

Re: Jenkins Is Getting Old

#97

Post by hizanberg »

user5994461 wrote: post #52
FrenchyJiby wrote: post #18

I sincerely wish I could move away from Jenkins for the reasons stated in TFA (GUI-oriented, slow, hard to backup/config, test-in-production mentality and boundless plugins) but I've never found something that fits the bill. The much-touted repo integrations (travis, circle...) all have an exclusive focus on build-test-deploy CI of single repos. But when you have many similar repos (modules) with similar build steps…

TeamCity from JetBrains is the same thing as jenkins, except the core features are working core features instead of broken plugins. It's paid software though, you get what you pay for. https://www.jetbrains.com/teamcity/ On the other hand there is Bamboo from Atlassian. https://www.atlassian.com/software/bamboo I really don't understand this mentality of there is no better tools when there are better tools than jenki…

TeamCity has an extremely generous 100 build configuration limit, if you’re exceeding that, than in all likelihood you’re getting far better value from it than the additional licensing cost.

Re: Jenkins Is Getting Old

#98

Post by detaro »

pilif wrote: post #91
kristianc wrote: post #38

Earlier quoted context omitted.

I'm not sure about the ethics of taking other people's content and putting it behind a paywall.

But it's Medium's content. You gave it away when you posted it here. In exchange, you got exposure[1] [1]: https://theoatmeal.com/comics/exposure

As far as I know, Medium writers opt-in to this, in exchange for money if a paying user reads the article.

Re: Jenkins Is Getting Old

#99

Post by fizwhiz »

KaiserPro wrote: post #95

I 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…

Why does a fictional butler offend you?

Re: Jenkins Is Getting Old

#100

Post by sudofail »

What I'd like to see is a CI/CD engine backend. Most CI/CD solutions have relatively the same feature set:

- Code builds

- Code deploys

- Git Hooks

- Parallel builds

- Matrix builds

- Build as configuration

- Etc

If there were an engine that supported these features, the community could create a number of frontends that target their specific needs.

Jenkins was held back, in my opinion, for a number of years by its antiquated UI. And while Jenkins does have an API of sorts, writing a new UI for it is not a simple task.

I've used Drone for a while, and it gets a lot of these things right, but at the end of the day it is a holistic, integrated solution.

I'd like to see a composable, modular CI/CD framework.

Post reply on HN