RabbitMQ is a multi-protocol messaging broker written in Erlang. It implements AMQP (Advanced Message Queuing Protocol) and can be further extended with STOMP (Streaming Text Oriented Messaging protocol), MQTT (Message Queuing Telemetry Transport), and other protocols.
- If an error occurs during the launch of a microservice (e.g. database seeding will fail because of badly configured SQL scripts) the build action will finish as failed. Until now, the build was waiting 5 minutes until the service had launched and happily continued despite the errors
- [Blockchain] The Ganache [ETH] service has been added to YAML/API
Telegram is a highly successful instant messaging service with over 200 million active monthly users. Our integration lets developers send automatic messages on finished builds and deployments to individual profiles, announcement channels and team groups.
Since the very beginning, we strived to make Buddy as intuitive as possible. We’ve come a long way since the beginnings (who remembers this?), but we never lost sight of our core values: simplicity and ease of use.
Let’s assume you’re a happy Buddy user with a bunch of meticulously configured pipelines. They are helping you deliver some awesome websites to awesome clients for awesome cash. In general, everything is awesome.
Suddenly, your CEO drops in and says you’re moving all your repos from GitHub to GitLab, and so should you with Buddy. “Oh no!” you think “Now I have to export all pipelines to YAML, create a new project for each repo, import the pipelines back in, and pray to the Holy Pixel I didn’t mess anything up! Not to mention I’ll lose the whole execution history!”
- Brand new build action view
- It is now possible to change the URL of the project
- Fixed a bug which prevented from adding webhooks for URL’s with capital letters in the protocol
- When a user didn’t have email address set in the account tried to commit changes online, the system was crashing because jgit requires the name to work. Fixed
- Until now, the YAML validator didn’t provide details what went wrong during the .yml parsing. From now on, full information is available on the Activity screen
Although Buddy’s actions are preconfigured, this doesn’t mean it gives you any less control over your workflow. In fact, each action can be fully modified, allowing you to change the Docker image, install packages required by your app, attach databases, and so on.
- [HTTP request] You can now set a timeout in the action
- [YAML] When switching the project from GUI to YAML Buddy will now automatically scan all branches (until now you had to push changes in the repo to process them from yaml)
- [Env Vars] Improved support for environment variables when testing an action in a pipeline
- [K8s] Updated kubectl version to 1.12.0 in all K8s actions
This week brings good news for developers orchestrating containers on AWS clusters: Buddy now officialy supports Amazon EKS!
In other words, if Jeff Bezos is your man and you often run
kubectl apply or
kubectl set image, you can finally benefit from the blessings of Buddy’s automation.
Buddy has always been about power and flexibility. One of the things that you lacked was the ability to use the artifacts from one pipeline in another. We’re happy to announce you can now do this with the dedicated Copy Files action.