{"push_id":4488454673,"size":1,"distinct_size":1,"ref":"refs/heads/image-name-output","head":"ee223b6ec28e35809147d603e079205170d3fb39","before":"2acec7d7fec15bb6b4eeb2be91a045007157f7e0","commits":[{"sha":"ee223b6ec28e35809147d603e079205170d3fb39","author":{"name":"Marc Bruggmann","email":"90946569598456f245d2eda5bb6f3ea6e0d4424d@spotify.com"},"message":"Optionally write out the image name to a file after build.\n\nIf the maven plugin is configured like so:\n```xml\n<configuration>\n  <to>\n    <image>gcr.io/some/path/to/image:tag</image>\n  </to>\n  <outputPaths>\n    <imageName>target/jib-image.name</imageName>\n  </outputPaths>\n</configuration>\n```\n\nThe jib-maven-plugin will create a file at that path with the\nimage name during the build, like so:\n```\n$ mvn jib:build\n...\n$ cat target/jib-image.name\ngcr.io/some/path/to/image:tag\n```\n\nThis is handy if you generate the image name or tag in a dynamic\nfashion (eg, including a timstamp) and you have other tools in a\nCD pipeline that operate on the generated image. In our case, we\nwould like to use the reference to the generated image to deploy to\nK8S, and our deployment tooling picks it up from a file.\n\nI have only implemented support in the maven plugin for now, since\nthat is what we are using and I'm not really familiar with Gradle.\nThat should be pretty straight-forward to add, if need be.\n\nWhen it comes to the implementation, I imitated how the image id\nand digests are written out, but happy to change as I'm not\nfamiliar with the codebase.","distinct":true,"url":"https://api.github.com/repos/mbruggmann/jib/commits/ee223b6ec28e35809147d603e079205170d3fb39"}]}
{"actor":{"display_login":"mbruggmann"}}