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

Automatic routing of jobs to agents in different OS platforms based on the script task interpreter

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Capabilities, Jobs, Tasks
    • None
    • 0
    • 3
    • 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.

      It would be very helpful if Bamboo would automatically route jobs or add some sort of capability/requirement to jobs based on the script task interpreter to make sure they get executed in the right place (e.g. Windows or Linux). This is to avoid a situation where, for instance, a job with script task executing a batch file is sent to a remote agent running on Linux.

      At the moment Bamboo sends those jobs to any available agent unless you work with (a) agent dedication and/or (b) requirements. This can become troublesome and difficult to maintain in large Bamboo deployments.

            [BAM-15189] Automatic routing of jobs to agents in different OS platforms based on the script task interpreter

            Run into this issue 8 years later and wondering that this is still an issue

            In most cases nobody may notice that behaviour because usually you have tasks in the stage which are directing the build to "the correct" agent. But if you have, as example, an stage that only runs some zipping of the artifacts after an MSBuild-task/stage than it might happen that this stage is run on "the wrong" agent.

            We've set requirements like "Operatingsystem match Windows" now as we had these "capability" set previous in our environment to make debuging of failing plans a bit easier. Now it helps us also here to avoid to run powershell on Linux.

            I would understand that beahviour if on our linuxagents the pwsh is installed - but it is not. So there is no real reason why Bamboo runs an Scripttask, with Powershell set, there.

             

            Joeran ZELLER added a comment - Run into this issue 8 years later and wondering that this is still an issue In most cases nobody may notice that behaviour because usually you have tasks in the stage which are directing the build to "the correct" agent. But if you have, as example, an stage that only runs some zipping of the artifacts after an MSBuild-task/stage than it might happen that this stage is run on "the wrong" agent. We've set requirements like "Operatingsystem match Windows" now as we had these "capability" set previous in our environment to make debuging of failing plans a bit easier. Now it helps us also here to avoid to run powershell on Linux. I would understand that beahviour if on our linuxagents the pwsh is installed - but it is not. So there is no real reason why Bamboo runs an Scripttask, with Powershell set, there.  

            The recently fixed BAM-10320 should help here a little bit (assuming bamboo is smart enough to handle Powershell as a requirement automatically) but still leaves OS confusion for the /bin/sh or cmd.exe entry for unfortunately.

            That said, I haven't use it yet so it may be better or worse than I think.

            Etan Reisner added a comment - The recently fixed BAM-10320 should help here a little bit (assuming bamboo is smart enough to handle Powershell as a requirement automatically) but still leaves OS confusion for the /bin/sh or cmd.exe entry for unfortunately. That said, I haven't use it yet so it may be better or worse than I think.

            Found this issue (and others) that already addresses my previous comment:
            https://jira.atlassian.com/browse/BAM-13499

            Matt Jernigan added a comment - Found this issue (and others) that already addresses my previous comment: https://jira.atlassian.com/browse/BAM-13499

            Now I'm really stuck. There is no way to specify agent requirements on a deployment to force them to select the right type of agent. !!! In this case I want to SCP and SSH from Linux to Linux, not from Windows to Linux.

            Matt Jernigan added a comment - Now I'm really stuck. There is no way to specify agent requirements on a deployment to force them to select the right type of agent. !!! In this case I want to SCP and SSH from Linux to Linux, not from Windows to Linux.

              Unassigned Unassigned
              pwatson paulwatson (Inactive)
              Votes:
              16 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated: