Topics created by Joseph.Saladino_7499

@atripp Thanks for the reply! I am not aware of any additional pipelines with that same name, but will do some digging and see if I can find it. Thanks for checking.

Hi @Joseph-Saladino_7499 , Hmm, that's really weird; the next thing I would try is to just restart all the machines (including the BuildMaster server). That's easy to do and the issue might go away. It could be a software error in the Windows networking stack It's possible that there's some intermediate network device that's interfering. Router, QoS device, etc. That's harder to diagnose, and would require some tracing ... starting by making sure that the RST packet is actually being received on the BuildMaster server (that's usually what indicates the error message), and then figuring out what device is sending it, and why. Our code doesn't work at the packet-level, but if the remote server (Inedo agent) is where the RST packets are coming from, it likely has to do with some obscure Windows setting... maybe even firmware on the network card. But at least something to look at. Cheers, Alana

Hi @Joseph-Saladino_7499, What version of BuildMaster are you currently running? In BuildMaster 6.2 there is a history on pipeline changes. You would view it by clicking on Deploy -> Deployment Pipelines and then clicking on the last modified date for the pipeline you would like to see history for. Here is a screenshot of the UI: Hope this helps! Thanks, Rich

@jrasch I tried creating a retention policy, like my attached screenshot. However, it deleted all of the artifacts in BuildMaster, not just orphaned ones. Is there a way to delete just the orphaned ones? We are using Version 5.8.3 (Build 7) of BuildMaster.