How can we help you today? How can we help you today?

Build server pipeline failing after auto-update of SQL Change Automation (v 4.4.22194.30982)

Our build servers are failing after the auto-update of SQL Change Automation (v 4.4.22194.30982) this morning. In our Azure Dev Ops pipelines, we have a specific step for SCA (that is NOT failing). However, when the Visual Studio Build "Build solution" step is executed, the SCA build fails because te DBClean task cannot locate a specific version of Newtonsoft.Json. (See error from build below).

I know that I could rework my VS solution configuration to bypass the SCA build in the "Build solution" step, however, this feels like a bug in SCA and I really don't want to have to edit many, many, many solutions and pipelines to get this fixed. 

Anyone else out there have this issue? Any ideas for resolution (without reworking the solution Build Configuration)?

Thanks,
Pam


##[error]C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\SqlChangeAutomation\SqlChangeAutomation.Data.Schema.Ssdt.targets(455,5): Error MSB4018: The "DBCleanTask" task failed unexpectedly.
System.IO.FileNotFoundException: Could not load file or assembly 'Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.
File name: 'Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'
at RedGate.Versioning.Engine.Shared.Logging.Api.Configuration.LoggerConfigurationManager.GetLogLevel(IServiceIdentifier serviceIdentifier)
at RedGate.Versioning.Engine.Shared.Logging.Serilog.SerilogLoggerConfiguration..ctor(IServiceIdentifier serviceId, ILoggerConfigurationManager configurationManager)
at RedGate.Versioning.Engine.Shared.Logging.Serilog.SerilogLoggerConfiguration..ctor(IServiceIdentifier serviceId)
at RedGate.Versioning.Client.MsBuild.MsBuildModule.Load(ContainerBuilder builder)
at Autofac.Module.Configure(IComponentRegistry componentRegistry)
at Autofac.ContainerBuilder.Build(IComponentRegistry componentRegistry, Boolean excludeDefaultModules)
at Autofac.ContainerBuilder.UpdateRegistry(IComponentRegistry componentRegistry)
at Autofac.Core.Lifetime.LifetimeScope.CreateScopeRestrictedRegistry(Object tag, Action`1 configurationAction)
at Autofac.Core.Lifetime.LifetimeScope.BeginLifetimeScope(Object tag, Action`1 configurationAction)
at Autofac.Core.Lifetime.LifetimeScope.BeginLifetimeScope(Action`1 configurationAction)
at Autofac.Core.Container.BeginLifetimeScope(Action`1 configurationAction)
at RedGate.Versioning.Client.MsBuild.SqlChangeAutomationTask`2.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()
PDQ
0

Comments

34 comments

Sort by
  • DanC
    Hi @BrendonM

    Would you be able to log a ticket with us at support and provide the full debug logs for us to investigate further?
    DanC
    0
  • InkZ
    BrendonM said:
    Hi

    It looks like a similar issue might have occurred again?


    I spent a couple of days changing all of the build runners after the last time.  They obviously aren't supporting or testing the old way of doing things now.  TBF I actually prefer the new .Net build runners.  They support DEVENV now, and you can DEVENV multiple projects in one build step where we had a load of command line steps in Team City previously, which is great for our SSRS, SSAS projects.
    InkZ
    0
  • BrendonM
    @DanC thanks - done.

    @InkZ thank you for the suggestion. In this case TeamCity is not using the deprecated MSBuild runner, it's using the RedGate SQL Change Automation Build step that comes with the RedGate SQL Change Automation TeamCity plugin. It does quite a bit in addition to building the projects so I would prefer not to try and replace it if possible.
    BrendonM
    0
  • BrendonM

    It seems to have been a false alarm. The builds are working now. It looks like it was somehow picking up the wrong versions of some MSBuild DLLs and once these were removed from the GAC it started working.




    BrendonM
    0

Add comment

Please sign in to leave a comment.