[JIRA] [git-plugin] (JENKINS-30876) Gitlab plugin is not well integrated with SCM plugin
Title: Message Title Vasili Kvockin commented on JENKINS-30876 Re: Gitlab plugin is not well integrated with SCM plugin Is it possibly related to JENKINS-26587? 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-26587) Checkout fails with Multiple SCMs plugin on commit notification
Title: Message Title Vasili Kvockin updated an issue Jenkins / JENKINS-26587 Checkout fails with Multiple SCMs plugin on commit notification Change By: Vasili Kvockin Attachment: JENKINS-26587.tar.gz Attachment: Screen Shot 2015-10-10 at 18.42.27.png Attachment: Screen Shot 2015-10-10 at 18.11.43.png Attachment: Screen Shot 2015-10-10 at 18.06.21.png 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-26587) Checkout fails with Multiple SCMs plugin on commit notification
Title: Message Title
Vasili Kvockin updated an issue
Jenkins / JENKINS-26587
Checkout fails with Multiple SCMs plugin on commit notification
Change By:
Vasili Kvockin
also similar to https://github.com/janinko/ghprb/issues/171Setup:* free style project* multiple scms repository setting* two git repositories configured* stash notifications for both repositories* a commit is pushed to second repositoryBuild console output:{code}commit notification 108127644b30e28d326702752aa1150e05227156[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Injecting as environment variables the properties content [EnvInject] - Variables injected successfully.[EnvInject] - Injecting contributions.Building on master in workspace /home/jenkins/workspace/TestNotification > /usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > /usr/local/bin/git config remote.origin.url ssh://g...@git.mydomain.com:7999/project/repo1.git # timeout=10Fetching upstream changes from ssh://g...@git.mydomain.com:7999/project/repo1.git > /usr/local/bin/git --version # timeout=10 > /usr/local/bin/git -c core.askpass=true fetch --tags --progress ssh://g...@git.mydomain.com:7999/project/repo1.git +refs/heads/*:refs/remotes/origin/* > /usr/local/bin/git rev-parse 108127644b30e28d326702752aa1150e05227156^{commit} # timeout=10FATAL: Command "/usr/local/bin/git rev-parse 108127644b30e28d326702752aa1150e05227156^{commit}" returned status code 128:stdout: 108127644b30e28d326702752aa1150e05227156^{commit}stderr: fatal: ambiguous argument '108127644b30e28d326702752aa1150e05227156^{commit}': unknown revision or path not in the working tree.Use '--' to separate paths from revisions, like this:'git [...] -- [...]'hudson.plugins.git.GitException: Command "/usr/local/bin/git rev-parse 108127644b30e28d326702752aa1150e05227156^{commit}" returned status code 128:stdout: 108127644b30e28d326702752aa1150e05227156^{commit}stderr: fatal: ambiguous argument '108127644b30e28d326702752aa1150e05227156^{commit}': unknown revision or path not in the working tree.Use '--' to separate paths from revisions, like this:'git [...] -- [...]' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1457) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1433) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1429) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1117) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1127) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:523) at hudson.plugins.git.GitAPI.revParse(GitAPI.java:258) at hudson.plugins.git.RevisionParameterAction.toRevision(RevisionParameterAction.java:85) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:872) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:985) at hudson.scm.SCM.checkout(SCM.java:488) at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:118) at hudson.model.AbstractProject.checkout(AbstractProject.java:1252) at hudson.model.
[JIRA] [git-plugin] (JENKINS-26587) Checkout fails with Multiple SCMs plugin on commit notification
Title: Message Title Vasili Kvockin commented on JENKINS-26587 Re: Checkout fails with Multiple SCMs plugin on commit notification updated pull request with latest master 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-27097) wrong timezone reported in changes
Vasili Kvockin commented on JENKINS-27097 wrong timezone reported in changes Thank you for the clarification. No, I see no need to retain 1.6 compatibility. It would probably help the users if the git-plugin page would mention the minimum required java version. It already mentions minimum requirements for dependencies and git runtime. Additionally, it would help developers if there would be some kind of check for minimum version. At least they wouldn't then ask the same question I did. 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] [git-plugin] (JENKINS-27097) wrong timezone reported in changes
Vasili Kvockin commented on JENKINS-27097 wrong timezone reported in changes What is the minimum JDK compatibility level for Jenkins? One of the tests breaks with JDK 1.6 for me. With 1.7 it works. (OSX 10.10.2) Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6.444 sec <<< FAILURE! - in hudson.plugins.git.GitChangeSetTest testIsoDate(hudson.plugins.git.GitChangeSetTest) Time elapsed: 1.01 sec <<< ERROR! java.lang.IllegalArgumentException: Illegal pattern character 'X' at java.text.SimpleDateFormat.compile(SimpleDateFormat.java:768) at java.text.SimpleDateFormat.initialize(SimpleDateFormat.java:575) at java.text.SimpleDateFormat.(SimpleDateFormat.java:500) at java.text.SimpleDateFormat.(SimpleDateFormat.java:475) at hudson.plugins.git.GitChangeSet.getTimestamp(GitChangeSet.java:209) at hudson.plugins.git.GitChangeSetTest.testIsoDate(GitChangeSetTest.java:154) $ java -version java version "1.6.0_65" Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716) Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode) $ java -version java version "1.7.0_21" Java(TM) SE Runtime Environment (build 1.7.0_21-b12) Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode) 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] [git-plugin] (JENKINS-26587) Checkout fails with Multiple SCMs plugin on commit notification
Vasili Kvockin commented on JENKINS-26587 Checkout fails with Multiple SCMs plugin on commit notification still the same with 0.4 and latest git-plugin master 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] [git-plugin] (JENKINS-26587) Checkout fails with Multiple SCMs plugin on commit notification
Vasili Kvockin commented on JENKINS-26587 Checkout fails with Multiple SCMs plugin on commit notification Craig Rodrigues, I will check it and give you feedback 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] [git-plugin] (JENKINS-26587) Checkout fails with Multiple SCMs plugin on commit notification
Vasili Kvockin commented on JENKINS-26587 Checkout fails with Multiple SCMs plugin on commit notification Jesse Glick, you were the latest commiter on multiple-scms-plugin project and current assignee seems to be inactive on this tracker for a long time. Does it make sense for me to wait till somebody assigns the issue to himself? 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] [git-plugin] (JENKINS-26587) Checkout fails with Multiple SCMs plugin on commit notification
Vasili Kvockin updated JENKINS-26587 Checkout fails with Multiple SCMs plugin on commit notification Change By: Vasili Kvockin (24/Jan/15 10:28 PM) Component/s: git-plugin 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] [multiple-scms-plugin] (JENKINS-26587) Checkout fails with Multiple SCMs plugin on commit notification
Vasili Kvockin commented on JENKINS-26587 Checkout fails with Multiple SCMs plugin on commit notification possible fix in https://github.com/jenkinsci/git-plugin/pull/296 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] [multiple-scms-plugin] (JENKINS-26587) Checkout fails with Multiple SCMs plugin on commit notification
Vasili Kvockin
created JENKINS-26587
Checkout fails with Multiple SCMs plugin on commit notification
Issue Type:
Bug
Assignee:
Kevin Bell
Components:
multiple-scms-plugin
Created:
24/Jan/15 8:55 PM
Description:
also similar to https://github.com/janinko/ghprb/issues/171
Setup:
free style project
multiple scms repository setting
two git repositories configured
stash notifications for both repositories
a commit is pushed to second repository
Build console output:
commit notification 108127644b30e28d326702752aa1150e05227156
[EnvInject] - Loading node environment variables.
[EnvInject] - Preparing an environment for the build.
[EnvInject] - Keeping Jenkins system variables.
[EnvInject] - Keeping Jenkins build variables.
[EnvInject] - Injecting as environment variables the properties content
[EnvInject] - Variables injected successfully.
[EnvInject] - Injecting contributions.
Building on master in workspace /home/jenkins/workspace/TestNotification
> /usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> /usr/local/bin/git config remote.origin.url ssh://g...@git.mydomain.com:7999/project/repo1.git # timeout=10
Fetching upstream changes from ssh://g...@git.mydomain.com:7999/project/repo1.git
> /usr/local/bin/git --version # timeout=10
> /usr/local/bin/git -c core.askpass=true fetch --tags --progress ssh://g...@git.mydomain.com:7999/project/repo1.git +refs/heads/*:refs/remotes/origin/*
> /usr/local/bin/git rev-parse 108127644b30e28d326702752aa1150e05227156^{commit} # timeout=10
FATAL: Command "/usr/local/bin/git rev-parse 108127644b30e28d326702752aa1150e05227156^{commit}" returned status code 128:
stdout: 108127644b30e28d326702752aa1150e05227156^{commit}
stderr: fatal: ambiguous argument '108127644b30e28d326702752aa1150e05227156^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'
hudson.plugins.git.GitException: Command "/usr/local/bin/git rev-parse 108127644b30e28d326702752aa1150e05227156^{commit}" returned status code 128:
stdout: 108127644b30e28d326702752aa1150e05227156^{commit}
stderr: fatal: ambiguous argument '108127644b30e28d326702752aa1150e05227156^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1457)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1433)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1429)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1117)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1127)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:523)
at hudson.plugins.git.GitAPI.revParse(GitAPI.java:258)
at hudson.plugins.git.RevisionParameterAction.toRevision(RevisionParameterAction.java:85)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:872)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:985)
at hudson.scm.SCM.checkout(SCM.java:488)
at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:118)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1252)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:624)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:530)
at hudson.model.Run.execute(Run.java:1732)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:234)
Environment:
Jenkins 1.568
multiple-scms-plugin 0.4-beta-1
git-plugin 2.3.5-SNAPSHOT
