R: Install a package directly from bitbucket

install_bitbucket {remotes} | R Documentation

## Install a package directly from bitbucket

### Description

This function is vectorised so you can install multiple packages in a single command.

### Usage

    install_bitbucket(repo, ref = "master", subdir = NULL,
      auth_user = bitbucket_user(), password = bitbucket_password(),
      host = "api.bitbucket.org/2.0", dependencies = NA,
      upgrade = c("ask", "always", "never"), force = FALSE,
      quiet = FALSE, build = TRUE, build_opts = c("--no-resave-data",
      "--no-manual", "--no-build-vignettes"), repos = getOption("repos"),
      type = getOption("pkgType"), ...)

### Arguments

`repo` | Repository address in the format `username/repo[/subdir][@ref|#pull]`. Alternatively, you can specify `subdir` and/or `ref` using the respective parameters (see below); if both is specified, the values in `repo` take precedence.
`ref` | Desired git reference; could be a commit, tag, or branch name. Defaults to master.
`subdir` | subdirectory within repo that contains the R package.
`auth_user` | your account username if you're attempting to install a package hosted in a private repository (and your username is different to `username`). Defaults to the `BITBUCKET_USER` environment variable.
`password` | your password. Defaults to the `BITBUCKET_PASSWORD` environment variable. See details for further information on setting up a password.
`host` | GitHub API host to use. Override with your GitHub enterprise hostname, for example, `"github.hostname.com/api/v3"`.
`dependencies` | Which dependencies do you want to check? Can be a character vector (selecting from "Depends", "Imports", "LinkingTo", "Suggests", or "Enhances"), or a logical vector. `TRUE` is shorthand for "Depends", "Imports", "LinkingTo" and "Suggests". `NA` is shorthand for "Depends", "Imports" and "LinkingTo" and is the default. `FALSE` is shorthand for no dependencies (i.e. just check this package, not its dependencies).
`upgrade` | One of "ask", "always" or "never". "ask" prompts the user for which out of date packages to upgrade. For non-interactive sessions "ask" is equivalent to "always". `TRUE` and `FALSE` are also accepted and correspond to "always" and "never" respectively.
`force` | Force installation, even if the remote state has not changed since the previous install.
`quiet` | If `TRUE`, suppress output.
`build` | If `TRUE` build the package before installing.
`build_opts` | Options to pass to `R CMD build`, only used when `build` is `TRUE`.
`repos` | A character vector giving repositories to use.
`type` | Type of package to `update`.
`...` | Other arguments passed on to `utils::install.packages()`.

### Details

To install from a private repo, or more generally, access the Bitbucket API with your own credentials, you will need to get an access token. You can create an access token following the instructions found in the Bitbucket App Passwords documentation. The App Password requires read-only access to your repositories and pull requests. Then store your password in the environment variable `BITBUCKET_PASSWORD` (e.g. `evelynwaugh:swordofhonour`)

### See Also

Bitbucket API docs: https://confluence.atlassian.com/bitbucket/use-the-bitbucket-cloud-rest-apis-222724129.html

Other package installation: `install_bioc`, `install_cran`, `install_dev`, `install_github`, `install_gitlab`, `install_git`, `install_local`, `install_svn`, `install_url`, `install_version`

### Examples

    ## Not run:
    install_bitbucket("sulab/mygene.r@default")
    install_bitbucket("dannavarro/lsr-package")

    ## End(Not run)

[Package remotes version 2.0.1 Index]