| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll-forward with fixes:
- Tests were missing for xzcat
- xz output was not supported
- bz2 input was missing declaration
--
MOS_MIGRATED_REVID=108325435
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
broke Speckle and Dataflow
*** Original change description ***
[docker] Print a clearer message when xzcat cannot be found and is needed
Also use the default shell env for docker deb files.
Fixes #611.
--
MOS_MIGRATED_REVID=108105646
|
|
|
|
|
|
|
|
|
| |
Also use the default shell env for docker deb files.
Fixes #611.
--
MOS_MIGRATED_REVID=108035989
|
|
|
|
|
|
|
|
| |
* It enables tar packages to be placed at "/usr/local", say, and removes
the need for the current workaround of repackaging the original tars.
--
MOS_MIGRATED_REVID=107983091
|
|
|
|
|
|
|
| |
Fixes #604.
--
MOS_MIGRATED_REVID=107972542
|
|
|
|
|
|
|
| |
Fixes #603.
--
MOS_MIGRATED_REVID=107959662
|
|
|
|
|
|
|
| |
Fixes #618.
--
MOS_MIGRATED_REVID=107957576
|
|
|
|
|
|
|
| |
This is a fallout of https://bazel-review.googlesource.com/#/c/2212/
--
MOS_MIGRATED_REVID=107496707
|
|
|
|
|
|
|
| |
external site.
--
MOS_MIGRATED_REVID=106135529
|
|
|
|
|
|
|
|
|
|
|
| |
This refactor a bit the docker rules to reuse the tarball construction.
Also introduce the debian archive for the release process.
RELNOTES[NEW]: Debian and tar packaging is now supported
(see tools/build_defs/pkg/README.md).
--
MOS_MIGRATED_REVID=105053604
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Incremental build and load of Docker layers
Previously we were always tar-ing all the layers in the final image.
This change does not build the full image except if required. It instead
only builds the concerned layer and a loader that loads all the layers
that were not previously loaded in your local registry.
This is somewhat incompatible with the previous version since the full
tar file is not built anymore if not explicitly requested.
See https://goo.gl/P6CVyG for an extensive comparison of this change.
RELNOTES: [docker_build] incremental loading is default now.
Specify explicitly //package:target.tar (with the .tar extension)
to obtain the full image.
--
MOS_MIGRATED_REVID=104844423
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke internal builds
--
MOS_MIGRATED_REVID=104801084
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously we were always tar all the layers in the final image.
This change do not build the full image except if required. It instead
only build the concerned layer and a loader that loads all the layer
that were not previously loaded in your local registry.
This is somewhat incompatible with the previous version since the full
tar file is no more build if not explicitely requested.
RELNOTES: [docker_build] incremental loading is default now.
Specify explicitly //package:target.tar (with the .tar extension)
to obtain the full image.
--
Change-Id: I75c96d819f2a0f7c9444723b04b660b4939350ec
Reviewed-on: https://bazel-review.googlesource.com/#/c/1820/
MOS_MIGRATED_REVID=104737560
|
|
|
|
|
|
|
|
| |
This ensure to correctly detect duplicate for directory entries
that might or might not contains ending slash.
--
MOS_MIGRATED_REVID=104502468
|
|
|
|
|
|
|
|
| |
This attribute specifies the default repository for the generated
image.
--
MOS_MIGRATED_REVID=104408398
|
|
|
|
|
|
|
|
|
|
| |
Before this change, adding a directory might leads to non-executable
directory if the mode is set to non-executable. This is never a
desirable behavior. This enforce the executbale bit when the read
bit is on for directory.
--
MOS_MIGRATED_REVID=104276003
|
|
|
|
|
|
|
|
|
|
|
|
| |
The workdir attribute set the initial working directory
when starting the docker container.
Contrary to the WORKDIR directive (see
https://docs.docker.com/reference/builder/#workdir), it only affects
the entry point.
--
MOS_MIGRATED_REVID=104201472
|
|
|
|
|
|
|
|
|
|
|
| |
The headers were modified with
`find . -type f -exec 'sed' '-Ei' 's|Copyright 201([45]) Google|Copyright 201\1 The Bazel Authors|' '{}' ';'`
And manual edit for not Google owned copyright. Because of the nature of ijar, I did not modified the header of file owned by Alan Donovan.
The list of authors were extracted from the git log. It is missing older Google contributors that can be added on-demand.
--
MOS_MIGRATED_REVID=103938715
|
|
|
|
|
|
|
| |
Previously, dotted files were though of having the './' prefix.
--
MOS_MIGRATED_REVID=103864015
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=103745334
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also adds a `mode` attribute to docker_build so you can specify the mode
you prefer.
RELNOTES: [docker] docker_build now set the permission to 0555 to files
added to the layer, use `mode = "0644"` to use the legacy
behavior.
--
MOS_MIGRATED_REVID=103743458
|
|
|
|
|
|
|
|
|
|
| |
This was not making any sense since the uid/gid in tar files should be correct
not like when importing a file from the exec root.
Due to that behavior, the tests were broken when using sandboxing in Bazel.
--
MOS_MIGRATED_REVID=103741843
|
|
|
|
|
|
|
|
|
|
|
|
| |
By default all input files path are taken relatively to their
declared package and no more relatively to the docker_build
package.
The old behavior can be restored by specifying `data_path = "."`
as an attribute of the docker_build target.
--
MOS_MIGRATED_REVID=103731161
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=103527154
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=103451349
|
|
|
|
|
|
| |
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/455
MOS_MIGRATED_REVID=103068929
|
|
|
|
|
|
|
| |
A lot of build rules weren't shiped in the Bazel binary because of those missing filegroups
--
MOS_MIGRATED_REVID=102223626
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some debs file actually does use the LZMA compression and reading
that format requires python 3. Backports of LZMA to python 2 are
using native deps which might be hard for the user to setup and
our support of python 3 is not really functional (it needs 2to3
to use gflags for instance). Until we fix Bazel's python 3 support,
we shell out to xzcat for supporting LZMA compressed file.
Also added test for the archive library. These tests shows some
wrong handling in the AR format padding, fixed.
--
MOS_MIGRATED_REVID=100474498
|
|
|
|
|
|
|
|
|
| |
Image generated by docker build might put "null" as entry
value in the JSON metadata. Ignore those value when doing
the deep copy to avoid error on assigning to "NoneType".
--
MOS_MIGRATED_REVID=100145909
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=100125974
|
|
|
|
|
|
|
|
| |
Before the leading slash were not striped before appending the
path prefix, leading to a double slash at that point.
--
MOS_MIGRATED_REVID=99807605
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the file is generated, by a genrule for instance, then
the stripping of the prefix was incorrect because the used path
was containing 'bazel-out/...' prefix. This change moved the prefix
stripping to the Skylark rule so we can use "short_path".
Also fix the test paths.
Tested by bazel test //tools/build_defs/docker:build_test.
--
Change-Id: Ia3eb98268505002bade1f6b0dd916e1a9767a530
Reviewed-on: https://bazel-review.googlesource.com/1770
MOS_MIGRATED_REVID=99710676
|
|
|
|
|
|
|
|
|
|
| |
Docker pulled image do not have the 'top' file but does have a one entry
repositories files. To enable using them as input to the docker_build rule,
we read the repositories file if no 'top' file is present and use the first
declared image as the parent name.
--
MOS_MIGRATED_REVID=99181235
|
|
|
|
|
|
|
| |
s/package/packages/
--
MOS_MIGRATED_REVID=99175780
|
|
docker_build is a Skylark rule that describe a docker image. You can
replace Dockerfile by a docker_build to use Bazel's incrementality model.
--
MOS_MIGRATED_REVID=99160762
|