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

101–106 of 106 posts

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

#101

Post by theptip »

pas wrote: post #99
theptip wrote: post #93

Earlier quoted context omitted.

Thanks for taking the time to ask. My primary concern is that instead of polishing the features that have already been released, the platform is trying to do too many new things. Some of that stuff is cool (k8s monitoring integration, though EEP is too expensive for me, and my Grafana dashboard does basically the same thing), while some of it seems a bit bloated (SAST/DAST for example, which was a few lines of code t…

> SAST/DAST for example, which was a few lines of code to implement ourself Could you elaborate on that please?

Sure, if you dig into the SAST Dockerfile you'll see that it's running `bandit` if you're in a Python repo. So add this step to your .gitlab-ci.yaml:

  bandit-check:
    # This check runs Openstack Bandit, a Python static analysis tool that checks for 
  security issues.
    stage: unit-test
    script:
    - bandit -r -x 'tests,test_,/migrations/,./src/' -c bandit-config.yaml -ll ."
DAST uses ZAP, which you can also run in a Dockerfile yourself.

Of course there's also some window dressing to display the errors on the main MR, instead of having to dig into a step failure, but that doesn't make a meaningful difference to me.

(This feature could well have moved on since it was first implemented, that was the only time I dug into it).

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

#102

Post by sytse »

pas wrote: post #98
InternetOfStuff wrote: post #85

Earlier quoted context omitted.

Sytse, thanks a lot for being present in the community. It's most appreciated, and I always look forward to your comments. With regards to your question: I agree with user kerny. Stop packing stuff on top. What I want from Gitlab is to use it to manage my repos. If you improve that aspect (which is already fine though IMO), you'll make me happier. If you improve Gitlab integration with other CI tools, you'll make me…

GitLab does one thing. And GitLab CI/CD does one other thing. GitLab Image Registry does yet an other thing pretty well. And GitLab Omnibus also does one thing. (It bundles those.) Making it more configurable (as in makeing more features disable-able) would be nice though.

Thanks InternetOfStuff for using GitLab and both you and pas for your kind words.

We think there is a lot of value in a single application for the complete DevOps lifecycle https://about.gitlab.com/2017/10/11/from-dev-to-devops/ and we'll continue to build that in 2018.

We'll also keep improving the existing parts of GitLab, such as the managing of repo's https://about.gitlab.com/direction/#code-review

We want to play nice with other CI tools and for example have great support for Jenkins https://about.gitlab.com/features/jenkins/

If you didn't use our CI since 1.5 years give it a shot, it is very good https://about.gitlab.com/is-it-any-good/#gitlab-ci-is-a-lead...

We don't want you to get suck with an integrated solution that is bad. We'll make sure that we'll keep improving every aspect of GitLab together with the wider community (100+ contributions in the last month). And if you want to use GitLab with something else you're welcome to https://about.gitlab.com/features/github/

And as a GitLab user you can turn off the things you don't want under project settings https://docs.gitlab.com/ee/user/project/settings/#sharing-an...

Please let us know if there is anything we should add there.

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

#103

Post by sytse »

theptip wrote: post #93
sytse wrote: post #73

Earlier quoted context omitted.

What can we improve in GitLab that would make you stay?

Thanks for taking the time to ask. My primary concern is that instead of polishing the features that have already been released, the platform is trying to do too many new things. Some of that stuff is cool (k8s monitoring integration, though EEP is too expensive for me, and my Grafana dashboard does basically the same thing), while some of it seems a bit bloated (SAST/DAST for example, which was a few lines of code t…

Thanks for voicing your valid concerns.

Regarding polish we're improving existing features all the time, we're very close to a big refactor of the merge request view.

Regarding CI/CD environment deletion I can find it in the API https://docs.gitlab.com/ee/api/environments.html#delete-an-e... but I'm not sure about the interface.

Support has had trouble scaling, we just hired a director to make sure we get on track, sorry about that.

Having you builds fail intermittently is bad, this should be a problem only on GitLab.com Reliability of that is not where it should be and we're taking drastic actions to improve it. If anyone reading this is up for the challenge please see https://jobs.lever.co/gitlab/a9ec2996-b7b6-4d87-aed0-1fc2ce3...

Regarding the yearly pricing this is a tradeoff we made, see point 7 of https://about.gitlab.com/handbook/product/pricing/#when-is-a... I thought we offered a 30 day money back guarantee but I can't find it onhttps://about.gitlab.com/pricing/ so I'll ask product marketing what is up with that.

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

#104

Post by dsumenkovic »

sytse wrote: post #103
theptip wrote: post #93

Earlier quoted context omitted.

Thanks for taking the time to ask. My primary concern is that instead of polishing the features that have already been released, the platform is trying to do too many new things. Some of that stuff is cool (k8s monitoring integration, though EEP is too expensive for me, and my Grafana dashboard does basically the same thing), while some of it seems a bit bloated (SAST/DAST for example, which was a few lines of code t…

Thanks for voicing your valid concerns. Regarding polish we're improving existing features all the time, we're very close to a big refactor of the merge request view. Regarding CI/CD environment deletion I can find it in the API https://docs.gitlab.com/ee/api/environments.html#delete-an-e... but I'm not sure about the interface. Support has had trouble scaling, we just hired a director to make sure we get on track, s…

To add to sytse's answer

Environments currently can't be deleted from the UI. We have an issue open about it at - https://gitlab.com/gitlab-org/gitlab-ce/issues/25388

The issue gained a lot of traction. It's scheduled for 11.1.

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

#105

Post by sytse »

wesleytodd wrote: post #69
sytse wrote: post #62

Earlier quoted context omitted.

Thanks for using GitLab. We want to be supportive of cherry picking GitLab features. For example we just release CI/CD with GitLab for GitHub https://about.gitlab.com/features/github/ Is there something we can add to GitLab to make it more composable?

Thanks for the good work on GitLab, I tell everyone I can how great of an experience it was to use it at my last company. The CI integration was GREAT, the ui is pretty nice and the maintenance overhead was minimal.

Thanks, great to hear that.

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

#106

Post by jhurewitz »

sytse wrote: post #103
theptip wrote: post #93

Earlier quoted context omitted.

Thanks for taking the time to ask. My primary concern is that instead of polishing the features that have already been released, the platform is trying to do too many new things. Some of that stuff is cool (k8s monitoring integration, though EEP is too expensive for me, and my Grafana dashboard does basically the same thing), while some of it seems a bit bloated (SAST/DAST for example, which was a few lines of code t…

Thanks for voicing your valid concerns. Regarding polish we're improving existing features all the time, we're very close to a big refactor of the merge request view. Regarding CI/CD environment deletion I can find it in the API https://docs.gitlab.com/ee/api/environments.html#delete-an-e... but I'm not sure about the interface. Support has had trouble scaling, we just hired a director to make sure we get on track, s…

It is actually 45 days and in our subscription terms, Section 5.2: "If Customer terminates this Agreement pursuant to Section 6.2 within 45 calendar days from receipt of the initial invoice for the Licensed Materials, GitLab will refund all Fees paid hereunder."
Post reply on HN