jQuery errors when a Code Deploy deployment is submitted

Issue #14978 resolved
Nathan Sepulveda
created an issue
  1. Go to any branch
  2. Click Deploy to AWS
  3. Select deployment group
  4. Click Submit
  5. Observe error in console. 500 Error:
POST /deployment?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJjb25uZWN0aW9uOjI4MzY5NSIsImlhdCI6MTUwNzU4NzkwNywicXNoIjoiMDQ0MWI1NmRjOThiZTAwN2RhMjZjNTU2MDMwMjgxZDZlYjljOGY3YjFhOTZkNmIwYjhiYTA2NjNkODAzMDRjZiIsImF1ZCI6ImNvbm5lY3Rpb246MjgzNjk1IiwiZXhwIjoxNTA3NTkxNTA3fQ.IAOsiv-QdiV9sF4EYxCvlmCEae_kbdpC6r7Evm5siZY&deployment_group=staging1&commit_like_id=dev-oct-9&repo_uuid={428c2228-f774-4ea0-912e-215cc57dae7b}&repo_url=http://bitbucket.org/labroots/website.git HTTP/1.1
Host: codedeploy.bitbucketconnect.com
Connection: keep-alive
Content-Length: 0
Accept: */*
Origin: https://codedeploy.bitbucketconnect.com
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
DNT: 1
Referer: https://codedeploy.bitbucketconnect.com/deploy?username=nsepulveda&idType=name&xdm_c=channel-bf38be22-a784-4e20-a7d5-b66610a52274&xdm_e=https%3A%2F%2Fbitbucket.org&crev=fb4dce18d19b&ui-params=eyJpc0RpYWxvZyI6IHRydWUsICJpc0lubGluZURpYWxvZyI6IGZhbHNlfQ%3D%3D&2=%7Bd222c4dd-2641-4658-b4d6-f08b4bc1638f%7D&commit_hash=5d306de506b4be8a0838afb970b2bc2b92ebe446&repo_url=http%3A%2F%2Fbitbucket.org%2Flabroots%2Fwebsite.git&repo_uuid=%7B428c2228-f774-4ea0-912e-215cc57dae7b%7D&type=branch&id=dev-oct-9&jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJjb25uZWN0aW9uOjI4MzY5NSIsImlhdCI6MTUwNzU4NzkwNywicXNoIjoiMDQ0MWI1NmRjOThiZTAwN2RhMjZjNTU2MDMwMjgxZDZlYjljOGY3YjFhOTZkNmIwYjhiYTA2NjNkODAzMDRjZiIsImF1ZCI6ImNvbm5lY3Rpb246MjgzNjk1IiwiZXhwIjoxNTA3NTkxNTA3fQ.IAOsiv-QdiV9sF4EYxCvlmCEae_kbdpC6r7Evm5siZY
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.8,ja;q=0.6

And also jQuery error:

Uncaught ReferenceError: e is not defined
    at Object.<anonymous> (deploy?username=nsepulveda&idType=name&xdm_c=channel-bf38be22-a784-4e20-a7d5-b66610a52274&xdm_e=https%3A%2F%2Fbitbucket.org&crev=fb4dce18d19b&ui-params=eyJpc0RpYWxvZyI6IHRydWUsICJpc0lubGluZURpYWxvZyI6IGZhbHNlfQ%3D%3D&2={d222c4dd-2641-4658-b4d6-f08b4bc1638f}&commit_hash=5d306de506b4be8a0838afb970b2bc2b92ebe446&repo_url=http%3A%2F%2Fbitbucket.org%2Flabroots%2Fwebsite.git&repo_uuid={428c2228-f774-4ea0-912e-215cc57dae7b}&type=branch&id=dev-oct-9&jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJjb25uZWN0aW9uOjI4MzY5NSIsImlhdCI6MTUwNzU4NzkwNywicXNoIjoiMDQ0MWI1NmRjOThiZTAwN2RhMjZjNTU2MDMwMjgxZDZlYjljOGY3YjFhOTZkNmIwYjhiYTA2NjNkODAzMDRjZiIsImF1ZCI6ImNvbm5lY3Rpb246MjgzNjk1IiwiZXhwIjoxNTA3NTkxNTA3fQ.IAOsiv-QdiV9sF4EYxCvlmCEae_kbdpC6r7Evm5siZY:135)
    at l (jquery.min.js:2)
    at Object.fireWith [as rejectWith] (jquery.min.js:2)
    at T (jquery.min.js:2)
    at XMLHttpRequest.r (jquery.min.js:2)

    (anonymous) @   deploy?username=nsepbdpC6r7Evm5siZY:135
l   @   jquery.min.js:2
fireWith    @   jquery.min.js:2
T   @   jquery.min.js:2
r   @   jquery.min.js:2
XMLHttpRequest.send (async)     
send    @   jquery.min.js:2
ajax    @   jquery.min.js:2
(anonymous) @   deploy?username=nsepbdpC6r7Evm5siZY:127
(anonymous) @   VM89:2
r   @   VM89:2
trigger @   VM89:2
dialogMessage   @   VM89:2
f   @   VM89:1
y   @   VM89:1
postMessage (async)     
r   @   connect-host.js?59e7:1807
i   @   connect-host.js?59e7:1827
(anonymous) @   connect-host.js?59e7:1940
(anonymous) @   connect-host.js?59e7:2981
dispatch    @   jquery.js:4435
g.handle    @   jquery.js:4121
trigger @   jquery.js:4350
e.event.trigger @   jquery-migrate.js:493
(anonymous) @   jquery.js:4901
each    @   jquery.js:374
each    @   jquery.js:139
trigger @   jquery.js:4900
r   @   connect-host.js?59e7:2598
(anonymous) @   connect-host.js?59e7:2604
dispatch    @   jquery.js:4435
g.handle    @   jquery.js:4121
n   @   raven.js?ae06:314

Official response

Comments (22)

  1. Thomas Kells staff

    We have a fix that we are currently validating on a small set of production servers. Once validation has passed we will deploy this fix to all servers. Assuming that the fix does pass validation on the first attempt we should be looking at a window of 1-2hrs from now. I will post further updates as we have them.

    Thanks,

    TJ

  2. Log in to comment