no revision found corresponding to

[Fabian Cenedese]

Hello

I think since an upgrade of Jenkins (and plugins) I now get many messages
in the log like this:

Oct 18, 2024 8:33:15 AM WARNING hudson.scm.SubversionSCM buildEnvironment
no revision found corresponding to https://SERVER/path/to/firstrepo/branches/name; known: [https://SERVER/path/to/secondrepo/trunk]

Those are two different svn repositories on our server, both accessible, both
used in the same (actually several) Jenkins job(s). Everything is working fine
except for these messages. I couldn't find out what the reason for these is.
Is this because of some older data that should be deleted? Is there a way
to get more information, like the actual job or anything? I'd like to get rid of
them as they fill up the log, pushing out more important messages.

Thanks

bye Fabi

[Verachten Bruno]

Hello,

It looks like the culprit is the subversion plugin:
https://github.com/jenkinsci/subversion-plugin/blob/53233cfc8eb305b0932f96c516f3c788c7585e24/src/main/java/hudson/scm/SubversionSCM.java#L743

Kind regards,

Bruno Verachten

> --
> 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/cfa23770ab03b479190614e548b812a9%40indel.ch.



--
Bruno Verachten

[Fabian Cenedese]

At 09:19 18.10.2024, Verachten Bruno wrote:

>Hello,
>
>It looks like the culprit is the subversion plugin:
>https://github.com/jenkinsci/subversion-plugin/blob/53233cfc8eb305b0932f96c516f3c788c7585e24/src/main/java/hudson/scm/SubversionSCM.java#L743

Yes, it says so in the log message:

>> Oct 18, 2024 8:33:15 AM WARNING hudson.scm.SubversionSCM buildEnvironment
>> no revision found corresponding to https://SERVER/path/to/firstrepo/branches/name; known: [https://SERVER/path/to/secondrepo/trunk]

But I don't see what the reason for the messages is. I now cleaned
all the older data that was available in "Manage Jenkins". However
that didn't help, there are still messages.

bye Fabi

[Maciej Jaros]

You might want to check your SVN setup:
https://jenkins2.mol.com.pl/manage/configure#subversion

For whatever weird reason Jenkins's default to some ancient version of
SVN. That version doesn't even support externals and I guess that might
be your problem. You probably want to set it to 1.8 (year 2013, format
6). So the highest Jenkins will go is still pretty old, but should be
enough for SVN to be stable.

You might need to clear your workspace after this change.

Regards,
Maciej Nux

Fabian Cenedese (2024-10-19 19:51):

[Fabian Cenedese]

At 09:28 21.10.2024, you wrote:

>You might want to check your SVN setup:
>https://jenkins2.mol.com.pl/manage/configure#subversion

Unfortunately that link doesn't work.

>For whatever weird reason Jenkins's default to some ancient version of SVN. That version doesn't even support externals and I guess that might be your problem. You probably want to set it to 1.8 (year 2013, format 6). So the highest Jenkins will go is still pretty old, but should be enough for SVN to be stable.
>
>You might need to clear your workspace after this change.

The Subversion config is already set to 1.8 and has been for years.

bye Fabi