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

Blue Ocean

jenkins.io

Post reply on HN
Print view View original

131–140 of 185 posts

Re: Blue Ocean

#131

Post by sytse »

drdaeman wrote: post #103
aeharding wrote: post #88

Earlier quoted context omitted.

Just a note - you can host your own CI node (runner) for project(s) on gitlab.com. It's super simple to setup, too. https://docs.gitlab.com/runner/install/linux-repository.html

This doesn't solve issues in runner-to-base comms. I had tried this kind of setup relatively recently, and almost every 10-15th build had failed for me because GitLab wasn't healthy (502 from Docker registry or problems up/downloading artifacts between stages, etc.) Fully self-hosted looks like the only sane way. Harder to set up, but at least one can check the whole chain that way.

Sorry about GitLab.com having performance problems. Self hosted is indeed the only way to work around it in the short term. I hope you can set it up quickly. Please use the Omnibus packages that should install in a few minutes https://about.gitlab.com/installation/

Re: Blue Ocean

#132

Post by robinhood »

aeharding wrote: post #85
sytse wrote: post #21

Earlier quoted context omitted.

GitLab CI has proper Docker support. You can set a default docker image for each runner `--docker-image ruby:2.1` or set one for the project in the .gitlab-ci.yml file. For more information see https://docs.gitlab.com/ce/ci/docker/using_docker_images.htm... Did you know GitLab also comes with a private container registry? https://about.gitlab.com/2016/05/23/gitlab-container-registr...

Also notable is services like docker-in-docker (and privileged docker containers) are allowed, which is a huge win over services like Atlassian's Pipelines. Without dind, it's really hard/annoying to us CI/CD to build docker images. But with Gitlab, they also provide a place to store docker images (the "registry") right next to your code, for free! At work, we're investigating moving to Gitlab for everything except i…

Thanks for the comment! Group-level integration with JIRA is a nice idea. I've created an issue for this [1]. If you would like to give us more details on how we could achieve this, or give us some insights of your use cases, please comment in this issue!

[1]: https://gitlab.com/gitlab-org/gitlab-ce/issues/25867

Re: Blue Ocean

#133

Post by debacle »

i386 wrote: post #39

Hey there, I am the community leader for Jenkins Blue Ocean and Product Manager for the project at CloudBees. It's really great to see Jenkins users getting excited about Blue Ocean! Please let us know if there are any missing features that are blocking your team from adopting Blue Ocean. We know there are some gaps between Jenkins Classic and Blue Ocean and while we have some good ideas, we are relying on your feedb…

How would a non-Java developer best contribute to Jenkins?

Re: Blue Ocean

#134

Post by mdekkers »

swozey wrote: post #95
sytse wrote: post #67

Earlier quoted context omitted.

I think there are two aspects to arbitrary builds: 1. Periodic jobs (not linked to a pushed commit) 2. Not linked to a git repo At GitLab we try to have 'infrastructure as code'. We think builds should be under version control to allow for collaboration. But periodic jobs make a lot of sense and it is discussed in https://gitlab.com/gitlab-org/gitlab-ce/issues/2989

The lack of arbitrary jobs in Gitlab is one of my huge pet peeves regarding it. I've used Gitlab-ee for a year now and really enjoy it for CI/CD stuff. But sometimes I want to throw up a quick shell job that is something super simple, like backing up a database, cleaning up docker images, things like that. I'm used to storing these in Jenkins/Bamboo so that they aren't left hidden on a server in a cron job. I can do…

look at stackstorm for that kind of stuff (and lots of other cool things). Right tool for the job, etc.

https://docs.stackstorm.com/rules.html

Re: Blue Ocean

#135

Post by dserodio »

mitchty wrote: post #101
i386 wrote: post #34

Earlier quoted context omitted.

Anything in particular you believe is missing?

The ansi output color plugin doesn't work with output. Nor the build timestamp plugin. The PR interface only works with Github, should also work with bitbucket pull requests. And the most annoying, when blue ocean is tailing a job thats running, it uses 100% cpu on safari. Those are the biggest issues I find with it as of today, otherwise its great for a manager mode until then.

