Traveling Ruby VS Travis CI.com

If you absolutely need a native binary distribution for your apps, there is a project called Traveling Ruby that originated at Phusion, makers of the popular Phusion Passenger Ruby application server. It's worth noting that this project has a number of open issues that are aging and the latest commits are from 2021, so I'm not sure about its current status. There are also important caveats with regard to native extensions and Windows. Given the popularity of packages that require native extensions (like the XML/HTML library Nokogiri), you may find that this solution simply doesn't work for you.

You may be to get a precompiled binary with OpenSSL 1.1 statically linked. Maybe Traveling Ruby? https://github.com/phusion/traveling-ruby

There's really not much else in this space. The main alternative - Traveling Ruby - has limitations on Windows and I don't think it supports Ruby 3.0.

But even with all of the above, you're absolutely right, it is just easier to ship a binary blob. That's where the rewrite totally pays off. I just wonder whether the team has stressed all the options when it comes to keep ruby. There are packaging solutions which ship with its own interpreter, such as Travelling Ruby. And mruby could also generate a binary blob, although they'd have to open another can of works, such as finding replacements for dependencies such as net-ssh, which AFAIK can't be used with mruby. So in the end, maybe they did. And given the prevalence of go products in hashicorp, maybe it makes sense to just invest a bit more in it?

You could try using Traveling Ruby as an alternative to Ocra. I have only used Ocra in the past for this task, but I'd say it's worth a try.

Travis CI: This hosted CI/CD service can seamlessly integrate with code hosting platforms like GitHub.

TRAVIS: With the help of Travis CI, you can easily synchronize your GITHUB projects. Travis offers more language support than circleCI and also you can run test on linux and mac OS at the same time. For more info: https://travis-ci.org/

Automation is a critical tool for improving DevOps efficiency. Many cloud platforms offer enhanced automation solutions for DevOps activities, such as CI/CD. CircleCI, Jenkins, GitLab, and Travis CI are all examples of such tools used for continuous integration. These technologies provide uniformity and speed while requiring minimal human intervention.

And finally, the engineers need to be able to easily deploy to Kubernetes, which can either be done with the same tools or with specialized CI/CD tools, such as Jenkins, Circle CI, or Travis CI.

To deploy an application to production, more complex continuous integration and deployment solutions exist. Since Kubernetes is so common now that almost all CI/CD tools support it, it does not really matter if these solutions are particularly specialized on Kubernetes or not. You should rather compare different solutions again and see which best fits your needs. A good starting point are these tools: Jenkins, Codefresh, Travis CI, and Circle CI.

And it became quite a good conversation like, well, I wish that it would also update my GitHub Actions tree because of my Travis CI tree because I wish it did this, I wish it did that. I think the biggest users were the WG, the browser rendering engine people. They had some requirements they couldn't use until they were fixed. So we had a really good conversation there. But yeah, tech is never the hard part; it's always the people.

This tool is written in Golang and still used travis-ci as CI. Furthermore, some parts of the release process were still manually, such as uploading the assets to a GitHub release and generating the release notes. We wanted to have this automated.

You should use a service like Travis CI. Much easier than the route you are taking.

https://fastlane.tools https://danger.systems https://www.sonarqube.org https://codemagic.io/ https://travis-ci.org

Datree has really good integration with CicleCi, TravisCi, GitHub Actions, GitLab also.