-
Notifications
You must be signed in to change notification settings - Fork 172
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
解决修改配置导致的中文乱码问题 #233
解决修改配置导致的中文乱码问题 #233
Conversation
@songhanlin were you hitting an issue that made you want to incorporate this change? EDIT: OK I see now ... instead of |
I tried to reproduce this locally by using Chinese characters but I could not. I also tried non-English latin characters and still no luck in reproducing. But the change proposed seems to have no negative impact in my limited testing. |
first, sorry about my bad english;
Jenkins: i download it whit homebrew, and i didn't update chatset setting; |
My test code like this:
|
我也遇到了这个问题,在使用Jenkins-rest 创建pipeline job 时,我的节点标签,参数,以及 stage 名称 都包含中文,可以正常创建job ,执行构建时,就一直卡在那。。。。jenkins-client 这个api 通过手动发起post 请求 可以暂时解决,但是我更希望用官方的api 来实现我的功能 |
Version |
Please do not create a Pull Request without first creating an ISSUE.
Any change needs to be discussed before proceeding.
Failure to do so may result in the rejection of the Pull Request.
Explain the details for making this change: What existing problem does the Pull Request solve? Why is this feature beneficial?
On adding new feautes/endpoints
No more than 1 endpoint should be coded within a Pull Request.
This alone requires enough code to review and adding more than 1 WILL result in your Pull Request either being ignored or rejected outright.
On adding Mock and Integ Tests
At least 2 mock tests and 2 integ tests are required prior to merging.
Each pair should should test what the success and failure of added change looks like.
More complicated additions will of course require more tests.
On CI testing (currently using travis)
Code will not be reviewed until CI passes.
Current CI does NOT exercise
integ
tests and so each Pull Request will have to be run manually by one of the maintainers to confirm it works as expected: please be patient.On automtatic closing of ISSUES
Put
closes #XXXX
in your comment to auto-close the issue that your PR fixes (if such).