• Home
  • Raw
  • Download

Lines Matching +full:deploy +full:- +full:docs

9   * [Clang](https://clang.llvm.org/) 9.0+ (clang-cl on Windows)
11 * GCC (should work with `--repo_env=CC=gcc`, but is not tested)
15 The instructions below will assume that this binary is called `bazel` - Bazelisk is a thin wrapper …
25 $ bazel run //:jazzer -- <arguments>
34 Target //:jazzer_release up-to-date:
35 bazel-bin/jazzer_release.tar.gz
49 …ntegration test (`java_fuzz_target_test`), you can start Jazzer in debug mode via `--config=debug`.
58 Requires an account on [Sonatype](https://issues.sonatype.org) with access to the `com.code-intelli…
60 ### One-time setup
62 1. Install GPG prerequisites via `sudo apt-get install gnupg2 gnupg-agent scdaemon pcscd`.
63 2. Execute `mkdir -p ~/.gnupg && echo use-agent >> ~/.gnupg/gpg.conf` to enable GPG's smart card su…
64 3. Execute `cat deploy/maven.pub | gpg --import` to import the public key used for Maven signatures
65 4. Plug in the YubiKey and execute `gpg --card-status` to generate a key stub.
66 …If you see a `No such device` error, retry after executing `killall gpg-agent; killall pcscd` to r…
71 2. Create a release, using the auto-generated changelog as a base for the release notes.
73 …This builds release archives for GitHub as well as the multi-architecture jar for the `com.code-in…
75 5. Check out the tag locally and, with the YubiKey plugged in, run `bazel run //deploy` with the fo…
76 …* `JAZZER_JAR_PATH`: local path of the multi-architecture `jazzer.jar` contained in the `jazzer` a…
83 …docker/push_all.sh` to build and push the `cifuzz/jazzer` and `cifuzz/jazzer-autofuzz` Docker imag…
87 …telligencetesting.github.io/jazzer-docs, which is populated from https://github.com/CodeIntelligen…
89 To update the docs after a release with API changes, follow these steps to get properly linked cros…
91 1. Delete the contents of the `jazzer-api` subdirectory of `jazzer-docs`.
92 …un `bazel build --//deploy:linked_javadoc //deploy:jazzer-api-docs` and unpack the jar into the `j…
94 4. Repeat the same steps with `jazzer-api` replaced by `jazzer` and then by `jazzer-junit`.