CI/CD for Elixir
đź“š Learn more about Elixir action features, integrations and alternatives.
With Buddy, you can create a pipeline that builds, tests, and deploys Elixir applications on a push to Git. The configuration is super simple and takes 10 to 15 minutes.
Example Elixir pipeline
1. Select your Git repository
Buddy supports all popular Git hosting providers, including GitHub, Bitbucket and GitLab. You can also use your own private Git server, or host code directly on Buddy.
Supported Git providers
2. Add a new delivery pipeline
Enter the pipeline's name, select the trigger mode, and define the branch from which Buddy will fetch your code:
Exemplary pipeline settings
Trigger modes
- Manually (on click) — recommended for Production
- On events (automatic) — recommended for Development
- On schedule (on time interval) — recommended for Staging/Testing
Event-based triggers allow you to run pipelines whenever a push is made to any branch in the repository, or whenever a branch, tag or a pull request is created or deleted.
On event pipeline trigger mode
On event pipeline trigger mode
3. Add actions
Buddy lets you choose from dozens of predefined actions. In this example, we'll add 4 actions that will perform the following tasks:
- Build and test your Elixir application
- Upload code to server together with compiled assets (FTP/SFTP/Rsync & more)
- Run db migrations & restart server
- Send notification to Slack
3.1 Build your Elixir application
Build actions in Buddy are run in isolated containers run from official Docker images. When the pipeline is run, Buddy launches the container, runs build commands, and shares the results in the pipeline filesystem with deployment actions.
Look up and click Elixir on the action list to add it to the pipeline:
Action list
The Run tab lets you determine the commands to execute. The default commands are:
mix deps.get
mix test$$
Elixir action commands console
3.1.2 Elixir version
You can change the version of Elixir and install missing packages & tools in the runtime environment tab:
Elixir action image
If your tests require a database to run, you can attach it in the Services tab:
Services tab
Services tab
3.2 Deploy application to server
The compiled application needs to be uploaded to the server. Head to the Transfer section and select your upload action (SFTP in our case):
File transfer actions
When adding the action you can choose what and where should be uploaded:
SFTP action configuration
3.3 Run db migrations & restart server
Once the app is deployed, you can run additional commands on your server with the SSH action:
SSH action selection
Enter the commands to execute in Run CMDs and configure authentication details in the Target tab:
SSH configuration
3.4 Send notification to Slack
You can configure Buddy to send your team a message after the deployment. In this example we'll use Slack:
Notification actions
If you add this action in the On Failure tab, Buddy will only send the message if something goes wrong with your build or deployment.
On failure notification
On failure notification
4. Summary
Congratulations! You have just automated your entire delivery process. Make a push to the selected branch and watch Buddy fetch, build, and deploy your project. With Continuous Delivery applied, you can now focus on what's really important: developing awesome apps! 🔥
Bear in mind that this article is only a brief example of what Buddy can do. You can create additional pipelines for staging and production environments, integrate with your favorite services (AWS, Google, Azure), trigger tests on pull requests, build Docker images, and push them to the registry—the possibilities are unlimited.
If you want us to create a delivery pipeline for your project, drop a line to support@buddy.works – we'll be happy to help!
Last modified on February 26, 2024