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

Mail optimization in the pipeline step #937

Open
chilianyi opened this issue Apr 6, 2023 · 1 comment
Open

Mail optimization in the pipeline step #937

chilianyi opened this issue Apr 6, 2023 · 1 comment
Assignees
Labels
area/devops kind/bug Categorizes issue or PR as related to a bug.

Comments

@chilianyi
Copy link
Contributor

chilianyi commented Apr 6, 2023

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?

  1. 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.
  2. 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.
  3. 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

@chilianyi chilianyi added the kind/bug Categorizes issue or PR as related to a bug. label Apr 6, 2023
@chilianyi
Copy link
Contributor Author

#947

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devops kind/bug Categorizes issue or PR as related to a bug.
Projects
No open projects
Status: No status
Development

No branches or pull requests

2 participants