Connection Management
Connection Settings
You can see the connection details by clicking the "Connection Settings" button in the build profile.
Different types of connections have different connection details in the connection settings.
OAuth Connection
For an OAuth connection, the details will be "Provider", "Token Owner", "Code", "Expire Access Token Date", "Expire Refresh Token Date", "Refresh Token", and "Token".
PAT Connection
For a PAT (personal access token) connection, the details will be "Token Owner", and "Personal Access Token".
In this section, you can view the PATs you have previously added, if any, and change them profile-specific.
You only need to make sure that the modified token has the required authorizations for the relevant repository.
Disconnect Build Profile
You can disconnect the build profile from the Git provider by using the Disconnect button below.
When you click on the "Disconnect" button, Appcircle will bring up a warning dialog box for confirmation.
When we open a disconnected build profile, Appcircle will bring us a popup to quickly Reconnect build the profile.
If you do not want to connect again at that moment, you can do it later by clicking the "Reconnect" button next to the "Connection Settings".
If you disconnect a build profile, only that build profile is disconnected from the Git provider.
When you reconnect a build profile again, only the relevant build profile will be connected again.
On the other hand, connection operations done from the Connections page affect all relevant build profiles using those connections.
Change Git Provider and Reconnect
Appcircle allows changing the Git provider while reconnecting a profile that has been disconnected.
For example, assume that a build profile was previously connected to GitLab and then its Git repository had been moved to GitHub. In this case, you can select the new Git provider for that build profile by clicking the "Reconnect" button next to "Connection Settings".
Appcircle will display the Git providers and "Connect via SSH" connection options in a selectable list.
Here you can select the Git provider you want to change or the "Connect via SSH" method regardless of the Git provider.
Once the connection operations are completed, the Git provider redirects to the Appcircle build profile with the repository selection window.
After you select the relevant Git repository and "Save", the build profile will be connected to the new Git provider.
After changing the Git provider and reconnecting the repository, you can use the existing branches that are also available in the new repository. When you try to Start Build with these branches, you should see the up-to-date "Commit ID" from the new repository.
Unavailable branches from the old repository connection will be inactive. You can see them in the branch list, but Appcircle does not allow building with the branches that do not exist in the new repository. These kinds of branches will be unusable.
While switching from one connection to another type of connection, the older connection method is not important.
You can select one of the listed options and switch to that one without considering anything about the previous one.
While changing the Git provider, your previous builds, tests, configurations, workflows, triggers and branch list will not be deleted.
Change Owner
The token owner of a build profile can now be changed without the need to create a new build profile on Appcircle. The Change Owner button in the build profile Connection detail will help you change the connection ownership so that you can resolve the broken connections or misconfigured repository authorization cases easily by yourself.
To use this feature, the user must have previously connected to the relevant Git provider on Appcircle via OAuth.
The build profile owners will not see the Change Owner button in the Connection detail for their build profiles.
When you browse the same build profile with a different member within the same organization, the Change Owner button will be visible in the window that's opened when we click on the Connection Settings button.
After clicking on the Change Owner button and giving approval on the confirmation screen that appears, the process of taking token ownership of the build profile connection will begin.
The connection ownership change will be permitted for users who are in the same organization (team members) and have Manager role in the build profile scope.
In addition, the user who wants to take ownership of the connection must also have access to the repository on the relevant Git provider.
When the process is completed successfully, you can click on the Connection Settings button again to see the changed ownership of the build profile connection. In the window that's opened, there won't be a Change Owner button because you are now the profile owner.
