In Spyder one can save the workspace by clicking on an icon (save as...) in the variable explorer window. Does anybody know what the equiavalnt command for this operation is?
Related
When i use file parameter in jenkins job and select some file from network drive location , after clicking "Build" job is run twice. I just tried create "Dummy" job which only takes selected file and copy this particular file into my jenkins workspace. Same result. Job is always duplicated.
When i choose file from local drive , problem doesn't occurs.
Any suggestions ?\
Thanks in advance ...enter image description here
I have a Jenkins job that runs a build. If build finishes sucessfully, it create a folder in the network with the installer package (it is not located in Job's workspace).
Is there a away to add a link to this installer package folder?
I've tried using Description Setter Plugin and Rich text publisher, link appears but nothing happens when pressing it.
** With a custom HTML page it works.
I am having hard times attempting to perform the simplest operation: run the custom MSBuild script (placed within dedicated "BuildScripts" folder) from the Lab test running build definition. What it is supposed to do prior to test execution is to trigger the child build, get the built sources and perform the modification of the config file by the means of MSBuild script. And that is what I struggle with. Supposing I have specified the build scripts folder among source settings (mapped to $(SourceDir)) and I use the MSBuild activity for running the script, what do I specify in the path for project file location?
Would appreciate any hints you might share.
Thank you.
If I understand your requirement correctly, you can select the MSBuild script file in Build Process as soon as you have uploaded the file into Version Control.
Clicking the button below:
You will get a dialog to select the solution or project you want to build:
And then click "Add..." button, you will be able to select the file from Version Control.
Never heard the "MSBuild script". If you mean to run powershell script during the build. So where do you want to specify the path for project file ? In the script or the configuration of the build template ? Suggest you to provide a screenshot.
Moreover, you can use "invokeprocess" workflow activity to invoke powershell script during the build.
When creating a build definition, the "Build Defaults" section lets you specify the staging location for the build.
It has 3 options:
This build does not copy output files to a drop folder.
Copy build output to following drop folder (UNC Path, etc...)
Copy build out to the server.
My question is in regards to choosing option 3.
Where exactly does the ".zip" file get saved?? In the database? On the build server? Where can I see this file?
The files are stored in a unversioned store inside of TFS. The days is inside the SQL database so you will need to allocate the space there.
That's no idea but if you chhose 2nd option (copying to spefic folder) then you already know the path (server share path).
For the 3rd option though you can choose Download drop as zip button which will let you download the saved zip file from the server location.
This will be stored inside file container in TFS,we can access using this container programatically using TFS web API's
I am using an InvokeProcess activity in TFS 2010 to try and run the corflags application on a built exe.
C:\Builds\4\testing\Sources\BuildAssets\corflags.exe C:\Builds\4\testing\Binaries\Executable.exe /32bit+
However I am getting the following message:
corflags : error CF001 : Could not open file for writing
I am running the TFS Build Agent on my local machine because I am currently in a testing phase, and when I run the exact same command from the command line, the corflags application completes without error.
Any ideas would be greatly appreciated.
I'm not familiar with the specific situation but some general ideas:
Who is the build running as? Does that user have permissions to the output path?
Another consideration is: Has the build completed before it attempts to execute your command?
Try changing the command to be something really simple eg Type "OutputFile" - Does this hit the same issue? If so, it's a permission/timing issue. If not, it's the specific command - but at least we'll have narrowed the problem down.
I don't know the corflags either, but it is using a file in the workspace (a file that is downloaded from Version Control). There is a readonly flag on this file by default.
So if you need this file to be writable:
1) either checkout the file if you need this file in your version control and afterwards check it in again (tf checkout / tf checkin)
2) remove the file from version control if the file is created by the app
3) remove the readonly flag with the attrib command.