[JIRA] [tfs] (JENKINS-20426) FATAL: The IdentityManagementService is not available from the server
Olivier Dagenais commented on JENKINS-20426 FATAL: The IdentityManagementService is not available from the server Pull request #22 was replaced by pull request #23 and merged. Changes will appear in the next release. 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/groups/opt_out.
[JIRA] [tfs] (JENKINS-3785) Add option to perform labeling for each TFS build
Olivier Dagenais closed JENKINS-3785 as Fixed Add option to perform labeling for each TFS build Fixed in release 3.1.1 Change By: Olivier Dagenais (25/Feb/14 4:44 PM) Status: Resolved Closed Assignee: redsolo jeffolson 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/groups/opt_out.
[JIRA] [tfs] (JENKINS-20426) FATAL: The IdentityManagementService is not available from the server
Olivier Dagenais resolved JENKINS-20426 as Fixed FATAL: The IdentityManagementService is not available from the server Fixed in release 3.1.1 Change By: Olivier Dagenais (25/Feb/14 4:44 PM) Status: InProgress Resolved Assignee: OlivierDagenais KyleOConnor 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/groups/opt_out.
[JIRA] [git] (JENKINS-21401) NTLM authentication issue when using Git repository hosted on Team Foundation Server 2013
Olivier Dagenais stopped work on JENKINS-21401 NTLM authentication issue when using Git repository hosted on Team Foundation Server 2013 Change By: Olivier Dagenais (24/Feb/14 3:40 PM) Status: InProgress Open 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/groups/opt_out.
[JIRA] [git] (JENKINS-21401) NTLM authentication issue when using Git repository hosted on Team Foundation Server 2013
Olivier Dagenais resolved JENKINS-21401 as Fixed NTLM authentication issue when using Git repository hosted on Team Foundation Server 2013 The fix should be in the next release of git-client-plugin Change By: Olivier Dagenais (24/Feb/14 3:41 PM) Status: Open Resolved Assignee: OlivierDagenais NicolasDeLoof 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/groups/opt_out.
[JIRA] [tfs] (JENKINS-20426) FATAL: The IdentityManagementService is not available from the server
Olivier Dagenais started work on JENKINS-20426 FATAL: The IdentityManagementService is not available from the server Change By: Olivier Dagenais (24/Feb/14 10:25 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/groups/opt_out.
[JIRA] [tfs] (JENKINS-20426) FATAL: The IdentityManagementService is not available from the server
Olivier Dagenais commented on JENKINS-20426 FATAL: The IdentityManagementService is not available from the server Pull request #22 was submitted. 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/groups/opt_out.
[JIRA] [git] (JENKINS-21401) NTLM authentication issue when using Git repository hosted on Team Foundation Server 2013
Olivier Dagenais commented on JENKINS-21401 NTLM authentication issue when using Git repository hosted on Team Foundation Server 2013 Pull request #116 submitted. 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21887) Check git version before attempting to use credential.helper
Olivier Dagenais created JENKINS-21887 Check git version before attempting to use credential.helper Issue Type: Improvement Assignee: Nicolas De Loof Components: git-client Created: 19/Feb/14 10:07 PM Description: GitHub's help page says: You need git 1.7.10 or newer to use the credential helper It would be nice if git-client could detect an unsupported version of Git and throw an error instead of making it look like something else is broken. (the call to git config succeeded, but the git fetch after it failed) Project: Jenkins Priority: Minor Reporter: Olivier Dagenais 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/groups/opt_out.
[JIRA] [git] (JENKINS-21401) NTLM authentication issue when using Git repository hosted on Team Foundation Server 2013
Olivier Dagenais started work on JENKINS-21401 NTLM authentication issue when using Git repository hosted on Team Foundation Server 2013 Change By: Olivier Dagenais (13/Feb/14 6:16 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/groups/opt_out.
[JIRA] [git] (JENKINS-21401) NTLM authentication issue when using Git repository hosted on Team Foundation Server 2013
Olivier Dagenais assigned JENKINS-21401 to Olivier Dagenais NTLM authentication issue when using Git repository hosted on Team Foundation Server 2013 Change By: Olivier Dagenais (13/Feb/14 6:16 PM) Assignee: NicolasDeLoof OlivierDagenais 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/groups/opt_out.
[JIRA] [tfs] (JENKINS-20591) Polling Does not happen with the latest TFS plugin
Olivier Dagenais resolved JENKINS-20591 as Not A Defect Polling Does not happen with the latest TFS plugin After working privately with the reporter, it was determined to be a configuration error: TEE CLC needed to be installed on the master (and in the path) The EULA needed to be accepted by the user running Jenkins on the master Change By: Olivier Dagenais (15/Nov/13 8:23 PM) Status: Open Resolved Assignee: OlivierDagenais anuraghReddy 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/groups/opt_out.
[JIRA] [tfs] (JENKINS-20591) Polling Does not happen with the latest TFS plugin
Olivier Dagenais commented on JENKINS-20591 Polling Does not happen with the latest TFS plugin Did you restart the agent/service on the slave? A change in environment variables isn't always propagated to running processes and often you need to restart the process and maybe even the process tree. What happens if you log on as user XXX on the slave, switch to the C:\Users\XXX\workspace\-Build folder and run tf? 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/groups/opt_out.
[JIRA] [tfs] (JENKINS-20591) Polling Does not happen with the latest TFS plugin
Olivier Dagenais assigned JENKINS-20591 to Olivier Dagenais Polling Does not happen with the latest TFS plugin Change By: Olivier Dagenais (15/Nov/13 2:29 PM) Assignee: redsolo OlivierDagenais 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/groups/opt_out.
[JIRA] [tfs] (JENKINS-20591) Polling Does not happen with the latest TFS plugin
Olivier Dagenais commented on JENKINS-20591 Polling Does not happen with the latest TFS plugin The default value for the TF command line executable setting is tf. It looks like you might have instead set it to an absolute path that's only valid on Windows. After making sure the value is set to tf, can you try installing the Team Explorer Everywhere CLC on the master and making sure the tf it installs is in the path for the user running Jenkins? On the Windows slave, make sure TF.exe is also in the path for the user running the agent. 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/groups/opt_out.
[JIRA] [tfs] (JENKINS-20426) FATAL: The IdentityManagementService is not available from the server
Olivier Dagenais commented on JENKINS-20426 FATAL: The IdentityManagementService is not available from the server Thanks for reporting this; a similar error was reported to me and I suspected TFS 2008 to be the problem. I only tested with TFS 2012. Until I get around to investigating what functionality of the SDK I can use instead, you can downgrade to version 2.0 of the 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/groups/opt_out.
[JIRA] [tfs] (JENKINS-20426) FATAL: The IdentityManagementService is not available from the server
Olivier Dagenais assigned JENKINS-20426 to Olivier Dagenais FATAL: The IdentityManagementService is not available from the server Change By: Olivier Dagenais (11/Nov/13 3:13 PM) Assignee: redsolo OlivierDagenais 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/groups/opt_out.
[JIRA] [rake] (JENKINS-18822) Unable to use default rake on Windows with certain JREs
Olivier Dagenais created JENKINS-18822 Unable to use default rake on Windows with certain JREs Issue Type: Bug Affects Versions: current Assignee: Olivier Dagenais Components: rake Created: 18/Jul/13 2:24 PM Description: Create a job with a rake step that is to use the default rake installation and then run the job on a Windows agent that has one of the affected JREs in use. The job will fail with: [workspace] $ rake.bat '"C:\path\to\Jenkins\jobs\jobName\workspace\ruby.exe"' is not recognized as an internal or external command, operable program or batch file. Build step 'Invoke Rake' marked build as failure This appears to be caused by JDK-8016721 : (process) Behavior of %~dp0 in .cmd and .bat scripts has changed whereby affected JRE versions try to create a sub-process with: cmd /c ""rake.bat"" ...instead of: cmd /c rake.bat ...as previous versions of the JRE used to. When configuring a non-default rake installation, the path to the batch file will be absolute and this seems to not break rake.bat. Environment: JRE 1.7.21 - JRE 1.7.25 on Windows Project: Jenkins Labels: windows plugin Priority: Minor Reporter: Olivier Dagenais 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/groups/opt_out.
[JIRA] [rake] (JENKINS-18822) Unable to use default rake on Windows with certain JREs
Olivier Dagenais started work on JENKINS-18822 Unable to use default rake on Windows with certain JREs Change By: Olivier Dagenais (18/Jul/13 2:25 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/groups/opt_out.
[JIRA] [rake] (JENKINS-18822) Unable to use default rake on Windows with certain JREs
Olivier Dagenais stopped work on JENKINS-18822 Unable to use default rake on Windows with certain JREs Change By: Olivier Dagenais (18/Jul/13 8:45 PM) Status: InProgress Open 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/groups/opt_out.
[JIRA] [rake] (JENKINS-7530) Rake plugin fails when Job configured to use (Default) Rake installation.
Olivier Dagenais commented on JENKINS-7530 Rake plugin fails when Job configured to use (Default) Rake installation. FYI, I have created (and submitted a fix for) issue JENKINS-18822 which might interest 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/groups/opt_out.
[JIRA] [rake] (JENKINS-18822) Unable to use default rake on Windows with certain JREs
Olivier Dagenais commented on JENKINS-18822 Unable to use default rake on Windows with certain JREs I have submitted pull request #13 to fix 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 -- 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/groups/opt_out.
[JIRA] [rake] (JENKINS-7530) Rake plugin fails when Job configured to use (Default) Rake installation.
Olivier Dagenais commented on JENKINS-7530 Rake plugin fails when Job configured to use (Default) Rake installation. John and Vikram: What version of Java is running on the machines where this happens? I think I narrowed a bug with the same repro steps as this one's title (and a similar work-around: specify a non-default Rake), but with a different root cause. I have reproduced when trying to launch the job on both a Windows master or a Windows slave, and I always get: [workspace] $ rake.bat '"C:\path\to\Jenkins\jobs\jobName\workspace\ruby.exe"' is not recognized as an internal or external command, operable program or batch file. Build step 'Invoke Rake' marked build as failure 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/groups/opt_out.
