Page 1 of 1

Module publishing process.

Posted: Thu Oct 22, 2015 7:31 am
by falconwmua
Does anyone have a good process or workflow for getting a module from source control to update to published module via PowerShellGet to changes checked into back into source control. Here is my process so far:
  • Get latest from source control in PSS
    Make changes and test
    Deploy to Temp folder in PSS
    Run Publish-Module cmdlet against temp folder
    If publish succeeds, check-in changes to source control
I'm not looking for feature changes at this time just so see if someone has a better way to do this because I'm about to have to expand the development of these module beyond myself on my team.

Module publishing process.

Posted: Thu Oct 22, 2015 7:31 am
by SAPIEN Support Forums
This is an automated post. A real person will respond soon.

Thank you for posting, falconwmua.

Here are some hints to help you get an accurate and complete answer to your question.

Ask in the best forum: If you asked in the wrong forum, just copy your question to the right forum.

Anticipate follow-up questions!

Did you remember to include the following?
  • 1. Product, version and build
    2. 32 or 64 bit product
    3. Operating system, e.g. Windows 7 64 bit.
    4. Attach a screenshot, if applicable
    5. Attach logs, crash reports, etc., in a ZIP file
If not, please take a moment to edit your original post or reply to this one.

*** Make sure you do not post any licensing information ***

Re: Module publishing process.

Posted: Wed Oct 28, 2015 8:28 am
by davidc
You can add custom commands to the deploy state: ... 14-part-3/

Using the additional build commands, you can call PowerShell.exe and pass the command to publish.
Additional Deployment Commands.png
Additional Deployment Commands.png (29.64 KiB) Viewed 2923 times
Part 4 links to all the previous articles on deployment: ... 14-part-4/

Alternatively, you can use PowerShell Studio's custom menu: ... ial-oh-my/ ... -template/


Re: Module publishing process.

Posted: Wed Oct 28, 2015 8:54 am
by jvierra
Just a note. The workflow for versioning is nearly always contained in the repository. The authentication is direct by account and the repository software usually posts a challenge for documentation updates if they are not included in source headers.

I would first check with the VCS manager to learn how to best integrate with your VCS. TFS can be extended now with PosH scripts so it can be more tightly integrated.