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

Jobs dependent Agent capabilities of type executable could be treated just like bamboo variables and passed as environment variables to script task

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Done
    • 5.0
    • None
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      when I have defined 7Zip capability on an agent it would be nice to have environment variable %bamboo_capability_7Zip% or bamboo variable ${bamboo.capability.7Zip}

          Form Name

            [BAM-13216] Jobs dependent Agent capabilities of type executable could be treated just like bamboo variables and passed as environment variables to script task

            Anders Blaagaard added a comment -

            I think this would be working if you use ${bamboo.capability.system.builder.command.7Zip}
            If so, then the problem is actually BAM-12681

            Anders Blaagaard added a comment - I think this would be working if you use ${bamboo.capability.system.builder.command.7Zip} If so, then the problem is actually BAM-12681

            Maciej Warszawski added a comment -

            I forgot to mention, my capability type is executable and type is command.

            when I use capability type custom it works fine, but custom type can't be used in command tasks.

            Maciej Warszawski added a comment - I forgot to mention, my capability type is executable and type is command. when I use capability type custom it works fine, but custom type can't be used in command tasks.

            Maciej Warszawski added a comment -

            indeed documentation states that it should work. but I have hard time to set it up.

            it was introduced in Bamboo 2.0, I've linked issues.

            as I stated, I defined capability 7Zip and when in inline script I've entered

            echo ${bamboo.capability.7Zip}

            variable was not substituted. in my build log I can find ${bamboo.capability.7Zip} string not C:\Program Files\7-Zip\7z.exe

            I've changed this issue type to bug, but I can't reopen it.

            Maciej Warszawski added a comment - indeed documentation states that it should work. but I have hard time to set it up. it was introduced in Bamboo 2.0, I've linked issues. as I stated, I defined capability 7Zip and when in inline script I've entered echo ${bamboo.capability.7Zip} variable was not substituted. in my build log I can find ${bamboo.capability.7Zip} string not C:\Program Files\7-Zip\7z.exe I've changed this issue type to bug, but I can't reopen it.

            James Dumay added a comment -

            This is possible today. See https://confluence.atlassian.com/display/BAMBOO/Using+global,+plan+or+build-specific+variables#Usingglobal,planorbuild-specificvariables-Specifyingcapabilitiesasvariables

            James Dumay added a comment - This is possible today. See https://confluence.atlassian.com/display/BAMBOO/Using+global,+plan+or+build-specific+variables#Usingglobal,planorbuild-specificvariables-Specifyingcapabilitiesasvariables

              Unassigned Unassigned
              f9936279885b Maciej Warszawski
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: