Is that possible to have a feature to backup all working copy files to another directory instead of manually copy one-by-one myself?
yes you can...you can set-up a cron job
from your server.
Are you looking for an export?
Related
I have one azure pipeline with two different stages.
The problem is, i have to include one directory for one stage and exclude the same directory for another stage. I need only one pipeline and I am trying to solve it it somehow.
Is there any ways of solving this ? Maybe some other technics ?
Thanks in response.
Is there a way to include and execute same directory in one pipeline?
The folder is the default git checkout location for Azure pipelines.
Checkout path
There no way to include and execute the directory.
But, you could use the copy task to move and delete the folder out of the folder if needed:
Copy Files task
Delete Files task
I have a pipeline that deploys code to an IIS folder on an on-premise server. I'm trying to figure out how to best delete old release folders. I'm not seeing anything obvious within DevOps.
Is there a native way of doing this? Or should I roll my own PowerShell script to delete old releases?
Is there a native way of doing this?
Yes, of course there is.
Open your deploy task, go Advanced Deployment Options and then enable the option Remove Additional Files at Destination
Noted: This "delete" operation I mentioned is not mean that clear all the files in local IIS folder. It just delete the files at the destination where there's no corresponding file in the package which is being deployed.
In one word, for some files which same with previous, it will be override as the latest files. And, for any left over files from a previous deployment that are no longer required, they will be deleted.
If you do not trust this option and want to clear the previous files completely, you can also add the Powershell task before IIS manage task and run delete script.
Here is the sample script to delete local files:
Remove-Item -Path "D:\Websites2\*"
You can replace "D:\Websites2\*" as your local website file path.
Hi I am trying to write a batch script that copies same set of configuration files from one application in depot to another application (trigger for copying those files once checked into first application). The idea in my mind is:
Add files from first application to client using p4 add
use p4 copy
p4 submit
Is this the right approach? Please help. Please provide any sample scripts available.
After trying for sometime, I was able to figure it out. The method I used is
create a new workspace
sync the files to workspace
copy the files using p4 copy and
submit the changes.
I am writing a build script that gets all the source code for a particular changelist and builds it. I would like to be able to run the script at any time, without having to shelve local changes or move files to a temporary location. The script will be used by others who have their own workspaces defined.
I thought it would be easiest just to get all the source code from Perforce at a temporary location and build from there. Unfortunately p4 sync does not seem to support this, it will only put files into the client view as specified by the workspace, meaning it would overwrite local changes before I could copy the files to the temporary location.
Is there any way to use p4 to copy files from Perforce into an arbitrary location?
You could create a dedicated workspace for the build script and then have the build script sync to it by using
p4 -c [workspace name] sync [depot path]
This is what a continuous build system would typically do. Be sure to blank out the Host: section of the workspace spec in this case so that it can be used on multiple systems.
An alternative might be to use p4 print with the -o option to dump the files to an arbitrary location without syncing them.
P4 sync can be done only to a client spec. Possibly, you need to create another client spec and sync to that client spec.
I was wondering if there is any way to make a copy of an existing web.config file(rename the newly created file) with the nant build.
Nant Task Reference
If all you want to do is a copy, then the copy task is your friend.