Create release scripts for rules_pkg_providers (#1028)

- create a new release_module workflow
  - takes subdir and version as args, default to `providers` for now. 
  - stole the buildifier technique we used in supply_chain
  - the code should work for toolchains if we split that.
- modify release_prep.sh to deal with old and new styles
- we need an ugly case statement because the release workflow we use
does not take the release_prep script name as a parameter.
   - ideally, I would do things from #1031, but that's less urgent.

Hand testing release_prep.sh seems to work. Testing the workflow is
nearly impossible until it exists the first time.

Next steps:
- verify it works
- figure out something for BCR releases.
- Hope for: https://github.com/bazel-contrib/publish-to-bcr/issues/368
- more pragmatic solution might be to have a shell script around the bcr
add-module script

Future work:
- generate git changelog on a per-subdir basis.
- allow better customization of release notes documentation link.
tree: 394a290540cfe630c25b0f290072c902eb3d868c
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. contrib/
  5. distro/
  6. doc_build/
  7. docs/
  8. examples/
  9. pkg/
  10. providers/
  11. tests/
  12. toolchains/
  13. .bazelignore
  14. .bazelrc
  15. .gitignore
  16. .pre-commit-config.yaml
  17. .typos.toml
  18. AUTHORS
  19. BUILD
  20. CHANGELOG.md
  21. CODEOWNERS
  22. CONTRIBUTING.md
  23. CONTRIBUTORS
  24. deps.bzl
  25. developers.md
  26. LICENSE
  27. mappings.bzl
  28. MODULE.bazel
  29. patching.md
  30. pkg.bzl
  31. README.md
  32. version.bzl
  33. WORKSPACE
  34. WORKSPACE.bzlmod
README.md

Bazel package building

Bazel rules for building tar, zip, deb, and rpm for packages.

For the latest version, see Releases (with WORKSPACE setup) / Documentation

Use rules-pkg-discuss@googlegroups.com for discussion.

CI: Build status

Basic rules

Package building rules

  • pkg - Rules for building packages of various types.
  • examples - Cookbook examples for using the rules.

As of Bazel 4.x, Bazel uses this rule set for packaging its distribution. Bazel still contains a limited version of pkg_tar but its feature set is frozen. Any new capabilities will be added here.

WORKSPACE setup

Sample, but see releases for the current release.

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "rules_pkg",
    urls = [
        "https://mirror.bazel.build/github.com/bazelbuild/rules_pkg/releases/download/0.9.1/rules_pkg-0.9.1.tar.gz",
        "https://github.com/bazelbuild/rules_pkg/releases/download/0.9.1/rules_pkg-0.9.1.tar.gz",
    ],
    sha256 = "8f9ee2dc10c1ae514ee599a8b42ed99fa262b757058f65ad3c384289ff70c4b8",
)
load("@rules_pkg//:deps.bzl", "rules_pkg_dependencies")
rules_pkg_dependencies()

To use pkg_rpm(), you must provide a copy of rpmbuild. You can use the system installed rpmbuild with this stanza.

load("@rules_pkg//toolchains/rpm:rpmbuild_configure.bzl", "find_system_rpmbuild")

find_system_rpmbuild(
    name = "rules_pkg_rpmbuild",
    verbose = False,
)

MODULE.bazel setup

bazel_dep(name = "rules_pkg", version = "0.0.10")

To use pkg_rpm(), you must provide a copy of rpmbuild. You can use the system installed rpmbuild with this stanza.

find_rpm = use_extension("//toolchains/rpm:rpmbuild_configure.bzl", "find_system_rpmbuild_bzlmod")
use_repo(find_rpm, "rules_pkg_rpmbuild")
register_toolchains("@rules_pkg_rpmbuild//:all")

For developers

We hold an engineering status meeting on the first Monday of every month at 10am USA East coast time. Add to calendar / meeting notes