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

Jenkins X: a CI/CD solution for cloud applications on Kubernetes

jenkins.io

Post reply on HN
Print view View original

11–20 of 106 posts

Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes

#11

Post by tomhoward »

ku6pk wrote: post #10

In no attempt to bash OP at all, but what is the HN policy on links that have been posted before? Edit: Previous posts for reference https://news.ycombinator.com/item?id=16622215 https://news.ycombinator.com/item?id=16626765 https://news.ycombinator.com/item?id=16628313 https://news.ycombinator.com/item?id=16658640

It's only considered a dupe if the story/topic/product release has had significant attention (front page presence and discussion) in the past 12 months. None of these posts got much attention.

See dang's comments on the issue for the official position:

https://hn.algolia.com/?query=dang%20dupe%20porous&sort=byPo...

Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes

#12

Post by manigandham »

nodesocket wrote: post #5
tuananh wrote: post #3

Earlier quoted context omitted.

it's using github pages for the main website i think so i'm not sure if it's possible to setup custom domain + custom ssl cert for it?

Should be able to use CloudFlare and "flexible" SSL setup. CNAME at the apex pointing to GitHub pages.

You should set it to "Full" instead. That will use TLS but won't verify the domain name in the certificate like it does in "Strict" mode so you can still use Github pages.

Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes

#13

Post by ku6pk »

tomhoward wrote: post #11
ku6pk wrote: post #10

In no attempt to bash OP at all, but what is the HN policy on links that have been posted before? Edit: Previous posts for reference https://news.ycombinator.com/item?id=16622215 https://news.ycombinator.com/item?id=16626765 https://news.ycombinator.com/item?id=16628313 https://news.ycombinator.com/item?id=16658640

It's only considered a dupe if the story/topic/product release has had significant attention (front page presence and discussion) in the past 12 months. None of these posts got much attention. See dang's comments on the issue for the official position: https://hn.algolia.com/?query=dang%20dupe%20porous&sort=byPo...

Thanks for the informative post and link.

Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes

#14

Post by tomhoward »

ku6pk wrote: post #13
tomhoward wrote: post #11

Earlier quoted context omitted.

It's only considered a dupe if the story/topic/product release has had significant attention (front page presence and discussion) in the past 12 months. None of these posts got much attention. See dang's comments on the issue for the official position: https://hn.algolia.com/?query=dang%20dupe%20porous&sort=byPo...

Thanks for the informative post and link.

No worries! By the way, it's frowned upon if one person posts the same link repeatedly without getting any traction - eventually it just gets annoying, especially for people who watch the 'new' feed and keep seeing the same thing coming up. But the above posts seem to be submitted by different people, so it's all good.

Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes

#15

Post by fredsted »

So 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 a CLI utility that generates git repos, k8s clusters and Jenkinsfiles for us? Is it a fork of Jenkins?

• What would we gain from switching to Jenkins X?

• How does it work with our existing setup?

Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes

#16

Post by [deleted] »

LethargicStud wrote: post #7
nodesocket wrote: post #5

Earlier quoted context omitted.

Should be able to use CloudFlare and "flexible" SSL setup. CNAME at the apex pointing to GitHub pages.

Please don't do this. It gives the user the illusion that their connection is secure, but the connection between Cloudflare and the site is not secure. Arguably it's better to encrypt some of the route rather than none of it, but also giving people a false sense of security comes with its own drawbacks.

[deleted]

Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes

#17

Post by vasco »

fredsted wrote: post #15

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

> We have a few issues with it, like Jenkins suddenly deciding to build & test all branches/PRs in all repos, killing the server.

I suspect you're using the "organization folder" plugin-thing that periodically re-scans your origin (Github/Bitbucket) and builds all branches that it discovers. Check this out: https://stackoverflow.com/questions/45832235/how-to-restrict...

Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes

#18

Post by pronoiac »

nodesocket wrote: post #2

No TLS on jenkins-x.com, tisk tisk.

Huh, they're using Github pages. I thought if you set up a redirect - a C dns response - to whatever.github.io, that would soothe the ssl complaints in the browser.

Looking at the dns records, it looks like they didn't do this, and instead set up an A record.

I realized Github probably documents this, and found: https://help.github.com/articles/using-a-custom-domain-with-...

My suggestion would likely work for a www subdomain, but not for the apex domain.

Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes

#19

Post by ec109685 »

fredsted wrote: post #15

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

He answers this to some extent here:

> Relationship between Jenkins and Jenkins X Jenkins is the core CI/CD engine within Jenkins X. So Jenkins X is built on the massive shoulders of Jenkins and its awesome community.

> We are proposing Jenkins X as a sub project within the Jenkins foundation as Jenkins X has a different focus: automating CI/CD for the cloud using Jenkins plus other open source tools like Kubernetes, Helm, Git, Nexus/Artifactory etc.

> Over time we are hoping Jenkins X can help drive some changes in Jenkins itself to become more cloud native, which will benefit the wider Jenkins community in addition to Jenkins X.

Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes

#20

Post by jhasse »

LethargicStud wrote: post #7
nodesocket wrote: post #5

Earlier quoted context omitted.

Should be able to use CloudFlare and "flexible" SSL setup. CNAME at the apex pointing to GitHub pages.

Please don't do this. It gives the user the illusion that their connection is secure, but the connection between Cloudflare and the site is not secure. Arguably it's better to encrypt some of the route rather than none of it, but also giving people a false sense of security comes with its own drawbacks.

I think the user mostly cares about his connection to anything outside his network (e.g. for public WiFis).
Post reply on HN