takezoe / gitbucket-ci-plugin

GitBucket plug-in that adds simple CI ability to GitBucket.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

compatibility for plugin version 1.2.1

karthikbalu opened this issue · comments

I am using gitbucket 1.18 what is the compatibility for CI plugin 1.2.1, not loading on gitbucket, only showing 1.0.1 and nothing beyond that on gitbucket

gitbucket-ci-plugin 1.2.1 was built with GitBucket 4.17.0, but it should work with GitBucket 4.17.0 and 4.18.0.

I am already using 1.0.1 and copied the latest version 1.2.1 to my gitbucket-home/plugins folder but its not showing up on gitbucket plugins screen even if i do reload and restart server

Do i need to do anything other than copy pasting the latest plugin file?

08:53:16.604 [main] ERROR gitbucket.core.plugin.PluginRegistry - Error during plugin initialization: gitbucket-ci-plugin-assembly-1.2.1.jar java.sql.SQLSyntaxErrorException: (conn:667951) Duplicate column name 'SKIP_WORDS' at org.mariadb.jdbc.internal.util.exceptions.ExceptionMapper.get(ExceptionMapper.java:158) at org.mariadb.jdbc.internal.util.exceptions.ExceptionMapper.getException(ExceptionMapper.java:118) at org.mariadb.jdbc.MariaDbStatement.executeExceptionEpilogue(MariaDbStatement.java:245) at org.mariadb.jdbc.MariaDbPreparedStatementClient.executeInternal(MariaDbPreparedStatementClient.java:218) at org.mariadb.jdbc.MariaDbPreparedStatementClient.execute(MariaDbPreparedStatementClient.java:153) at org.mariadb.jdbc.MariaDbPreparedStatementClient.executeUpdate(MariaDbPreparedStatementClient.java:186) at com.zaxxer.hikari.pool.ProxyPreparedStatement.executeUpdate(ProxyPreparedStatement.java:61) at com.zaxxer.hikari.pool.HikariProxyPreparedStatement.executeUpdate(HikariProxyPreparedStatement.java) at io.github.gitbucket.solidbase.migration.MigrationUtils.updateDatabase(MigrationUtils.java:20) at io.github.gitbucket.solidbase.migration.LiquibaseMigration.migrate(LiquibaseMigration.java:93) at io.github.gitbucket.solidbase.migration.LiquibaseMigration.migrate(LiquibaseMigration.java:54) at io.github.gitbucket.solidbase.Solidbase.migrate(Solidbase.java:45) at io.github.gitbucket.solidbase.Solidbase.migrate(Solidbase.java:29) at gitbucket.core.plugin.PluginRegistry$.$anonfun$initialize$3(PluginRegistory.scala:284) at gitbucket.core.plugin.PluginRegistry$.$anonfun$initialize$3$adapted(PluginRegistory.scala:265) at scala.collection.immutable.List.foreach(List.scala:389) at gitbucket.core.plugin.PluginRegistry$.initialize(PluginRegistory.scala:265) at gitbucket.core.servlet.InitializeListener.$anonfun$contextInitialized$1(InitializeListener.scala:86) at gitbucket.core.servlet.InitializeListener.$anonfun$contextInitialized$1$adapted(InitializeListener.scala:57) at com.github.takezoe.slick.blocking.BlockingJdbcProfile$BlockingAPI$BlockingDatabase.$anonfun$withTransaction$2(BlockingProfile.scala:207) at slick.JdbcProfileBlockingSession$BlockingSession.withTransaction(TransactionalJdbcBackend.scala:26) at com.github.takezoe.slick.blocking.BlockingJdbcProfile$BlockingAPI$BlockingDatabase.$anonfun$withTransaction$1(BlockingProfile.scala:207) at com.github.takezoe.slick.blocking.BlockingJdbcProfile$BlockingAPI$BlockingDatabase.withSession(BlockingProfile.scala:200) at com.github.takezoe.slick.blocking.BlockingJdbcProfile$BlockingAPI$BlockingDatabase.withTransaction(BlockingProfile.scala:207) at gitbucket.core.servlet.InitializeListener.contextInitialized(InitializeListener.scala:57) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:843) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:533) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:816) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:345) at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1406) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1368) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:778) at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:262) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:522) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:105) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61) at org.eclipse.jetty.server.handler.StatisticsHandler.doStart(StatisticsHandler.java:252) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131) at org.eclipse.jetty.server.Server.start(Server.java:422) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:105) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61) at org.eclipse.jetty.server.Server.doStart(Server.java:389) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at JettyLauncher.main(JettyLauncher.java:127) Caused by: java.sql.SQLException: Duplicate column name 'SKIP_WORDS' Query is: ALTER TABLE gitbucket.CI_CONFIG ADD SKIP_WORDS VARCHAR(200) NULL, ADD RUN_WORDS VARCHAR(200) NULL at org.mariadb.jdbc.internal.util.LogQueryTool.exceptionWithQuery(LogQueryTool.java:146) at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.executeQuery(AbstractQueryProtocol.java:223) at org.mariadb.jdbc.MariaDbPreparedStatementClient.executeInternal(MariaDbPreparedStatementClient.java:212) ... 43 common frames omitted

I found a workaround to this problem

I manually dropped those fields in my database and later it throwed more errors on build folder
org.apache.commons.io.FileExistsException: Destination '/opt/gitbucket/gitbucket-data/repositories/sdvdsv/sdvsdv/build' already exists

I manually emtied the build directories inorder to make it work finally...

I guess automatic migration was failed for some reason.