- 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
Module publishing process.
Forum rules
Do not post any licensing information in this forum.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
Do not post any licensing information in this forum.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
- falconwmua
- Posts: 2
- Last visit: Mon Feb 04, 2019 7:57 am
Module publishing process.
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:
- SAPIEN Support Forums
- Posts: 945
- Last visit: Thu Oct 22, 2015 1:10 pm
Module publishing process.
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:
Anticipate follow-up questions!
Did you remember to include the following?
*** Make sure you do not post any licensing information ***
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:
- - Scripting question? For questions about Windows PowerShell or other scripting languages, use Scripting Answers.
- Software question? For questions about PowerShell Studio, PrimalScript, or other SAPIEN products, use Product Support Forums for Registered Customers.
- Trial question? For questions about trial versions of any SAPIEN product, use Trial Software Questions.
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
*** Make sure you do not post any licensing information ***
Re: Module publishing process.
You can add custom commands to the deploy state:
https://www.sapien.com/blog/2014/04/14/ ... 14-part-3/
Using the additional build commands, you can call PowerShell.exe and pass the command to publish.
Part 4 links to all the previous articles on deployment:
https://www.sapien.com/blog/2014/04/21/ ... 14-part-4/
Alternatively, you can use PowerShell Studio's custom menu:
https://www.sapien.com/blog/2013/01/08/ ... ial-oh-my/
https://www.sapien.com/blog/2015/10/01/ ... -template/
David
https://www.sapien.com/blog/2014/04/14/ ... 14-part-3/
Using the additional build commands, you can call PowerShell.exe and pass the command to publish.
Part 4 links to all the previous articles on deployment:
https://www.sapien.com/blog/2014/04/21/ ... 14-part-4/
Alternatively, you can use PowerShell Studio's custom menu:
https://www.sapien.com/blog/2013/01/08/ ... ial-oh-my/
https://www.sapien.com/blog/2015/10/01/ ... -template/
David
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: Module publishing process.
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.
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.