yaegor/runas

The RunAs plugin for JetBrains TeamCity lets you run automated build jobs under different user accounts, or perform extra actions before or after a build. The core benefit is security and flexibility: in a shared continuous-integration setup you can isolate jobs from one another and control exactly which permissions each build gets. TeamCity is a server that automatically compiles, tests, and packages software. By default its "build agents" run each job under a single fixed account. This plugin adds a configurable command that wraps the build script, so the script can be handed off to another executable or user before it runs. You set a property on the agent pointing to a helper program, such as Windows Sysinternals PsExec or the Linux sudo command, and the plugin injects the real build command into that helper. Build parameters can supply the target username and password, so a single agent can impersonate different users per project. This is useful for teams that need strict permission boundaries. For example, a build that deploys to production might require an account with deployment access, while a normal compile job should use a restricted account. On Linux, the plugin's example script changes ownership of the working and temp directories to the target user, then runs the build via sudo. A practical requirement is that the agent itself must already be running under a privileged account, since it needs permission to spawn and manage processes as other users. The project is built in IntelliJ IDEA and packaged as a zip that you drop into the TeamCity plugins folder, after which a server restart pushes the update to all agents. The README provides Windows and Linux examples but doesn't go into detail on advanced configuration beyond them.