VIP Deploy Troubleshooting

Unknown
Unknown
edited February 2022 in Support Agents

I'm going to work on some training on this for everyone because VIP deploys are weird and we don't have the same deploy integration in teams that we had with slack.

The VIP self-deploy process is a bit weird and something that was built by Ops but supported by Product. In theory, we'll get better error messaging in it eventually. But things to try:

  • Get an idea of when the client deployed.
  • Note the release version on client's site
  • The PR the client is trying to deploy. If they can tell us what they're trying to change specifically, that's really helpful.
  • Check the site config - make sure VIP deploys are actually set up. You're looking for this:
X5f__D8NikrgHcOijdq4v0sQlvxjKcUouj_Z4pVoiH0znIyM9Y8pVLRPteMtoF6x4HC4lALk7bKcM3nUR8Jk2nmEErtOfib_syogFLRrT6Jd4Te9GpZ5UkqTR0TeucsqXNGs316v=s0
  • and
fHADRc9F71-RvE3BFhrkKV2_BW5-iTPx4FHWp_6v9Di5SoizxMHliG13ajpcEOD5tz0KQuhQa9aIRYVKIhNKqXVKFy6xAI6qvcD8iKNWYnAg1z2rJ4Kkq1y7F_BW1EsmrW5b7bSb=s0
  • That tells us that it's been enabled and what repo it's set to. If the PR the client wants is not in that repo, no change is going to happen.

Check the dev-deploy channel in slack and see if you can find the client's deploy attempt. It'd look something like this:

Xpog1eqUpuBfrGmYVvzBEpRwWTPVoIvL0i2eptyKcAeuuHu9a30M0SpZMX5vwNV9D8kY_Nb8B5exfLSBIC3GLV0NXHZHUuVacjqrkrkO9Xpj3B5rInMBwOoTYMN_1i8eLdeGbcrF=s0

Navigate to the VIP Code Deploy section (/settings/deploy). Note the repo being used (should align with what's in Config) and press the button again. It'll do a process.

ryX5S_7BkKMB04xOamv_4WIpiF01ixuk8zH_NGF1X4iEYKdATKKrOT2BXJojpqnUv3JN_pNOUTzRDJtLGrLJmptm7MM9OV_K6fwXOJNUhgZGp_qEgm3h5pmiWZ-dS-py0NKQIX3p=s0

This bit can take some time. If you still have slack access, you can check the #dev-deploys section and actually see that it was successful.

-WFFCKzzvy_WMzsRvARle4iHgQ_NXIfnQNxbGLW8L3i3HTnEZzn1zHscScbHlzYDVrC5QejdPwq93qlsa2Gwr566BtCWTMTq-lGm1Npk8FLNVFM33TMwQyr3mpLPpzpm1pMuLb4j=s0

(I'm hoping we can get that deploy notification channel in Teams).

- Once the package is pushed, see if you can work out if the expected change is there or not.

- If it's not, file the ticket with all this information so AppEng can investigate.


If we have someone that sends us a ticket every other day about a VIP deploy failing, we want to push back on them and help them test their PRs. There is a lot of power in the VIP Deploy, and it's the client's responsibility to test whatever they want to send out. Eduardo wrote a pretty great rundown on how to test PRs here (https://github.com/vanilla/support/issues/4684#issuecomment-881901844) - I've diplomatically reworded this to a few clients and I rarely see deploy failures from them now.


Additional reference on VIP Deploy: https://github.com/vanilla/dev-inter-ops/issues/93

Categories