Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 2 of 2 for REQUIREMENTS_FILE_NAME (0.28 sec)

  1. ci/official/requirements_updater/BUILD.bazel

    load("@python//3.9:defs.bzl", compile_pip_requirements_3_9 = "compile_pip_requirements")
    load("@updater_config_repository//:updater_config_repository.bzl", "REQUIREMENTS_FILE_NAME")
    
    compile_pip_requirements_3_9(
        name = "requirements_3_9",
        extra_args = ["--allow-unsafe"],
        requirements_in = REQUIREMENTS_FILE_NAME,
        requirements_txt = "requirements_lock_3_9.txt",
    )
    
    compile_pip_requirements_3_10(
        name = "requirements_3_10",
    Plain Text
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Wed Mar 27 18:00:18 GMT 2024
    - 3K bytes
    - Viewed (2)
  2. ci/official/requirements_updater/README.md

    By default, the name of the base requirements file is `requirements.in`, but it
    can be set using the `REQUIREMENTS_FILE_NAME` variable. \
    For example:
    
    ```
    export REQUIREMENTS_FILE_NAME=my_requirements.in
    ```
    
    To specify the file via a Bazel command argument, use the following:
    
    ```
    --repo_env=REQUIREMENTS_FILE_NAME=my_requirements.in
    ```
    
    ### How to run the updater
    
    ```
    bash updater.sh
    ```
    
    Plain Text
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Tue Jan 23 02:14:00 GMT 2024
    - 3.9K bytes
    - Viewed (0)
Back to top