Daniel Beck commented on Bug JENKINS-27977

It is a blocker because we cannot use HTTPS (and disable HTTP) if Jenkins does not work properly (always) in HTTPS.

Makes sense. The second quote looked like the exact opposite to me.

I agree with your first suggestion because "sometimes" the credentials that we set in the job configuration just .. disappear.

They should not. While it takes a moment for them to load the proper name, they should exist out of the box. Do you have Job Config History installed to track config changes?

By external, you mean svn externals, right ? if it is the case, fyi we do no use svn externals at all.

Yes. Well, one source of problems gone.


To clarify, AFAICT the error message basically occurs if Subversion asks for authentication and none/no valid one is provided by Jenkins. So I'd try to investigate why that config issue happens.

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