> when blue ocean is tailing a job thats running, it uses 100% cpu on safari

Also on Chrome and Firefox

Re: Blue Ocean

#136

Post by Felipe_Artur »

aeharding wrote: post #85
sytse wrote: post #21

Earlier quoted context omitted.

GitLab CI has proper Docker support. You can set a default docker image for each runner `--docker-image ruby:2.1` or set one for the project in the .gitlab-ci.yml file. For more information see https://docs.gitlab.com/ce/ci/docker/using_docker_images.htm... Did you know GitLab also comes with a private container registry? https://about.gitlab.com/2016/05/23/gitlab-container-registr...

Also notable is services like docker-in-docker (and privileged docker containers) are allowed, which is a huge win over services like Atlassian's Pipelines. Without dind, it's really hard/annoying to us CI/CD to build docker images. But with Gitlab, they also provide a place to store docker images (the "registry") right next to your code, for free! At work, we're investigating moving to Gitlab for everything except i…

Hi! Thanks for your kindness =)

We have a couple of open issues about integration with multiple JIRA projects: https://gitlab.com/gitlab-org/gitlab-ce/issues/25541 and https://gitlab.com/gitlab-org/gitlab-ce/issues/25758. Having group level integration can be a good solution for these requests. We will talk about it on those issues feel free to join the discussion.

Re: Blue Ocean

#137

Post by mi100hael »

petepete wrote: post #9
nubela wrote: post #4

Earlier quoted context omitted.

Why Gitlab CI? What makes it better than Jenkins?

I think the consensus is that Jenkins offers more power and flexibility at the cost being more complicated to set up. GitLab CI is easier to get up and running with and superbly integrated with GitLab (as one would hope).

I dunno, I found the opposite. Jenkins is an easy stand-alone package that I can just install & immediately navigate to the UI. GitLab-CI requires you to install & configure & link "runners" in a manner that I found less intuitive.

Re: Blue Ocean

#138

Post by corney91 »

mtalantikite wrote: post #129
haldean wrote: post #98

Earlier quoted context omitted.

You can "apt-get install jenkins" and go straight to the webui. Or are you talking about restoring a configuration as well?

I'd guess the OP means restoring configs and the fact that Jenkins setups tend to turn into snowflake servers. Here are some issues: - State is stored on the filesystem across a bunch of XML files, rather than in a DB. - Configuration of Jenkins itself happens primarily from the UI rather than in config files. This makes it very difficult to provision automatically. - No HA story. Or there is a workaround and it reli…

I agree Jenkins isn't the easiest to automate but surely the fact that it's all XML files makes it easier than a database -- using config management you can install Jenkins and template out the necessary configuration file(s). I much prefer systems that use files instead of the db for configuration...

Re: Blue Ocean

#139

Post by dserodio »

jacques_chester wrote: post #68
deng wrote: post #7

Earlier quoted context omitted.

Well, that's Jenkins in a nutshell. You usually need to extend Jenkins with lots of plugins because they provide functionality that should have been in core in the first place. Then you realize that those plugins are not properly sandboxed and often do not work well together (especially with multi-configuration builds), not to speak of how updating Jenkins becomes a nightmare with plugins breaking left and right beca…

In fairness, Jenkins did not have the benefit of hindsight. Plugins were the this-is-how-you-support-extension architectural style of the period (see also Wordpress, Eclipse). I've been working on a Concourse tutorial video series. One of the points I've made is that plugins are unsafe to compose. They need to know too much about each other to prevent interference. Concourse instead composes on resources, which all h…

I'd love to see -- or even better, read :) -- about how you "compose on resources".

Re: Blue Ocean

#140

Post by oblio »

pm90 wrote: post #113
alexellisuk wrote: post #104

This news is from September, I gave my first impressions on Hacker News then, here's my blog post including an interview from the team behind Blue Ocean. http://blog.alexellis.io/tag/jenkins/ They are doing a great job at reinventing JenkinsCI (but remember it's still Java)

What's wrong with Java?

Resource usage, especially RAM. And I say this as a longtime Jenkins admin.
Post reply on HN