Downloaded and installed Oracle Extenstion 4.1.1 without any errors. Sincere thanks! I will begin to setup an Oracle db deploy and test the results. Thanks again, Dan.

Hi, Thanks for the bug report; this will be addressed in the next release of ProGet, which is due in just a few days!

Thank you for posting the action log. When extracting the zip file, the deploy artifact action attempts to run the unzip program, is that program available on the server? Based on the log above, the exact command is: unzip -o "/home/dmccaffr/_A3/_S4/TMP/[artifactName].zip" -d "/home/dmccaffr" An IOException is thrown if the exit status returned is not equal to 0. Can you verify that running that command on the server above actually unzips the artifact, and that its exit code is 0?

Hello, that cryptic message means that the RENAME FILES action does not yet work with the SSH-based agent. Your best bet is to write a simple shell script that can do the same.

Decided to go with the embedded version, install worked fine, I'll revisit this once I move out of testing mode and perhaps we can figure out what the issue is. Thanks! D

Yes, it's from the Dummy extension. When I click the "Add Server" button on the Servers page, it lets me choose an agent type -- self-hosted, IIS-hosted, SSH-based, or Dummy Agent. I was hoping to use dummy servers as stand-ins for real servers that don't (yet) exist so I could create my deployment plan before the servers exist. Then, once they exist, I would just point the deployment steps to the real servers.

What happens if you put the name of a specific artifact? If it were broken, it would be a problem with the extension (which can be easily fixed and published for download pretty quickly). The source code for this particular action is here: https://github.com/Inedo/bmx-jenkins/blob/master/GetArtifactAction.cs

I must be missing something here, but if you remove the View Only privilege to download packages, you should be forbidden from downloading packages... Are you saying you removed your View Only privileges, or that you removed them from the Anonymous User such that it has no privileges? If it's the latter, can you send a Fiddler trace containing the requests that Visual Studio extension is attempting to send?

The service does need to be running mainly to index packages. If you selected the IIS option during install, the web server in the service will not run. If you are switching from integrated web server to IIS, make sure to update the service's .exe arguments to exclude the /urls argument and then the web server component of the service will not run.

This sound like it's just a tough process to model. No matter what you do, you can't have it both ways such that you could deploy to either a subset of DevX servers to an arbitrary subset of QAX servers. The options you'll have to decide on are either: use different workflows and different environments to separate Dev1 from Dev2, which will force releases to use a specific set of servers after a build is created for it use abstract environments (Dev, QA) with server variables that resolve to different server groups (e.g. DevSet1, DevSet2, or whatever), and select the result either at release, build, or promotion time so it provides historical context with the release/build In BuildMaster, the idea of an Environment (i.e. a different stage of testing) is meant to be abstracted from a Server (i.e. a physical/virtual machine), so whatever follows most closely to this paradigm would be the way to go.

Thanks for the report - this should be fixed on the server end now, and you should be able to see the release notes on your end.

No, the URL triggered builds are designed to be "fire and forget". However, even without a quiet period, the builds are still queued in a sense that they will not run over the top of themselves until the previous one is completed.

The extension bundles a version of svn.exe, and you can actually find it in and run it from the {BuildMasterInstallDir}\_WEBTMP\ExtTemp\Subversion\Resources\ directory. The command that it runs to validate a connection to a SVN repo is: svn.exe info http://inedo-test-project.googlecode.com/svn/trunk --xml --non-interactive --trust-server-cert [--username xxxx] [--password xxxx] Try that and see what happens when you run it.

I didn't run it as an admin, but I think it popped up the UAC prompt. Also, it managed to delete most of the contents of the proget directory in program files. Unfortunately, that's all the info I've got. Hope it helps you out.

The dependencies in BuildMaster don't quite work like, say, NuGet dependencies or something. It's more meant for sharing artifacts and the like. But, check out the "Create Build" or "Promote Build" actions.

There's no file verification per se as the mask is simply a string mask... there would be times where no matching is ideal - it all depends on the situation. If you wanted, you could log all the entries, it's part of the action's configuration.

Unfortunately at this point, we have no good examples of this sort of thing. You might be able to get away with inheriting from DirectoryPackageStore and extending its behavior on EnableChangeNotifications() to add your own FileSystemWatcher, but it all seems unnecessarily complicated when a simple scheduled task would do the trick.

It wasn't clear to me, from the UI, that I should be selecting the path to the solution file, rather than to the project. When I selected the solution file, the recipe proceeded to create a couple of problematic actions - "Subversion does not support the "Apply Label" operation. I think you're right - I'd be better served building up my deployments from scratch, rather than trying to use the recipes. The recipes seem to make assumptions that don't always fit, and it's easier to build your own than to figure out what they are doing that isn't working.

We have added this fix to our issue tracker as BM-1428. Keep an eye out on the release notes for it (not sure if it will be 4.1.8 or in 4.2.X when it first comes out).

We've made settings part of BuildMaster like that in the past (e.g. FormsAuthenticationTimeout). Since I'm not sure how we'll handle this particular setting in the future, you can set the value in machine.config for the time being. You can find the .config here: C:\Windows\Microsoft.NET\Framework[version]\config\machine.config