You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2016/05/26 06:32:12 UTC

[jira] [Assigned] (INFRA-11982) SCMRevisionState$None cannot be cast to hudson.scm.SVNRevisionState

     [ https://issues.apache.org/jira/browse/INFRA-11982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin reassigned INFRA-11982:
-----------------------------

    Assignee: Gavin

> SCMRevisionState$None cannot be cast to hudson.scm.SVNRevisionState
> -------------------------------------------------------------------
>
>                 Key: INFRA-11982
>                 URL: https://issues.apache.org/jira/browse/INFRA-11982
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Maxim Solodovnik
>            Assignee: Gavin
>
> I start getting following errors from Jenkins: 
> FATAL: hudson.scm.SCMRevisionState$None cannot be cast to hudson.scm.SVNRevisionState
> java.lang.ClassCastException: hudson.scm.SCMRevisionState$None cannot be cast to hudson.scm.SVNRevisionState
> 	at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:726)
> 	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:861)
> 	at hudson.scm.SCM.checkout(SCM.java:485)
> 	at hudson.model.AbstractProject.checkout(AbstractProject.java:1276)
> 	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
> 	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
> 	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
> 	at hudson.model.Run.execute(Run.java:1738)
> 	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
> 	at hudson.model.ResourceController.execute(ResourceController.java:98)
> 	at hudson.model.Executor.run(Executor.java:410)
> https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%203.2.x/65/console
> can you please fix it? or maybe there is any workaround for this issue?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)