Install Self-Hosted
Get Started on Cloud
BasicsPipelinesTargetsActions & ServicesIntegrationsSelf-HostedYAMLBuddy GitTroubleshootingAPI

CI/CD for Go

Hint

📚 Learn more about Go action features, integrations and alternatives.

With Buddy, you can create a pipeline that builds, tests, and deploys Golang applications on a push to Git. The configuration is super simple and takes 10 to 15 minutes.

Image loading...Go pipeline example

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.

Image loading...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:

Image loading...Adding a new pipeline

Hint

Trigger modes

  • Manually (on click) — recommended for Production
  • On events (automatic) — recommended for Development
  • On schedule (on time interval) — recommended for Staging/Testing
Success
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. Image loading...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 Go application
  • Upload code to server together with compiled assets (FTP/SFTP/Rsync & more)
  • Restart server
  • Send notification to Telegram

3.1 Build and test your Go app

Success
Build actions in Buddy are run in isolated containers run from official Docker images. When the pipeline is run, Buddy pulls the container, runs build commands, and uploads the results to the pipeline filesystem.

Look up and click Go on the action list to add it to the pipeline:

Image loading...Action list

The Run tab lets you determine the commands to execute. The default commands are:

bash
go test
go build$$

Image loading...Default build commands for Go

3.1.2 Go version

You can change the version of Go and install missing packages & tools in the runtime environment tab:

Image loading...Go action image

Tip
If your tests require a database to run, you can attach it in the Services tab: Image loading...Services tab

3.2 Deploy application to server

The website is ready for upload. Head to the Transfer section and select your deployment action (SFTP in our case):

Image loading...File transfer actions

When adding the action you can choose what and where should be uploaded:

Image loading...Setting up an SFTP action

3.3 Restart server

Once the app is deployed, you can run additional commands on your server with the SSH action:

Image loading...SSH action selection

Enter the commands to execute in Run CMDs and configure authentication details in the Target tab:

Image loading...SSH commands console

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 Email notification:

Image loading...Notification actions

Hint
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. Image loading...Notification actions

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! 🔥

Success
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.
Tip
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 Sep 23, 2024

Previous pagePipeline configurationNext pageC/C++