You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we are using TDS .update package to deploy code to servers. TDS is producing the *.files.update. We are using in-house deployment approach with custom controller and action doing it.
We would like to move to Sitecore.Ship, however seems like package is processed (no errors in the logs), JSON with processed entries is being returned, but the files from the package are not updated on the server.
Sitecore logs:
> 1568 19:35:15 INFO Committing files.
> 1568 19:35:16 INFO Executing post installation actions.
> 1568 19:35:16 INFO Executing post installation actions finished.
>
I had a look into the Ship implementation for building the PackageInstallationInfo and it looks like this:
var info = new PackageInstallationInfo
{
Mode = InstallMode.Install,
Action = UpgradeAction.Upgrade,
Path = packagePath
};
Our deployment action however has one difference in that matter - ProcessingMode:
var installationInfo = new PackageInstallationInfo
{
Action = UpgradeAction.Upgrade,
Mode = InstallMode.Install,
Path = path,
ProcessingMode = ProcessingMode.Files
};
Is this why the files are not showing up on the server after the deployment? If yes - is there any workaround or this should become a feature request?
The text was updated successfully, but these errors were encountered:
Sitecore 8.2 161221
Sitecore.Ship 0.4.0.150818
Currently we are using TDS .update package to deploy code to servers. TDS is producing the *.files.update. We are using in-house deployment approach with custom controller and action doing it.
We would like to move to Sitecore.Ship, however seems like package is processed (no errors in the logs), JSON with processed entries is being returned, but the files from the package are not updated on the server.
Sitecore logs:
I had a look into the Ship implementation for building the
PackageInstallationInfo
and it looks like this:Our deployment action however has one difference in that matter - ProcessingMode:
Is this why the files are not showing up on the server after the deployment? If yes - is there any workaround or this should become a feature request?
The text was updated successfully, but these errors were encountered: