Daniel Santos_157bm4 Atlassian Team

I wrote the message above without seeing your last response... I guess it still applies to it =]

Hey @Jozef Vandenmooter I just want to add another idea as a second option. You could configure the plan branch to disable itself when it runs for the first time. For this, you would need to create a script task at the end of your build with a bash script like: # If this is not the main plan branch if […

Hi @cirosantilli, yes I know. The DB and the Sed are the only options I see at the moment. I hope you don't have any plan key with numbers. They will never be suggested by Bamboo... but can be deliberately created if a user decides to do so. You can check if there is any like that using the query below: SELECT title,…

You are welcome @josh bouganim I'm glad to be helpful. Have a good one!

Hello @Mike Burton, I was able to get the information we needed from a Pipelines developer. According to him, we don’t actually expose that variable in the step of a pipeline. It’s only present in the pipe itself. Which means that someone writing a custom pipe can use it, but not outside of it. If you are trying to use…

Hello @Jim Schwarz Due to the nature of this problem, we will need to request from you instance data and therefore it will require a different support channel to handle it privately. I've opened a support ticket for you to allow us investigating this problem. As soon as you get it, please share with us the following: * The…

Hello @Koen Jansen This type of problem can have different causes and we will need details of what you see in your logs when it happens. Please try: * reproduce the problem and take a not of the time. * check the Bamboo server logs at <Bamboo_Home>/logs/atlassian-bamboo.log. * share the error you see with us. ⚠️ please…

Hi @Ari_Mahpour You could get this information by comparing revisions of each source repository. You will need to check the following Bamboo variables: * bamboo_planRepository_#_revision * bamboo_planRepository_#_previousRevision Considering this could be a pain for you I spent some time to build a bash shell script to do…

For some reason, I forgot to update this one, sorry about that. I was able to talk to a developer about this and he shared that this is not possible considering how Bamboo is designed at the moment.

Hi @lance_lyons There is no public API to change this flag directly, but I see two other options that may help: * Use Bamboo specs. In specs the following code part would disable the task:.stages(new Stage("Default Stage") .jobs(new Job("Default Job", new BambooKey("JOB1")) .tasks(new ScriptTask().enabled(false) More…

Hello @Matthew Lyons, I'm really sorry to hear that you are facing this issue. I'll do what I can to help you move forward. We don't have a formal process to roll back an upgrade, but you could take the following steps to restore the old instance: * Make sure there is no Bamboo process running in the server machine. *…

Hi @kapusj01 Yes, this problem is recent and caused by the GDPR required changes in the API. We are really sorry that this is causing you trouble. You can find more details about this event and how to overcome it here: * Unable to add or edit Bitbucket Cloud repository i... - Atlassian Community Basically, you have two…

Hi @upsampled Thank you for pointing that out, I'll file an improvement request for the document that should contain this information. This was the page that use to have the whole details about the ports: * Compare Atlassian cloud vs server You can see that it was referenced in this community article: * Connecting Local…

Hi @maxgrenderjones I understand your pain and I would love to have a better solution for your now. I visited the Bitbucket support team to talk about this issue and check if it would be better opening a different issue to cover the simplified case involving the same pipelines account. Our conclusion was that we prefer to…

Hey @James Hume I've opened a ticket in the Bitbucket Cloud support to allow us investigating this one deeply. We will need to check your repository to understand what is causing this issue. You should receive an email with the support ticket soon. Once the issue is resolved, please share your findings here. This will…

Hi @cirosantilli There is no variable with this information available out of the box, but we could build it from the ${bamboo.planKey}. I would use a command like: echo ${bamboo.planKey} | sed -E 's/([A-Z0-9]+-[A-Z]+)[0-9]*/\1/g' ⚠️Please notice that you might need to adjust the sed command configuration depending on the…

Hi @poovaraj What is the difference between the agent that works and this one in terms of: * Operating system * Networking * Resources available for the JVM Did you see any error in the agent logs before the ones you shared here?

You are welcome! I'm glad I could help you with this one.

Thank you for sharing. I'll be in touch with the development team to check why this is happening. As soon I have something to share I'll be posting it here.

Hi @John Lindahl Thank you for the detailed description of your scenario. Let me share what I know about it: * The 1h limit is measured by a rolling window which means that in every minute you may have back some "credits" to run new requests until the total of 1000. That explains why you are not blocked for 1h. * Any…

Hi @Mike Burton I want to help you with this one, but I'll need some more clues to understand where the variables BITBUCKET_PIPE_SHARED_STORAGE_DIR come from. Did you declare that variable in repository variables? If I do it here, I'm able to use it as expected.

Hello @maxgrenderjones I see what you mean, but unfortunately, this feature is not available. There is an improvement request for this at [#13162] - Pipelines for pull requests from forks. I suggested the following workaround in this post Trigger pipeline on pull request from fork. * Create a new branch just for submitting…

Hi @poovaraj Thank you for sharing the logs =] I hope that you didn't have other errors before this one, otherwise, I'll kindly ask you to share them with us as well. This type of error may have different reasons which also includes unsupported Java version on the remote agent. I have a couple of questions that will help…

Hi @James Hume, I believe you are facing some edge case or bug. I was not able to reproduce this scenario. When I browse the pipelines logs I see this in the first part of it: Build setup (section) + umask 000 + GIT_LFS_SKIP_SMUDGE=1 git clone --branch="master" --depth 1…

Hi @koteswararao, Good question! First of all, I would like to make it clear that this is an Atlassian labs plugin. (...)The apps are often developed in conjunction with Atlassian hack-a-thons and ShipIt days and are provided to you completely “as-is”, with all bugs and errors, and are not supported by Atlassian.(...)…

Hello @Jeroen De Vlieger It was a reasonable assumption about the way Bamboo would rerun old builds, but at the moment such behavior is not available. Specs is the first step to allow this in the future but we can't promise when this will be done. I created a bug and filed a feature request when checking the scenario you…

Hi @Allan Libby I think I clearly understand your need but I have to say that Bamboo does not provide such a feature neither other add-ons, at least not the ones I know. What I think you could do it to configure a remote agent to run with a user that has the needed permissions and create a requirement for the job needing…

Hi @YildizNet App Thank you for raising this one to try clarifying this exception. The exceptions you see are will cause no harm in your instance, they can be ignored. They happen due to an incorrect metamodel for some Bamboo autogenerated classes. You can see this in more details here: * [BAM-18777] Hibernate generates…

You will keep using the Bitbucket source repository, but in Bamboo side, you will use a different method for linking the repository. Instead of using the Bitbucket linking you will use the Git one as shown below: : More details on how to configure can be found here: Git - Atlassian Documentation. Let me know if you have…

Hi @upsampled, Thank you for the detailed description of this question =] If I understood you correctly you are using a different port, other than 80 or 443. You will need to provide port 80 or 443 for Bamboo. This is our dor reference: 3. Are you linking Atlassian Cloud applications? If an application involved in your…