Release Management questions

Hi all,
I've been looking at Visual Studio Release Management and on the whole, I think it's good, but I have a few issues that someone here may have already worked around.
Can I send an email to a group of users once the deployment is complete that includes custom text
including details about the build (e.g. build number)?
Is it possible to skip stages? We have 4 Development environments, but may not always want to deploy to all of them before moving onto Test
Our builds create 4 different sets of output - one for each environment (DEVT, TEST, STAG and PROD). Each of these is in a separate folder. Do I have to define separate components for each of these and specify the build number of each of them when triggering
a release? One of our apps has 7 different components and if I have to enter the build number 7x4 times it is going to take a while!
How can I run a script against a database that is not in a fixed location - e.g. c:\buildoutput\app\1.2.3 (4.5.6.7)\scripts\scripttorun.sql if the folder that contains the build output is different for every build (i.e. the version number changes)
Easy questions to answer I'm sure, but any help will be appreciated :)

Hi Mark
If you are planning on going for RM 'all in', in my experience it's probably best to be prepared to ditch what you already have in terms of deployment artefacts and start again so it works best with RM. This isn't as bad as it sounds. My thoughts as follows:
As far as I can see RM doesn't have a role in deploying to desktop clients as it's not designed for that.
My preference is to xcopy stuff where possible. If there are problems xcopy feels like it's going to be the easiest to debug.
You want to define one build definition that results in each of your deployables in 9 separate folders (I'm assuming the client is now out of scope here) as files you can xcopy with a tokenisation story in place for each deployable. (Different
story for web apps and services.)
You define your environments via Configure Paths > Environments
You link your environments / stages in a chain / pipeline via Configure Paths > Agent-based Release Paths (assuming you are not using DSC)
You create 9 components for each of your deployables. You don't worry about the build version as RM dynamically supplies this but you do specify the 'Path to package' eg \WebApp1Folder\_PublishedWebsites\WebAppName. The component will also
deal with tokenisation.
The components are used in the Agent-based Release Template which is based on the Agent-based Release Path specified earlier. Your 9 components will be used at each stage. The 'Path to package' will always be the same but the config will change as
required for each stage. There is no need to specify a parameter for the environment since you will reuse the component in each environment.
Your DEVT / virtual garages problem sounds like it needs some thought. Is DEVT part of the deployment pipeline ie is it a critical part of the route to live? If not then you will want to treat them separately.
Hope all this makes sense. At my work we are implementing continuous delivery on existing applications and it's 50 times harder than creating a demo pipeline.
Very happy to be helping by the way - other people's problems are a great source of possible blog posts :).
Cheers - Graham

Similar Messages

Anyone experience with Oracle Release Management?

Hi,
I don't know in which forum to post this, but Order Management seems to be most appropriate.
I am looking for someone with experience in Oracle Release Management. We are an Automotive company and a couple of our customers use EDI and we have many repeating orders / schedules. We don't have EDI set up yet, that's planned for later. We were wondering if it makes sense to start using Release Management. What we have in mind is to use the Release Workbench to enter Order Schedules faster than in OE/OM.
However, even after reading the implementation & user manual this is still very unclear to me... What features are worth to be used with and without EDI etc. How does it fit in the whole concept and what benefits it can bring.
I am looking for someone who has experience in this area and is willing to share some knowledge. Anyone here from companies that use this module?
Btw., we are using eBusiness Suite 11i (11.5.10.2) and have Order Management and a couple of other modules heavily used.
Thanks,
David.

Well your question is from a few years back, but I am still curious if you had any answers? If so would you be so kind to share those with me? I am currently more or less in a same position. We want to use Release Management to prefent of releasing orders when a customer is beyond his forecast, but I have no idea if we can do it with this module.
Thanks: Pum van der Lit

Release Management Server/Client clarification

Hi there,
I am using TFS 2010 and i would like some assistance in regards to what i would like to do please.
At my place of work we have a Build server, call it Server A which has a controller and 2 build agents. It builds my projects and outputs them in a drop folder on that server.
Firstly, can i use my existing custom build template to allow others to trigger a build via the Release Management Client tool?
The existing custom template i am using builds all the projects in the solution and then generates several *.MSI files at the end. I use this template in all of my Build Definitions.
Secondly, Do i have to install the Release Management Client tool and Deployment Agent on the Build server as well?Correct me if i am wrong because i read that if you want to do automated deployment i have to do this.
Thirdly, am i allowed to use custom scripts, executable side by side with the Deployment Agent. The reason i ask that is at some point i would like to extend the process so that once the build has finished, i can install it on Server B. Is this possible?
Lastly, do i have to install Visual Studio 2013 on the build server for Release Management Server to work correctly?
If you have any questions on the above please let me know.
Thanks,

Hi IndusKing,
Thanks for your reply.
If your build definition using the ReleaseDefaultTemplate.xaml template, and you want only to build the solution(needn’t to trigger release template), you can set the
Release Build = False in build definition>>Process>>Release.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.
So if i understand correctly i can either use the ReleaseDefaultTemplate.xaml in all my build definitions or i can modify my existing template to use the Release Template functionality e.g Release Build = False.
As far as I know RM Client not support trigger TFS build definition. You can install the VS on your RM Client machine, then trigger build definition in Team Explorer, or trigger the build definition by execute TfsBuild
Start command line.
Are you saying that RM client can only deploy finished finished builds?

Is it possible to do Continuous deployment for azure cloud services(website,web and worker roles) using VSO Release management?

Hi,
I am trying to do continuous deployment using visual studio online and release management for Azure cloud services. But not able to find the way to do it(with the help of different blogs, those are describing using VM only).
I tried using Release management visual studio extension also. But no Luck.
Please help me if it is possible to do continuous deployment using release management.
Thanks,
Phani

Hi,
Please refer to the following Forum Thread with similar question which has been answered. Let us know if this helps.
https://social.msdn.microsoft.com/Forums/en-US/9d8322f6-36e5-4cca-a982-d420d34d2072/realease-management-deployment-to-azure-websites-webworker-roles?forum=tfsbuild
Regards,
Nithin Rathnakar

Could you please tell what is encryption mechanism used in Release Management for storing any password

Could you please tell what is encryption mechanism used in Release Management for storing any password

Hi y e ll e sh,
I am trying to involve someone to further look at your question. There might be some time delay. You can also check replies for the similar question in this
thread. Appreciate your patience and thanks for your understanding.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Alternate development landscape and transport path - release management

We are discussing a proposal within our company to build a landscape that includes separate clients and transport paths for development of new system enhancements vs. ongoing production support. The idea is to keep all new development in a separate stream and prevent any conflicts with any required production support changes. This approach was used on a project where I previously worked, and we are seeking input from other SAP shops that use this approach, as well as any best practice documentation to assist us in development of an internal proposal on the topic. I would be grateful for any input on this topic, as well as the topic of release management. I have done quite a bit of searching on SDN and BPX and am just not finding anything.
Note that I also posted this question in the BPX general discussion forum because I was not clear exactly how it should be categorized. I apologize if this was not the appropriate course of action.

Hi Bob
without being an expert. You could check the documentation for "Change and Transport System" (CTS) in help.sap.com. It comes with some "strategic" information as well.
The CTS "belongs" to SAP NetWeaver, and an extended version is available "CTS". Further recommendation would be that you check out the SAP Servicemarketplace information for SAP NetWeaver for "CTS". The use of such large functions is normally described in presentations as well.
regards
Andreas R

LCM Change and Release Management - How to maintain job integrity

Hi
We are using BO in a three scale landscape. DEV, QA and PRD are all are in a same network. I installed Business Objects Life Cycle Manager 3.1 SP3 on my dev system.
I created a job for DEV -> QA. (Multiple iterations - for changes in DEV while testing)
Once the final version is tested in QA, those objects suppose to be moved from QA -> PRD not directly from DEV -> PRD. Because when i make a copy of the existing job, that's not allow me to change the source system.
Now, my question is, I want to maintain integrity of job promotion, means I want to move the same objects which tested in QA to PRD,
1. DEV -> QA -> PRD. Is it possible in LCM or any other tool?
2. Is it possible to change the source system of LCM jobs?
3. To maintain the interity, is it required to create two jobs
DEV -> QA - Job1
QA -> PRD - Job2 (With same objects as in Job1)
4. What is the right approch for BO Change and Release Management?
Thanks
Deep

Same query as in How to maintain LCM job integrity while promoting?
Please do not cross post. See the [Rules of Engagement|http://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement].
Closing and locking this thread as the one mentioned above is in the correct forum.
- Ludek

Release Management - How to bring testing calls in the Release Pipeline

Dear Team
I had set up a new application release path using RM Client. The release pipeline contains deploying a new web site with IIS.
Using the release template - able to trigger build and deployment happens.
Question #1. In the Build log, the Quality tag is NOT assigned? What is the procedure to assign a quality tag?
In the deployment in QA Environment - launch also testing done - call automated tests from VSTS Coded UI like smoke suite, functional suite for execution and share results
Question #2: Is there any existing services call available or new component need to be developed.
Thanks in advance.

Hi VikramGopu,
I'd like to know the TFS version you're using. For your questions, please check the replies as below:
1. Build quality will not be assigned to a build result unless you choose the values manually. To get the TFS build result assigned a build quality, you can check the links below for more information:
https://social.msdn.microsoft.com/Forums/vstudio/en-US/030a9cc7-4c91-4132-a9fa-0fbcf119218d/tfs2010-team-build-automatically-update-build-quality?forum=tfsbuild
http://stackoverflow.com/questions/19730128/tfs2010-automatically-set-build-quality
2. You can run the coded UI test by using Visual Studio locally or Microsoft Test Manager. If you want to run coded UI test in TFS build, you have to run the build service interactively. To run test duing the build/deployment process, you
can use command tools in Release Management to call mstest to run the tests. Whether you need to create a new component depends on your requirements. You can also refer to this
blog about run tests with Release Management.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. <br/> Click <a
href="http://support.microsoft.com/common/survey.aspx?showpage=1&scid=sw%3Ben%3B3559&theme=tech"> HERE</a> to participate the survey.

Release Management in PCM

Hi all
I wondered how others deal with release management in a PCM environment? Most of my projects have at least a development/test and a production environment; some have one each for development, test and production. In each case, moving changes from one environment to the next is time-consuming and requires a lot of cross-checking. It feels like there ought to be a better way.
Does anyone use software tools or particular techniques to manage this process on PCM projects? If so, what are they, and what has your experience of using them been like?
Steve

Hi Steve,
I've pondered this question since you posted it, and tried to think of an adequate response. I'm not sure I have one. I sure don't have a one-size-fits-all answer. My experience is similar to yours. Each implementation is typically fairly unique and subject to the customer's view of what should be in DEV vs. QA vs. PROD. A lot of times, model migrations are pretty straightforward, but occasionally there's a need to migrate new aspects of a model in chunks.
As far as tools go, we've built a tool for ourselves and our clients that allows for comparison of assignments between models, or between versions & periods within a model (it also allows full model assignment reports to be generated.) It has helped for some clients, but it's not something that we use everywhere.
Mike

Release Management performance - Each step takes over a minute to complete

We have set up a Release Management pipeline using vNext Release Templates with PS/DSC. We noticed that every release step takes about 1:47m to complete, whereas the actual tasks that are performed within each step (i.e. copying the component and executing
the PowerShell script) take only a few seconds. We tested this by copying files and executing PowerShell scripts outside of Release Management.
One of our deployments took about half an hour to complete (and should have taken only a few minutes). (I wanted to include a screenshot but got "Body text cannot contain images or links until we are able to verify your account." when trying to
submit this question.)
We also tested this with a minimal component, containing only one file (one PowerShell script), but even then the deployment took about 1:47m.
Can you tell us what the reason is for this delay? What should be done in order to speed up this process?

Hi Frank,
Does this Release Management performance isssue occurred when you use it at first time? Do you have any setting on your TFS? Would you please tell us your TFS version?
If you have any repro steps, please share with us, thank you.
Best Regards,
Dear Molly,
Yes, this issue has occurred right from the beginning when we started using Release Management.
Could you please clarify what you mean by "do you have any setting on your TFS"? As far as I know, our TFS installation is a straightforward and normal one.
Our TFS version is TFS 2013.
The steps to reproduce (in the simplest scenario) are as follows:
Create a new project in Visual Studio 2013, containing one PowerShell script file. In the script file, perform a simple command such as "New-Item E:\Temp3 -itemtype directory -force".
Perform a successful build of the project, making sure that the script file is copied to the drop folder.
Create a vNext Component in the Release Management Client, that refers to the directory in the drop folder that contains the script file.
Create a new vNext Release Template in the Release Management Client, containing one "Deploying using PS/DSC" action. In that action, set the PSScriptPath to the script file we created.
Perform a new Release using the Release Template we just created. The Deploy action will take a long time, even though the script itself takes less than a second to run.
Please let me know if you need any more information.

Deployer Installation: Failed to validate Release Management Server for Team Foundation Server 2013

Attempting to install the deployer on a machine and getting the below error. Not sure what that means, out of turn error or what actually occurs at this step, validating release management server, during the configuration piece. The user,
that we set for the service was validated fine. The user is an service account in the TFS RM Server, is an admin on the local box as well.
I am able to get into the TFS RM Server through the client just fine. I can hit the TFS RM UI just fine as well.
Curious what would not allow the deployer to complete as mentioned below.
Any help is appreciated.
I, 2013/12/16, 14:46:26.521, Validated account to use as identity for Release Management Services.
I, 2013/12/16, 14:46:26.521, Validating Release Management Server for Team Foundation Server 2013...
E, 2013/12/16, 14:46:30.905, Received Exception : Microsoft.TeamFoundation.Release.CommonConfiguration.ConfigurationException: Failed to validate Release Management Server for Team Foundation Server 2013.
at Microsoft.TeamFoundation.Release.CommonConfiguration.DeployerConfigurationManager.ValidateServerUrl()
at Microsoft.TeamFoundation.Release.CommonConfiguration.DeployerConfigurationManager.ValidateAndConfigure(DeployerConfigUpdatePack updatePack, DelegateStatusUpdate statusListener)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
I, 2013/12/16, 14:46:30.905, Work completed for GetConfiguration() call : got out of turn error
E, 2013/12/16, 14:46:30.905, Failed to validate Release Management Server for Team Foundation Server 2013.

Hi Kpdn,
Thanks for your post.
All your participation and support are very important to build such harmonious/ pleasant / learning environment for MSDN community.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Problems setting up release management

Hi I am running into problems in setting up Microsoft Release Management. I have 2 domains. My tfs (separate server), release management server and release management client (both on single physical server) are in domain1 and deployer is in domain2 in Azure
VM. I am using a VPN tunnel to connect release management server, release management client and deployer. They connect with each other nicely. The problem comes when I add reference to tfs in release management client. TFS fails to verify. Now
the user I am using to connect has Make requests on behalf of
others' permissions so that is not the issue. I get TF400324 error. I even used wireshark to troubleshoot but it looks as if release management
client is not even trying to connect. I can access tfs url via web browser with vpn connected from machine on which release management client is running. when Now if I disconnect the vpn and try to verify tfs from release
management client it works. Does release management client supports connecting via ipv6 tunnel?

Hi abhijitdamle,
I'd like to know how do you connecting via ipv6 tunnel, and when you get the error(without vpn connection?) . If your machine can be access via HTTP/HTTPS, then RM client can also be connected. For your situation, seems you got the
issue resolved after using vpn.
If you have other concerns about the error, you can also check the methods below to see if it works for you:
1. Check the permission of the user account you use, make sure it has the permission of "make requests on behalf of others"
2. Clean team foundation cache on your RM client machine
3. Check the team project collection url to ensure it's input correctly, or use the solution on this
page
Best regards,

Release management with Azure and Visual Studio Online (Cloud TFS)

What strategy would you use to manage the releasing of versioned software to Azure cloud services (web and worker roles)? We are not looking for continuous integration. We are using Visual Studio 2013 and Visual Studio Online (Cloud TFS).
At one point, we were releasing straight from Visual Studio using the Azure Cloud Project Publish tool. This is really bad practice in my opinion as you can never be sure what you are really releasing. Additionally, there is no automated control on the labeling
or branching of code, or the running of unit tests and code analysis checks.
Next, we employed Release builds on Visual Studio Online. Before deployment, one would edit the appropriate Build Definition (whether it be for Test or Production by and filling in the code label (under the "Get Version" build property) that is to
be released. This would then get the appropriate code (by the label specified), build it, and release it to whatever cloud service is specified in the targeted Cloud Project profile (this is using the AzureContinuousDeployment.11.xaml template).
There is still a degree of manual intervention involved. Also, the fact that a version of code is built every time before it is released is not ideal (as far as I understand it would be better if it was packaged once).
Microsoft Release Management tools
look ideal for the job, but are not supported with Visual Studio Online.
Is there a better way of handling our releases?

/waves hand.. These are not the tools you seek. You are looking for continuous integration.
Although CI has the word continuous in there, it does not mean "all the time, every checkin". It can easily refer only to those bits you want to release - -and the way to tell the system which bits you want released is to merge them to a Releases
branch.
If you do this, not only do you get all the joy of controlled CI, but you guarantee what you release is exactly what is controlled in your SCM - under the Releases branch, preferably tagged or otherwise noted as a particular release. That means you can also
rollback to a previous release by simply reverting to a previous release in your SCM!
Of course you don't have to let it happen automatically, you can set it up to build 'continually' and then remove the check on the SCM to see if any changes have been committed. You can replace this with the manual build button.

Unable to Create Website using "Create Web Site" action component in Release Management

Hi Team,
I am trying to use Release Management to Deploy my Website along with DB in staging servers.
I have set-up 2 Staging Servers SIT & UAT Both 2012 Servers with IIS 8.5 Configured.
Defined Release Path and Release template.
Deployment Sequence is something like this :
Deployment Sequence - Server Name - Create Folder - XCopy - Create Website - Configure Website
Build is successful, drops the output to Output folder and RM gets initiated with it's work.
It creates folders as mentioned in the "Create Folder" activity.
It copies the whole content from _PublishedWebsites to the mentioned location.
It gets stuck with the "Create Website" step.
Initially I have provided details as follows :
AppPoolName
IsPreloadEnabled
IsAutoStart
SiteName FabrikamSIT
PortNumber 80
PhysicalPath c:\FabrikamRM\WebSite\SIT
Later, I tried providing
AppPoolName DefaultAppPool
IsPreloadEnabled 1
IsAutoStart 1
SiteName FabrikamSIT
PortNumber 80
PhysicalPath c:\FabrikamRM\WebSite\SIT
Then also no luck.
Deployment gets rejected and the error that you can see when you hover the mouse is :
Task failed with the exit code -2146232576".
No much info available with this eror code in net also.
Any help in getting this simple site created is highly appreciated.
Thanking you in advance,
Regards,
TFS Queries

Hi,
For the deployment sequence, you might need add the action of "create application pool" before creating a website.
Another method is check whether the build output can be deployed manually. If yes, then you can trobleshoot the problem in your deployment sequence and parameters. You can create the website manually and deploy your build output to the website. If you have
any other concerns about the deployment, you can also open a new thread in IIS forum for a better response.
If the issue persists, please elaborate more details about your scenario with sceenshots.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

How best we can use the Rollback and RollbackAlways mechanism in Visual Studio Release Management Template

Hello All,
We need a clarification on Rollback and RollbackAlways in Release template.
We checked a scenario for Rollback and RollbackAlways:
In Release Template, we have the first activity as “Configure Application Pool” and then followed by a rollback action of “Create Application Pool”
and “Create Web Site” then followed by "Code Deployment" via TFS build.
We tested with 2 scenario’s:
With App Pool and Web Site already existing: when triggered the build, configure
app pool succeeded, then Rollback action was skipped (as previous action was successful), finally deploy the code executed (code deployed) and build got succeeded.
Deleted App Pool and Web Site: when triggered the build, configure app pool failed (as no app pool existed), Rollback action executed (as previous action failed) – created app pool and web site then finally
deploy the code executed (code deployed)
But build failed (Error: Configure app pool action failed).
Ideally the build should succeed as the roll back action got executed and code deployed successfully.
Please correct us if our understanding is wrong.
Also, Kindly let us know how best we can use the Rollback and RollbackAlways mechanism in Release Management
Looking forward for your positive response.
Thanks in advance.
Regards,

Hi Shashank,
Rollback Always runs if any of the actions in the template failed. Rollback will run if action just above rollback fails or if any of the actions below the Rollback fails.
Article here (http://www.incyclesoftware.com/2014/03/understanding-rollbacks-release-management/) clearly explains how Rollback and Rollback
Always work.
I think you come across this issue since you are using build to do the "code deployment" action. You should use the release template to do that.
As far as I know you cannot use Rollback to achieve condition check (App pool exist in your case) action.
For this you can create your own Power Shell component (which checks if the app pool exist and is not create it) and add it as a tool in RM server (RM Server Inventory).
Another option is you can follow the workaround in below thread "Answer" quoted below. That is execute Remove app pool regardless if it exist or not (which does not fail) and then create app pool.
I was able to get it working by removing the app pool which does not fail if it doesn't exist. Removing then creating seems the long way around but it works.
Flow:
Remove Application Pool
Create Application Pool
https://social.msdn.microsoft.com/Forums/en-US/43bf21c8-e233-4e58-a5a8-2592b78bc466/vs-2013-release-management-create-application-pool-fails-if-it-already-exists?forum=tfsbuild
Cheers!
Chaminda

Release Management questions

Similar Messages

Maybe you are looking for