Activity overview
Latest activity by SebastianHolc
Peter, just to double check: I understand that "Principal '<mySecurityPrincipal>' could not be created. [...]" error occurs during execution of the "Redgate SQL Change Automation: Release" task on your pipeline? If so, what's the authentication method you've set for this task? Adding Azure AD Password auth method to the Build task Kendra mentioned will make the IF DB_NAME() NOT LIKE 'sql_change_automation_%'workaround obsolete (assuming you actually want to create the users on a temporary database), however from what I understand you're having issue with the Release task at the moment. / comments
Peter, just to double check: I understand that "Principal '<mySecurityPrincipal>' could not be created. [...]" error occurs during execution of the "Redgate SQL Change Automation: Release" task on ...
First let me point out few things that may be helpful:
Unfortunately the only control over the .nupkg generated by the Build task is to whether you want to publish it or not. The package is always generated in current working directory (the "/_work/x/s/" directory you mentioned, available in $(System.DefaultWorkingDirectory) YAML property). If you choose to publish it, it's always published under "Database Build Artifact" name.
In Release task, you choose from which directory Build Artifact (.nupkg) will be grabbed, using the NuGetFile input parameter (set it to the directory where .nupkg is located).
I'm not aware of scenario, where either Build or Release task would delete the Build Artifact.
You can use the default CopyFiles@2 task, to copy the Build Artifact to any directory of your choosing, then specify that directory to the Release task, e.g.:
- task: RedgateSqlChangeAutomationBuild@4
# [...]
# Copy Build Artifact to /_work/x/a/
- task: CopyFiles@2 inputs: SourceFolder: '$(System.DefaultWorkingDirectory)' Contents: '$(PackageName)*.nupkg' TargetFolder: '$(Build.ArtifactStagingDirectory)\Database Build Artifact' OverWrite: true
- task: RedgateSqlChangeAutomationRelease@4
inputs:
Operation: 'Create'
NuGetFile: '$(Build.ArtifactStagingDirectory)\Database Build Artifact'
# [...]If you opt-in to publish the Build Artifact during the Build task, you can download the published artifact later on, using the DownloadPipelineArtifact@2 (example in Kendra's post above). Maybe just copying the .nupkg, right after the Build task, to $(Build.ArtifactStagingDirectory) or something else would help? / comments
First let me point out few things that may be helpful:
Unfortunately the only control over the .nupkg generated by the Build task is to whether you want to publish it or not.The package is always g...