How can we help you today? How can we help you today?
StephenMclean
Robert Clenshaw wrote: Hi Stephen, What output are you getting from the build step? I'd like to know if the build step is actually registering the schema with DLM Dashboard or if it's encountering a problem and not registering it. Another thing you could do to verify that the schema has been registered is to do the following - Visit http://localhost:21060 in your browser In the top menu click on Documents. In the left hand pane click on SqlCompareSnapshots. In the main window, look for a snapshot with the package name that you were trying to register it with. If you can find it in the list then you've been able to register the schema and the problem is somewhere else. Another thing I would do is to extract the nuget package to a blank folder and then use SQL Compare to compare it to the database - if there has been some sort of issue with the sync step then there might be a schema difference. That would be a possible explanation for the dashboard not recognising the schema as the one that you registered. Thanks. We have looked at the snapshots and the name is blank. We compared the nugget package to the SYNC database and they were identical. We're also seeing this in the Jenkins log at the end of the BUILD step:- COMPLETED SUCCESSFULLY: Validating database state STARTING: Publishing database package Writing package to C:Program Files (x86)JenkinsjobsManzen Database TrunkworkspaceNewCIPackage.2.509.nupkg... Written database package to C:Program Files (x86)JenkinsjobsManzen Database TrunkworkspaceNewCIPackage.2.509.nupkg COMPLETED SUCCESSFULLY: Publishing database package Registering schema with DLM Dashboard... Done / comments
Robert Clenshaw wrote: Hi Stephen, What output are you getting from the build step? I'd like to know if the build step is actually registering the schema with DLM Dashboard or if it's encounteri...
0 votes