I have a build plan that builds the product and creates artifacts that a separate deployment plan can grab and deploy to various servers. I have the JUnit Parser installed and I've used it in a build plan, but for some reason it's not available to be added to a deployment plan. Why is that? Is there a way to get it to show up as an available module? What other options are there that would give me the same results in case I'm unable to use that module?
Bamboo version: 5.8.1 build 5866
It was a design decision not to enable all types of tasks for deployments. JUnit Parser was one of them. We're not associating test results with Deployments so we felt this task doesn't belong there.
Can you describe your use case in more detail?
We have a branch that we build on a daily basis and it has its own set of automated tests that get run after the auto-deployment of the build. Once a week we cut a release branch and we don't have our automation run every time that we compile and package the release branch since we don't auto-deploy it once it's built. We have a separate deployment plan for deploying the build that we then want to run the automation on. We don't want to auto-deploy the build because we sometimes have a bug fix that gets checked in while I'm still doing other testing and I don't want to have the servers taken off-line in the middle. I understand your decision to not allow it, but as you can see I have a use case that could really use this functionality. Is it possible to manually add the functionality to the server or is it specifically blocked by the application?
Unfortunately even if it was possible to enable JUnitParser for Deployments test results would be ignored. I understand you can fail Deployment without JUnitParser with the same task that actually runs tests (it can return non-zero result code).
We have a very similar issue in our public tracker: https://jira.atlassian.com/browse/BAM-13276, please add your vote there to increase chances of implementing this.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot