Skip to content

Conversation

@crazy-max
Copy link
Member

@crazy-max crazy-max commented Feb 4, 2023

follow-up #3614

v0.11 is released so we can remove build information implementation on master branch.

tonistiigi

This comment was marked as outdated.

@crazy-max

This comment was marked as outdated.

@crazy-max crazy-max changed the title buildinfo: mark as deprecated remove buildinfo Feb 10, 2023
@tonistiigi

This comment was marked as outdated.

@crazy-max

This comment was marked as outdated.

@crazy-max crazy-max force-pushed the deprecate-buildinfo branch 2 times, most recently from 9f26b07 to 363767c Compare February 28, 2023 07:16
@crazy-max crazy-max marked this pull request as ready for review February 28, 2023 08:51
case keyOCITypes:
err = parseBoolWithDefault(&c.OCITypes, k, v, true)
case keyBuildInfo:
err = parseBoolWithDefault(&c.BuildInfo, k, v, true)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

buildinfo=false should be still valid for compatibility reason

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By "valid" you mean should not fail when exporting?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes

Copy link
Member Author

@crazy-max crazy-max Mar 10, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It does not afaik:

$ docker buildx build --output type=docker,buildinfo=false .
...
#34 [binaries-linux 4/4] COPY --link --from=buildkitd /usr/bin/buildkitd /
#34 merging 0.1s done
#34 DONE 0.2s

#35 [buildkit-linux 1/1] COPY --link --from=binaries / /usr/bin/
#35 DONE 0.2s

#36 exporting to docker image format
#36 exporting layers
#36 exporting layers 3.7s done
#36 exporting manifest sha256:26bff5cd69b2f771dad27d23b2c62c56377d6e8b91e4528b4af0f6bc9e4504e8 0.0s done
#36 exporting config sha256:e790b681a392ef3add1e375eda8fe35885ffb6ecd1f351dba3152169f7f22fdb 0.0s done
#36 sending tarball
#36 sending tarball 1.0s done
#36 DONE 4.7s

#37 importing to docker
#37 DONE 0.7s

See

default:
rest[k] = v
}

@crazy-max crazy-max force-pushed the deprecate-buildinfo branch from 363767c to 6d9c24d Compare March 10, 2023 09:03
Copy link
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SGTM, but not too familiar with this.

Do current versions print a warning if someone is using this?

@jedevc
Copy link
Member

jedevc commented Mar 13, 2023

r.e. warnings - there is no warning as of now. We could add a warning to the v0.11 release branch, but I'm not convinced it's worth it.

One of the main reasons for the removal of the feature is that not really anyone uses it AFAIK.

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

Successfully merging this pull request may close these issues.

5 participants