Topics created by jstarbird_7831

It looks like the Legacy Plan Importer currently does not support the ExecutionStatusPredicate and ReleaseStatusPredicate, which is throwing the error; we will fix this in a maintenace release, but as a work-around you can delete the predicate before converting.

Sorry for a late follow up on this. So one place where this solution falls apart is that your Jenkins add-on for BuildMaster does not support the meta-tags in the version field.

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

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.

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.

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.

Yes, in the new/v5 execution engine, we wrote a variable function called $EnvironmentVariable(name) that returns the machine environment variable. The current/v4 execution engine does not provide agent/server context in a variable function, so there's no way to write a variable function that executes on a remote machine.

Yes, that's correct; if your doing this with a custom extension, then you can use the "StoredProcs.Variables_CreateOrUpdateVariableDefinition" method directly, and pass null in where appropriate.

In the v5 plans (which we will ship in 4.9), you can have "output variables" from your powershell scripts. But currently, you can't communicate back to the BuildMAster execution engine via a script with anything but exit codes.

All fixed and I finally realized what I was doing wrong the admin password, need to learn where my uppercase characters go in passwords! Thanks, Jon