- From now on environment variables in pipelines can be managed by all users with the ‘Pipeline: Manage’ level of permissions. You still need to be an admin to manage the project and workspace tiers of the variables, though
- There’s no need to clear the cache upon changing the clone depth in the pipeline settings anymore
- Upload from scratch is now available in AWS Elastic Beanstalk deployments
- Docker images with self-signed certificates can now be pushed to the registry
- Transactions and invoices have been separated in the Billing tab
- Fixed bug with wildcard pipelines in recurrent mode not working correctly if the option ‘execute only if there were changes in the branch since the last execution’ was set
This week we host the team behind Flow, the awesome project management suite for teams, that uses Buddy to deploy and monitor their marketing site.
Buddy is a delivery automation tool that heavily relies on integrations with other services like AWS or Google Cloud.
Until now, the integration was performed at the moment an action has been added for the first time. If you wanted to add more integrations to a service, you had to do it from the Integrations tab in My-ID settings.
- Better support of multiple integrations in pipeline actions:
- Deployments: AWS S3, Elastic Beanstalk, CodeDeploy, Lambda, DigitalOcean, Rackspace, Heroku, Shopify, Google Cloud Storage, Google App Engine
- Notifications: Slack
- DevOps: AWS CLI, Heroku CLI, Invoke Lambda function
- Cache invalidation: AWS CloudFront, Google CDN, Cloudflare
- Improved support of revoked GitHub integrations. Until now, if a user revoked a GitHub integration we simply showed an empty list of repositories. From now on, you will be asked to authorize in the GitHub account once again
- Buddy parameters are now working properly in the CloudFront’s ‘distributionID’ field
- Fixed bug with listing only 50 most recent Docker image tags in the Docker build action
- Fixed bug with Elastic Beanstalk applications not being deployed properly if they contained spaces in their name (thanks Paul for reporting this)
- Fixed emoji support in readme files 😎
At the heart of Paris, a team of 20 mobile experts at Green Panda uses Buddy’s pipelines to update their games played by 45 million gamers worldwide.
As you know very well, we put special emphasis on reducing pains with configuring your CI/CD process. Every delivery pipeline can be configured literally in a dozen of minutes.
This is especially important for those who never tried automation in fear of complicated and time-consuming configuration. Automation veterans, on the other hand, are free to set up their delivery with a YAML file. What we missed, however, was the ability to export and import pipelines from the GUI. For example, if you wanted to move them between workspaces, or make a backup of your process.
- It is now possible to import/export pipelines
- Fix bug with ignore rules not working correctly if white spaces were added
- [API] The method of adding a branch to the project has been refactored and improved. Thanks to In’saneLab for reporting this
- Until now, if you run a pipeline with ‘clear cache’ turned on, you had to wait until the cache is cleared before the build kicks off. Now the execution is performed immediately, with cache files first moved to trash and removed when the build is over
- Monitoring actions (Web, Ping, TCP) now run two additional retries before informing of errors
- You can now log to a private Docker registry without the need of pushing an image in the Docker build action
- You can now specify the depth of
git clonefor a pipeline. By decreasing the depth, you can speed up your builds and reduce the size of built Docker images
- Errors related to SSL certificates are now ignored in the Web monitoring action. This way you can also monitor your Dev and Stage servers with self-signed certificates
- From now on, immediately after receiving a webhook from GH/BB/GL the status is returned, with all remaining information and additional requests to the provider run in a separate thread. This way we managed to solve the problem with timeouts that some of our users have observed in Bitbucket
- When GitHub/Bitbucket wasn’t able to deliver a webhook several times in a row (usually due to networking issues), the webhook was getting suspended. You can now solve this by clicking ‘Refresh’ in the Code tab without the need of removing the old webhook
docker loginin the Docker build action is now run with the parameter
passwordparameter is no longer recommended by Docker)
- The dedicated PHPUnit action has been rebranded to PHP because a vast majority of users used it solely for downloading PHP dependencies with Composer (only a small percent was running unit tests). Bear in mind, however, that the Docker image is the same and you can still use it to run PHPunit tests
- Java upgraded to 1.8.0_144
Arsenal, the newly launched content marketing platform for game developers, broadcasters and influencers, uses Buddy to deploy their dockerized API service and web portal to Amazon ECR & EC2.
- Many users were reporting than monitoring actions are too ‘sensitive’. From now on, the action will try to connect 3 times until it’s marked as Failed
- You can now select a single file to archive in the Zip action instead of a directory only
- Deployment to AWS ElasticBeanstalk & AWS Code Deploy have been optimized for performance + the logs for both actions are now much clearer
- You can now select the config file from the pipeline filesystem in Apply deployment to K8s and GKE actions
- The commit input in the file editor now supports
- Fixed bug with commits from external repositories not synchronizing correctly because of special characters in the name
- Fixed bug in the AWS S3 action with incorrect path invalidation if both ‘cloudfrontId’ and Buddy parameters in the ‘RemotePath’ were provided
- Fixed bug with Zip action not packing files and directories starting with
- Fixed bug with wrong files getting uploaded to the server because some ignore paths in the Rsync action were not working correctly
- Fixed bug with errors showing for some server certificates in the Web Monitoring action
One of the most important components of pipelines is the filesystem: a reserved disk space with a clone of your repository, where Buddy installs dependencies, merges & compresses the assets, and generates artifacts.
With this week’s release we’ve added a UI distinction for three types of files and folders in the filesystem: