[JIRA] (JENKINS-45480) GIT Build with Parameters is not listing branches
Title: Message Title Robson Hermes commented on JENKINS-45480 Re: GIT Build with Parameters is not listing branches Oh damn it. You are right, now I have failure starting from the 2nd attempt. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45480) GIT Build with Parameters is not listing branches
Title: Message Title Robson Hermes updated an issue Jenkins / JENKINS-45480 GIT Build with Parameters is not listing branches Change By: Robson Hermes Attachment: image-2019-03-06-11-03-41-468.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45480) GIT Build with Parameters is not listing branches
Title: Message Title Robson Hermes commented on JENKINS-45480 Re: GIT Build with Parameters is not listing branches I had the same problem, and changing from SSH to HTTP did not work. I got the error below when trying HTTP: I managed to "fix" the problem by creating a new project cloning the existing one. The new one worked fine. I did not change any config at all. Thus I suppose this is really some sort of problem in the Git plugin. Not a user config problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45480) GIT Build with Parameters is not listing branches
Title: Message Title Robson Hermes updated an issue Jenkins / JENKINS-45480 GIT Build with Parameters is not listing branches Change By: Robson Hermes Attachment: image-2019-03-06-09-41-20-264.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54369) Env-inject writing \u0000 in injectedEnvVars.txt from windows slave
Title: Message Title Robson Hermes updated an issue Jenkins / JENKINS-54369 Env-inject writing \u in injectedEnvVars.txt from windows slave Change By: Robson Hermes I am having a problem with the envInject, cause it seems to be writing NUL (Unicode char) from the env of a Windows slave. 1 - Basically I am creating a new job which runs in a Windows slave. This job executes a powershell code that writes variables to a file env.properties (attachment 01.png). I am doing that cause these values are used later in other job steps.2 - The file is written without any problems in the windows slave (attachment 02.png)3 - When I try to run the job the next time, I have the error: {code:java}java.lang.IllegalArgumentException: Invalid environment variable name: "CURRENT_ARCHIVE" at java.lang.ProcessEnvironment.validateName(Unknown Source) at java.lang.ProcessEnvironment.put(Unknown Source) at java.lang.ProcessEnvironment.put(Unknown Source) at hudson.Proc$LocalProc.environment(Proc.java:234) at hudson.Proc$LocalProc.(Proc.java:219){code} 4 - As you can see, apparently the name of the variable is fine. However, if I open the injectedEnvVars.txt in our Linux master, between each char, envinject added a u char, which causes the method ProcessEnvironment.validateName to throw an exception. (see attachments 03 and 04) All other variables are fine. Just the ones I wrote are messed up. Result is that I can run the job only first time. Any subsequent attempt fails, that's why I classified as major. Sorry if this interpretation is incorrect. Add Comment
[JIRA] (JENKINS-54369) Env-inject writing \u0000 in injectedEnvVars.txt from windows slave
Title: Message Title Robson Hermes updated an issue Jenkins / JENKINS-54369 Env-inject writing \u in injectedEnvVars.txt from windows slave Change By: Robson Hermes Attachment: 03.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54369) Env-inject writing \u0000 in injectedEnvVars.txt from windows slave
Title: Message Title Robson Hermes updated an issue Jenkins / JENKINS-54369 Env-inject writing \u in injectedEnvVars.txt from windows slave Change By: Robson Hermes Attachment: 03.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54369) Env-inject writing \u0000 in injectedEnvVars.txt from windows slave
Title: Message Title Robson Hermes updated an issue Jenkins / JENKINS-54369 Env-inject writing \u in injectedEnvVars.txt from windows slave Change By: Robson Hermes Attachment: 02.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54369) Env-inject writing \u0000 in injectedEnvVars.txt from windows slave
Title: Message Title Robson Hermes updated an issue Jenkins / JENKINS-54369 Env-inject writing \u in injectedEnvVars.txt from windows slave Change By: Robson Hermes Attachment: 02.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54369) Env-inject writing \u0000 in injectedEnvVars.txt from windows slave
Title: Message Title Robson Hermes created an issue Jenkins / JENKINS-54369 Env-inject writing \u in injectedEnvVars.txt from windows slave Issue Type: Bug Assignee: Unassigned Attachments: 01.png, 02.png, 03.png, 04.png Components: envinject-plugin Created: 2018-10-31 14:11 Environment: jenkins master: Debian 8 Jenkins ver. 2.110 envinject 2.1.3 jenkins slave: Windows Server 2016 Labels: plugin environment Priority: Major Reporter: Robson Hermes I am having a problem with the envInject, cause it seems to be writing NUL (Unicode char) from the env of a Windows slave. 1 - Basically I am creating a new job which runs in a Windows slave. This job executes a powershell code that writes variables to a file env.properties (attachment 01.png). I am doing that cause these values are used later in other job steps. 2 - The file is written without any problems in the windows slave (attachment 02.png) 3 - When I try to run the job the next time, I have the error: java.lang.IllegalArgumentException: Invalid environment variable name: "CURRENT_ARCHIVE" at java.lang.ProcessEnvironment.validateName(Unknown Source) at java.lang.ProcessEnvironment.put(Unknown Source) at