[JIRA] (JENKINS-54358) AWS flavor got broken by a wrong update

[email protected] (JIRA) Tue, 30 Oct 2018 14:24:07 -0700

Title: Message Title

So the update from 134 to 135 failed:

 
                                                                cat updates.auditlog| jq .updateLevel | head
134
135
134
133
132
131
130
129
128
127
  
                                                            

So first interesting thing (just retrieved the full json from UL 134 and 135 using ~~INFRA-1769~~, yey!):

Despite the only difference between the metrics plugin:

 
                                                                evergreen_prod=> select commit from updates where id=135;
                  commit
------------------------------------------
 6bffe54dc7265b90e714da21f1cb248e1e2f2319
(1 row)
 
                                                            

 
                                                                $ diff ul134.json ul135.json
2c2
<   "timestamp": 1540568443089,
---
>   "timestamp": 1540570564042,
624,625c624,625
<       "version": "4.0.2.2",
<       "url": "https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/metrics/4.0.2.2/metrics-4.0.2.2.hpi",
---
>       "version": "4.0.2.3-rc229.d9b0eb3c576d",
>       "url": "https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/metrics/4.0.2.3-rc229.d9b0eb3c576d/metrics-4.0.2.3-rc229.d9b0eb3c576d.hpi",
628c628
<         "signature": "b60b49ab946cd8b960f999876b7da880fadf9ca07dd9524f9f0af63a5d0342eb"
---
>         "signature": "1c1b95da5a0131a1af73ca81d90e4135ee3d05919a7382cc0c4f8195c9133aba"
 
                                                            

Here is what was served by the backend to the instance for this update:

(as we can see, the part about metrics plugin is correct, but there's an chunk about EC2 and aws-java-sdk that shouldn't be here to be analyzed)

 
                                                                {
  "timestamp": "2018-10-29T14:31:30.363Z",
  "updateLevel": 135,
  "manifest": {
    "meta": {
      "channel": "general",
      "level": 135
    },
    "core": {},
    "plugins": {
      "updates": [
        {
          "url": "https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/metrics/4.0.2.3-rc229.d9b0eb3c576d/metrics-4.0.2.3-rc229.d9b0eb3c576d.hpi",
          "artifactId": "metrics",
          "checksum": {
            "type": "sha256",
            "signature": "1c1b95da5a0131a1af73ca81d90e4135ee3d05919a7382cc0c4f8195c9133aba"
          }
        },
        {
          "url": "https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/aws-java-sdk/1.11.341/aws-java-sdk-1.11.341.hpi",
          "artifactId": "aws-java-sdk",
          "checksum": {
            "type": "sha256",
            "signature": "ebe7cca7755dc020d138ef537a7bf7b61e3bbad41f7f0f6be4004917c0769238"
          }
        },
        {
          "url": "https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/ec2/1.39/ec2-1.39.hpi",
          "artifactId": "ec2",
          "checksum": {
            "type": "sha256",
            "signature": "fdd8670b1a71bcdacc5d7a358fa67fb8c44efc6f2ecc717d5e572c669934a0a7"
          }
        }
      ],
      "deletes": []
    }
  }
}
 
                                                            

Add Comment

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-54358) AWS flavor got broken by a wrong update

Reply via email to