Help needed with Multi-Branch Project Plugin question

[David Aldrich]

Hi

I am experimenting with the Multi-Branch Project Plugin and it looks great. However, I don't understand the 'Sync Branches Schedule' feature.

The 'Sync Branches Log' shows that the branches scan last ran at:

"Started on Nov 27, 2015 9:52:52 AM"

I have set the Sync Branches Schedule to 'H/30 * * * *' and Jenkins says:

"Would last have run at Friday, November 27, 2015 12:52:40 PM GMT; would next run at Friday, November 27, 2015 1:22:40 PM GMT."

It is now 1:25 PM GMT, so it should have run.

I added a branch at 11:38 GMT today. The plugin has not added a job for the new branch and the 'Sync' job has not run since 9:52 (as shown above). Why might that be please?

Best regards

David

[David Aldrich]

Hi

An update on this: I noticed that the system log contains:

"svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled."

My understanding is that this exception is associated with not specifying 'Additional Credentials' for the Subversion repository.

I notice that the Multi-Branch Project Plugin doesn't offer an option to enter 'Additional Credentials' for Subversion. The author says that that is the responsibility of the SCM API plugin, not the Multi-Branch Project Plugin:

https://github.com/mjdetullio/multi-branch-project-plugin/issues/9

I'm out of my depth now. Can anyone offer me any help with this please?

BR

David

> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-
> users/41302A7145AC054FA7A96CFD03835A0A0BA061A0%40EX10MBX02.EU
> .NEC.COM.
> For more options, visit https://groups.google.com/d/optout.
>
>
> Click
> https://www.mailcontrol.com/sr/4wmkQflPkEfGX2PQPOmvUstiqgZjxB51Nfu
> WOjjriIp!rtd6Twjy+FKxacsZnrUtOLuDLOvIMfeqQH8FWVwkvA== to report
> this email as spam.