Mark Waite commented on Bug JENKINS-25176

I cannot duplicate the problem in the case I tested. Here are the steps I tried

  1. install Jenkins 1.583 in a container on my Ubuntu 14.04 Linux machine.
  2. install Git plugin on that Jenkins instance, and restart
  3. define a new job, and configure it to use git for SCM
  4. enter a valid, secured git repository and confirm that it warns about it not being accessible
  5. use the Add button from firefox 33.0 and from google chrome stable and add a credential
  6. choose the newly added credential from the drop down list (newly added credential was not made the chosen credential after it was added)
  7. save the job
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.

Reply via email to