Angaben zum Datum
Datum aus der Quelle.
Erstmals gesehen am .
Bitbucket wird als Quelle für Elestio CI/CD unterstützt
Bitbucket ist jetzt eine vollwertige Quelle in Elestio CI/CD, sodass jeder Push auf einen gewählten Branch die App auf einer eigenen VM automatisch neu bereitstellt.
Bitbucket + Elestio: Auto-Deploy Your Repo on Every Push
If your team lives in Bitbucket, you know how deployment usually goes. Someone writes a bitbucket-pipelines.yml that builds the app, then SSHes into a server and runs a deploy script that only one person fully understands. It works until that person goes on vacation, the SSH key gets rotated, or the server needs a security patch nobody scheduled.
Until now, Elestio's CI/CD could build and deploy straight from GitHub and GitLab, and Bitbucket users had to mirror their repos or move them. That changed this week: Bitbucket is now a first-class source in Elestio CI/CD. You connect your Bitbucket account, pick a repository and a branch, and every push to that branch redeploys your app on a VM that's yours alone. This guide walks through the setup, what happens under the hood, and the few things that trip people up.
What You Get
Elestio CI/CD builds your code on every push, the way Heroku, Render or Railway do. The difference is where it runs: on a dedicated VM in your Elestio project, not on a shared cluster. That VM can also host any of Elestio's 400+ managed open-source services, so your app, its PostgreSQL database, a Redis cache and a Keycloak login server can all live in the same project, managed the same way.
With Bitbucket support, the deployment sources are now:
Source
What it deploys
Redeploys on push
GitHub …