Page History
...
Here is a summary of the steps involved. Click on the links for more detail:
On the build machine, Install the GitLab Runner.
On GitLab web site, Configure GitLab Runner Server Settings.
On a Developer's machine Configure the GitLab Runner's repository in the source code repository and commit and push the changes.
Check on the GitLab web site that the CI/CD pipeline is flagged as passed.
Close any open Git Bash command line windows. They may interfere with the GitLab Runner.
The system is ready to be used.
...
Now, if you go to your repository on GitLab, access "Settings > CI/CD" and expand the "Runners settings" you are able to see your runner already assigned to your project. If the green circle is not showing its probably because you haven't started the Runner on the Target System.
Beside the Specific Runners section, click on Disable shared Runners.
and then expand "Settings > CI/CD" Environment Variables and setup these variables:
GIT_STRATEGY = none ensures that the Runner does not perform any git operations itself. It leaves it up to the jobs to do that task. LANSA requires the git operations to be performed in its own directory structure with web sites, etc, correctly configured
...
LANSA_PARTITION is the partition identifier.
Configure the GitLab Runner's repository
...