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!

    Deploy never ends

    Scheduled Pinned Locked Moved Support
    buildmaster
    4 Posts 1 Posters 2 Views
    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.
    • ? This user is from outside of this forum
      Guest
      last edited by

      Hey,

      I have a frustrating problem i'm having hard time understand.

      I have a pretty easy deployment plan, that creates a bat file that calls other bat files that are on the server already:

      this is bat file being created:

      call script1.bat           
      call script2.bat     
      call script3.bat        
      call script4.bat
      

      The next step is running this bat file.
      All the script are running perfectly fine. but when it finishes the last script (script4.bat) it's just stuck there. not doing anything for infinite time.

      I also added "Exit" command in the script4.bat script and yet it doesn't go back to the mother script and finished the deployment?

      Why? What am i doing wrong?

      Thanks.

      Product: BuildMaster
      Version: 4.9.6

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        There is nothing on BuildMaster's end that would be causing this to happen; to run the batch file, BuildMaster would simply just invoke a process (cmd.exe), which would then run the batch file. If that process never terminates, then the deployment would never terminate.

        Anything number of things can cause a process not to terminate, but the most common is halting to prompt for user input... either via command line or a window that pops up. This is not uncommon in automation systems, because the server has a different environment context or configuration than your workstation.

        More generally, you should consider using PowerShell instead of DOS/BATCH.

        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          Hey Alana, thanks for the answer.

          Is there a chance it happend because the job hasn't been promoted to the next environment?

          I created another env and ask to promote automatically.

          but what if i don't want to have another env? just get success or error?

          Thanks.

          1 Reply Last reply Reply Quote 0
          • ? This user is from outside of this forum
            Guest
            last edited by

            That shouldn't cause a problem.

            But you can verify it by disabling the group with your batch file calling, and then replace it with the sleep action,

            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