Python BUddy

Python deployment pipeline for Buddy.works - guide

Uploaded by

Jarek Bob Dylewski

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

35 views

Python BUddy

Python deployment pipeline for Buddy.works - guide

Uploaded by

Jarek Bob Dylewski

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 6

Python

Buddy lets you create delivery pipelines that will build, test and deploy your Python
application on a single push to branch. The pipelines consist of actions that you can
configure depending on your needs.

The configuration is very easy and takes only a couple of minutes.

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.

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:
Branch assignment — this is the branch from which Buddy will deploy. If
you set the trigger mode to On push, Buddy will execute the pipeline upon
every push to that branch.

Trigger modes
Manual (on click) — recommended for Production
On push (automatic) — recommended for Development
Recurrently (on time interval) — recommended for Staging/Testing

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 Python application

Upload application to server
Run db migrations & restart application
Send notification to Slack

3.1 Build and test your Python app

Look up and click the Python action to configure it. Here you can choose the version
of Python and determine the commands to execute. The default commands are:

pip install -r requirements.txt

nosetests
If your tests require a database to run, you can attach it in the Services tab:

There is also a dedicated action for Django projects.

3.2 Deploy application to server

The built application needs to be uploaded to the server. Head to the Transfer section
and select your action (SFTP in our case):

When adding the action you can choose what and where should be uploaded:
3.3 Run db migrations & restart application

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

Enter the commands to execute and configure authentication details:

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:

If you add this action to 'Actions run on failure', Buddy will only send a
message if something went wrong with your build or deployment.

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!

Questions? Sign up for Buddy Digest

Not sure how to configure a pipeline for your Best practices on CI/CD and
process? Reach out on the live-chat,contact fresh changelogs delivered
support, or ask the developers on our forum. weekly to your inbox.

Email address… Sign up

SOLUTIONS PLATFORM LEARN COMPANY

Pipelines: your doorway to Status Page Documentation Our Blog

CI/CD
Pricing & Features Help & Support About Us
Laravel in Docker
On-Premises API support@buddy.works
Node.js in Docker
Ask the Community
Selenium in Node.js with   
WebDriver.io

Automate Kubernetes
workflows