Just a quick update... Upon researching it further, it seems that modifying PSCall in this manner might be quite a bit complicated; not so much technically, but we'd have to balance with how PSExec works as well. Definitely something for us to consider as we work towards getting closer with PowerShell/DSC in the coming versions. The current thought is to add a new variatic variable function: PSEvalAsset(OptionalRaftName::AssetName[, arg.1..n]) This could return a scalar ($), vector (@), or map (@). Unfortunately there are no named arguments in OtterScript variable functions (unlike operations), but I think that's OK... hopefully assets will be very simple and not have a lot of arguments.

This is exactly what I was looking for, thank you!

We will implement this eventually once we have the specs nailed down. The plan is to offer a per-variable setting (in the same vein as the "sensitive" option) so it shouldn't break backwards compatibility.

You could look at the event log under Admin > Events and possibly see when/who deleted it, but there's no way to know "why" it was deleted. ProGet will not automatically delete package versions unless you specify that in a retention policy, or if they're removed from disk or database.

That makes much more sense! Thank you for the clarification. So I effectively do not need to specify targets in any of the Buildmaster actions that would require that information. Thanks for your help Tod

i'm afraid we won't be able to help with that; please consult with the BizTalk ESB team or forums.

I'll put a note in to add this to the next maintenance release this week.

Glad that worked! I created an issue for this; we should get this behavior a little more intuitive in an upcoming maintenance release.

Please note that this (or any multi-node) installation requires a ProGet Enterprise or ProGet Load Balanced License to be purchased. ProGet Basic and ProGet Free only permit a single server to be used in a single installation. That said, we recommend IIS because it's the easiest to support (by your own network admin team) and has many configuration options. In theory, you could probably use the integrated server. A HA configuration ought to use a SQL Cluster, otherwise you have a single point of failure.

Please see the ProGet feature comparison. There are no limits to the number of feeds.a

OK, I will upgrade to the latest version. It turns out the ProGet service wasn't running. I hadn't even realized it because the Web site and NuGet/NPM feeds were working normally. Starting the service was all that was needed to get those tasks running. Thanks

thanks we managed to find it as nuget was packing the release and debug files over the top of each other for some stupid reason in just the packages generated for this project. no idea why it did not affect any other solution on our build server

Great questions. a second Raft, that uses the same Git repo but a different branch? This was definitely something we considered when designing rafts... i.e. the ability to "promote" changes between environments. This is somewhat common in other IaC tools, such as Chef, where a cookbook is tied to a git repository. Some folks will use branches in this "promotion" manner. I was also thinking of having a second Otter Server instance for the pre-production environment This is fine; actually, our licensing model is designed for this. One instance of Otter managing pre-production servers (typically free), then the other instance managing production servers. Obviously you loose the unified visualization, but a lot of folks prefer having two totally different dashboards anyway. A lot of folks will also set up a second instance of Otter as more of a "Sandbox". It isn't to "test" the configuration plans, but more to test extensions, play around, try upgrades, etc. hope that helps.

Retention policies are available on paid versions of ProGet, so "ProGet Basic" and up; you can see current ProGet Pricing here.

Well... the error is a bit strange, because EnumerateFileSystemInfos is in fact a method on System.IO.DirectoryInfo. It's a core .NET class, so this error is "impossible" then... I'm wondering if there's an older version of powershell or .net on the server? There has to be some other difference between the servers I would think... You can trigger the RoutineServerChecker under Admin > Service. Hopefully you'll find some clues by running it repeatedly...

There is no way to configure that in the schedule, but you can somewhat accomplish this by either: setting the filter to "newest active release" and moving the release to the top on the Release Sequence page or, if you don't mind multiple failed builds in your release, setting the filter to "all releases" and filtering at the top of the build plan, e.g. if $CompareReleaseSequence(!=, $ReleaseNumber, $DesiredReleaseNumber) { Log-Information `$ReleaseNumber is $ReleaseNumber, skipping.; fail; }

Alana, I think it maybe a UTC boom... I will try today to "fiddler" it.

I see. Is it possible to leave a reminder of that limit on UI somehow? Like how many characters left that kind?

It is working :) Thank you Have a nice week-end Regards Philippe