You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
We recently switched to using git from subversion. Trying to reconfigure our build server to check out code from the git repo, and we're unable to do so. I can see the requests coming in on the git server (gitolite) :
2012-11-01.18:40:20 build 172.18.100.177 git-upload-pack 'portal-package.git'
2012-11-01.18:40:21 build 172.18.100.177 git-upload-pack 'portal-package.git'
The 'Build Result Summary' even lists the revisions (which match whats in the repo ), but the Bamboo server fails the job w/ the following exception:
com.atlassian.bamboo.repository.RepositoryDefinitionException: Task failed since repository with id 294914 does not exist. It may have been deleted, please update the task and pick a new repository
at com.atlassian.bamboo.repository.RepositoryFunctions$IdSelectorToRepositoryDefinition.apply(RepositoryFunctions.java:87)
at com.atlassian.bamboo.repository.RepositoryFunctions$IdSelectorToRepositoryDefinition.apply(RepositoryFunctions.java:51)
at com.atlassian.bamboo.task.repository.RepositoryTaskHelper.getRepositoryDefinitionByIdSelector(RepositoryTaskHelper.java:129)
at com.atlassian.bamboo.v2.build.task.CheckoutDirectoriesSnapshotHelper.<init>(CheckoutDirectoriesSnapshotHelper.java:103)
at com.atlassian.bamboo.v2.build.task.InitializeBuild.prepareCheckoutDirectories(InitializeBuild.java:102)
at com.atlassian.bamboo.v2.build.task.InitializeBuild.doCall(InitializeBuild.java:84)
at com.atlassian.bamboo.v2.build.task.InitializeBuild.call(InitializeBuild.java:51)
at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.build(DefaultBuildAgent.java:206)
at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl.waitAndPerformBuild(BuildAgentControllerImpl.java:103)
at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent$1.run(DefaultBuildAgent.java:111)
at com.atlassian.bamboo.build.pipeline.concurrent.NamedThreadFactory$2.run(NamedThreadFactory.java:52)
at java.lang.Thread.run(Thread.java:662)
Problem turned out to be a documentation issue, the docs state you can use the pattern user@yourgitserver.com:repo.git This is not correct, and will result in weird errors, the : is only valid for hosts. You need to use a different git URL, like git@yourserver.com/repo.git
I had this issue when I changed my plan repository (github) to a linked repository.
It was solved by going back to the "Checkout Source Code" step and just saving it again. For some reason it linked to my old plan repository.
HTH
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Rafal, looks like when you reconfigured your Plan to use Git instead of Subversion the Jobs 'Checkout source task' was not updated and is still refering to the old Subversion repository (thats now deleted).
To fix, for each job in your plan go to the 'Checkout source task' in the Task list and ensure you are checking out the Git repository defined in your Plan.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My case:
1) The repository definition had been deleted
2) I re-created the repository definition and specified the repository in the plan. Ran the build, but got errors (several times)
3) Checked the job - the plan's repository was listed in the Source Code Checkout task. I saved the task and the plan ran successfully.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So I'll buy that as a possibility, however I wiped my bamboo install and started clean. There are no Subversion repos defined, only git ones. And I've had no luck with it. If I have one 'default' repository it will get checked out ok, however if I have a 2nd one in the same build plan it will fail to check it out w/ the following error in the log:
com.atlassian.bamboo.repository.RepositoryDefinitionException: Task failed since repository with id 1376259 does not exist. It may have been deleted, please update the task and pick a new repository at com.atlassian.bamboo.repository.RepositoryFunctions$IdSelectorToRepositoryDefinition.apply(RepositoryFunctions.java:87) at com.atlassian.bamboo.repository.RepositoryFunctions$IdSelectorToRepositoryDefinition.apply(RepositoryFunctions.java:51) at com.atlassian.bamboo.task.repository.RepositoryTaskHelper.getRepositoryDefinitionByIdSelector(RepositoryTaskHelper.java:129) at com.atlassian.bamboo.v2.build.task.CheckoutDirectoriesSnapshotHelper.<init>(CheckoutDirectoriesSnapshotHelper.java:103) at com.atlassian.bamboo.v2.build.task.InitializeBuild.prepareCheckoutDirectories(InitializeBuild.java:102) at com.atlassian.bamboo.v2.build.task.InitializeBuild.doCall(InitializeBuild.java:84) at com.atlassian.bamboo.v2.build.task.InitializeBuild.call(InitializeBuild.java:51) at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.build(DefaultBuildAgent.java:206) at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl.waitAndPerformBuild(BuildAgentControllerImpl.java:103) at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent$1.run(DefaultBuildAgent.java:111) at com.atlassian.bamboo.build.pipeline.concurrent.NamedThreadFactory$2.run(NamedThreadFactory.java:52) at java.lang.Thread.run(Thread.java:662)
However if I create a 'fake' build configuration and set it up w/ the repository thats failing above, and it will check the source out correctly.
This is pretty frustrating right now, I've been trying to get the git integration working for a week.
Thoughts?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Problem turned out to be a documentation issue, the docs state you can use the pattern user@yourgitserver.com:repo.git This is not correct, and will result in weird errors, the : is only valid for hosts. You need to use a different git URL, like git@yourserver.com/repo.git
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I too had same issue, tried recreating the linked repo, job etc but did not help. Went back to checkout source code task and saved it again, everything started working
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm happy to announce that Bamboo 7.2 has been released and it’s overflowing with awesome new features. This will be the last major Server release before the launch of Bamboo DC. Bamboo logs We...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.