Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide an option to serialize DAG build-step execution #681

Closed
briandealwis opened this issue Jul 20, 2018 · 3 comments
Closed

Provide an option to serialize DAG build-step execution #681

briandealwis opened this issue Jul 20, 2018 · 3 comments
Milestone

Comments

@briandealwis
Copy link
Member

briandealwis commented Jul 20, 2018

Users hitting registry authentication/authorization issues find Jib's output text imply that the operations are completed.

[INFO] Retrieving registry credentials for registry.hub.docker.com...
[INFO] Getting base image gcr.io/distroless/java...
[INFO] Building dependencies layer…

For a good time: mvn jib:build -Dimage=foo/bar/baz and try to make sense of the result!

@TadCordle
Copy link
Contributor

@briandealwis Is there more to do on this issue or is it fixed by #682?

@briandealwis
Copy link
Member Author

I see that image push seems to push up the layers/blobs in parallel.

Jul 24, 2018 2:11:40 PM com.google.api.client.http.HttpRequest execute
CONFIG: -------------- REQUEST  --------------
HEAD https://quay.io/v2/briandealwis/jibtest/blobs/sha256:8f125ded1b483229a567e48eece98cc8867c2bee55fb73e9cd65ceecc448b7c7
Accept: 
Accept-Encoding: gzip
Authorization: <Not Logged>
User-Agent: jib 0.9.8-SNAPSHOT jib-maven-plugin Google-HTTP-Java-Client/1.23.0 (gzip)

Jul 24, 2018 2:11:40 PM com.google.api.client.http.HttpRequest execute
CONFIG: -------------- REQUEST  --------------
HEAD https://quay.io/v2/briandealwis/jibtest/blobs/sha256:a988b67f65865e95c004400d61fee34b39651fb3437fedf2e44c9d5f01ff1290
Accept: 
Accept-Encoding: gzip
Authorization: <Not Logged>
User-Agent: jib 0.9.8-SNAPSHOT jib-maven-plugin Google-HTTP-Java-Client/1.23.0 (gzip)

Jul 24, 2018 2:11:40 PM com.google.api.client.http.HttpRequest execute
CONFIG: -------------- REQUEST  --------------
HEAD https://quay.io/v2/briandealwis/jibtest/blobs/sha256:1ad24c91d38c2f3a908e16e428f6fb3d96c4743f0f65559e163b115ddaa521c9
Accept: 
Accept-Encoding: gzip
Authorization: <Not Logged>
User-Agent: jib 0.9.8-SNAPSHOT jib-maven-plugin Google-HTTP-Java-Client/1.23.0 (gzip)

Jul 24, 2018 2:11:40 PM com.google.api.client.http.HttpRequest execute
CONFIG: -------------- REQUEST  --------------
HEAD https://quay.io/v2/briandealwis/jibtest/blobs/sha256:2052c536956a5e02c60080e4e88cbbecddd2f65fb0ccfe015456b75cc77e6ea5
Accept: 
Accept-Encoding: gzip
Authorization: <Not Logged>
User-Agent: jib 0.9.8-SNAPSHOT jib-maven-plugin Google-HTTP-Java-Client/1.23.0 (gzip)

Jul 24, 2018 2:11:40 PM com.google.api.client.http.HttpRequest execute
CONFIG: -------------- REQUEST  --------------
HEAD https://quay.io/v2/briandealwis/jibtest/blobs/sha256:ba7c544469e514f1a9a4dec59ab640540d50992b288adbb34a1a63c45bf19a24
Accept: 
Accept-Encoding: gzip
Authorization: <Not Logged>
User-Agent: jib 0.9.8-SNAPSHOT jib-maven-plugin Google-HTTP-Java-Client/1.23.0 (gzip)

@briandealwis
Copy link
Member Author

I'm just trying it again and everything is serialized. Oh, I just discovered why: I used jibSerialize not jibSerialized (missing the d).

/me sighs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants