[JIRA] [teamconcert-git-plugin] (JENKINS-25762) Build Engine going inactive due to no credentials

[bb...@paychex.com (JIRA)]

bbonn created JENKINS-25762 Build Engine going inactive due to no credentials Issue Type: Bug Assignee: Krishna Kishore Components: teamconcert-git-plugin Created: 24/Nov/14 3:38 PM Description: Hi there, We were recently required by our security group to disable anonymous access in Jenkins. This has had a negative effect on our RTC integration. We have never required folks to put in credentials into the build engine. Not many folks have taken to kicking off builds from the Eclipse, and it is one more place to forget to change your password. When we made the change we had a bunch of build engines shut down, i.e. go inactive. Is there any way around this, we don't want to ask developers to put credentials in unless they want the 2 way interaction (kicking off builds from Eclipse). Thanks! Environment: Windows Server 2008 & 12 Project: Jenkins Labels: teamconcert RTC, Priority: Major Reporter: bbonn

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.