You'd have to imagine that the term Blue Ocean would be trademarked for contexts like this
Blue Ocean
31–40 of 185 posts
Re: Blue Ocean
#32Seeing how much people recommend other solutions, I've actually moved from Travis to Jenkins, and never looked back. Yes, Jenkins has its issues (crappy UX, poor/awkward docs), but where it shines is the fact it's self-hosted, so I can SSH onto the instance to debug a failing build or replay it with a modified Jenkinsfile on the fly. I'm quite proud of the current setup we have; We're hosting our app with Google's Co…
how are you deploying secrets to your kuberenetes CI pipeline ? for example on a build, you create (I'm assuming) a new namespace.
it seems you are using glusterfs for your persistentvolumeclaim.. why not gce-pd ?
Re: Blue Ocean
#33We used Jenkinsfiles and pipelines recently. And also introduce Blue Ocean on our jenkins server. It come with a few glitches: Some plugins are not compatible with Blue Ocean, causing a white-page-of-death. However I found there where already issues created for them, i just turned off the plugin. But the biggest downer, is that blue ocean is just a small UI on viewing pipelines. Its not a replacement for jenkins. And…
The blank screen issue is extremely important to us to fix and we hope to have a change that fixes it shortly. It's a consequence of the new REST API depending on all the plugins installed on your system and exposing its data for JS plugins. If one plugin misbehaves then it 500s the REST response. We've got an approach to isolating per plugin failures so that you can load the page even if one plugin fails.
You can follow progress here https://issues.jenkins-ci.org/browse/JENKINS-39647
Re: Blue Ocean
#34I just want to mention that I loved the idea of BlueOcean at the begining. It looks sleak an works well with pipeline. However, for us it's unusable in production setting. I know that it's still in beta, but as one example it doesn't support parameters. When user starts a job through BlueOcean it will fail.(Officialy they don't plan to implement it any time soon as I found out) That means It stays disabled in our jen…
we too found that it doesn't support all of the original jenkin's features after we tried it , and its disabled at prod .
Anything in particular you believe is missing?
Re: Blue Ocean
#35I like blue ocean - but wouldn't moving to something like Concourse CI or GOCD be a better idea in the end?
We currently have a Jenkins setup and recently looked into both Concourse CI and GoCD as candidates for a change. We decided not go with Concourse, because it has a complex setup with bosh. Not much other use cases are really covered in the docs other than a simple one machine setup so you are left to figure things out on your own (don't really have the time to go into all that, jenkins + ec2 plugin is very simple an…
Good news is parameters are coming mid-Jan https://issues.jenkins-ci.org/browse/JENKINS-38805
Are there any other missing gaps you think are important? I'm keen to get them solved :)
EDIT: I missed the comment regarding search and that is something we are working on. I hope to have a design up for it on https://issues.jenkins-ci.org/browse/JENKINS-38982 in early January and we believe it should be quick for us to ship.
Re: Blue Ocean
#36Seeing how much people recommend other solutions, I've actually moved from Travis to Jenkins, and never looked back. Yes, Jenkins has its issues (crappy UX, poor/awkward docs), but where it shines is the fact it's self-hosted, so I can SSH onto the instance to debug a failing build or replay it with a modified Jenkinsfile on the fly. I'm quite proud of the current setup we have; We're hosting our app with Google's Co…
FWIW, Circle CI offers the ability to SSH in to build nodes and free nodes for public projects
Re: Blue Ocean
#37Seeing how much people recommend other solutions, I've actually moved from Travis to Jenkins, and never looked back. Yes, Jenkins has its issues (crappy UX, poor/awkward docs), but where it shines is the fact it's self-hosted, so I can SSH onto the instance to debug a failing build or replay it with a modified Jenkinsfile on the fly. I'm quite proud of the current setup we have; We're hosting our app with Google's Co…
FWIW, Circle CI offers the ability to SSH in to build nodes and free nodes for public projects
It's really well implemented too, it grabs authorised public keys from the github repo directly, so if you can push to the repo for the project, you can just ssh straight into the build machine. Magic.
Re: Blue Ocean
#38They should rethink the deployment model instead.
You cannot provision jenkins unattended without 3rd party hacks and undocumented features. Until this is fixed I recommend avoiding it, as you'll get pet servers. This is totally retrograde to the devops mindset. Now why should I not use that mindset if that proves to be productive at other parts of work?
Re: Blue Ocean
#39Hey 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 feedback to help us prioritise what to work on next.
If you've got any questions feel free to drop a comment here and Ill do my best to answer them or join our Gitter community [1]
Thanks, James
Re: Blue Ocean
#40They should rethink the deployment model instead. You cannot provision jenkins unattended without 3rd party hacks and undocumented features. Until this is fixed I recommend avoiding it, as you'll get pet servers. This is totally retrograde to the devops mindset. Now why should I not use that mindset if that proves to be productive at other parts of work?
I'd be very interested in i386's comments here.