-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
0
-
3
-
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.
- is duplicated by
-
BAM-21069 Automatic routing of jobs to Windows or Linux agents based on the script task interpreter
- Closed
-
BAM-16651 As a user I would like Bamboo to create an OS requirement based on the script task type
- Closed
- is related to
-
BAM-15825 Powershell scripts should not run on non Windows agents
- Gathering Interest
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.