[JIRA] (JENKINS-49723) Powershell execution within GIT Multibranch pipeline failing
Title: Message Title Mike Henderson commented on JENKINS-49723 Re: Powershell execution within GIT Multibranch pipeline failing Thanks for looking at this! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49723) Powershell execution within GIT Multibranch pipeline failing
Title: Message Title Mike Henderson commented on JENKINS-49723 Re: Powershell execution within GIT Multibranch pipeline failing Works both ways for me, with and without the extension. I did this on the Windows 2008 R2 box which then makes me think it is some kind of path issue when run from within the pipeline. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49723) Powershell execution within GIT Multibranch pipeline failing
Title: Message Title Mike Henderson updated an issue Jenkins / JENKINS-49723 Powershell execution within GIT Multibranch pipeline failing Change By: Mike Henderson Attachment: image-2018-04-12-13-22-38-763.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49723) Powershell execution within GIT Multibranch pipeline failing
Title: Message Title Mike Henderson commented on JENKINS-49723 Re: Powershell execution within GIT Multibranch pipeline failing Yes, that seems to work fine. Also, other than pipeline, the powershell commands I call from Jenkins work fine too, if that helps. I have three nodes currently and I basically have just limited the jobs to run on the Windows 2016 node if it is a pipeline because the other two nodes with Window 2008 R2 fail still. I have a lot of older jobs though running standard "Freestyle project" and they execute on all of my nodes without issue and just about every one has a Powershell step. Thanks Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49723) Powershell execution within GIT Multibranch pipeline failing
Title: Message Title Mike Henderson commented on JENKINS-49723 Re: Powershell execution within GIT Multibranch pipeline failing My new Jenkins server with Windows 2016 is working when jobs run locally, but if they run on a remote node with Windows 2008 R2, I still get this issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49723) Powershell execution within GIT Multibranch pipeline failing
Title: Message Title Mike Henderson commented on JENKINS-49723 Re: Powershell execution within GIT Multibranch pipeline failing I stood up a new instance of 2.89.4 with latest plugins on a Windows 2016 machine and this does not exhibit this issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49723) Powershell execution within GIT Multibranch pipeline failing
Title: Message Title Mike Henderson created an issue Jenkins / JENKINS-49723 Powershell execution within GIT Multibranch pipeline failing Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2018-02-23 21:03 Environment: Jenkins 2.89.3 and 2.89.4 running on Window 2008 R2 Labels: pipeline Priority: Blocker Reporter: Mike Henderson I have been using Jenkins GIT Multibranch for a few weeks now. Today I upgraded to 2.89.4 and consequently my existing job started failing on the powershell execution: Started by user Mike Henderson > C:\Program Files\Git\bin\git.exe rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://pbsorters.visualstudio.com/Sorter%20Projects/Sorter%20Projects%20Team/_git/Software_C_Sharp > C:\Program Files\Git\bin\git.exe config remote.origin.url https://pbsorters.visualstudio.com/Sorter%20Projects/Sorter%20Projects%20Team/_git/Software_C_Sharp timeout=10 Fetching origin... Fetching upstream changes from origin > C:\Program Files\Git\bin\git.exe --version # timeout=10 using GIT_ASKPASS to set credentials Jenkins Feb-2018 > C:\Program Files\Git\bin\git.exe fetch --tags --progress origin +refs/heads/:refs/remotes/origin/ Seen branch in repository origin/Release1.5 Seen branch in repository origin/Task11982 Seen branch in repository origin/TestJenkinsFile Seen branch in repository origin/sqa1.5 Seen 4 remote branches Obtained Jenkinsfile from 55e5fb519d6276a4b566d6dfdf5de88e395cc125 Running in
[JIRA] [core] (JENKINS-35257) Release plugin ignores release parameters in Jenkins 2.7
Title: Message Title Mike Henderson commented on JENKINS-35257 Re: Release plugin ignores release parameters in Jenkins 2.7 I found a workaround that I used to deal with this issue. My project(s) that use the release plugin did not use any parameters, so I added the same string parameter label as a build parameter. This allowed the release plugin sting parameter to overwrite/update the build parameter and keep my workflow the same. I hope this helps others with the same issue. I am using Jenkins 2.8 with Release Plugin 2.5.4 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-12806) Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes
Mike Henderson commented on JENKINS-12806 Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes Is there any chance that this will be worked on? I know you considered it minor, but it really isn't for us. I have 6-10 jobs that I have to manipulate manually in the config.xml because the editor is broken with this bug. I can not safely ignore the error, the editor is unusable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12806) Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes
Mike Henderson commented on JENKINS-12806 Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes It acts differently in some browsers. Chrome fails completely and returns to the login screen. (This is my primary browser and the one I was basing my response on) Firefox seems to allow the changes but has this as an error below the map box: "HTTP/0.9 403 Forbidden Server: Winstone Servlet Engine v0.9.10 Content-Type: text/html;charset=UTF-8 Content-Length: 781 Connection: Close Date: Fri, 05 Oct 2012 16:50:01 GMT X-Powered-By: Servlet/2.5 (Winstone/0.9.10) Set-Cookie: JSESSIONID.a0ab2be0=af1fd378a0d73bbc661ac71ae7df2b3c; Path=/; HttpOnly Authentication required " IE 9 also shows the "ERROR Authentication required" below the map box. Other browsers (with combinations of plugins and updates unknown) have no luck with this as I have seen on my colleagues computers. So, I have been responsible for months manipulating these jobs by hand. Today when I retested it did seem to work in Firefox and IE9 but I have had troubles in the past with these as well. Firefox and IE never log the person out like Chrome does though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12806) Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes
Mike Henderson created JENKINS-12806: Summary: Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes Key: JENKINS-12806 URL: https://issues.jenkins-ci.org/browse/JENKINS-12806 Project: Jenkins Issue Type: Bug Components: perforce Affects Versions: current Environment: Windows 2003 R1 32 Bit / Jenkins 1.450 / Perforce 1.3.7 Reporter: Mike Henderson Attachments: config.xml I have a job that gathers a lot of different components from Perforce and we recently added a few new lines. After the job built once we attemt to go back into the config screen for the job and the settings come up but we get a ERROR just below the mapping that once you click on it it shows a 404 error and after that the user is logged out of Jenkins. If I delete the project mapping from the config.xml and reload from the disk the job is editable again until the next build. I have tried to use the clientspec feature but this also adds back in the projectPath key in the config.xml and again the error reoccurs after the first build. Right now the only work around is to modify the job file manually with a text editor. The jobs seem to build just fine. I have attached a job config file to show the issue. If I reduce the mapping down to 2974 bytes the error goes away and does not seem to return. My feeling is it is in the parser of the mapping, but that is a guess. For user login control we currently are using Project-based Matrix Authorization Strategy with Jenkins's own user database. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12806) Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes
[ https://issues.jenkins-ci.org/browse/JENKINS-12806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159176#comment-159176 ] Mike Henderson commented on JENKINS-12806: -- If I remove security by allowing everyone to do anything the bug changes to showing a parsing error in the workspace mapping at the line where it flows over 2975 bytes. This error does not seem to effect the job itself and the entire workspace is synced just fine. I hope that helps to pinpoint the issue. Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes - Key: JENKINS-12806 URL: https://issues.jenkins-ci.org/browse/JENKINS-12806 Project: Jenkins Issue Type: Bug Components: perforce Affects Versions: current Environment: Windows 2003 R1 32 Bit / Jenkins 1.450 / Perforce 1.3.7 Reporter: Mike Henderson Labels: jenkins, user, windows Attachments: config.xml I have a job that gathers a lot of different components from Perforce and we recently added a few new lines. After the job built once we attemt to go back into the config screen for the job and the settings come up but we get a ERROR just below the mapping that once you click on it it shows a 404 error and after that the user is logged out of Jenkins. If I delete the project mapping from the config.xml and reload from the disk the job is editable again until the next build. I have tried to use the clientspec feature but this also adds back in the projectPath key in the config.xml and again the error reoccurs after the first build. Right now the only work around is to modify the job file manually with a text editor. The jobs seem to build just fine. I have attached a job config file to show the issue. If I reduce the mapping down to 2974 bytes the error goes away and does not seem to return. My feeling is it is in the parser of the mapping, but that is a guess. For user login control we currently are using Project-based Matrix Authorization Strategy with Jenkins's own user database. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12806) Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes
[ https://issues.jenkins-ci.org/browse/JENKINS-12806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159188#comment-159188 ] Mike Henderson commented on JENKINS-12806: -- I get a Invalid mapping: followed by whichever line hits the 2975 bytes. If I shorten the mapping, the error goes away. Thanks for the sure fast follow up! Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes - Key: JENKINS-12806 URL: https://issues.jenkins-ci.org/browse/JENKINS-12806 Project: Jenkins Issue Type: Bug Components: perforce Affects Versions: current Environment: Windows 2003 R1 32 Bit / Jenkins 1.450 / Perforce 1.3.7 Reporter: Mike Henderson Assignee: Rob Petti Labels: jenkins, user, windows Attachments: config.xml I have a job that gathers a lot of different components from Perforce and we recently added a few new lines. After the job built once we attemt to go back into the config screen for the job and the settings come up but we get a ERROR just below the mapping that once you click on it it shows a 404 error and after that the user is logged out of Jenkins. If I delete the project mapping from the config.xml and reload from the disk the job is editable again until the next build. I have tried to use the clientspec feature but this also adds back in the projectPath key in the config.xml and again the error reoccurs after the first build. Right now the only work around is to modify the job file manually with a text editor. The jobs seem to build just fine. I have attached a job config file to show the issue. If I reduce the mapping down to 2974 bytes the error goes away and does not seem to return. My feeling is it is in the parser of the mapping, but that is a guess. For user login control we currently are using Project-based Matrix Authorization Strategy with Jenkins's own user database. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
