Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-13670

Creating a plan variable with a long value prohibits the plan from starting

    • Icon: Bug Bug
    • Resolution: Handled by Support
    • Icon: Low Low
    • 7.1.2
    • 5.0.1
    • Variables

      I have a variable with a length of 872 characters. The value is saved into the plan's configuration correctly. Triggering the plan results in this error:

      Plan 'ISC-EC' could not be started. Hibernate operation: Could not execute JDBC batch update; SQL []; Data truncation: Data too long for column 'VARIABLE_VALUE' at row 1; nested exception is java.sql.BatchUpdateException: Data truncation: Data too long for column 'VARIABLE_VALUE' at row 1

            [BAM-13670] Creating a plan variable with a long value prohibits the plan from starting

            Hi darthted,

            We need to gather other information, such as the database you are using and any logs, that can be used to fix this issue.

            Thanks
            James

            James Dumay added a comment - Hi darthted , We need to gather other information, such as the database you are using and any logs, that can be used to fix this issue. Thanks James

            Sultan, James,
            It really wasn't a request for support. It was reporting a bug in Bamboo, that it cannot handle variables long enough to contain authentication tokens for eBay API for integration test.

            Ted Tencza added a comment - Sultan, James, It really wasn't a request for support. It was reporting a bug in Bamboo, that it cannot handle variables long enough to contain authentication tokens for eBay API for integration test.

            Dear Ray,

            I have created a JIRA support ticket for you at: support.atlassian.com You should receive an email shortly containing a direct link to the support ticket.

            Please refer to the support ticket for any future correspondence relating to this issue.

            In future can you please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com, not in http://jira.atlassian.com. As our support engineers respond to cases in ttps://support.atlassian.com, it will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.comis configured so that only Atlassian and you have access to the case, therefor it is a more appropriate location for us to gather any required system data and configuration from you.

            Regards,
            Sultan

            Sultan Maiyaki (Inactive) added a comment - Dear Ray, I have created a JIRA support ticket for you at: support.atlassian.com You should receive an email shortly containing a direct link to the support ticket. Please refer to the support ticket for any future correspondence relating to this issue. In future can you please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com , not in http://jira.atlassian.com . As our support engineers respond to cases in ttps://support.atlassian.com, it will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.comis configured so that only Atlassian and you have access to the case, therefor it is a more appropriate location for us to gather any required system data and configuration from you. Regards, Sultan

            Ray Ward added a comment -

            It's an authentication token for the eBay API to run some integration tests.

            It's being passed as an environment variable into the phpunit task, so setting it there works fine, but it would be a bit easier to manage the token (and some other credentials) from a UX perspective if I could reference it from a plan variable, rather than a big long environment string.

            Ray Ward added a comment - It's an authentication token for the eBay API to run some integration tests. It's being passed as an environment variable into the phpunit task, so setting it there works fine, but it would be a bit easier to manage the token (and some other credentials) from a UX perspective if I could reference it from a plan variable, rather than a big long environment string.

            James Dumay added a comment - - edited

            Hi Ray,

            I've asked our support team to reach out to you and get some more information about the problem you are experiencing.

            Out of curiosity, why is your variable so long?

            Thanks
            James

            James Dumay added a comment - - edited Hi Ray, I've asked our support team to reach out to you and get some more information about the problem you are experiencing. Out of curiosity, why is your variable so long? Thanks James

              Unassigned Unassigned
              92c835279cf3 Ray Ward
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: