Release-Management | Provides a suite of scripts | Continuous Deployment library

Given the scenario, you can do it multiple ways. One could be adding another play for repodownload role to your main playbook that runs only on localhost. Then remove delegate_to: localhost from the role tasks and move the variables accordingly.

How to take code backup in TFS 2015 during Release Management/Pipeline

Indeed, Backing up existing release code on the server is really a tricky issue, if your release server path differs with different an ID. It seems we have to create several task to back up release code from different release server path or we have to write the scripts(PS, Batch) to back up those release code.

To resolve this question, I would like provide a workaround, you can check if it works for you. The tasks would be:

1. Deploy build artifact to the server.
2. Use Copy task to back up the build artifact to the local folder of the TFS server machine with condition Only when all previous tasks have succeeded.
3. Deploy backup artifact to the server with condition Only when all previous tasks failed (Also check the option Clear Target Folder under the Advanced tab).

Some explanations for tasks 2 and task 3:

Task2: This steps is use to back up the release code of the last successful deployment, and save it to the local folder on the server.

Task3: This steps is used to deploy the back up the release code to overwrite the release code that failed to deploy before, if the previous deployment task failed.

Hope this helps.

To merge development branch into master branch in a VSTS release environment, you can achieve it by adding a PowerShell task. Details as below:

Add a PowerShell task with the script:

The documentation isn't clear on this point, and the developercommunity post is incorrect: https://developercommunity.visualstudio.com/content/problem/175267/release-environment-artifact-triggers-not-availabl.html

The comment below from @MarinaLiu-MSF confirms Environment Artifact Filters feature are not available for onsite TFS 2017 nor for the first release of onsite TFS 2018. To date, this functionality is only currently available in the online VSTS.

I found a post on the VisualStudio User Voice site that mentions it being available in the next major on-prem version: https://visualstudio.uservoice.com/forums/330519-visual-studio-team-services/suggestions/13413054-trigger-release-definition-only-for-specific-branc

ADMIN VSTS Team (Product group, Microsoft Visual Studio) responded · July 11, 2017 We are happy to let you know that your suggestion is now available on Team Services. It will become available to the on-prem version in the next major version of TFS. You can read more about it at https://www.visualstudio.com/en-us/docs/build/concepts/definitions/release/triggers#release-triggers

No.

The same answer I provided in the other answer applies here: Don't. Publish them as NuGet packages or as separate build artifacts; a release definition can have multiple artifacts linked to it.

Refer to this screenshot and check it:

Kind of a trivial thing, but it'll save you some $$$: the default-http-backend is not designed to be outside facing, and thus should not have type: LoadBalancer -- it is merely designed to 404 so the Ingress controller can universally /dev/null traffic for Pod-less Services.

Moving slightly up the triviality ladder, and for extreme clarity: I do not think what you have is wrong but I did want to offer you something to decide if you want to change. Typically the contract for a Pod's container is to give an ideally natural-language name to the port ("http", "https", "prometheus", whatever) that maps into the port of underlying image. And then, set targetPort: in the Service to that name and not the number which offers the container the ability to move the port number without breaking the Service-to-Pod contract. The nginx-ingress Deployment's container:ports: agrees with me on this one.

Now, let's get into the parts that may be contributing to your system not behaving as you wish.

I can't prove it right now, but the presence of containers:hostPort: is suspicious without hostNetwork: true. I'm genuinely surprised kubectl didn't whine, because those config combinations are a little weird.

I guess the troubleshooting step would be to get on the Node (that is, something within the cluster which is not a Pod -- you could do it with a separate VM within the same subnet as your Node, too, if you wish) and then curl to port 31452 of the Node upon which the nginx-ingress-controller Pod is running.

kubectl get nodes will list all available Nodes, and

kubectl get -o json pod nginx-ingress-controller-deployment-4106313651-v7p03 | jq -r '.items[0].status.hostIP' should produce the specific VM's IP address, if you don't already know it. Err, I just realized from your prompt you likely don't have jq -- but I don't know PowerShell well enough to know its JSON-querying syntax.

Then, from any Node: curl -v http://${that_host_IP_value}:31452 and see what materializes. It may be something, or it may be the same "wha?!" that the LoadBalancer is giving you.

As for the Ingress resource specifically, again default-http-backend is not supposed to have an Ingress resource -- I don't know if it hurts anything because I've never tried it, but I'd also bet $1 it is not helping your situation, either.

Since you already have a known working Service with default:webcms, I would recommend creating an Ingress resource in the default namespace with pretty much exactly what your current Ingress resource is, but pointed at webcms instead of default-http-backend. That way your Ingress controller will actually have something to target which isn't the default backend.

If you haven't already seen it, adding --v=2 will cause the Pod to emit the actual diff of its nginx config change, which can be unbelievably helpful in tracking down config misunderstandings

I'm so sorry that you're having to do battle with Azure, Ingress controllers, and rough-around-the-edges documentation for your first contact with Kubernetes. It really is amazing when you get all the things set up correctly, but it is a pretty complex piece of machinery, for sure.

I was able to figure out an answer for this issue. I am herewith sharing same for others reference.

If we don’t link an artifact(build definition), then the artifacts for the release/release definition will not be filled with the data, so we won’t be able to refer to the attachment that got uploaded as part of the build.

Hence as per current API implementation, Below are the steps to follow to achieve this requirenment.

• Writing data in to log while extension run as build task
• Read above data once build completes (in client side)
• Display retrieved (processed if required) data in release tab.

I found below code which explains retrieving data from log (reference : https://github.com/Dynatrace/Dynatrace-AppMon-TFS-Integration-Plugin/blob/master/src/enhancer/dynatrace-testautomation.ts)

The PowerShell execution in TFS Build and Release is only in non-interactive mode possible. The build and release process will only streams the execution result to the build console.

You have to create a variable with the username. For the password you should use hidden variable:

Yes you have to place the arguments inside the argument box of the PowerShell step

Note: The password field seems secure and not readable but it is not really hard to read the content of a hidden variable.

Create the variables and set the values. After that you can use this command line parameter in the PowerShell step argument box.