Quickstart
Create a Prodgator organization, connect a CI/CD provider and see your first pipeline run.
This guide takes you from a new account to live pipeline runs. You need admin access on the provider side:
| Provider | Access you need |
|---|---|
| GitHub | Owner of the GitHub organization, or your own personal account |
| GitLab (gitlab.com) | Maintainer or Owner of a group |
| Bitbucket Cloud | Admin of a workspace |
| Azure DevOps | Member of an organization connected to Microsoft Entra ID, and Project Administrator on its projects |
| Jenkins (beta) | A Jenkins user that can read jobs, and permission to edit Jenkinsfiles |
Sign in and create an organization
Go to app.prodgator.io and sign in with email, Google, Microsoft or your company's SSO if your organization has set it up.
The first time you sign in, onboarding asks for an organization name. Everything in Prodgator (runs, deployments, alerts, settings) belongs to an organization. The person who creates the organization is its admin. You can belong to several; see Organizations.
Connect a provider
Onboarding moves on to Connect provider. You can also do this later from Organization > Integrations, which only Org admins see. Pick your provider:
GitHub
Install the Prodgator GitHub App.
GitLab
Sign in with GitLab and pick a group.
Bitbucket
Sign in with Bitbucket and pick a workspace.
Azure DevOps
Sign in with Microsoft and pick an organization.
Jenkins (beta)
Enter your Jenkins URL and API token, then add a snippet to your Jenkinsfiles.
Prodgator creates the webhooks for GitHub, GitLab, Bitbucket and Azure DevOps itself. For Jenkins, your pipeline posts to Prodgator. For CircleCI, Buildkite and other CI systems, see Any CI. How many connections you can have depends on your plan; see Plans and features.
Run a pipeline
Push a commit, open a pull request or start a workflow by hand. The run shows up on the Pipelines page within a few seconds and updates as it progresses. Prodgator only sees runs that start after the connection is made.
Invite your team
Invite people from Organization > Invitations (or the last onboarding step). The invitation sets each new member's role, and an Org admin can change roles later in Organization > Members. See Invite people and change roles.
Next steps
- Key concepts: the words the rest of the docs use
- Approve deployments
- Get notified in Slack