[JIRA] [git-plugin] (JENKINS-30350) Jobs get triggered twice from polling git scm
Title: Message Title tsondergaard commented on JENKINS-30350 Re: Jobs get triggered twice from polling git scm Seeing same behaviour as reported in previous comment, except we are using bitbucket webhooks to "git-notify" jenkins. We are running jenkins 1.609.2 git client plugin 1.19.0 git plugin 2.4.0 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] [git-plugin] (JENKINS-30032) Git plugin cannot find ssh with Git for Windows version 2.5.0
Title: Message Title tsondergaard resolved as Fixed After retrying again tonight, it works fine. My bad. Setting the bug back to resolved-fixed. Jenkins / JENKINS-30032 Git plugin cannot find ssh with Git for Windows version 2.5.0 Change By: tsondergaard Status: Reopened Resolved Resolution: Fixed 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] [git-plugin] (JENKINS-30032) Git plugin cannot find ssh with Git for Windows version 2.5.0
Title: Message Title tsondergaard commented on JENKINS-30032 Re: Git plugin cannot find ssh with Git for Windows version 2.5.0 Sorry Mark Waite, I made a mistake. The PATH I showed was after uninstalling Git for Windows 2.5.0 and installing the previos 1.9.5 version. The difference is that git is found in C:\Program Files\Git\cmd instead. It is the 64-bit version of git 2.5.0 I have tried and the Windows is 64-bit, as you have deduced. I will give Git for Window 2.5.0 another go with jenkins and report back. 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] [git-plugin] (JENKINS-30032) Git plugin cannot find ssh with Git for Windows version 2.5.0
Title: Message Title
tsondergaard edited a comment on JENKINS-30032
Re: Git plugin cannot find ssh with Git for Windows version 2.5.0
Yes, I did restart the jenkins server. The slave system information reports{panel:title=java.library.path}C:\java\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\java\bin;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\strawberry\perl\site\bin;C:\strawberry\perl\bin;C:\Ruby193\bin;C:\Program Files (x86)\CVSNT\;C:\Program Files\Microsoft Windows Performance Toolkit\;C:\Program Files (x86)\PuTTY;C:\Program Files (x86)\Xoreax\IncrediBuild;C:\Program Files (x86)\Windows Installer XML v3.5\bin;C:\Program Files (x86)\CMake 2.8\bin;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\SafeNet\Authentication\SAC\x64;C:\Program Files\SafeNet\Authentication\SAC\x32;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;C:\Program Files (x86)\Git\cmd;"C:\java\bin";.{panel}I set the PATH to the above in a cmd.exe prompt and ssh is not in it:{noformat}C:\Users\jenkins>where sshINFO: Could not find files for the given pattern(s).{noformat}
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] [git-plugin] (JENKINS-30032) Git plugin cannot find ssh with Git for Windows version 2.5.0
Title: Message Title tsondergaard commented on JENKINS-30032 Re: Git plugin cannot find ssh with Git for Windows version 2.5.0 Yes, I did restart the jenkins server. The slave system information reports java.library.path C:\java\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\java\bin;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\strawberry\perl\site\bin;C:\strawberry\perl\bin;C:\Ruby193\bin;C:\Program Files (x86)\CVSNT\;C:\Program Files\Microsoft Windows Performance Toolkit\;C:\Program Files (x86)\PuTTY;C:\Program Files (x86)\Xoreax\IncrediBuild;C:\Program Files (x86)\Windows Installer XML v3.5\bin;C:\Program Files (x86)\CMake 2.8\bin;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\SafeNet\Authentication\SAC\x64;C:\Program Files\SafeNet\Authentication\SAC\x32;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;C:\Program Files (x86)\Git\cmd;"C:\java\bin";. I set the PATH to the above in a cmd.exe prompt ssh is not in it: C:\Users\jenkins>where ssh INFO: Could not find files for the given pattern(s). 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 receiv
[JIRA] [git-plugin] (JENKINS-30032) Git plugin cannot find ssh with Git for Windows version 2.5.0
Title: Message Title tsondergaard reopened an issue Problem still occurs with new git client plugin 1.19.0: 12:07:15 Started by upstream project "easyviz-7.1-packages" build number 66 12:07:15 originally caused by: 12:07:15 Started by user Thomas Sondergaard 12:07:15 [EnvInject] - Loading node environment variables. 12:07:16 Building remotely on bob-w7 (win32-vc120 win32) in workspace f:\jenkins\workspace\easyviz-7.1-packages\arch\win32 12:07:18 > C:\Program Files\Git\bin\git.exe rev-parse --is-inside-work-tree # timeout=10 12:07:18 Fetching changes from the remote Git repository 12:07:18 > C:\Program Files\Git\bin\git.exe config remote.origin.url g...@bitbucket.org:karoshealth/easyviz.git # timeout=10 12:07:18 Pruning obsolete local branches 12:07:18 Fetching upstream changes from g...@bitbucket.org:karoshealth/easyviz.git 12:07:18 > C:\Program Files\Git\bin\git.exe --version # timeout=10 12:07:18 using GIT_SSH to set credentials 12:07:18 FATAL: ssh executable not found. The git plugin only supports official git client http://git-scm.com/download/win 12:07:18 java.lang.RuntimeException: ssh executable not found. The git plugin only supports official git client http://git-scm.com/download/win 12:07:18 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getSSHExecutable(CliGitAPIImpl.java:1569) 12:07:18 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.createWindowsGitSSH(CliGitAPIImpl.java:1575) 12:07:18 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1305) 12:07:18 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:62) 12:07:18 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:313) 12:07:18 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) 12:07:18 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) 12:07:18 at hudson.remoting.UserRequest.perform(UserRequest.java:121) 12:07:18 at hudson.remoting.UserRequest.perform(UserRequest.java:49) 12:07:18 at hudson.remoting.Request$2.run(Request.java:325) 12:07:18 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) 12:07:18 at java.util.concurrent.FutureTask.run(Unknown Source) 12:07:18 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 12:07:18 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 12:07:18 at hudson.remoting.Engine$1$1.run(Engine.java:69) 12:07:18 at java.lang.Thread.run(Unknown Source) 12:07:18 at ..remote call to bob-w7(Native Method) 12:07:18 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1360) 12:07:18 at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) 12:07:18 at hudson.remoting.Channel.call(Channel.java:753) 12:07:18 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145) 12:07:18 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 12:07:18 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 12:07:18 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 12:07:18 at java.lang.reflect.Method.invoke(Method.java:497) 12:07:18 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131) 12:07:18 at com.sun.proxy.$Proxy69.execute(Unknown Source) 12:07:18 at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:761) 12:07:18 at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1012) 12:07:18 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1043) 12:07:18 at hudson.scm.SCM.checkout(SCM.java:484) 12:07:18 at hudson.model.AbstractProject.checkout(AbstractProject.java:1274) 12:07:18 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) 12:07:18 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 12:07:18 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531) 12
[JIRA] [git-plugin] (JENKINS-30032) Git does not work with new Git for Windows version 2.5.0
Title: Message Title tsondergaard created an issue Jenkins / JENKINS-30032 Git does not work with new Git for Windows version 2.5.0 Issue Type: Bug Assignee: Nicolas De Loof Attachments: log.txt Components: git-plugin Created: 19/Aug/15 1:09 PM Environment: Windows 7 slave, Jenkins 1.609.2, git plugin 2.4.0, git client plugin 1.18.0. Priority: Critical Reporter: tsondergaard The git plugin is confused about ssh.exe not being in the path. Please see the attached log. I have the slave set up with git tool path set to C:\Program Files\Git\bin\git.exe.
[JIRA] [core] (JENKINS-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
tsondergaard commented on JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive The problem appears to be eliminated or at least significantly reduced by disabling the "Windows Search" indexing service. Also look out for anti-virus programs causing problems. http://www.pcmag.com/slideshow_viewer/0,3253,l=251692&a=251692&po=4,00.asp 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 -- 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] [envinject] (JENKINS-24785) BUILD_CAUSE always UPSTREAMTRIGGER in multi-configuration jobs
tsondergaard edited a comment on JENKINS-24785 BUILD_CAUSE always UPSTREAMTRIGGER in multi-configuration jobs I have made a pull request that fixes this problem. The idea is to introduce a ROOT_BUILD_CAUSE variable that expands Cause.UpstreamCause to it's root causes. https://github.com/jenkinsci/envinject-plugin/pull/33 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 -- 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] [envinject] (JENKINS-24785) BUILD_CAUSE always UPSTREAMTRIGGER in multi-configuration jobs
tsondergaard edited a comment on JENKINS-24785 BUILD_CAUSE always UPSTREAMTRIGGER in multi-configuration jobs I have made a commit here to try to fix this problem. The idea is to introduce a ROOT_BUILD_CAUSE variable that expands Cause.UpstreamCause to it's root causes. https://github.com/tsondergaard/envinject-plugin/commit/30bce2733346983097b00c46a313a26767756818 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 -- 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] [envinject] (JENKINS-24785) BUILD_CAUSE always UPSTREAMTRIGGER in multi-configuration jobs
tsondergaard edited a comment on JENKINS-24785 BUILD_CAUSE always UPSTREAMTRIGGER in multi-configuration jobs I have made a commit here to try to fix this problem. The idea is to introduce a ROOT_BUILD_CAUSE variable that expands Cause.UpstreamCause to it's root causes. https://github.com/tsondergaard/envinject-plugin/commit/f8e1589d9b5ad6e68b4b09cfb4df76247fd15048 I haven't tested it yet, but perhaps someone here could take a look at it 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 -- 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] [envinject] (JENKINS-24785) BUILD_CAUSE always UPSTREAMTRIGGER in multi-configuration jobs
tsondergaard updated JENKINS-24785 BUILD_CAUSE always UPSTREAMTRIGGER in multi-configuration jobs Change By: tsondergaard (22/Sep/14 6:22 AM) Summary: BUILD_CAUSE useless always UPSTREAMTRIGGER in multi-configuration jobs 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 -- 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] [envinject] (JENKINS-24785) BUILD_CAUSE useless in multi-configuration jobs
tsondergaard commented on JENKINS-24785 BUILD_CAUSE useless in multi-configuration jobs I have made a commit here to try to fix this problem. The idea is to introduce a ROOT_BUILD_CAUSE variable that expands Cause.UpstreamCause to it's root causes. https://github.com/tsondergaard/envinject-plugin/commit/842b5a2e0eb7a04da34d5920dbd304a02dac0dfb It doesn't quite compile because Cause.UpstreamCause.getUpstreamCauses() cannot be found by the compiler. I assume it is because this function is not marked with @Exported(visibility=3), but I don't know enough about Java or the jenkins code base to be sure. 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 -- 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] [envinject] (JENKINS-24785) BUILD_CAUSE useless in multi-configuration jobs
tsondergaard created JENKINS-24785 BUILD_CAUSE useless in multi-configuration jobs Issue Type: Bug Assignee: Gregory Boissinot Components: envinject Created: 20/Sep/14 7:57 PM Description: BUILD_CAUSE is always set to UPSTREAMTRIGGER in the slaves/children of of multi-configuration jobs, which is not very useful. Environment: Jenkins version 1.509.4, envinject version 1.85 Project: Jenkins Priority: Major Reporter: tsondergaard 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 -- 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-14336) Too many open files upon HTTP listener init or shutdown
tsondergaard commented on JENKINS-14336 Too many open files upon HTTP listener init or shutdown Also on 1.485 running on RHEL-6.2 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-14138) New git branch has empty changelist
tsondergaard commented on JENKINS-14138 New git branch has empty changelist @nhnb: The change to use the merge target as baseline for computing the changelog has been accepted (commit 5ae255594bd7e118bee6c58eae504d1c49e9f97b). As far as I'm concerned this bug can be resolved now, but I don't think the OP is satisfied. 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-15019) Improvements when used with non-java code using gcovr
tsondergaard created JENKINS-15019 Improvements when used with non-java code using gcovr Issue Type: New Feature Assignee: stephenconnolly Components: cobertura Created: 02/Sep/12 7:04 PM Description: With gcovr the cobertura plugin can be used for coverage reports for C and C++ programs. The following changes would be very useful in this context: Being able to remove the "Classes" statistics from tables and graphs as the data is identical to the "Files" statistics. Being able to relabel "Packages" as "Directories" in graphs and tables Being able to use / as separator instead of . in package-names (directory-names) With these changes the "java-ness" would be removed from the interface. This changes could be enabled based on a marker in the cobertura xml. Already gcovr puts "gcovr 2.5-prerelease (r2774)" as the version attribute on the root element, so it is easy to detect. Project: Jenkins Priority: Minor Reporter: tsondergaard 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-14138) New git branch has empty changelist
tsondergaard commented on JENKINS-14138 New git branch has empty changelist No, the patch only changes the behavior for the case where there is a merge target. The merge target branch is a reasonable reference for new (not built before) branches - Without it what would you consider a reasonable reference? From your comment 9/Jun/12 12:03 it is clear that you would want the changeset to be relative to 'master', but 'master' is just another branch to git. How should it know that you want change sets to be computed relative to 'master'? A change that could serve both of us would be to add a configuration option to the git plugin where you can specify that you want changesets to be computed relative to a named branch, ie you would have to check a box "Compute changesets relative to named branch" and fill in the name of the branch. That would work for both of us. 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-14138) New git branch has empty changelist
tsondergaard updated JENKINS-14138 New git branch has empty changelist Patch to make git plugin compute changelog differently for jobs configured with a merge-target Change By: tsondergaard (23/Jul/12 12:19 PM) Attachment: git-plugin.diff 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-14138) New git branch has empty changelist
tsondergaard commented on JENKINS-14138 New git branch has empty changelist I'm seeing a similar problem. I am using the git plugin with a configured. It is therefore quite typical for devs to check in temporary branches that git then merges to the branch and pushes back to the central repo. As it is now this means that jenkins doesn't send emails in the case of a build failure for such new branches. I've noticed in the console output from builds on new branches that the git-plugin writes No change to record in branch XXX This is written by the git-plugin if it cannot find a previous build. In the case where a job is configured with a mergeTarget I believe that the right solution is either 1. always use / as the previous ref or 2. Look for a previous build for the branch first and then fall back to / The names and are from the config.xml file, where I for example have: origin release/5.0.0 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-14026) git plugin doesn't support branch name contains slash ("/")
[
https://issues.jenkins-ci.org/browse/JENKINS-14026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163697#comment-163697
]
tsondergaard commented on JENKINS-14026:
I'm on jenkins 1.467 and with git plugin version 1.1.19 I get the following
error. After downgrading to version 1.1.16 the problem went away. Is it the
same problem as reported in this bug?
Here's the log output with git plugin 1.1.19 and a fresh workspace:
Started by upstream project "easyviz-5-integrate" build number 21
[EnvInject] - Loading node environment variables.
Building remotely on bob-w7-64 in workspace
c:\jenkins\workspace\easyviz-5-integrate\arch\win32
Checkout:win32 / c:\jenkins\workspace\easyviz-5-integrate\arch\win32 -
hudson.remoting.Channel@2f860a43:bob-w7-64
Using strategy: Default
Last Built Revision: Revision d7e55522feb251a876a5e8c1d1370686b77db1b5
(origin/for-5.0.0/bug-14364-build-manual)
Fetching changes from 1 remote Git repository
Fetching upstream changes from
ssh://buildu...@git.medical-insight.com/var/git/easyviz.git
Pruning obsolete local branches
Commencing build of Revision e3e816d8d00386d76bfb615044c0acf1fa89f963
(origin/for-5.0.0/bug-14466-cppcheck)
Merging Revision e3e816d8d00386d76bfb615044c0acf1fa89f963
(origin/for-5.0.0/bug-14466-cppcheck) onto release/5.0.0
FATAL: Command "C:\Program Files (x86)\Git\bin\git.exe rev-parse
origin/release/5.0.0^^\{commit\}" returned status code 128:
stdout: origin/release/5.0.0^^\{commit\}
stderr: fatal: ambiguous argument 'origin/release/5.0.0^^\{commit\}': unknown
revision or path not in the working tree.
Use '--' to separate paths from revisions
hudson.plugins.git.GitException: Command "C:\Program Files
(x86)\Git\bin\git.exe rev-parse origin/release/5.0.0^^\{commit\}" returned
status code 128:
stdout: origin/release/5.0.0^^\{commit\}
stderr: fatal: ambiguous argument 'origin/release/5.0.0^^\{commit\}': unknown
revision or path not in the working tree.
Use '--' to separate paths from revisions
at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:786)
at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:748)
at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:758)
at hudson.plugins.git.GitAPI.revParse(GitAPI.java:261)
at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1214)
at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1197)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2180)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1$1.run(Engine.java:60)
at java.lang.Thread.run(Unknown Source)
> git plugin doesn't support branch name contains slash ("/")
> ---
>
> Key: JENKINS-14026
> URL: https://issues.jenkins-ci.org/browse/JENKINS-14026
> Project: Jenkins
> Issue Type: Bug
> Components: git
>Reporter: Yi Wen
> Labels: branch
>
> When a branch contains slash (/), if we try to specify such a branch in
> "Branch Name" field, it will not be able to fetch such branches. If we leave
> branch name as **, the job can fetch branch name containing slash without
> problem.
> I am not a Java person, but this method looks suspicious in Branch.java, just
> trying to help debug
> private static String strip(String name) {
> return name.substring(name.indexOf('/', 5) + 1);
> }
>
--
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-13647) Environment variables from EnvInject plugin are not inherited/parsed by batch tasks
[ https://issues.jenkins-ci.org/browse/JENKINS-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tsondergaard updated JENKINS-13647: --- Attachment: config.xml Note that in the attached config.xml the environment variables (EVVERSION among others) are manually duplicated in the make-release batch task (to make it work) > Environment variables from EnvInject plugin are not inherited/parsed by batch > tasks > --- > > Key: JENKINS-13647 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13647 > Project: Jenkins > Issue Type: Bug > Components: batch-task >Affects Versions: current >Reporter: tsondergaard >Assignee: Kohsuke Kawaguchi > Attachments: config.xml > > > Environment variables set for a job with the "Prepare an environment for the > run" and not processed/used for batch tasks. This is very similar to bug > JENKINS-5580 reported for batch tasks and the now deprecated setenv plugin -- 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-13647) Environment variables from EnvInject plugin are not inherited/parsed by batch tasks
tsondergaard created JENKINS-13647: -- Summary: Environment variables from EnvInject plugin are not inherited/parsed by batch tasks Key: JENKINS-13647 URL: https://issues.jenkins-ci.org/browse/JENKINS-13647 Project: Jenkins Issue Type: Bug Components: batch-task Affects Versions: current Reporter: tsondergaard Assignee: Kohsuke Kawaguchi Environment variables set for a job with the "Prepare an environment for the run" and not processed/used for batch tasks. This is very similar to bug JENKINS-5580 reported for batch tasks and the now deprecated setenv plugin -- 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
