I'm new to deploy automation.
Here we have a backend app made in golang, coded by a team with two developers.
Our code is versioned in bitbucket git.
The deploy environment is a DigitalOcean droplet (vps).
I'm not using Docker, once each app runs in a dedicated server. But if you tell me a good reason, I'll be happy to use it.
Our goal is to send one directory with an executable, one static assets directory and a single config json file.
Our current procedure today is:
- Git push to master;
- Git pull ( from target/deploy server )
- delete previous version
- go build and copy the executable to target directory
- copy the other asset files to destiny folder
- run the app ( as nohup )
How to move from this manual procedure to automated mode, considering our simple scenario?
Is Bitbucket Pipelines the best option?
Is it better to build in my machine and send the executable, or git-pull from deploy machine and then build there?
Should I use another ci tool, like rundeck?
Am I looking to the wrong direction?
We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events