Summary
The following error appears at log.
The content in ConfigPackage Name:Config and Version:1.0.0.20180315.2 in Service Manifest 'TwoServicePkg' has changed, but the version number is the same.
I changed only the code of one of the services, so I changed only one version of the code in the manifest.
In this case, there is no problem with the upgrade through Visual Studio.
However, upgrading via VSTS will cause the above error.
Details
I created VSTS CI/CD for Service Fabric as default. (Pipeline: VSTS Git Repo -> Build -> Release)
First 'Commit > Build > Release' is Okay.
Service Fabric Manifest Versions
MyAppType: 1.0.0
OneService: Pkg 1.0.0 / Code 1.0.0 / Config 1.0.0
TwoService: Pkg 1.0.0 / Code 1.0.0 / Config 1.0.0
Now, I fix OneService Code only. And Edit verisons of service fabric manifest.
Service Fabric Manifest Versions
MyAppType: 1.0.1(*)
OneService: Pkg 1.0.1(*) / Code 1.0.1(*) / Config 1.0.0
TwoService: Pkg 1.0.0 / Code 1.0.0 / Config 1.0.0
Second Commit > Build is Okay. But Release is Failed. The following error appears at log.
The content in ConfigPackage Name:Config and Version:1.0.0.20180315.2 in Service Manifest 'TwoServicePkg' has changed, but the version number is the same.
But I didn't modify TwoService Pkg (Both Code, Config).
Moreover, It's good to Publish To 'Azure Cloud Service Fabric Cluster' through VS2017 IDE, Immediately. (Of course, 'Upgrade the Application' option checked.)
Current temporary solution is to version up all (all pkg / code / config) like below.
Service Fabric Manifest Versions
MyAppType: 1.0.1(*)
OneService: Pkg 1.0.1(*) / Code 1.0.1(*) / Config 1.0.1(*)
TwoService: Pkg 1.0.1(*) / Code 1.0.1(*) / Config 1.0.1(*)
I want to construct build pipeline, But It's Confusing.
Additional Information
I just use default VSTS Service Fabric template.
And modify only Publish Profile name (Cloud.xml -> Cloud.Development.xml).