indication that pipline may not have been triggered on new agent

Follow

Jason Duff

November 26, 2013 14:23

One of the issues we have is, when a new GO agent is added to the mix, knowing if a pipeline needs to be re-triggered in order to deploy to this new server/agent. The scenario is this: Say you have a pipeline that deploys artifacts (e.g. website) to a cluster of 4 load-balanced servers. Let's also suppose 1 of the servers is offline for maintenance when the pipeline trigger/deploy is exercised and so will not get the artifacts. When it comes back online, it will be out of sync with the other 3 servers and will in fact still contain the old artifacts which could obvioulsy be a serious issue. GO should provide some indication if all of the agents matching a given tag are indeed in sync with what is expected. All this information exists (e.g. last pipeline triggered on an agent, label, artifact set delivered...), just need an indication/alert that these are out of sync and need to be re-deployed. Thanks in advance.

0

• 

  Princy November 27, 2013 09:39

  Hi Jason

  Thank for the feedback. We will analyse this request and if we have further questions we will get back to you.

  Regards,

  Princy

  0

  Comment actions Permalink

Please sign in to leave a comment.