19.03.5for Docker and
Execution time for the 'Prepare Environment' step is now displayed
[Build actions] Docker image dropdown menu has its tags properly sorted with semantic versions comming first
In this article, we'll show how easy it is to get a Java application running in AWS Lambda by using Buddy for your Continuous Integration and Continuous Deployment. In 15 minutes time, you're going to be running your software in the cloud.
AWS Lambda has become a powerhouse of software deployment. It encourages simple, self-contained, stateless functions that run themselves and eliminate a large portion of the traditional operational overhead that is associated with running software. Alas, many CI/CD tools have a lot of catching up to do before they're even close to the kind of ease that AWS Lambda offers.
The difference between Buddy and other CI/CD tools is that you can seamlessly add it to your existing setup with dozens of integrations. Right now, each integration is assigned to an individual user. One of the imnprovements we are currently working on is the ability to share the integration with other workspace members. During the works, we decide to change the ID's of the integrations from numerical to hash. This is important for users keeping pipeline configuration in YAML files as the ID defines which integration should be used in the action.
Numerical ID's will be suported for two more months. From February 2020 onwards, adding new or modifying existing actions will require the new type of ID.
While lots of people think of CI/CD as something that lets developers deploy software faster and more frequently, let us not forget about its core principle: testing. Without testing, it is impossible to keep high standards of the code which constitutes the website. However, testing does not stop with deployment. Once our application is on the server, it should be constantly monitored for performance. Performance is one of the key factors that determine the position of the website in Google, the difference between life or death in online business.
For this, we can use Lighthouse, an open-source tool allowing developers to run performance audits on their websites. Buddy incorporates this tool as a dedicated action that you can use recurrently for round-the-clock coverage, or after every deployment to check the impact of changes on the website.