We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-17059

Bamboo Variables not correctly checked before Colon

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • None
    • 5.10-OD-10-008
    • Docker
    • None

      Summary

      • Bamboo Variables not being properly checked before colon

      Environment

      • Bamboo Cloud

      Steps to Reproduce

      1. Access any Bamboo instance, and browse through to "Configure Plan"
      2. Create or Edit a 'Docker' Task
      3. In the Repository field, use a variable before a colon, like ${ variable }:${ variable }

      Expected Results

      • Fully accepted field configuration

      Actual Results

      • Displaying "Invalid repository name (${variable}), only [a-z, A-Z, 0-9_.-] are allowed"

      Notes

      It looks like the Repository field is checking for the special characters before the Colon without considering that a variable may be used in that place. If the Repository field does not contain a colon, it will provide an error for the variable without performing the proper variable replacements first.

      Bamboo should make sure to perform its validation of the URL after the Variables have properly replaced the value before the colon.

      Workaround

      No current workaround

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Bamboo Data Center'
            1. Bamboo Data Center
            2. BAM-17059

            Bamboo Variables not correctly checked before Colon

              • Icon: Bug Bug
              • Resolution: Duplicate
              • Icon: Low Low
              • None
              • 5.10-OD-10-008
              • Docker
              • None

                Summary

                • Bamboo Variables not being properly checked before colon

                Environment

                • Bamboo Cloud

                Steps to Reproduce

                1. Access any Bamboo instance, and browse through to "Configure Plan"
                2. Create or Edit a 'Docker' Task
                3. In the Repository field, use a variable before a colon, like ${ variable }:${ variable }

                Expected Results

                • Fully accepted field configuration

                Actual Results

                • Displaying "Invalid repository name (${variable}), only [a-z, A-Z, 0-9_.-] are allowed"

                Notes

                It looks like the Repository field is checking for the special characters before the Colon without considering that a variable may be used in that place. If the Repository field does not contain a colon, it will provide an error for the variable without performing the proper variable replacements first.

                Bamboo should make sure to perform its validation of the URL after the Variables have properly replaced the value before the colon.

                Workaround

                No current workaround

                        Unassigned Unassigned
                        jvela Justin Vela
                        Votes:
                        2 Vote for this issue
                        Watchers:
                        6 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            jvela Justin Vela
                            Affected customers:
                            2 This affects my team
                            Watchers:
                            6 Start watching this issue

                              Created:
                              Updated:
                              Resolved: