[JIRA] [mstestrunner-plugin] (JENKINS-30292) MSTestRunner Plugin not visible in Conditional BuildStep Plugin
Title: Message Title Ido Ran started work on JENKINS-30292 Change By: Ido Ran Status: Open In Progress 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] [mstestrunner-plugin] (JENKINS-29391) Add support to GLOB Ant pattern in test files
Title: Message Title Ido Ran resolved as Fixed Fixed in 1.2.0 Jenkins / JENKINS-29391 Add support to GLOB Ant pattern in test files Change By: Ido Ran Status: Open Resolved Assignee: Ido Ran 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] [mstestrunner-plugin] (JENKINS-30292) MSTestRunner Plugin not visible in Conditional BuildStep Plugin
Title: Message Title Ido Ran resolved as Fixed Fixed in version 1.2.0 of MSTestRunner plugin Jenkins / JENKINS-30292 MSTestRunner Plugin not visible in Conditional BuildStep Plugin Change By: Ido Ran Status: In Progress 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] [mstestrunner-plugin] (JENKINS-28869) Does not split test files string on newline if input is loaded from properties file
Title: Message Title Ido Ran resolved as Fixed Fixed in 1.2.0 Jenkins / JENKINS-28869 Does not split test files string on newline if input is loaded from properties file Change By: Ido Ran Status: Open 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] [mstestrunner-plugin] (JENKINS-29389) Categories option does not allow quotation marks around single value
Title: Message Title Ido Ran resolved as Fixed Fixed in 1.2.0 Jenkins / JENKINS-29389 Categories option does not allow quotation marks around single value Change By: Ido Ran Status: Open 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] [mstestrunner-plugin] (JENKINS-24984) MSTestRunner is not usable as part of the conditional-buildstep plugin
Title: Message Title Ido Ran resolved as Fixed Fixed in 1.2.0 Jenkins / JENKINS-24984 MSTestRunner is not usable as part of the conditional-buildstep plugin Change By: Ido Ran Status: Open 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] [mstestrunner-plugin] (JENKINS-22618) NullPointerException at org.jenkinsci.plugins.MsTestBuilder.perform(MsTestBuilder.java:144)
Title: Message Title Ido Ran closed an issue as Fixed no response and no repro Jenkins / JENKINS-22618 NullPointerException at org.jenkinsci.plugins.MsTestBuilder.perform(MsTestBuilder.java:144) Change By: Ido Ran Status: Open Closed 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] [mstestrunner-plugin] (JENKINS-30292) MSTestRunner Plugin not visible in Conditional BuildStep Plugin
Title: Message Title Ido Ran commented on JENKINS-30292 Re: MSTestRunner Plugin not visible in Conditional BuildStep Plugin Can you please direct me to docs about the difference between ToolDescriptor and BuildStepDescriptor? 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] [core] (JENKINS-17569) False positive on git polling
Title: Message Title Ido Ran commented on JENKINS-17569 Re: False positive on git polling I have similar issue. I'm using Jenkins to deploy NodeJS app to Heroku, I'm doing so by having two git repositories configure, one I pull the code from and the other is Heroku's git to which I push. Because there is no way to define where to pull from when polling for changing Jenkins try to pull from everywhere and fail to pull from Heroku. The problem is when failing to pull it still decide there are changes. Using strategy: Default [poll] Last Built Revision: Revision 91905f2cdbf8fc109f7f11fcefdd171c94675e76 (origin/qa) using GIT_SSH to set credentials Seebo Jenkins SSH Key git -c core.askpass=true ls-remote -h g...@heroku.my-app.git qa # timeout=10 [poll] Couldn't get remote head revision Done. Took 3.4 sec Changes found 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] [gradle-plugin] (JENKINS-27310) gradle automatic install Invalid tool ID
Ido Ran created JENKINS-27310 gradle automatic install Invalid tool ID Issue Type: Bug Assignee: Gregory Boissinot Components: gradle-plugin Created: 10/Mar/15 11:51 AM Description: I've install Jenkins 1.602 on Mac OS X 10.10. When I install the gradle plugin and go into the Configure System page under Gradle I have Gradle Installations and I add Install from Gradle.org installer - the problem is I'm getting textbox instead of ComboBox to enter the Version parameter. I've try to write 2.2.1 inside the Version textbox but then I got this output when building the job: Gradle - Launching build. Invalid tool ID 2.2.1 Gradle - ERROR Can't retrieve the Gradle executable. Environment: Mac OS X 10.10 Project: Jenkins Priority: Critical Reporter: Ido Ran 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] [gradle-plugin] (JENKINS-27310) gradle automatic install Invalid tool ID
Ido Ran commented on JENKINS-27310 gradle automatic install Invalid tool ID You solve the problem - for some reason I didn't have this file. I've copy it from another installation I have and not it is working. I've done some manual copy of plugins, so it's probably something there went wrong. But I did uninstall and install Gradle plugin. I'll be happy to try and provide any information to try and repro the problem. Thank you, Ido. 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] [core] (JENKINS-27310) gradle automatic install Invalid tool ID
Ido Ran resolved JENKINS-27310 as Not A Defect gradle automatic install Invalid tool ID Issue was a missing file, I'm not sure why but it's not a bug. Change By: Ido Ran (10/Mar/15 5:20 PM) Status: Open Resolved Resolution: NotADefect 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] [core] (JENKINS-27310) gradle automatic install Invalid tool ID
Ido Ran commented on JENKINS-27310 gradle automatic install Invalid tool ID Sorry, didn't find it. I did had trouble downloading the plugin due to local internet problems so it may be related to that. Thank you. 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] (JENKINS-20941) Stored git credentials not used when submodule is updated
Ido Ran
commented on JENKINS-20941
Stored git credentials not used when submodule is updated
I also see this issue, I can use ssh credentials to fetch git repository from BitBucket but when it tries to fetch the submodule repository, which is on the same account, I get permission exception.
Fetching upstream changes from g...@bitbucket.org:mycomp/at.git
C:\CI\Git\bin\git.exe --version
using GIT_SSH to set credentials Bitbucket key
C:\CI\Git\bin\git.exe fetch --tags --progress g...@bitbucket.org:mycomp/at.git +refs/heads/:refs/remotes/origin/
C:\CI\Git\bin\git.exe rev-parse "origin/ci^{commit}"
Checking out Revision a079842300ba7fc9e6f4e7182c94af2cfc3af0ba (origin/ci)
C:\CI\Git\bin\git.exe config core.sparsecheckout
C:\CI\Git\bin\git.exe checkout -f a079842300ba7fc9e6f4e7182c94af2cfc3af0ba
C:\CI\Git\bin\git.exe rev-list a079842300ba7fc9e6f4e7182c94af2cfc3af0ba
C:\CI\Git\bin\git.exe remote
C:\CI\Git\bin\git.exe submodule init
C:\CI\Git\bin\git.exe submodule sync
C:\CI\Git\bin\git.exe config --get remote.origin.url
C:\CI\Git\bin\git.exe submodule update
FATAL: Command "C:\CI\Git\bin\git.exe submodule update" returned status code 1:
stdout:
stderr: Cloning into 'include/portal_air'...
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Clone of 'g...@bitbucket.org:mycomp/portal_air.git' into submodule path 'include/portal_air' failed
hudson.plugins.git.GitException: Command "C:\CI\Git\bin\git.exe submodule update" returned status code 1:
stdout:
stderr: Cloning into 'include/portal_air'...
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Clone of 'g...@bitbucket.org:mycomp/portal_air.git' into submodule path 'include/portal_air' failed
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1406)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:87)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$6.execute(CliGitAPIImpl.java:741)
at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:77)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:908)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1414)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580)
at hudson.model.Run.execute(Run.java:1684)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
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] [mstestrunner] (JENKINS-20367) If a failed test result the plugin causes a Failed build
Ido Ran started work on JENKINS-20367 If a failed test result the plugin causes a Failed build Change By: Ido Ran (04/Jun/14 3:02 PM) Status: Open InProgress 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] [mstestrunner] (JENKINS-20367) If a failed test result the plugin causes a Failed build
Ido Ran resolved JENKINS-20367 as Fixed If a failed test result the plugin causes a Failed build Fixed in version 1.1.0. I've add a checkbox for Continue On Failed Test which is off by default but when turned on the plugin will report success even when test have failed. Change By: Ido Ran (04/Jun/14 3:28 PM) Status: InProgress Resolved Resolution: Fixed 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] [mstestrunner] (JENKINS-17937) MSTestRunner issues when the path to the test project contains a space
Ido Ran resolved JENKINS-17937 as Fixed MSTestRunner issues when the path to the test project contains a space This issue has been resolved in version 1.0.1 Change By: Ido Ran (04/Jun/14 3:31 PM) Status: Open Resolved Assignee: IdoRan Resolution: Fixed 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] [mstestrunner] (JENKINS-20366) Results file field doesn't allow a folder to be specified before file name
Ido Ran commented on JENKINS-20366 Results file field doesnt allow a folder to be specified before file name Is that issue still relevant? 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] [mstestrunner] (JENKINS-17937) MSTestRunner issues when the path to the test project contains a space
Ido Ran edited a comment on JENKINS-17937 MSTestRunner issues when the path to the test project contains a space This issue has been resolved in version 1.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 -- 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] [mstestrunner] (JENKINS-22618) NullPointerException at org.jenkinsci.plugins.MsTestBuilder.perform(MsTestBuilder.java:144)
Ido Ran commented on JENKINS-22618 NullPointerException at org.jenkinsci.plugins.MsTestBuilder.perform(MsTestBuilder.java:144) Is this issue still relevant? 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-14316) Mstestrunner plugin adds /noisolation parameter to command which causes hanging of test
Ido Ran commented on JENKINS-14316 Mstestrunner plugin adds /noisolation parameter to command which causes hanging of test The fix was published on version 0.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-14273) Matrix jobs don't get loaded
Ido Ran commented on JENKINS-14273 Matrix jobs dont get loaded Version 1.475 is not release yet. How can I workaround this issue? 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-13007) Git plugin cannot find revision to build on Windows
[ https://issues.jenkins-ci.org/browse/JENKINS-13007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162794#comment-162794 ] Ido Ran commented on JENKINS-13007: --- I've work around the problem by installing previous version 1.1.15 of the plugin. You can download it from here http://updates.jenkins-ci.org/download/plugins/git/ Git plugin cannot find revision to build on Windows --- Key: JENKINS-13007 URL: https://issues.jenkins-ci.org/browse/JENKINS-13007 Project: Jenkins Issue Type: Bug Components: git Environment: Windows 2008 Server 64 Bit NTFS Reporter: ritzmann Assignee: Nicolas De Loof Priority: Critical After we upgraded the Git plugin from 1.1.14 to 1.1.16, all our builds on Windows build slaves started failing like this: Started by user anonymous Building remotely on win-slave1 in workspace d:\hudson\workspace\my-app Checkout:my-app / d:\hudson\workspace\my-app - hudson.remoting.Channel@95ff886:win-slave1 Using strategy: Default Last Built Revision: Revision e00e2c1328a011ca99980e0ffd90f7534b34 (origin/master) Checkout:my-app / d:\hudson\workspace\my-app - hudson.remoting.LocalChannel@470a4b80 Fetching changes from 1 remote Git repository Fetching upstream changes from d:\hudson\shared\repo.git ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. The builds on our Linux slaves are not affected. Wiping the workspaces on the Windows slaves did not help. Both clones and checkouts/updates seem to fail with the same error. Downgrading back to 1.1.14 made the Windows builds work again. -- 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-13007) Git plugin cannot find revision to build on Windows
[ https://issues.jenkins-ci.org/browse/JENKINS-13007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162768#comment-162768 ] Ido Ran commented on JENKINS-13007: --- I also have the same problem. After I upgrade from 1.1.15 to 1.1.18 I get this exact error Git plugin cannot find revision to build on Windows --- Key: JENKINS-13007 URL: https://issues.jenkins-ci.org/browse/JENKINS-13007 Project: Jenkins Issue Type: Bug Components: git Environment: Windows 2008 Server 64 Bit NTFS Reporter: ritzmann Assignee: Nicolas De Loof Priority: Critical After we upgraded the Git plugin from 1.1.14 to 1.1.16, all our builds on Windows build slaves started failing like this: Started by user anonymous Building remotely on win-slave1 in workspace d:\hudson\workspace\my-app Checkout:my-app / d:\hudson\workspace\my-app - hudson.remoting.Channel@95ff886:win-slave1 Using strategy: Default Last Built Revision: Revision e00e2c1328a011ca99980e0ffd90f7534b34 (origin/master) Checkout:my-app / d:\hudson\workspace\my-app - hudson.remoting.LocalChannel@470a4b80 Fetching changes from 1 remote Git repository Fetching upstream changes from d:\hudson\shared\repo.git ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. The builds on our Linux slaves are not affected. Wiping the workspaces on the Windows slaves did not help. Both clones and checkouts/updates seem to fail with the same error. Downgrading back to 1.1.14 made the Windows builds work again. -- 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
