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
What is version of KubeSphere DevOps has the issue?
v3.3.1
How did you install the Kubernetes? Or what is the Kubernetes distribution?
kubekey
What happened?
With parameters, the single quote automatically used by the graphical interface can cause parameters to not be effective. The method of avoiding this is to edit the Jenkinsfile and change it to double quotes.
With parameters, if the notation is $PARAM, the parameter and non-parameter values need to be separated by a space to distinguish them. If the notation is ${PARAM}, it can be directly recognized. It is recommended to use the second notation.
There is a requirement that the value of the 'from' field in the mail must be exactly the same as the EMAIL_FROM_ADDR parameter configured in Jenkins in order to send an email. Otherwise, an error will be reported: SMTPSendFailedException: 553 Mail from must equal authorized user. Therefore, adding a 'from' parameter has no meaning or is not supported (cannot be customized).
Relevant log output
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
What is version of KubeSphere DevOps has the issue?
v3.3.1
How did you install the Kubernetes? Or what is the Kubernetes distribution?
kubekey
What happened?
$PARAM
, the parameter and non-parameter values need to be separated by a space to distinguish them. If the notation is${PARAM},
it can be directly recognized. It is recommended to use the second notation.Relevant log output
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: