Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Pipeline names must be unique by name and application

    Scheduled Pinned Locked Moved Support
    6 Posts 2 Posters 9 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J Offline
      Joseph.Saladino_7499
      last edited by

      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!

      1 Reply Last reply Reply Quote 0
      • atrippA Offline
        atripp inedo-engineer
        last edited by

        Hi @Joseph-Saladino_7499 ,

        I think this may be specific to your pipeline data. You should be able to go to the pipeline in "edit view", and share us the JSON document.

        You can send that to support at inedo dot com with [QA-874] in the subject (so we can find it) , or also just you open a new ticket. If you do send to support email, please let us know on here that you sent it, since we don't regularly check that email.

        thanks,
        Alana

        J 1 Reply Last reply Reply Quote 0
        • J Offline
          Joseph.Saladino_7499 @atripp
          last edited by

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

          atrippA 1 Reply Last reply Reply Quote 0
          • atrippA Offline
            atripp inedo-engineer @Joseph.Saladino_7499
            last edited by

            Hi @Joseph-Saladino_7499 ,

            Thanks, received! We'll debug/investigate this today or tomorrow.

            Cheers,
            Alana

            atrippA 1 Reply Last reply Reply Quote 0
            • atrippA Offline
              atripp inedo-engineer @atripp
              last edited by

              Hi @Joseph-Saladino_7499 ,

              I wasn't able to reproduce the error using the UI, but I could figure out what's causing it and reproduce he error state using the API.

              Basically, you have two pipelines named "Standard «redacted» Service Pipeline". One pipeline may be global, one may be part of the application. But in any case, the validation logic is not allowing this to save because it detects a duplicate.

              To resolve this, delete one of the pipelines.

              Cheers,
              Alana

              J 1 Reply Last reply Reply Quote 0
              • J Offline
                Joseph.Saladino_7499 @atripp
                last edited by

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

                1 Reply Last reply Reply Quote 0

                Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                With your input, this post could be even better 💗

                Register Login
                • 1 / 1
                • First post
                  Last post
                Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation