bamboo compile failure disables all plans

[thomas jaison]

My Bamboo spec job failed in compilation as one of the dependencies i provided in the pom resides in artifactory.

I have 2 questions..

1. How can I pull dependencies from my repository instead of going to the maven repo?

2. The failure of the bamboo spec job disables all the plans and deploy project. How can I stop it from disabling things in case of failure?

[Roberto Cardenas]

Hi,

1. What do you mean by your repository: Any repository configuration can be set up using your settings.xml file or in your repository configuration in the pom. You don't have to go maven but also if you are using Nexus, you don't have to go to maven repo, the nexus proxies configuration will deliver the packages to you, in case those artifacts are not available, then Nexus will download those once and again it will be the one that delivers the packages to your applications. Actually, it is a good practice to use one single repository for packages and dependencies resolution.

2. I need more details for the second questions

[thomas jaison]

Thanks Roberto! I was able to get the setup the repository through pom.

Re, 2 - Currently when I commit to the bamboo spec repo it was failing during compiling as it it did not find a dependency in the Maven Repo(which is now fixed). But the issue we saw was that, when the Bamboo Spec failed it disabled all the build and deploy jobs that were part of the Bamboo spec linked repositories.

I was trying to create a new build and deploy plan using the bamboo spec, but the failure affected all the other jobs as well. I was wondering if there was an option to not disable existing deploy plans in case of a failure.