Builds Don't Trigger

Search Results

Problem

I added a .probo.yaml file to my repository and opened a pull request, but I do not see a build.

Solution

There are three main reasons this will occur.

First, your configuration file may contain invalid YAML. Validate the contents of your .probo.yaml file with a tool like our YAML syntax checker or yamllint.com, then commit the corrected file.

Second, your subscription may not be active. Builds will not trigger without an active trial or paid subscription. You can check this on the Subscription Information tab in your Probo.CI project. You must be an account administrator to see this option.

Third, and most likely, your git hosting provider may have invalidated your OAuth token. This sounds scarier than it is. Probo 5.2.0 added automatic OAuth token refresh for GitHub, GitLab, and Bitbucket, which resolves most cases on its own, and further improvements are in progress. The problem shows up in three ways:

Builds from your repository do not trigger Probo.CI builds, and no message appears in Probo or on GitHub, GitLab, or Bitbucket.
Attempts to rebuild a Probo build fail with a red error box.
The branch selection menu above the list of builds shows a red “Failed to load” message.

To fix this, click the Activate Repos button, go to your organization, and toggle the repository off and back on. This forces a refresh of the OAuth token for your account and organization. You must be an administrator on the git repository in question to do this. Soon we will have a token access control panel that reports your token status and lets you refresh it.

If you feel like it should work or if you had missing asset references in your build, you can re-deliver the payload of your build by Rebuilding Without a Pull Request. This will help you resolve these issues without needing to close and re-create your pull request.

Explanation

Probo builds will fail to trigger if the configuration file contains invalid YAML. We recommend linting your configuration file when you first write it and after you make any significant changes.

Also make sure your subscription is active and that Probo.CI still holds a valid OAuth token for your git hosting provider.