FYI - that's the "Operation" for our Otter product, but the BuildMaster Action works about the same... But in either case you will need to have an agent installed in order to stop the app pool on that server. Alternatively, you could use powershell script to do it, but that would require additional ports and the like be open on the remote server (RPC, maybe?)

Hi Stephen, Although we don't offer reseller discounts, we are happy to (and often do!) work with any software reseller. If you have an approved reseller on your list, chances are they have already purchased from us before... and if not, we make it very easy. They can just submit a purchase order to us (or start by requesting a formal quote), and we will go from there. Does that help? best, Alana

Thanks. That would be great to, app to app, I am referring to within an app itself. But it sounds like both would be the same so that would be perfect. Looking forward to 5.

That shouldn't cause a problem. But you can verify it by disabling the group with your batch file calling, and then replace it with the sleep action,

Tod, Thanks very much for this piece of info and the source. Very useful. I've been able to do complete my extension, working all good!

Thanks Jon, I can how that was ambiguous! I've now updated it w/ more accurate info.

Although we do not provide a reseller discount, we do work with quite a few software resellers who purchase on behalf of their clients, as those clients prefer to have a single source for all procurement. If, as a reseller, you purchase directly from the MyInedo portal, just contact us with the end-user information, and we will update the licensing information. You can also submit a quote request as needed.

So I stand corrected. This just doesn't work for me. I have an application variable set for the BUILD scope, it's a string with the other variable of $MajorVersionNumber in it and it will never get expanded regardless of how I use it. Is this variable not available during Build? It's marked as a Release variable which I took to mean anytime during the entire process, build, deploy, etc.

That's great news ! Thank you for following up :)

update, I have found that after I have Deployed the app to our Development plan I can now see the links to the reports on the that build page. However they do not show under the Build plans results page which is where I would also expect them to appear. Still nothing showing on the applications Overview page either.

You could use a different workflow (or in v5, "pipelines" as they will be called)... and then have a different build importer/feed on each. Alternatively, you could not use the build importer, and just have a build step download the package and incorporate it as an artifact.

The Publish action (for NuGet extension v4.7.1) requires that the URL is entered into the action itself (Server URL property) or it uses whatever is in NuGet.config, it doesn't fall back to the server URL specified in the configurer.

Thanks Jon, I've added this as an issue -> https://github.com/Inedo/bmx-nuget/issues/14 We'll likely get this in v5, since we want to do some additional refactoring as well. And perhaps updagde the client version.

This would be very easy to do with a PowerShell script, so as an immediate solution, I'd suggest to do that. It'd also be very easy to patch/modify that particular action (CreateIisAppPoolAction.cs) That being said, this all applies to the "v4 execution engine", which will very soon be replaced with an indescribably better execution engine (the one that Otter currently uses). When we migrate the "v4 App Pool Action" to the "v5 App Pool Operation", it will basically look like the Ensure-AppPool Operation. So, as you continue to explore BuildMaster, do keep this in mind :) If you're doing server/infrastructure configuration (which, creating applications is definitely a part of), I'd strongly recommend looking at Otter as well!

Thanks, I'll add this as a feature request; there should be a link on the "perform manual action page" that links to the execution, but you can see all current executions on the home page dashboard.

Great! Thanks for the quick turnaround.

Yes, that's the directory used by the "local agent", for the buildmaster server.

Hi Mike, Apologies for the delay, but the problem is with the NuGet extension for BuildMaster. There is a new version (4.7.2) available that can be updated from within BuildMaster on the Admin > Extensions page.

thx for the guidance