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

@atripp Thanks for the reply! I've sent an email to Inedo Support.

Let me know if there is anything else you need me try.

Thanks!

Hello,

We are facing an issue with BuildMaster 6.1.27 where we cannot make any changes to a pipeline. The last change that was made to this pipeline was 6/8/2020. The full stack trace is below.

Stack trace: System.InvalidOperationException: Pipeline names must be unique by name and application.
at Inedo.BuildMaster.API.Pipelines.PipelinesImpl.UpdatePipeline(Pipeline pipeline, Int32 pipelineId, Nullable`1 active)
at Inedo.BuildMaster.API.Pipelines.PipelinesImpl.CreateOrUpdateGroupApproval(Int32 pipelineId, String stageName, GroupApproval approval, Nullable`1 index)
at Inedo.BuildMaster.Web.WebApplication.Pages.Pipelines.EditGroupApprovalPage.<>c__DisplayClass9_0.<CreateChildControls>b__0(Object s, EventArgs e)
at Inedo.Web.Controls.ButtonLinks.PostBackButtonLink.Inedo.Web.Controls.ISimpleAsyncPostControl.ProcessValidPostAsync()
at Inedo.Web.PageFree.SimplePageBase.<ProcessPostAsync>d__64.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Inedo.Web.PageFree.SimplePageBase.<ProcessPostAsync>d__64.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.Web.PageFree.SimplePageBase.<ProcessRequestAsync>d__47.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.TaskAsyncHelper.EndTask(IAsyncResult ar)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Any help would be much appreciated.

Thanks!

@atripp Hello! Thanks for the reply!

We have the firewalls on the servers in question turned off, so I wouldn't think that would be the issue.

We are using AES encryption for the agent connections. They seem to work fine for quite a while, then suddenly fall into the "Checking..." state after a random period of time. There doesn't seem to be any rhyme or reason as to why they start failing to connect. This started happening about a month ago, but we cannot figure out what might be causing the connection to drop.

Hello,

Just recently, we have been having agents fall into a "Checking..." state, which has caused issues with deployments. When checking the logs for the agents from the servers page, there are no errors listed. Similarly, we do not see anything listed in the event viewer on the machines themselves.

We did, however, notice an influx of the below error on the admin page:

System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
--- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.IO.Stream.ReadByte()
at Inedo.Agents.ServerConnection.<SendHandshakeAsync>d__15.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.Agents.InedoAgentClientBase.<ConnectAsync>d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Inedo.BuildMaster.Windows.ServiceApplication.ServerCheckerRunner.<CheckAgentAsync>d__10.MoveNext()

All of the affected servers are running v46 of the InedoAgent, and are Windows 2008 or 2012R2. We are running v6.1.27 of BuildMaster

Any help would be appreciated.

Thanks!

Hello,

Is there any way to enable some form of version control for pipeline changes, or are the changes logged anywhere similar to how changes to config files are? We have multiple people managing pipelines, and it is very easy for someone to accidentally remove/change a variable that they shouldn't.

Thanks in advance!

@jrasch Awesome. Thanks for the swift reply!

If we have a retention policy in place for releases, do we need a completely separate policy to purge the orphaned artifacts, or can that be included in the same policy as the releases?

Excellent, thank you!

Hello,

We currently have a retention policy set up to purge all releases older than 20. There is also a policy to keep 365 days worth of build, execution, etc logs for audit's sake.

It is to my understanding that when BuildMaster purges the 21st release of an application, it will completely disregard that 365 day log policy, thus deleting any build, execution, etc. logs for that release, as well as all older releases.

Is this accurate?

Thanks!