Pipeline Stage doesn't run

Follow

Comments

6 comments

  • Avatar
    Manoj

    Hi Stephen,


    Are you saying that you had configured a stage as manual, then changed it to automatic?


    This will come into effect in the next run of the pipleine ( from the first stage ) . For any run of the pipeline before the change to automatic, you have to manually approve the stage.


    Also, if you rerun your second stage, it should automatically trigger the third stage when the second stage passes.


    Manoj

  • Avatar
    Scott, Stephen

    Hi Manoj,


    Sorry no I'm obviously not clear, I'm saying that in an attempt to diagnose the issue I set the 3rd stage from automatic to manual and reran the pipeline. I was still unable to approve the 3rd stage, so I've now gone back to automatic. 


    I've also restarted the go-agent as well as the server.


    This has only started since installing a 2nd agent on a different machne. I now have these agents allocated as resources and the pipelines using specific resources. This is the only pipeline out of 5 that run either on a schedule or on an svn commit that is having a problem.


     


    Steve

  • Avatar
    Scott, Stephen

    Well after trying all sort of things that would appear to be insignificant I've now got it working simply by changing the name of the stage from Deploy_and_restart to Deploy.


     


    Is there a maximum string length for a stage name?

  • Avatar
    Anush Ramani

    Hi Stephen,


    What version of Go are you using (found on the footer)?


    This sounds similar to an issue we saw with another customer. If you see this issue manifest again, do let us know. It appears to happen under some very specific scenarios.


    To answer your last question, there is a max length (255 chars), but that was definitely not an issue with your stage name.

  • Avatar
    Scott, Stephen

    Hi Anush,


    It's Go 2.2 with an evaluation copy of the Enterprise Licence.


    Steve

  • Avatar
    Anush Ramani

    Can you provide the full version string, including the build number please? Should look something like "2.2.0 (12345-1b3185eb05617c)".

Please sign in to leave a comment.