I have a VSTF build server which we use to build and deploy our applications mostly C#. I have now been challenged with deploying SSIS packages. From a manual perspective on my laptop we can get things accomplished, but on the build server we are having issues. This has been our guide, but it was written in 2017. https://www.red-gate.com/simple-talk/sql/ssis/deployment-automation-for-sql-server-integration-services-ssis/
We are on VSTF2019, VS2019. On the build server we use only the MSBuild tools, but it seems like SSIS on the build server wants the full UI for VS2019 and SQL Server Management Studio and SSIS.
Our issue is our C-Drive has insufficient space to support these UI's and they don't fully allow us to deploy them to the D-Drive where we have more then enough space.
I am looking for a document or how-to add SSIS (2019) to our build server so that it can be built and deployed using the least amount of space on the c-drive, like build tools. or does SSIS need a build server of its own?
You can use SSDT standalone installer to install Integration Services without a SQL server. See document here for more information.
does SSIS need a build server of its own?
Building SSIS package needs the required tools(VS2019+SSIS) to be installed in the build server. If this is achievable. You can just install the tools in your existing build server.
Or you can just create on-premise build agent on a new build server which has the tools installed.
If you are able to have a build server with Visual Studio and SSIS designer installed. Deploying SSIS packages would be much easier. You can use the SSIS Build/Deploy task directly in your pipeline. See document here.
Related
Is there any way we can pass the password for the solution to get built properly with no error?
If you install the SQL Server Integration Services (SSIS) DevOps Tools Azure DevOps extension, there's an option to specify the password for your project.
Project password
Password of the SSIS project and its packages. This argument is only valid when the protection level of the SSIS project and packages is EncryptSensitiveWithPassword or EncryptAllWithPassword. For package deployment model, all packages must share the same password specified by this argument.
Please make sure to use Version 1.* , since the project password is a Version 1.* property.
Enhancements in version 1.*:
Remove the dependency on Visual Studio and SSIS designer. Build task can run on Microsoft-hosted agent or self-hosted agent with Windows OS and .NET framework 4.6.2 or higher.
No need of installing out-of-box components.
Support protection level EncryptionWithPassword and EncryptionAllWithPassword.
I'm setting up my first pipeline job in azure devops. My C++ application uses the QT framework with qmake to create the make files. It also makes heavy use of the QT framework.
I'd like to use the Microsoft managed ubuntu server. How do I get the QT open source framework and tools installed on the build server? Or, do I have to use a self-managed server?
You can find all the supported Software packages in Ubuntu 1604 image at here. So as per the official docs QT is not supported by the Ubuntu hosted agent,which means you have to use your own custom agent for the build.
I have a build definition on visual studio online which creates an msi installation package using WiX.
How can I automatically deploy the msi package from VSO build agent to Azure VM after the build completes successfully?
Note: I prefer to use a post-build batch or powershell script as part of the build process. The script should copy the msi to the vm and install it.
You should use Release Management Online. It comes with VSO and allows you to easily orchestrate installing an MSI on any Azure server.
http://nakedalm.com/building-release-pipeline-release-management-visual-studio-2013/
Microsoft just added RM in VSO and its simple to use. I setup an end to end web app deployment, buy as its just a PowerShell to do the install an MSI would be trivial. RM takes care of getting all of the bits to the right spot...
http://nakedalm.com/create-release-management-pipeline-professional-developers/
Honestly, it sounds hard, but is much easier than trying to do it all yourself.
Is anyone aware of an installer (msi or otherwise) that drops the SSIS Deployment Wizard executable (ISDeploymentWizard.exe) onto a server (generally found in C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn). We have a web server (we use this as our TFS Agent) that we want to deploy our SSIS 2012 packages from - it is a fairly vanilla server (with IIS, .NET, etc) and hence we don't want a fully blown install of SSIS and/or VS2012 (SSDT) just to deploy SSIS packages.
I realise we can use T-SQL (which requires an instance level perm'd user as an OPENROWSET BULK import is used) and/or MOM to deploy SSIS packages to a remote SQL Server 2012 instance however the preference is to use the SSIS Deployment Wizard
I would have thought ISDeploymentWizard.exe would have been part of the SQL Server 2012 Feature Pack (http://www.microsoft.com/en-us/download/confirmation.aspx?id=35580) however it is unclear exactly whether this is the case and indeed which msi it would belong to
I needed the same ISDeploymentWizard.exe on our build server. We didn't want a full installation of SQLServer on the build box. Using the ISO (en_sql_server_2012_developer_edition_with_sp1_x64_dvd_1228540) from MSDN subscriptions
I chose "Integration Services"
However, if you look thru the files in the ISO there is
sql_is.msi
Which is likely the MSI you looking for. That placed isdeploymentwizard.exe in for out 64-bit machine.
C:\Program Files\Microsoft SQL Server\110\DTS\Binn\ISDeploymentWizard.exe
Can you please enlighten me on my task?
My task is to create a nightly builds of MSI (done in WiX) and install it to our web server using powershell.
TFSBuild server build an MSI
Run Powershell to uninstall and install the newly build MSI.
Run Powershell to Start the windows service.
The WiX MSI contains WindowsService and a Web Application.
Below are list of what i have done so far:
Solution.sln : Configuration Manager and "x86|debug" (check all the files that needs to be built '.wixproj' already checked)
Created a build definition and set "x86|debug" for configurations to build and set projects to build is my solution file.
but after the build has completed, there is no MSI files on the binaries build folder on the build server. :(
Thanks in advance.
Few pointers:
Have you installed Wix on the buildserver?
Which version of Team Build are you using? 2010 has the preference here as the tooling has progressed a lot since 2008.
Did you configure to run msbuild in auto or x86 mode (auto can result in 64-bit which has some issues with the latest stable version of wix) link link
Is your build agent running on a 64 bit server? If so, you either need to run the build agent under an administrative account or do some mucking around in the registry to fix issues with Wix. link
To install the build using Powershell, I personally prefer TFSDeployer, which can monitor your build output and trigger powershell scripts based on the build outcome. It takes away the deployment responsibility from the build server and saves a lot of headaches around security and account configurations.