hbase/hbase-asyncfs/.blazar.yaml

# Note: this blazar yaml has been copied to all of the maven submodules (EXCEPT hbase-assembly) so
# that they can be properly configured. If you make changes to this, you will need to make sure all
# submodules are also updated accordingly. If you added a new submodule, you'll need to make sure
# it gets a copy of this .blazar.yaml. In either case, use copy_blazar_yaml.sh to copy to all
# subdirs containing a pom.xml.
# Make sure to also check hbase-assembly/.blazar.yaml to see if any changes should be added there as well.
# Prefer making changes to prepare_environment.sh instead, if possible.

buildpack:
  host: git.hubteam.com
  organization: HubSpotProtected
  repository: Blazar-Buildpack-Java
  branch: v2

before:
  - description: "Prepare build environment"
    commands:
      - $WORKSPACE/build-scripts/prepare_environment.sh
Add maven and RPM building in blazar This uses our standard buildpack, but each module must get a custom .blazar.yaml to pass in required properties to the build. One can distribute that .blazar.yaml using build-scripts/copy_blazar_yaml.sh. In order to minimize the duplication, most of the customizations are consolidated in build-scripts/prepare_environment.sh. The RPM build is hooked into the standard build hbase-assembly, as a post-build step. The RPM build scripts in hbase-assembly/rpm-build handle turning the assembled tar.gz into multiple RPMs. We required some minor changes to the descriptor in hbase-assembly to account for the fact that our build processes each module independently instead of as a single reactor build. As a result, moduleSet does not work, so moduleSet usages were converted to dependencySet. 2021-06-09 09:51:16 -04:00			`# Note: this blazar yaml has been copied to all of the maven submodules (EXCEPT hbase-assembly) so`
			`# that they can be properly configured. If you make changes to this, you will need to make sure all`
			`# submodules are also updated accordingly. If you added a new submodule, you'll need to make sure`
			`# it gets a copy of this .blazar.yaml. In either case, use copy_blazar_yaml.sh to copy to all`
			`# subdirs containing a pom.xml.`
			`# Make sure to also check hbase-assembly/.blazar.yaml to see if any changes should be added there as well.`
			`# Prefer making changes to prepare_environment.sh instead, if possible.`

			`buildpack:`
			`host: git.hubteam.com`
			`organization: HubSpotProtected`
			`repository: Blazar-Buildpack-Java`
			`branch: v2`

			`before:`
			`- description: "Prepare build environment"`
			`commands:`
			`- $WORKSPACE/build-scripts/prepare_environment.sh`