We are using TFS agile process in our MSBI project. I am new to VSTS. We created new team project into VSTS and we checked in our SSAS project into VSTS. Now we have to deploy SSAS project from VSTS to local development server. First I tried to build the project from VSTS. It's not worked. I googled but I couldn't find any solution.
Can anyone please tell me how to build and deploy SSAS project from VSTS to local development server step by step?
The SSAS projects can be build with the Visual Studio Build step.
The deployment of .asdatabase files (which are the output of the build) can be done with Microsoft.AnalysisServices.Deployment.exe
Related
We migrated from TFS 2015 to Azure DevOps. The XAML builds also ported over to Azure. But we need to migrate them to Azure build pipelines as the XAML builds are still running on On premises TFS Server. We have hundreds of builds and cant manually create new pipeline for each build one at a time. Can some one help please?
XAML builds are still supported with Azure DevOps Service (with some limitations), see official response from Microsoft, in my answer here.
We're currently in the process of migrating from TFS to Azure DevOps and we're not planning on upgrading any of our legacy XAML builds (we're creating vNext builds going forward), as they were successfully migrated into Azure.
I figured out a way ( I am not done yet)..
we can call the api and export the build defs into json files
Use the Json files to port them over to the new Build defs. (Porting involves creating new builds programatically and using Azure Api .. + the data from Json files we just exported).
Regarding CI and CD.
As of now the manual approach followed by developers is the developers are using bea workspace studio for their builds and these builds are sent to Ops team to deploy the ear files in the backend. Workspace studio contains .metadata wherein .plugins will be created while using the workspace. As part of the DevOps implementation we need to build that in their onpremise build server which is sun solaris. The server has weblogic but not workspace studio. Is there any alternate approach to build in the build server apart from using workspace studio.
Currently, we are using TFS 2012 and we have a heavily customized build process as described below.
1. Build the source
2. Run an EXE as console to host WCF services
3. Restore databases on local sql server
4. Run functional test
5. delete databases
6. close the exe started in step 2.
7. Create an Installable exe using WiX ( Wix with custom bootstratpper)
8. Update version number file to TFS
Now we want to move to Visual Studio online from onpremise. Trying to setup a build process with Private Build agent. I have created an VM , installed and registerd agent. I do see agent name back in website.
When I go back to Visual studio and try to create new xaml build definition I am getting below error.
TFS22501: Creating a build definition requires a build controller be defined for this team project collection. There may not be any controllers configured or you may not have permissions to view them. contact your team foundation server administrator.
can somebody please help ?
If you're using XAML build, you have to use the old-style XAML build controller/agent. The VSTS agent is for the new build system.
I would strongly recommend migrating your builds to the new build system as part of your migration to VS Team Services, as the XAML build system is effectively dead.
We have some SSIS packages which we are trying to automate using TFS so that the packages will be picked from repository instead of local machine of developer and then those packages can be deployed to file system. I tried to build the SSIS package solution file using TFS but there is no output, might be because MSBuild cannot understand SSIS packages. Please let me know if you have any idea of how to deploy the SSIS packages from TFS repository to a file system. Well I can easily change the configuration and setup to one environment, but my need is that it has to happen through TFS.
I tried to configure my SSIS Project but I was unable to do so because I was using SQL Server 2008R2 and TFS was 2012. So, I was facing compatibility issue.
However! These links might help you automating your deployment.
Integration Services (SSIS) and Visual Studio Team Foundation Server
Automating SSIS Package deployement using TFS
Automating SSIS 2012 ‘Project’ Deployment
TFS vs SSIS project versioning
Many pardons for this Linkuish answer!
With the new TFS 2008 and the upcoming TFS 2010, are Web Deployment Projects depreciated? We used them in our 2005 projects because we needed the multiple distribution of files across a cluster but now that TeamBuild does that, and we are just now moving out of VSS to TFS 2008, I was wondering if there was an argument to be made on removing the WDPs and just go with a strict TeamBuild solution.
We use CruiseControl.NET to build currently but was looking at moving to one solution instead of just using the CC.NET plugin to build from TFS Source Control.
Typically speaking, in a team environment you want to use Web Application Projects anyway which lends itself to xcopy style deployments. We have dozens of applications that are under active development using this method.
When using Team Build, I highly recommend you get a copy of TFS Deployer which enables you to utilize powershell scripts that are hooked into the Build Quality settings.
Our setup is CI (leveraging TFS 2008) with TFS Deployer. A successful check in causes a build and deployment to our dev servers. When we change the build quality to "In Staging" TFS Deployer moves the projects to our staging servers. When our infrastructure team changes it to "In Production" in deploys to our web farms.
Simple, to the point