You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: SECURITY.md
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -17,13 +17,13 @@ You should receive a response within 24 hours. If for some reason you do not, pl
17
17
18
18
Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
19
19
20
-
* Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
21
-
* Full paths of source file(s) related to the manifestation of the issue
22
-
* The location of the affected source code (tag/branch/commit or direct URL)
23
-
* Any special configuration required to reproduce the issue
24
-
* Step-by-step instructions to reproduce the issue
25
-
* Proof-of-concept or exploit code (if possible)
26
-
* Impact of the issue, including how an attacker might exploit the issue
20
+
* Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
21
+
* Full paths of source file(s) related to the manifestation of the issue
22
+
* The location of the affected source code (tag/branch/commit or direct URL)
23
+
* Any special configuration required to reproduce the issue
24
+
* Step-by-step instructions to reproduce the issue
25
+
* Proof-of-concept or exploit code (if possible)
26
+
* Impact of the issue, including how an attacker might exploit the issue
27
27
28
28
This information will help us triage your report more quickly.
Copy file name to clipboardExpand all lines: docs/input/docs/reference/build-servers/gitlab.md
+20-19Lines changed: 20 additions & 19 deletions
Original file line number
Diff line number
Diff line change
@@ -9,25 +9,26 @@ To use GitVersion with GitLab CI, either use the [MSBuild
9
9
Task](/docs/usage/msbuild) or put the GitVersion executable in your
10
10
runner's `PATH`.
11
11
12
-
A working example of integrating GitVersion with GitLab is maintained in the project [Utterly Automated Software and Artifact Versioning with GitVersion][]
12
+
A working example of integrating GitVersion with GitLab is maintained in the project [Utterly Automated Versioning][utterly-automated-versioning]
13
13
14
-
Here is a summary of what it demonstrated (many more details in the [README.md][])
14
+
Here is a summary of what it demonstrated (many more details in the [Readme][readme])
15
15
16
-
- Is a reusable working example known as a Guided Exploration ([GE Manifesto][]) - so job logs and package artifacts can be reviewed. The project can also be imported to your own GitLab group or instance as a starting point for your own work.
17
-
- IMPORTANT: It demonstrates how to override GitLab CI's default cloning behavior so that GitVersion can do a dynamic copy. Selectively clones GitVersion.yml so that these settings take effect. This best practice demonstrates the best way to do this while avoiding a double-cloning of the project (once by GitLab Runner and once by GitVersion).
18
-
- Implements GitVersion as a CI/CD Extension that can be reused across many projects using includes.
19
-
- Implements GitVersion as a single job that runs the GitVersion container and passes the version number downstream into both _pipeline_ and _job_ level variables, which means...
20
-
- It can be used with ANY coding language, framework or packaging engine.
21
-
- Generates example packaged artifacts:
22
-
-Two ways of building Sem Versioned NuGet packages (msbuild-ish and nuget.exe-ish) and uploads them and tests them from a [GitLab NuGet repository][].
23
-
-A Sem Versioned [GitLab Generic Package][]
24
-
-A Sem Versioned docker container and uploads to [GitLabs Container Registry][].
25
-
- It creates a Sem Versioned [GitLab Release](GitLab Releases Feature Help) and Git tag using the [GitLab release-cli][] and links the generic package as evidence.
16
+
-Is a reusable working example known as a Guided Exploration ([Guided Exploration Manifesto][guided-exploration-manifesto]) - so job logs and package artifacts can be reviewed. The project can also be imported to your own GitLab group or instance as a starting point for your own work.
17
+
-IMPORTANT: It demonstrates how to override GitLab CI's default cloning behavior so that GitVersion can do a dynamic copy. Selectively clones GitVersion.yml so that these settings take effect. This best practice demonstrates the best way to do this while avoiding a double-cloning of the project (once by GitLab Runner and once by GitVersion).
18
+
-Implements GitVersion as a CI/CD Extension that can be reused across many projects using includes.
19
+
-Implements GitVersion as a single job that runs the GitVersion container and passes the version number downstream into both _pipeline_ and _job_ level variables, which means...
20
+
-It can be used with ANY coding language, framework or packaging engine.
21
+
-Generates example packaged artifacts:
22
+
-Two ways of building Sem Versioned NuGet packages (msbuild-ish and nuget.exe-ish) and uploads them and tests them from a [GitLab NuGet Repository][gitlab-nuget-repository].
23
+
-A Sem Versioned [GitLab Generic Package][gitlab-generic-package]
24
+
-A Sem Versioned docker container and uploads to [GitLab Container Registry][gitlab-container-registry].
25
+
-It creates a Sem Versioned [GitLab Release][gitlab-release-help]and Git tag using the [GitLab Release Cli][gitlab-release-cli] and links the generic package as evidence.
[Utterly Automated Software and Artifact Versioning with GitVersion]: https://gitlab.com/guided-explorations/devops-patterns/utterly-automated-versioning/
Copy file name to clipboardExpand all lines: docs/input/docs/reference/build-servers/jenkins.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -25,10 +25,10 @@ Integrating GitVersion into your Jenkins build varies based on the project type:
25
25
26
26
Injecting environment variables is not supported in Jenkins natively, but
27
27
Jenkins plugins exist that provide this functionality. Of these plugins
28
-
[EnvInject] appears to be the most popular with over 20k downloads per month.
28
+
[EnvInject][env-inject] appears to be the most popular with over 20k downloads per month.
29
29
30
30
To inject the GitVersion variables as environment variables for a build job
31
-
using [EnvInject], do the following:
31
+
using [EnvInject][env-inject], do the following:
32
32
33
33
1. Add an **Execute Windows batch command** build step with _Command_:
34
34
`gitversion /output buildserver`
@@ -51,7 +51,7 @@ You can verify correct injection of environment variables by adding another
51
51
52
52
### Pipeline Projects
53
53
54
-
For pipeline projects, GitVersion variables can be accessed by reading the `gitversion.properties` file using the [Pipeline Utility Steps] plugin. Variables from a property file are not automatically merged with the environment variables, but they can be accessed within a script block.
54
+
For pipeline projects, GitVersion variables can be accessed by reading the `gitversion.properties` file using the [Pipeline Utility Steps][pipeline-utility-steps] plugin. Variables from a property file are not automatically merged with the environment variables, but they can be accessed within a script block.
0 commit comments