github.com/abayer/test-infra@v0.0.5/prow/cmd/initupload/README.md (about)

     1  # `initupload`
     2  
     3  `initupload` reads clone records placed by `clonerefs` in order to determine job status. The status
     4  and logs from the clone operations are uploaded to cloud storage at a path resolved from the job
     5  configuration. This utility will exit with a non-zero exit code if the clone records indicate that
     6  any clone operations failed, as well as if any fatal errors are encountered in this utility itself.
     7  
     8  `initupload` can be configured by either passing in flags or by specifying a full set of options
     9  as JSON in the `$INITUPLOAD_OPTIONS` environment variable, which has the same form as that for
    10  `gcsupload`, plus the `"log"` field. See [that documentation](./../gcsupload/README.md) for
    11  an explanation.
    12  
    13  ```json
    14  {
    15      "log": "/logs/clone-log.txt",
    16      "bucket": "kubernetes-jenkins",
    17      "sub_dir": "",
    18      "items": [
    19          "/logs/artifacts/"
    20      ],
    21      "path_strategy": "legacy",
    22      "default_org": "kubernetes",
    23      "default_repo": "kubernetes",
    24      "gcs_credentials_file": "/secrets/gcs/service-account.json",
    25      "dry_run": "false"
    26  }
    27  ```
    28  
    29  In addition to this configuration for the tool, the `$JOB_SPEC` environment variable should be
    30  present to provide the contents of the Prow downward API for jobs. This data is used to resolve
    31  the exact location in GCS to which artifacts and logs will be pushed.