|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Hello Daniel,![]()
It is a blocker because we cannot use HTTPS (and disable HTTP) if Jenkins does not work properly (always) in HTTPS.
It is the same
I agree with your first suggestion because "sometimes" the credentials that we set in the job configuration just .. disappear.
For example, we try to start the job several times, then we go in the job config: the credential setting switched from the correct one to "none".
By external, you mean svn externals, right ? if it is the case, fyi we do no use svn externals at all.