Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add global configuration as code example #1528

Merged
merged 1 commit into from
Nov 23, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions README.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -426,7 +426,31 @@ If the workspace is removed, the tag that was applied is lost.
Tagging a workspace made sense when using centralized repositories that automatically applied the tag to the centralized repository.
Applying a git tag in an agent workspace doesn't have many practical uses.

[#configuration-as-code]
=== Configuration as code

The global settings of the git plugin can be defined with the Jenkins link:https://plugins.jenkins.io/configuration-as-code/[configuration as code plugin].
Detailed descriptions of the individual settings are available in the link:#global-configuration[global configuration settings] section of this document.

An example configuration might look like this:

[,yaml]
----
unclassified:
scmGit:
addGitTagAction: false
allowSecondFetch: false
createAccountBasedOnEmail: false
disableGitToolChooser: false
globalConfigEmail: "[email protected]"
globalConfigName: "jenkins-user"
hideCredentials: false
showEntireCommitSummaryInChanges: true
useExistingAccountWithSameEmail: false
----

[#security-configuration]

=== Security Configuration

image:/images/git-security-configuration.png[Security Configuration]
Expand Down