[build] Generate ironbank docker context#89933
Conversation
|
Pinging @elastic/kibana-operations (Team:Operations) |
|
A heads up, some of the files were changed to use what they call a hardening manifest file. That work was done in https://repo1.dso.mil/dsop/elastic/kibana/kibana/-/merge_requests/35/diffs Additionally, there are changes in https://repo1.dso.mil/dsop/elastic/kibana/kibana/-/merge_requests/38 to bring us closer in-line with the our Dockerfile. With this, I think we might be able to use a single Dockerfile. For example, I think it's worth adding the HEALTHCHECK to our Dockerfile. |
|
@elasticmachine merge upstream (should include docker contexts in the upload report now) |
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
⏳ Build in-progress, with failures
Failed CI StepsHistory
To update your PR or re-run it, just comment with: |
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
* [build] Generate ironbank docker context * replace download.json with hardening_manifest.yml * update dockerfile * rm jenkinsfile Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
|
7.x: 6d0fff8 |
This adds the source files and build steps for generating the docker Ironbank context. The output can be found in
target/kibana-ironbank-8.0.0-SNAPSHOT-docker-build-context.tar.gzafter runningyarn build.