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!

    Build fails in release pipeline

    Scheduled Pinned Locked Moved Support
    3 Posts 2 Posters 8 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
      Justinvolved
      last edited by

      Hello,

      I have a build Script that succeeds when executed as just the script, but it fails as part of the release pipeline build step.

      When I execute just the script the log is: 5e13131a-cd6a-45bb-8bbb-ba618f011f01-image.png

      As part of the Build step in the release pipeline the log is:
      1eeca735-d9e7-4c62-a944-62be42a83085-image.png

      The difference is that the execute script uses the LocalAgent, and in the pipeline I have set the Agent to be an Inedo Agent installed on the local server.
      Do I need some additional configuration for the Agent?

      Thanks,

      Justin

      1 Reply Last reply Reply Quote 0
      • gdivisG Offline
        gdivis inedo-engineer
        last edited by

        Hi Justin,

        Looking at the error, I'm wondering if the directory is actually too long for git, and it's reporting the wrong error message. You could try changing the agent temp directory in the %PROGRAMDATA%\Inedo\SharedConfig\InedoAgent.config file by adding a <BuildMasterRootPath> element to the configuration file with a shorter path like C:\Temp.

        However, if you just need to run on the local server, there's no reason not to just use the local agent instead - it can do everything the Inedo agent can do.

        -Greg

        1 Reply Last reply Reply Quote 0
        • J Offline
          Justinvolved
          last edited by

          Hey Greg,

          Thanks, changing to C:\Temp solved the issue indeed, so I guess the path was too long.
          I'm experimenting with the Inedo Agent to make sure I can scale up and not have everything tied to Localhost, seems that was a good call given these subtle differences :-)

          Cheers,
          Justin

          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