{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":18605951,"defaultBranch":"master","name":"docker-custom-build-environment-plugin","ownerLogin":"jenkinsci","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2014-04-09T17:16:18.000Z","ownerAvatar":"https://github.com/avatars/u/107424?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1679537278.0","currentOid":""},"activityList":{"items":[{"before":"c3da4fa3e757e55ce78e3477d3e6f96b7ab865e2","after":"01d447eb9c4d308c7d9786b7b1b66533575ffaa0","ref":"refs/heads/master","pushedAt":"2023-07-30T23:26:27.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"jonhermansen","name":"Jon Hermansen","path":"/jonhermansen","primaryAvatarUrl":"https://github.com/avatars/u/660911?s=80&v=4"},"commit":{"message":"JENKINS-66171: Get built docker image ID using --iidfile (#82)\n\nPreviously we were capturing `docker build` output, which led to some problems:\r\n1. Other programs could print similar strings, which would match but did not\r\ncontain the image ID. This was fixed by taking the last capture as image ID.\r\n2. `docker build` output has changed in version 23, so now we'd have to match\r\nthe output twice. First pass for docker < 23, and another for >= 23\r\n\r\nDocker has had the `--iidfile` option for some time now, so switch to using it.\r\nIt is a much less fragile way to capture the image ID.\r\n\r\nTested with Docker 20.10.23 and 23.0.1\r\n\r\nCo-authored-by: Jon Hermansen <jon@jh86.org>","shortMessageHtmlLink":"JENKINS-66171: Get built docker image ID using --iidfile (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"1688862700\" data-permission-text=\"Title is private\" data-url=\"https://github.com/jenkinsci/docker-custom-build-environment-plugin/issues/82\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/jenkinsci/docker-custom-build-environment-plugin/pull/82/hovercard\" href=\"https://github.com/jenkinsci/docker-custom-build-environment-plugin/pull/82\">#82</a>)"}},{"before":null,"after":"fac2e9cff017bfd2d1d4a902d28daea645bb84fc","ref":"refs/heads/JENKINS-66171/fix-capturing-built-image-id-again","pushedAt":"2023-03-23T02:07:58.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"jonhermansen","name":"Jon Hermansen","path":"/jonhermansen","primaryAvatarUrl":"https://github.com/avatars/u/660911?s=80&v=4"},"commit":{"message":"JENKINS-66171: Get built docker image ID using --iidfile\n\nPreviously we were capturing `docker build` output, which led to some problems:\n1. Other programs could print similar strings, which would match but did not\ncontain the image ID. This was fixed by taking the last capture as image ID.\n2. `docker build` output has changed in version 23, so now we'd have to match\nthe output twice. First pass for docker < 23, and another for >= 23\n\nDocker has had the `--iidfile` option for some time now, so switch to using it.\nIt is a much less fragile way to capture the image ID.\n\nTested with Docker 20.10.23 and 23.0.1","shortMessageHtmlLink":"JENKINS-66171: Get built docker image ID using --iidfile"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAADYDi8UQA","startCursor":null,"endCursor":null}},"title":"Activity · jenkinsci/docker-custom-build-environment-plugin"}