michael soukup edited a comment on Bug JENKINS-21785

seems additional credentials for this specific external (same credentials as for the root project with the realm being the url to the external repo) made it work, but I have no intention of doing this for all my 50 projects...
edit: This did not work at all, the test case i made for it did that (see workaround)

workaround that works for me at the moment:

  • create new project that watches the changes in my library (the external that is in common for all and fails with the revision check, repository depth=empty)
  • configure other project as triggered by this new one

this seems to make the revision check work properly

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.

Reply via email to