Cannot make DVCS work with GitHub and JIRA - errors with installation and repos addition

Anna Sikorska July 18, 2012

My JIRA version is v4.4.1#660-r161644 . I have tried to install this plugin with 0.15.10, 0.15.9 and 0.15.8. None of them work. Below what happens for the latest version 0.15.10.

First when installing this error shows up:

012-07-19 11:34:27,818 pool-2-thread-1 INFO as 581x576x1 1d8s2u8 80.65.54.242,127.0.0.1 /rest/plugins/1.0/ [atlassian.plugin.loaders.ScanningPluginLoader] Plugin Unit: /opt/xxx/atlassian/jira-appdata/plugins/installed-plugins/plugin.9127589413244495152.jira-dvcs-connector-plugin-0.15.10.jar (1342712067000) created

2012-07-19 11:34:27,904 pool-2-thread-1 INFO as 581x576x1 1d8s2u8 80.65.54.242,127.0.0.1 /rest/plugins/1.0/ [atlassian.plugin.util.WaitUntil] Plugins that have yet to be enabled: [com.atlassian.jira.plugins.jira-bitbucket-connector-plugin], 60 seconds remaining

2012-07-19 11:34:27,990 Spring executor 25 WARN as 581x576x1 1d8s2u8 80.65.54.242,127.0.0.1 /rest/plugins/1.0/ [plugin.osgi.factory.OsgiPlugin] Ignoring the Spring context that was just created for plugin com.atlassian.jira.plugins.jira-bitbucket-connector-plugin. The plugin is in an invalid state, DISABLED, that doesn't support a transition to enabled. Most likely, it was disabled due to a timeout.

But the plugin is successfully enabled in JIRA.

Then when adding any repo this error shows up:

2012-07-19 11:35:29,477 BitbucketConnectorExecutorServiceThread:thread-1 WARN as 695x2844x1 1d8s2u8 80.65.54.242,127.0.0.1 /secure/admin/AddGithubRepository!finish.jspa [jira.plugins.bitbucket.DefaultSynchronizer]

java.lang.NullPointerException

at com.atlassian.jira.plugins.bitbucket.spi.github.GithubChangesetFactory.transform(GithubChangesetFactory.java:34)

at com.atlassian.jira.plugins.bitbucket.spi.github.impl.StoppablePageIterator.next(GithubChangesetIterator.java:120)

at com.atlassian.jira.plugins.bitbucket.spi.github.impl.GithubChangesetIterator.internalNext(GithubChangesetIterator.java:61)

at com.atlassian.jira.plugins.bitbucket.spi.github.impl.GithubChangesetIterator.hasNext(GithubChangesetIterator.java:43)

at com.atlassian.jira.plugins.bitbucket.spi.DefaultSynchronisationOperation.synchronise(DefaultSynchronisationOperation.java:66)

at com.atlassian.jira.plugins.bitbucket.DefaultSynchronizer$1$1.run(DefaultSynchronizer.java:59)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

On screen synching does not work of course:
Sync Failed: java.lang.NullPointerException

What is wrong?

2 answers

0 votes
Michael Downey July 25, 2012

I get the same behavior with JIRA 4.4 and JIRA DVCS Connector plugin version 0.5.10. When trying to do a "Force Sync" from the Manage DVCS Repositories page, the following appears in the JIRA application log:

2012-07-25 17:45:01,025 BitbucketConnectorExecutorServiceThread:thread-2 WARN useridgoeshere 1029x2884x1 18k9x46 127.0.0.1 /rest/bitbucket/1.0/repository/1/sync [jira.plugins.bitbucket.DefaultSynchronizer] 
java.lang.NullPointerException
	at com.atlassian.jira.plugins.bitbucket.spi.github.GithubChangesetFactory.transform(GithubChangesetFactory.java:34)
	at com.atlassian.jira.plugins.bitbucket.spi.github.impl.StoppablePageIterator.next(GithubChangesetIterator.java:120)
	at com.atlassian.jira.plugins.bitbucket.spi.github.impl.GithubChangesetIterator.internalNext(GithubChangesetIterator.java:61)
	at com.atlassian.jira.plugins.bitbucket.spi.github.impl.GithubChangesetIterator.hasNext(GithubChangesetIterator.java:43)
	at com.atlassian.jira.plugins.bitbucket.spi.DefaultSynchronisationOperation.synchronise(DefaultSynchronisationOperation.java:66)
	at com.atlassian.jira.plugins.bitbucket.DefaultSynchronizer$1$1.run(DefaultSynchronizer.java:59)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

0 votes
Stew O'Connor July 19, 2012

we get the same exact thing here.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events