Hi, I have tested with npm and all is working now. Thanks very much. Regards Fabrice

Hi @mhull_0872, We just released the latest version of ProGet 5.2.26 on 2/28/2020 which includes the new Package Deployment API. You can learn more about the package deployment tracking feature here. We also have documentation on how to use the API endpoint here. Thanks, Rich

Thanks Alana, [EDO-2856] has been raised. Thanks, Clint

Release template values are currently only used by the user interface, as a means of assisting users enter key/value pairs (variables) for a release or package. They API does not reference these, but you can pass variables into the APi quite easily.

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...

Thanks for your response, Alana. Can you elaborate a little bit on the API commands you would leverage in this instance? I had considered that before, but I'd be curious to know how you'd approach this.

Hi Ryan, That's definitely unusual! There should definitely be a bunch of logs here, especially showing the exact SCM command-line command that was run. So, something quite unexpected is happening... What source control provider are you using? And also, what happens when you test connection? Can you share the configuration of the provider (a screenshot should be ok), you can send this to us at support - at Inedo dot com.

There have not been any updates that would have impacted this recently, or known issues like this. Unfortunately, there are a lot of things that can cause this, but one of the most common ones is one or more agents with a bad network connection. Because agent communication is pooled, and I/O is a bottleneck, often time one server is waiting for another to finish, sometime it can be difficult to tell which specific agents are causing the problem. The easiest way to find problem agents is this... Stop the BuildMaster service from the Web UI, then Start it You will see a bunch of "AgentUpdaterChecks" running simultaneously These should take seconds at most to complete Try to identify ones that are taking too long Once you've found agents that never seem to complete the check, stop the service, then disable those servers (Edit Server > Active) Go back to the beginning Once you isolate the servers, it should be relatively easy to find them out.

v3.3.11 has been released that should resolve this issue.

Thank you for the report - this will be fixed in the maintenance release coming out today (v3.1.1)

Looks like Chocolatey now requires the description field to have a value, whereas pre-v0.9.8 it did not require one. We've updated the editor for v3.1.1 to require a description, though this will not impact existing data, so you'd still have to edit existing descriptions so that they have a value.

Oddly, running the service in interactive mode seems to have solved the problem: the deployment is now complete. I didn't do anything but stop the service and start it interactively, and I didn't notice anything unusual in the output. It did look like it found the action and ran it, as far as I can tell, but didn't say what had been in the way.

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).

I believe this is a bug in NuGet; https://nuget.codeplex.com/workitem/4050 If not, I would suggest to do a fiddler trace to see specifically which url is failing,.

Thanks for the report, I've reproduced the behavior and logged it to be fixed in the next maintenance release.

do some timelapse macro lense work where a flweor starts as a bud, opens, and life falls from its grasp project it on glass as a video for an exhibition . sell the time lapse sequences to oxford scientific .. or get it in film and tv commercials or spiders spinning a web set the camera up on a tripod taking pictures as a sequence as the spider spins is web . maybe it rains in the footage maybe its always sunny . maybe the sun sets to be replaced by the moon, the spiders work continues at night till the break of the new day and the rising of a new sun new life .. time detail growth .

This feature was actually added in v4.0, just change the workflow properties to allow deployments to any environment.

Not currently; but you could use a combination of actions (Generate RElease Notes, SEnd Email) to accomplsih a similar effect.

I think I just figured it out. We have some unit tests running which are creating the GUID based XML file in question. I still have to do some more investigation.

Yes we do support other regions, we will file this as a bug targeted for the next release. Thank you for the report.