com.atlassian.upgrade.UpgradeException

Plan FWORK-MASTER has 0 repositories configured while it should have exactly 1

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web6

  • via Atlassian JIRA by Mark Chaimungkalanont, 1 year ago
    Plan FWORK-MASTER has 0 repositories configured while it should have exactly 1
  • via Atlassian JIRA by Mark Chaimungkalanont, 11 months ago
    Plan FWORK-MASTER has 0 repositories configured while it should have exactly 1
  • via Atlassian JIRA by Mark Chaimungkalanont, 1 year ago
    Plan DWHEAD-LSGTEST has 0 repositories configured while it should have exactly 1
  • Stack trace

    • com.atlassian.upgrade.UpgradeException: Plan FWORK-MASTER has 0 repositories configured while it should have exactly 1 at com.atlassian.bamboo.upgrade.tasks.UpgradeTask2704InitializeRepositoryChangesets.getRepositoryDefinitionId(UpgradeTask2704InitializeRepositoryChangesets.java:295) at com.atlassian.bamboo.upgrade.tasks.UpgradeTask2704InitializeRepositoryChangesets.access$100(UpgradeTask2704InitializeRepositoryChangesets.java:37) at com.atlassian.bamboo.upgrade.tasks.UpgradeTask2704InitializeRepositoryChangesets$2.doInHibernate(UpgradeTask2704InitializeRepositoryChangesets.java:161) at org.springframework.orm.hibernate.HibernateTemplate.execute(HibernateTemplate.java:370) at com.atlassian.bamboo.persistence.BambooTransactionHibernateTemplate$1.doInTransaction(BambooTransactionHibernateTemplate.java:39) at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:127) at com.atlassian.bamboo.persistence.BambooTransactionHibernateTemplate.executeWithResult(BambooTransactionHibernateTemplate.java:34) at com.atlassian.bamboo.upgrade.tasks.UpgradeTask2704InitializeRepositoryChangesets.processBRS(UpgradeTask2704InitializeRepositoryChangesets.java:135) at com.atlassian.bamboo.upgrade.tasks.UpgradeTask2704InitializeRepositoryChangesets.doUpgrade(UpgradeTask2704InitializeRepositoryChangesets.java:103) at com.atlassian.bamboo.upgrade.AbstractUpgradeManager.runUpgradeTask(AbstractUpgradeManager.java:200) at com.atlassian.bamboo.upgrade.UpgradeManagerImpl.doUpgrade(UpgradeManagerImpl.java:91) at com.atlassian.bamboo.upgrade.UpgradeLauncher$1.call(UpgradeLauncher.java:115) at com.atlassian.bamboo.upgrade.UpgradeLauncher$1.call(UpgradeLauncher.java:112) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at com.atlassian.bamboo.build.pipeline.concurrent.NamedThreadFactory$2.run(NamedThreadFactory.java:50) at java.lang.Thread.run(Thread.java:662)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.