daml/extractor
gleber aa70c7f64e
Enforce consistent formatting of BUILD files. (#412)
* Add buildifier targets.

The tool allows to check and format BUILD files in the repo.

To check if files are well formatted, run:

    bazel run //:buildifier

To fix badly-formatted files run:

    bazel run //:buildifier-fix

* Cleanup dade-copyright-headers formatting.

* Fix dade-copyright-headers on files with just the copyright.

* Run buildifier automatically on CI via 'fmt.sh'.

* Reformat all BUILD files with buildifier.

Excludes autogenerated Bazel files.
2019-04-12 13:10:16 +02:00
..
bin open-sourcing daml 2019-04-04 09:33:38 +01:00
src Fix DAML runtime for the new DAML-LF type Map (#204) 2019-04-10 21:30:33 +02:00
.gitignore open-sourcing daml 2019-04-04 09:33:38 +01:00
BUILD.bazel Enforce consistent formatting of BUILD files. (#412) 2019-04-12 13:10:16 +02:00
README.md open-sourcing daml 2019-04-04 09:33:38 +01:00
UNRELEASED.md open-sourcing daml 2019-04-04 09:33:38 +01:00

Extractor

Build

The code uses SBT as a build system

sbt compile

To run the tests

sbt test

Release

  1. Create a branch extractor-release-<major>-<minor>-<point> for the release. Check the file ledger-tools/extractor/version.sbt. For example, let's say the the current version of the project is 0.9.3-SNAPSHOT. You need to create a branch called extractor-release-0-9-3;
  2. Move the ## Unreleased section of ledger-tools/extractor/UNRELEASED.md to the new release version you have created in ledger-tools/extractor/CHANGELOG.md and commit to that branch. The message of the commit is not important as it will be discarded;
  3. Run sbt release . This will ask for the release version and the next version, and will create commit with the release version and next version, and also takes care about tagging;
  4. Push your branch and tag:
git push origin release/extractor/0.9.3    # check the tag that has been created, and push it
git push -u origin extractor-release-0-9-3 # push your branch
  1. Go to the release Jenkins job Enter the tag you published and run the job.
  2. Create a Pull Request from your branch, have it reviewed and merged. After it's done, you can delete the branch.