Support
If a build fails and the pages here do not explain why, write to us. A message that names the organization, the repository and the exact error gives us what we need to look into it.
Contact us
Section titled “Contact us”Email support@cloudrepo.io. Contact details for sales and pricing questions are on the contact page.
To report a security concern, use the contact details on CloudRepo’s security page rather than a support message.
What to include
Section titled “What to include”Put these in the first message:
- Your organization’s name and the repository’s name.
- The exact error text, including the status code, copied rather than retyped.
- What you ran: the command, the tool and its version, and where it ran (your machine or a CI platform). If the build runs in CI, the name of the platform.
- When it started and what changed just before.
- What you expected and what happened instead.
- What you already tried.
Do not send a password or a repository token. Remove your token from any log or file first: a tool’s debug output can hold it (see Troubleshooting). If a token has been in a message, revoke it on the Repository Tokens page and create a new one.
Check these first
Section titled “Check these first”- A build failing with
401,403,404or409: Troubleshooting maps each status to its usual cause. - A refused credential: Repository Tokens has the checks for every client.
- An error with a code: Error codes explains the codes documented so far.
- A quick question: the FAQ.
- Whether CloudRepo is having a problem: status.cloudrepo.io.