mig42

<!-- save this file as %PROGRAMFILES%\PlasticSCM5\client\remoting.conf or /opt/plasticscm5/client/remoting.conf -->
<configuration>
<system.runtime.remoting>
        <application>
            <channels>
                <channel type="Codice.Channels.PlasticTcpChannel, plastictcpchannel" name="normal">
                    <clientProviders>
                        <provider type="Codice.Channels.ClientSinkProvider, plastictcpchannel" />
                        <formatter ref="binary" />
                    </clientProviders>

mig42

<!-- NOTE: Replace "@@VERSION@@" by the installed PlasticSCM server version. Example: Replace "@@VERSION@@" by "5.4.16.619" -->

<ScriptActions>
  <Actions>
    
    <SetStatus Msg = "Downloading Plastic SCM installer (@@VERSION@@) ..." />
    <SetDistraction Msg = "" />
    <SetProgress Value = "20" />

    <Download

mig42

Gmaster doesn't currently support OAuth to login to GitLab (either at gitlab.com or hosted). Unfortunately, GitLab only allows OAuth login to access its API. This is a temporary workaround to access your GitLab account information from Gmaster until we finally implement OAuth support for GitLab!

The "Personal token" field is the key here. You have two options: either use your unique Private Token from GitLab or create a Personal Access Token.

Using the Private Token

First of all, you need to have in mind that this Private Token is only useful for API operations, such as creating a new repository or listing your currently available repositories. This means that you'll need to enter your credentials later if you wish to clone one of your repos.

mig42

param (
    [Parameter(Mandatory=$true)][string]$SrcRev,
    [Parameter(Mandatory=$true)][string]$DstRev,
    [bool]$Force
)

function ExtractFileNameFromRev([string]$rev)
{
    if ("$rev" -match '^([^:#@]*:)?([^@]*).*$')
    {