未验证 提交 621be2a4 编写于 作者: O Oleg Nenashev 提交者: GitHub

Merge pull request #3899 from jsoref/properties-quotes

Fix single quotes in properties files
......@@ -6,7 +6,7 @@ CLI.Usage=Jenkins CLI\n\
\ -ssh : use SSH protocol (requires -user; SSH port must be open on server, and user must have registered a public key)\n\
\ -i KEY : SSH private key file used for authentication (for use with -ssh)\n\
\ -noCertificateCheck : bypass HTTPS certificate check entirely. Use with caution\n\
\ -noKeyAuth : don't try to load the SSH authentication private key. Conflicts with -i\n\
\ -noKeyAuth : don''t try to load the SSH authentication private key. Conflicts with -i\n\
\ -user : specify user (for use with -ssh)\n\
\ -strictHostKey : request strict host key checking (for use with -ssh)\n\
\ -logger FINE : enable detailed logging from the client\n\
......@@ -15,7 +15,7 @@ CLI.Usage=Jenkins CLI\n\
\ Passing credentials by file is recommended.\n\
\ See https://jenkins.io/redirect/cli-http-connection-mode for more info and options.\n\
\n\
The available commands depend on the server. Run the 'help' command to \
The available commands depend on the server. Run the ''help'' command to \
see the list.
CLI.NoURL=Neither -s nor the JENKINS_URL env var is specified.
CLI.NoSuchFileExists=No such file exists: {0}
......
......@@ -24,6 +24,6 @@ warning.core = Jenkins core: {0}
warning.plugin = {0}: {1}
blurb = This section allows you to suppress warnings, applicable to your Jenkins \
configuration, provided by the updates sites. If you do, they won't be shown by \
configuration, provided by the updates sites. If you do, they won\u2019t be shown by \
the Update Site Warnings administrative monitor. \
Checked warnings are reported (the default), unchecked warnings are hidden.
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册