# PowerShell "Team" Collaboration

**URL:** <https://forums.powershell.org/t/powershell-team-collaboration/5998>\
**Category:** PowerShell Help\
**Created:** [March 14, 2016, 3:53am UTC](https://forums.powershell.org/t/powershell-team-collaboration/5998 "2016-03-14T03:53:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![stephen-testino](https://avatars.discourse-cdn.com/v4/letter/s/65b543/32.png) [@stephen-testino](https://forums.powershell.org/u/stephen-testino)\
**Post date:** [March 14, 2016, 3:53am UTC](https://forums.powershell.org/t/powershell-team-collaboration/5998/1 "2016-03-14T03:53:04Z")

</div>

Hi guys,

Are there any PowerShell “teams” out there?

Currently, I’m a one-man show; using SVN for version control, Pester for Unit Testing, Jenkins for automated builds, and an internal ticketing system to track projects. It works great for _me_, but I can’t see this workflow scaling up to support a team.

How today’s teams are keeping track of projects, features requests, bugs, version controlling their source code, and automating builds?

Thanks,  
ST

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/powershell/original/1X/385e4f9fe133561ad30a814262fe0e0ae6bc3ef0.png) [@system](https://forums.powershell.org/u/system)\
**Post date:** [March 14, 2016, 4:07am UTC](https://forums.powershell.org/t/powershell-team-collaboration/5998/2 "2016-03-14T04:07:39Z")

</div>

Same as any other software development. There are lots of options, but you’ve got all the basic blocks covered in your current arrangement.

We use:

- TeamCity for CI
- Octopus Deploy for delivery
- Pester for unit testing PowerShell code
- Jira for ticketing
- Usually git for source control, though we have some customers who use TFS or VSO instead.

---

<div class="post-metadata">

**Author:** ![adbertram](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/adbertram/32/193_2.png) [@adbertram](https://forums.powershell.org/u/adbertram)\
**Post date:** [March 14, 2016, 4:24am UTC](https://forums.powershell.org/t/powershell-team-collaboration/5998/3 "2016-03-14T04:24:02Z")

</div>

We use TFS for CI, source control and work items  
Home-grown PowerShell for delivery  
Pester for unit and integration testing

---

<div class="post-metadata">

**Author:** ![pscookiemonster](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/pscookiemonster/32/634_2.png) [@pscookiemonster](https://forums.powershell.org/u/pscookiemonster)\
**Post date:** [March 14, 2016, 7:33am UTC](https://forums.powershell.org/t/powershell-team-collaboration/5998/4 "2016-03-14T07:33:55Z")

</div>

Hi!

What sort of team is this? In an org with significant talent and the expectation that you’ll treat production code as production code? In org where you have a bunch of click-next-admins who need prodding just to use tools you write, let alone source control? For ops teams (sysadmins, dbas, security, etc.), dev teams, or a mix?

Anyhow! We use the following in a predominantly \*nix ecosystem:

- Source control: GitLab CE (git)
- Unit testing: Pester (for PowerShell)
- CI: GitLab CE CI
- CD: GitLab CE CI + Various scripts. e.g. [PSDeploy](http://ramblingcookiemonster.github.io/PSDeploy/)
- Tracking: Internal ticketing system, Trello, Hipchat, etc. Bug tracking and feature requests might move to GitLab issues. Not very formal (small team encompassing nearly all roles)

When you say you don’t see the workflow scaling up, what issues are you imagining? Those components are very important if you have code running in production (regardless of whether your ops team is proactive enough to be learning them).

Cheers!

---

<div class="post-metadata">

**Author:** ![dotnVo](https://avatars.discourse-cdn.com/v4/letter/d/4af34b/32.png) [@dotnVo](https://forums.powershell.org/u/dotnVo)\
**Post date:** [May 16, 2024, 8:42pm UTC](https://forums.powershell.org/t/powershell-team-collaboration/5998/5 "2024-05-16T20:42:40Z")

</div>

Closed on May 16, 2024, 8:42pm UTC