Daniel Santos_157bm4 Atlassian Team

Hello @Phillip Bonner Thank you for sharing your findings, they saved me some time when investigating this. According to my tests your inline script should start with: #!c:\progra~1\git\bin\bash.exe ⚠️ No spaces in the path and no surrounding quotes. This is the default format of shebang (which comes from Unix systems).…

Done! =]

Hi @Octane CI Plugins Owner Thank you for reaching out to us to move forward on this one. In order to set you for success, I suggest you ask the same question on a different channel, more aligned to this content. This is the one: * The Atlassian Developer Community (tag: Bamboo)I It is more likely that your question will…

Hi @yash_shanker24 I think I get it now, you have an old instance (as stated before), but this instance is running with an embedded DB and now you need to generate an export to import it in a fresh instance and use an external DB. Please correct me If I'm wrong. You don't need an export with artifacts, it can be done…

Hi @yash_shanker24 Thank you for sharing that. Unfortunately, the import process is even slower than the export one. Short instructions on this one: * We don't need the export with artifacts and build logs * We should try to shrink this instance to the minimum size possible before moving forward * Yes, we will need more…

Hi @NetEdgeManoj I'm led to think that the issue you are facing is caused by a wrong JDK version installed in your server. You need version 1.8 for Bamboo. Can you confirm that JAVA_HOME is configured and pointing to a JDK 1.8?

If you don't mind I can remove that one. =]

Hi @Günther Bär I'm very glad that you were able to finish the installation. I found this issue reported, but it was closed with a fix in our docs: * [BAM-18438] AccessDeniedException when storing the cipher on Windows if bamboo.home is within Program Files This was the document changed: * Installing Bamboo on Windows -…

Hi @Nikolaos Rafail Papadakis Thank you very much for coming here to share your findings. It personally means a lot to me when I see someone caring about unknown people. That is what you are doing here taking part of your time to share what you got (even facing multiple issues with our spam queue). Thank you very much,…

Hi @Nikolaos Rafail Papadakis Your prior message was somehow categorized as spam. It happened probably because the same message was posted in two different threads. I've cleaned all the attempts you did from our spam queue so it does not try to filter your next comments out =] Message to foreign users If you are trying to…

Hi @Jonathan Epstein Thank you for opening a ticket with our support channel to investigate this one. This type of issue requires a fine troubleshooting that usually requires an instance configuration review. This can only be performed with your instance Support Zip which carries private data and for the same reason could…

Hi @lance_lyons If I had to solve this problem with Bamboo I would try to set/get this information from the source code. This would assure that whenever an old build is a rerun or an old deploy is redeployed I would have the correct name used for that image. We can't achieve that through Bamboo variables. You cannot set…

Hi @yash_shanker24 Yes, you can add the artifacts later, but that is only possible if you use the option [x] Export Results when exporting the data. I'm working on a different question from you: * Is my Bamboo Export Process still in progress ? Let's focus our efforts on that one. Depending on what you are trying to…

Hi @yash_shanker24 While the export is running you should see a pair or message like: 2019-10-17 14:41:40,064 INFO [http-nio-8085-exec-12] [XmlMigrator] Exporting with: com.atlassian.bamboo.buildqueue.migration.stream.AgentAssignmentMapper 2019-10-17 14:41:40,317 INFO [http-nio-8085-exec-12] [XmlMigrator] Finished writing…

Hi @Günther Bär I'm led to think you are facing permission issues when Bamboo is trying to create the cipher file in your filesystem. Please check this thread: * Solved: bamboo cipher keys are seemingly not generated (Kiran01BM's comment) Are you using a service to run the Bamboo process? Can you assign a local user with…

Hi @Ajay Kumar The channel to get updates on this implementation is: #12753 - Allow customers to connect the pipelines builds to their own VPN server. That is the channel our developers use to deliver their news and update the status of the issue/feature/bug. That suggestion will be prioritized among other requests…

Hi @GK That plugin was designed by https://calmware.be/ which does not seem to be in the game anymore or was acquired by https://www.evolane.be/. Since it was not designed by Atlassian, we can't do anything about it. Can you share what is the native feature missing from that plugin that makes it so essential in your case?…

Hi @Roozbeh Shafiee First of all, let me explain why this process is slow. The export feature you are using will get the data from your DB and convert it to a DB independent format (XML) and backup your home directory with it. This process is really slow since every piece of data needs to be converted and then (depending…

Hi @daneshrao We don't have an API to compare tags directly, but you can use a sequence of steps to get the information you need using multiple requests. General steps: * Get the commit associated with each tag using the following request:curl -u <USER>:<PASSWORD> \ -X GET…

Hi @Neil Nand I'm not sure if I really got what is your intent with this configuration. * Can you share a little bit more on what problem you are trying to solve? * How the steps that would consume the deployment variables would be triggered? * Why repository variables are not an option for you? Sorry for the questions, I…

Hi @joncanning, Yes, you would need to use git log with the right commit given by the BITBUCKET_COMMIT variable. The command would something like: git log --format=%B -n 1 $BITBUCKET_COMMIT Example of a pipeline that creates a variable with the commit message: pipelines: default: - step: script: - COMMIT_MESSAGE=`git log…

Hi @Keith Paskett That is not possible. The best approach to this one would be creating a new repository with the history you want to share. When needing to update the new repository you can create pull requests and update it. This would be the public-facing repository where you would allow people to clone it. You probably…

Hi @Ross Crawford It is good to know you consider this a step in the right direction. Our product manager already got your feedback. Thank you very much!

Probably I misunderstood what the leader told me and the tags were already there. Anyway, the reason for that change was the one I shared. By the way, I'm from Bamboo team. I'll raise this one for one of our Jira folks.

Hi @[deleted] Given the really low number of questions for this plugin in our community, I would suggest you check their support channel directly through: * Wittified Jira - Support You can also try to email de vendor directly. Their contact is in the following page: * Build Status Tracker for Bamboo (support) | Atlassian…

You are welcome! =]

Hi @Anton_Kuryan I'm sorry for the delay here, I needed some quiet time to work on this and it was difficult to find. This is the feature request I created based on your comment: * [BAM-20677] Allow triggering an environment only when multiple specified environments run with success This is a feature request that is…

Hi @Cameron Thom I want to apologize for this inconvenient, it was a different community leader (not @Ollie Guan) that updated the title of this question. His intention was to make it more searchable through tags. The Nex-Gen part (which was in between square brackets) was removed and the nex-gen and nexgen tags were added…

Hey @Nikolaos Rafail Papadakis Thank you very much for sharing your findings here. This will help other users to understand what was causing the issue. It all makes sense now. I'll wait for your latest updates then. =]

Hi @Günther Bär Some times we have different errors in sequence and we might think that they are the same thing. The errors you shared are clearly affected by the encryption configuration that is performed when we are upgrading Bamboo or even reinstalling it without cleaning the folders. Would you mind sharing the errors…