Richard White _TechTime_ Atlassian Partner

Hi Nathaniel, We have done similar renaming procedures for some of our customers. The general procedure we have been following is this: - Bulk move the users from your AD user directory to Jira / Confluence / BB internal directory. We use a feature of our User Management App (available on Jira, Confluence and Bitbucket) to…

Probably best to ask this over at https://community.developer.atlassian.com/c/bamboo-development. However I have seen something similar happen in the case where we were using a recent version of jdk with patch version higher than 255: Bamboo Fails to start with java version higher than 255 - Bamboo KB 

Interesting, it does seem like it could be a bug. In terms of a workaround, you could always add an additional remote with a unique name, so that it does not affect other builds using the same repo.

I haven't run into this exact issue before, but I have run into issues with the git repo the agent is working with not being fully up to date, and I wonder if this is related. I would investigate if there is some difference in the linked repository settings between the demo and production repositories. I would particularly…

Glad I could help. If it solved the underlying problem, feel free to mark the answer as solution, it helps other people having the same issue find the answer. Cheers, Richard

That can happen if you haven't matched all of your quotes: e.g you have a starting " but not an ending one. There is also slightly typo in my comment, url should be http://bamboo:8085/rest..., not http://bamboo:8085rest. If it's still not clear after a close look at your command, maybe paste it here (minus the username and…

Hi Chethan, As far as I know there is no direct way through the rest api. I do know of a workaround though. Adding a comment with the issue key, links it correctly to the jira issue. The first request to start the plan returns xml including the build key and number. If you parse that build number and then make a comment…

Hi John, We make a marketplace app called EasyTime, which is meant to solve the same problem (not wanting to waste developer time / effort on manual time tracking - which is usually not accurate) However, our solution is completely different from what I think you are asking for and I am just curious for a little more…

Hi Bruce, It looks like the technical question has already been answered, but if you have many users to deactivate (or need to do it regularly) there is an easier solution. The company I work for (TechTime) - has an app designed exactly for this use case: User Management for Jira It allows you to deactivate users in bulk,…

What is included and what is ignored is defined by the artifact copy pattern if you are using manual clover integration. See attached screenshot showing a typical configuration: This is defined in the configuration for whichever stage should be generating the clover report. You can verify what is included in the artifact…

Unfortunately, I think you can only use the actual path matching part. In you example, the best you could do would be: pre* which would obviously match both precon and predition as well as pretest. I don't think there is a way to include the exclusions like in the ant reference. The original link you provided from…

Hi Manjunatha, One possibility is your artifact pattern isn't downloading all of the css and related files from clover's site output. I would double check the artifact manually, and check that all of the files are present that you see when generating the report manually. On this documentation page there is an example…

Hi Markus, Unfortunately, Bamboo uses ant path matching, not regex. I don't believe there is a way to satisfy that in a single artifact pattern. The only workaround I can think of, would be to define two artifacts (one for precon and one for predition in your example). Obviously that would not work for every use case…

Hi, As I understand it, bamboo logs all stderr messages in red and stdout logs normally. I don't think it's related to the return code.

Hi again Raveendra, I personally I would try the goals - clean - instrument (not instrument-test) - aggregate - clover For testing I would remove the flush policy and flushInterval and just use the default settings. I am assuming you are just doing coverage for unit tests via surefire at the moment, not trying to get…

Hi Raveendra, Unfortunately that's not an error I have seen before, and other than suggesting you use the newer open clover clover-maven-plugin, I'm not sure what could be wrong with that configuration.

Ah I see, so the problem is that you need to set the variables' value in between the time when the build was run and when the deployment was run. In Jira Software, I know this can be done when you create a "release build" where you can override the deployment variables. I don't think that can easily work with JSD though,…

Hi Raveendra, We do this in a couple of our projects and it is not too tricky. The aggregate goal will merge all of the moduleXClover.DB into a single db and then you can use the clover task to generate the report. For example, if running locally, and you have the open-clover plugin specified in your pom.xml you can run:…

Hi Sar, As I understand it, you would like the same issue key variable to be used in build and subsequent deploy stage? I think in this case you can use an inject bamboo variables task in the build stage, with scope set to "Result". This should mean the variable is available in subsequent deploy stages, and you can use it…

Hi, I have noticed when I do a manual deployment the variable: bamboo.ManualBuildTriggerReason.userName is set to the deploying user's username, which should hopefully work for your case too? This variable was not set in the case of automatically triggered deployments. Usually, the logs of a deployment will show all…

Hi @Dibyasankar , Assuming your web apps are java based it should be possible. Basically you will need to use clover to compile an instrumented version of your webapp and run your automation tests against that version. The exact configuration will depend a lot on your setup, e.g how you would usually compile and build the…

Hi Sunder, As I understand, there is no native way to do this from bamboo UI, there is an open ticket for this functionality here: https://jira.atlassian.com/browse/BAM-2537 As a workaround, you could set up the build to send emails to your jira, and create bug reports using automation on the jira side. There are other…

Oh, forgot to actually answer the question: First we have a checkout task, which checks out the dependencies master branch. Then, we have a script task with contents similar to below: #!/bin/bash -x EXPECTED="${bamboo_variable_for_target_branch}" git branch -a git checkout $EXPECTED CURRENT=`git rev-parse --abbrev-ref…

@danieldaeschle We ran into a similar problem, where we wanted to checkout specific tags or branches of dependencies, depending on the versions used in the main project that is being tested. I did find a solution, but it is not exactly "clean" - in fact it is really complicated given the simplicity of what I wanted to…

@Eshwar Prasad Yaddanapudi I would suggest you are better asking this particular query in https://community.developer.atlassian.com/c/bamboo-development =

Hi @Eshwar Prasad Yaddanapudi , It is not an error I have personally seen before, I can only suggest to delete the target directory and run the build again. What command are you using, when the first error message happens? It looks like it is happening during the 'run' phase, but in your second log, it looks like you may…

Ah I see, I my response will only give the status for each job, not each task. To the best of my knowledge there is no rest api which will give you task information.

Hi, You can use the plan endpoint to get this information: /rest/api/latest/plan/<plan-key>?expand=stages.stage.plans If you set header Accept:"application/json` you will get something in the following format: { "expand":"actions,stages,branches,variableContext", ..., "project":{ <project info like key description etc.>,…