This is now in Admin > All Settings, under ReservationUrls

This was indeed removed from v5 for a variety of reasons, but we do plan to bring it back. It was very problematic to display this information on the web after connecting to it from an agent, etc.

Sure, that would solve the issue.

Alana, Might I suggest updating the documentation to state that. Currently it is specified for the Upload operation but not the other two.

Awesome Dean. Thanks for taking a look.

ah yes, sorry. I setup the creds a couple of months ago and forgot about that option. thanks.

The Feed Clean-up task, which is run from the service on a schedule you define in Admin > Tasks, will clean up these. if it's not happening according to that schedule, please ensure the service is running. You may want to restart the service. You can also manulaly trigger it too; if you do that, then it will clean up the missing packages right away.

In this case, you are pointing PRoGet to a SQL Server on a different machine. You will need to either use a different connection string (name/[assword), run proget service/web under a domain account and continue to use integrated auth, or allow connections from that machine in SQL Server (not recommended).

Hi Tod, Thank you! I'm never sure if I'm being helpful or just getting in the way. Just can't sit still long enough :).

This isn't an answer, but more information as to why the uninstaller might be failing. When I run these manual steps, I see an exception. > C:\BuildMaster\Service\bmservice.exe UninstallWeb C:\BuildMaster\Service\bmservice.exe : Error stopping service: Service INEDOBMWEBSRV was not found on computer '.'. At line:1 char:1 + C:\BuildMaster\Service\bmservice.exe UninstallWeb + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (Error stopping ...n computer '.'.:String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError Removing INEDOBMWEBSRV service... Unable to remove service: Object reference not set to an instance of an object. Service removed. I think maybe the uninstaller doesn't handle this situation and so stops in the middle?

Alana- looks like this one is actually on me, the reverse proxy was stopping the single quotes. But, the extra trailing slash is what causes the issue with Packages(), same as it does with the earlier problem. I have it sorted out now.

I was able to reproduce this, it only happens when a child environment is created for first time. The case is OTTER-121, and wil be resolved in a future maintenance release.

Unfortunately i'm not familiar enough with CakePHP to advise on how to stop the service non-interactively. I would perhaps suggest to modify the batch file to not look for an exit code? BuildMaster will basically just run whatever process you ask to, so the batch file is what's waiting...

Hello Thank you for the reply. I use OTTER for a few weeks now, So I have to understand the otter model :) I will apply my DSC in a classical way (start-DSCconfiguration script) Regards Philippe

For my requirement at hands, simply having an option to include the notes as free text would do, as we won't be putting too much rich formatting notes inside, simply a reference number. Similar with "Additional Options" in Deployment Execution Completed event listener, if we could provide a checkbox to include Notes in Approval Required event listener should be fine for now.

I've updated the proget plugin to support pipeline script. It hasn't had a lot of testing (PC died and haven't had a chance to fully rebuilt it yet) but the changes were minimal so should be fine. It's also built against the latest LTS of Jenkins so I hope that won't be an issue for you. I'm also trying to do the same with the BuildMaster plugin but that one is proving to be harder to do and I've had to raise an issue on the Jenkins mailing list.

Hi Philippe , I think i understand, but it's much easier to visualize :) Especially once we see your data. could you send a screenshot to us via support - at Inedo - dot com? And feel free to hilite the areas, etc. you suggest to improve.

Please disregard now. It's all working fine. Someone changed the issues I was seeing in Jira yesterday and moved them to another release, incorrectly, at about the same time I was viewing them. I got the legacy aspect figured out as well so all of future configs should be non-legacy. Thanks.