SharePoint Solution Deployer (SPSD) helps you to deploy SharePoint solution packages (.wsp) to multiple SharePoint environments. It deploys, retracts and upgrades one or more WSPs and can be extended to perform additional custom tasks in PowerShell before or afterwards. Unlike the most of the available scripts on the net, it performs all necessary prerequisite checks and post-deployment actions on all servers in the farm to assure the deployment runs smooth.
This pull request contains various changes in SPSD scripts:
Small bugfixes and spelling issues in comments
Refactor three functions: GetEnvironmentFile, GetVariablesFromFile and LoadEnvironment to more clear responsibility. Now GetEnvironmentFile only find what file will be readed, GetVariablesFromFile only parse and load variables from input file and LoadEnvironment orchestrate them.
A major change is rewritten Log function. Before this, using SPSD in build agents (TFS) doesn't output anything in TFS console. Also i come back logging into file when SPSD run in AppMode. Later this feature was removed in 9109bfa14c8585fdf733b71789a5b98fa54b8b95
Because TFS run every powershell script with a Verbose log level, all sharepoint commands and some others gave additional outputs in console. This issue was solved by explicitly turn off Verbose log level in these commands
Updated SPSD version number because significant changes
Resulting screenshot:
Existing issues
There is strange behavior when SPSD call CustomEnter-PSSession function, for example in RecycleAppPools. TFS console output breaked while file output not
2018-01-13T09:05:22.3537558Z 'XXXX.wsp' (farm solution)
2018-01-13T09:05:22.3547527Z Updating...Done
2018-01-13T09:05:22.3617567Z Waiting to finish job 'solution-deployment-XXXX.wsp-0'........................Finished
2018-01-13T09:05:22.3647547Z Checking deployment...Ok
2018-01-13T09:05:22.3657530Z (00:00:54.0646162)
2018-01-13T09:05:22.3667557Z Running 'Deployment' actions
2018-01-13T09:05:22.3687773Z Recycling IIS application pool on server XXXXXX
2018-01-13T09:05:22.3977576Z Deployment status for machine 'XXXXX' : 'Passed'
When SPSD run in AppMode CustomEnter-PSSession do nothing, therefore settings to run commands in all servers in a farm has no effect
This pull request contains various changes in SPSD scripts:
GetEnvironmentFile
,GetVariablesFromFile
andLoadEnvironment
to more clear responsibility. NowGetEnvironmentFile
only find what file will be readed,GetVariablesFromFile
only parse and load variables from input file andLoadEnvironment
orchestrate them.Log
function. Before this, using SPSD in build agents (TFS) doesn't output anything in TFS console. Also i come back logging into file when SPSD run in AppMode. Later this feature was removed in 9109bfa14c8585fdf733b71789a5b98fa54b8b95Resulting screenshot:
Existing issues
CustomEnter-PSSession
function, for example inRecycleAppPools
. TFS console output breaked while file output notCustomEnter-PSSession
do nothing, therefore settings to run commands in all servers in a farm has no effect