Travis CI is an open source continuous integration platform, that enables users to run and test simultaneously on different environments, and automatically catch code failures and bugs.
$69
per month 1 concurrent job
Waves
Score 10.0 out of 10
N/A
Waves is an all-encompassing gateway blockchain protocol, from Waves Technologies in headquartered in Berlin. Leveraging the Waves protocol, the solution is designed to offer a developer-friendly infrastructure as an experimental ground for innovation.
TravisCI is suited for workflows involving typical software development but unfortunately I think the software needs more improvement to be up to date with current development systems and TravisCI hasn't been improving much in that space in terms of integrations.
There really is no scenario that Waves could not be used well suited for a studio environment. For instance, when I have someone come over to record, I use waves tune realtime in post production. And it really helps just get the flat/sharp notes on key easily. And the Abbey Road collection!! WOW!!! It sounds so good! Also, I use the API and SSL on my master chain to give it that "polished" feel in the end
I think they could have a cheaper personal plan. I'd love to use Travis on personal projects, but I don't want to publish them nor I can pay $69 a month for personal projects that I don't want to be open source.
There is no interface for configuring repos on Travis CI, you have to do it via a file in the repo. This make configuration very flexible, but also makes it harder for simpler projects and for small tweaks in the configuration.
TravisCI hasn't had much changes made to its software and has thus fallen behind compared to many other CI/CD applications out there. I can only give it a 5 because it does what it is supposed to do but lacks product innovation.
After the private equity firm had bought this company the innovation and support has really gone downhill a lot. I am not a fan that they have gutted the software trying to make money from it and put innovation and product development second.
Jenkins is much more complicated to configure and start using. Although, one you have done that, it's extremely powerful and full of features. Maybe many more than Travis CI. As per TeamCity, I would never go back to using it. It's also complicated to configure but it is not worth the trouble. Codeship supports integration with GitHub, GitLab and BitBucket. I've only used it briefly, but it seems to be a nice tool.
Waves seems to be the industry standard for mixing plugins. It integrates well with most DAWs and even has the option for Waves sound grid for live mixing. Using a DAW like Cubase, Protools, etc could introduce latency, while Sound Grid provides a near latency-free experience. Other solutions could prove to be difficult to implement.
It's improved my ability to deliver working code, increasing my development velocity.
It increases confidence that your own work (and those of external contributors) does not have any obvious bugs, provided you have sufficient test coverage.
It helps to ensure consistent standards across a team (you can integrate process elements like "go lint" and other style checks as part of your build).
It's zero-cost for public/open source projects, so the only investment is a few minutes setting up a build configuration file (hence the return is very high).
The .travis.yml file is a great way for onboarding new developers, since it shows how to bootstrap a build environment and run a build "from scratch".
It gave me the ability to tune vocals without them sounding "autotuned," therefore, making the singer feel like they sang it that much better. Just a confidence booster.
It gives me the opportunity for simply mastering a song. If a customer only wants a song mastered, I can effectively do that.
It is a bit costly when you first purchase, but it makes up for itself when you need it. I feel like it was money well spent.
