Sun* CI Documentation

# FAQ

# Grant access to organization

After Sync account you should see all workspaces of your account. If Sun* CI does not show any workspace that mean Sun* CI does not have access to your organization. You need to go OAuth application settings and give access of your organization to Sun* CI. After that you need to comeback Sun* CI and Sync account again.

# SSO issue

  • Organization uses SSO, repository enabled CI but there's no build when creating new commit?

This error occurs when your token is blocked by SSO, you need to re-authenticate your SSO and try again.

  1. Go to https://github.com/orgs/<your-organization>/sso to authenticate.
  2. Get back to Sun* CI and log out.
  3. Log back in and Sync account if necessary.
  • Organization uses SSO, I sync the account but repository doesn't show up at Sun* CI?

Because your organization enable SSO, old OAuth tokens are not safelisted for use, so the owner who enable CI need to re-create them after enabling SSO with the following steps:

  1. Log into the affected organization on GitHub using SSO.
  2. Go to OAuth application settings
  3. Select the Sun* CI token and revoke it.
  4. Go to Sun* CI and log out if necessary.
  5. Log back in -which should prompt you to grant authorization- and make sure Sun* CI is authorized to access the organization.

After having done all the steps above then Sync account so Sun* CI will show your repositories.

# Repository has invalid token, what happens to my repository?

Repository has invalid token, you need to contact ___ to refresh token

Invalid repository has cases:

  1. Repository's owner who enabled CI is no longer collaborators.
  2. The organization uses SSO and repository owner doesn't validate github's SAML for 24 hours so this token has expired

So what do i need to do?

In case Repository's owner who enabled CI is no longer collaborators, you need to contact the user who is the admin of the repository to re-enable CI.

You re-enable CI by following steps:

  1. Use the repository's admin account and was login CI.
  2. Go to https://ci.sun-asterisk.com/account/<your-scm>/repositories (your-scm can be github, gitlab,...) to re-enabled.
  3. Disable and enable CI for a repository with an invalid token.

Now, CI will use the new token that the admin of the repository has re-enabled CI

In case the organizion uses SSO.

If the organization uses SSO, you need to re-authenticate your SSO and try again, you can follow the steps here