Comments
Sort by recent activity
Unfortunately PowerShell has a tendency of loading the old version of PowerShellGet by default, even if you've got a newer version installed. To be absolutely certain, you'll need to run the following: Import-Module PowerShellGet -MinimumVersion 1.6 -Force<br>Import-PackageProvider PowerShellGet -MinimumVersion 1.6 -Force<br><br>Install-Module SQLChangeAutomationI'm assuming you're doing this all on a development machine to test things out by the way. The various SQL Change Automation build/release extensions have their own auto-updating mechanism to download the latest version of SQL Change Automation from PowerShellGet, which does some more complicated things to make sure that it can work without admin permissions (if you're interested in the gory details, you can look in the extension directory for the file PowerShellGallery.ps1 to see what we do). / comments
Unfortunately PowerShell has a tendency of loading the old version of PowerShellGet by default, even if you've got a newer version installed. To be absolutely certain, you'll need to run the follow...
SQL Source Control is licensed per-user, so you'll need a license for each employee who makes database changes. / comments
SQL Source Control is licensed per-user, so you'll need a license for each employee who makes database changes.
We've just released version 2.0.26 of the DLM Automation 2: Build extension which should fix this. If you're using VSTS the extension should auto-update, but if you're using TFS you'll need to install the updated version. / comments
We've just released version 2.0.26 of the DLM Automation 2: Build extension which should fix this. If you're using VSTS the extension should auto-update, but if you're using TFS you'll need to inst...
Hope that's worked for you. You could also just have copied the PowerShellGallery.ps1 and SqlCi.ps1 files from 2.0.23 to 2.0.24, because that's all that was missing. I'm really not sure why it's not updating to 2.0.25 though. I'm not aware of any progressive rollout, unless it's something Microsoft does from their end. / comments
Hope that's worked for you. You could also just have copied the PowerShellGallery.ps1 and SqlCi.ps1 files from 2.0.23 to 2.0.24, because that's all that was missing. I'm really not sure why it's no...
That's very strange. What version do you see when you go to https://marketplace.visualstudio.com/items?itemName=redgatesoftware.redgateDlmAutomationBuild / comments
That's very strange. What version do you see when you go to https://marketplace.visualstudio.com/items?itemName=redgatesoftware.redgateDlmAutomationBuild
Sorry about that. We had a packaging error in that release of the VSTS extension, and that file was missed out. We released another build, 2.0.25 soon after that should have fixed the problem. / comments
Sorry about that. We had a packaging error in that release of the VSTS extension, and that file was missed out. We released another build, 2.0.25 soon after that should have fixed the problem.
Hi @markg - are you using VSTS or TFS? And if your're using TFS, which version? Under VSTS, the tasks should auto-update. For TFS, you'll have to manually update, following Microsoft's instructions: https://docs.microsoft.com/en-us/vsts/marketplace/get-tfs-extensions?view=tfs-2018 / comments
Hi @markg - are you using VSTS or TFS? And if your're using TFS, which version?Under VSTS, the tasks should auto-update. For TFS, you'll have to manually update, following Microsoft's instructions:...
Does your build agent actually have access to the internet, and specifically Powershell Gallery? The first step of doing the auto-update check is downloading PowerShellGet 1.6 if it's not already installed - and it's that part that's failing. We'll put some more error handling around it so that doesn't fail the build, but the auto-update mechanism will not work without that. If you run the following PowerShell on the agent, what's the output? Get-PSRepository<br>Get-Module PowerShellGet -ListAvailable<br> / comments
Does your build agent actually have access to the internet, and specifically Powershell Gallery?The first step of doing the auto-update check is downloading PowerShellGet 1.6 if it's not already in...
Hi, That's a warning message, and it's safe to ignore it. It's telling you that it was unable to access the PowerShell Gallery to download the latest version of the DLM Automation module - probably because you're running on a private agent that only has PowerShell 3 (and therefore doesn't have the PowerShell Gallery cmdlets available). The code will fall back to using the installed version of DLM Automation, but you won't be able to get automatic updates to the latest version of DLM Automation. If you want auto updates to work, and to get rid of the warning message, you can either update the agent to a newer version of PowerShell using the WMF installer (see https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-windows-powershell?view=powershell-6 for details) or install the package management MSI for PowerShell 3/4. In the next release of the VSTS addons, we'll improve that warning message so it's clearer what's going on. / comments
Hi,That's a warning message, and it's safe to ignore it. It's telling you that it was unable to access the PowerShell Gallery to download the latest version of the DLM Automation module - probably ...
Yes, sorry. When we changed the addins to prefer the DLM Automation module from the PowerShell Gallery, we introduced an incompatibility with older PowerShell versions (<5.1) - as soon as the problem was reported, we shipped a fix in 2.0.23. / comments
Yes, sorry. When we changed the addins to prefer the DLM Automation module from the PowerShell Gallery, we introduced an incompatibility with older PowerShell versions (<5.1) - as soon as the probl...