- Improved validation and error handling for Amazon ECR added as a custom repository
- Fixed a bug with editing the Slack action causing deletion of attachments
When we develop new features, we try to keep things simple, yet with no compromise to flexibility. A couple weeks ago we delivered parameterized builds. Although it was met with very positive feedback from the community, some users missed the option to parameterize executions via the API as well.
This option has just been delivered: from now on, you can run a pipeline via the API and pass the parameters that will be available in all actions.
get podsmethod is deprecated and no longer used in K8s actions
In response to popular demand from Atlassian developers, HipChat notifications are now available in Buddy!
As you probably know, pipelines in Buddy can be run in three ways:
The last method can prove very powerful when properly put practice. For example, you can use it to monitor your servers or backup WordPress sites. However, the recurrent mode lacked advanced config settings, such as running the pipeline only on working days. We have addressed that by adding cron jobs to the pipeline settings.
Web development is a desktop thingie. You sit at your desk, sip coffee, and watch Buddy turn your code into beautifully crafted websites while you give an occasional poke to that Vault-Boy bubblehead you got when leaving your first job at the local burger joint.
A while ago we introduced trigger conditions letting you run actions only if there were changes in the repository. Now we’re adding another use case: running actions on certain values to environment variables. The feature is available in More options at the bottom of every action.
Recently, we’ve added a new authorization method for GKE (which stands for Google Kubernetes Engine) cluster solution in all K8s actions. Today, as we promised, we released its new authentication method: Service Account.
#in its name
14 days of unlimited trial. No credit card required.