Bamboo can't recognize the decrypted variable while importing Specs


Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

    

Summary

Sometimes users need to import Java or YAML Specs generated by Bamboo containing encrypted variables into a different instance.

Environment

Bamboo 6.9+

Diagnosis

The following message can be found during the Java or YAML Specs execution:

Bamboo can't recognize the decrypted variable 'variableName' because it might be imported from another Bamboo instance.

Cause

Bamboo uses different encrypted keys to generate the variables. Therefore, each Bamboo instance has its own encryption key which generates the encrypted variables.

Solution

  1. Remove all the encrypted variables from the Specs code;
  2. Go to Specs >> Bamboo Specs encryption and paste the value of your encrypted variables from the previous Bamboo instance (more info at Bamboo Specs encryption) You can also use Bamboo REST API (http://bamboo-server:8085/rest/api/latest/encrypt) to do this;
  3. Copy the encrypted variables generated in the previous step and add it to the Specs code;
  4. Run the Specs again.


Last modified on Aug 9, 2021

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.