-
Notifications
You must be signed in to change notification settings - Fork 441
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
Character encoding issue in updateConfig function #86
Comments
This is a bug. In my test, both |
Thanks for your reply. I extracted the config xml string of an existing job from jenkins server and pasted in my main method. When I used the string to create a new job, the description was fine, but when I used it to update the one that I just created, the description was filled with error code. Here is a link to my code on go playground, and I have attached two screenshots of the jenkins job I created. Is there anything that I could do on my end to fix this? Thanks again. |
@thierry1129 Thanks for your detail information. As I can not open the go playground url: |
Thanks for your reply and sorry for the inconvenience. I've attached my code here. I just realized some of the formats(like line breaks) are lost in txt file, so here is another copy in docx. |
As I got the same problem,does there any alternative solution?thanks! |
Has anyone solved this problem? |
我也遇到了这个问题 测试 >> æµ�è¯ |
都卡住了 |
已修复,添加charset=utf-8到Content-Type标头显式指定字符编码修复 |
So I use a very similar approach to create and modify jobs , and it works perfectly when I try to add Chinese or Japanese character in job description while creating a new job.
However when I modify an existing job and try to add a Chinese character in job description by calling the updateConfig function, there is only unreadable code in the description area after executing the function.
Any suggestions on how to resolve this? It really baffles me for the last few days since the CreateJob function works fine but the UpdateConfig function doesn't.
BTW thanks for resolving my last issue!
The text was updated successfully, but these errors were encountered: