Skip to content
GitLab
Next
Projects
Groups
Snippets
Help
Loading...
Help
See what's new at GitLab
4
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
gitlab-runner
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Locked Files
Issues
1,983
Issues
1,983
List
Boards
Labels
Service Desk
Milestones
Iterations
Merge Requests
216
Merge Requests
216
Requirements
Requirements
List
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Test Cases
Security & Compliance
Security & Compliance
Dependency List
License Compliance
Operations
Operations
Incidents
Environments
Packages & Registries
Packages & Registries
Container Registry
Analytics
Analytics
CI / CD
Code Review
Insights
Issue
Repository
Value Stream
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
GitLab.org
gitlab-runner
Commits
d81282e2
Commit
d81282e2
authored
May 30, 2019
by
Steve Azzopardi
Committed by
Evan Read
May 30, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add documentation for windows development
parent
f6ea9389
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
38 additions
and
0 deletions
+38
-0
docs/development/README.md
docs/development/README.md
+38
-0
No files found.
docs/development/README.md
View file @
d81282e2
...
...
@@ -160,6 +160,44 @@ please ensure the vendored copies is updated with the appropriate `dep ensure` c
Don't add dependency from upstream master branch when version tags are available.
## Developing for Windows on a non-windows environment
We provide a
[
Vagrantfile
](
https://gitlab.com/gitlab-org/gitlab-runner/tree/master/Vagrantfile
)
to help you run a Windows Server 2019 or Windows 10 instance, since we
are using
[
multiple machines
](
https://www.vagrantup.com/docs/multi-machine/
)
inside of Vagrant.
The following are required:
-
[
Vagrant
](
https://www.vagrant.com
)
installed.
-
[
Virtualbox
](
https://www.virtualbox.com
)
installed.
-
Around 30GB of free hard disk space on your computer.
Which virtual machine to use depends on your use case:
-
The Windows Server machine has docker pre-installed and should always
be used when you are developing on Runner for Windows.
-
The Windows 10 machine is there for you to have a windows environment
with a GUI which sometimes can help you debugging some Windows
features. Note that you cannot have Docker running inside of Windows
10 because nested virtualization is not supported.
Running
`vagrant up windows_10`
will start the Windows 10 machine for
you. To:
-
ssh inside of the Windows 10 machine, run
`vagrant ssh windows_10`
.
-
Access the GUI for the Windows 10, you can connect via
RDP by running
`vagrant rdp windows_10`
, which will connect to the
machine using a locally installed RDP program.
For both machines, the GitLab Runner source code is synced
bi-directionally so that you can edit from your machine with your
favorite editor. The source code can be found under the
`$GOROOT`
environment variable. We have a
`RUNNER_SRC`
environment variable which
you can use to find out the full path so when using:
-
Windows batch scripts, you can run
`cd %RUNNER_SRC`
.
-
PowerShell, you can use
`cd $Env:RUNNER_SRC`
.
## Troubleshooting
### executor_docker.go missing Asset symbol
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment