Docs CI Rework for Versioned Deploy

[stanbrub]

Added docs-ci-v2.yml to deploy to directory deephaven-core-v2, while docs-ci.yml remains unchanged.

• Pull request to for main
  • Build the docs
• Push to main
  • Build the docs
  • Upload artifacts to Github
  • Deploy docs to deephaven.io (e.g. ~/deephaven-core-v2/main)
• Push to release/v*
  • Set symlinks for latest (pointing to newest release dir)
  • Build the docs
  • Upload artifacts to Github
  • Deploy docs to release dir (e.g. ~/deephaven-core-v2/release/v0.30.0)

New Directory structure

• Paired down to include mostly docs directories
• deephaven-core-v2 is what's new

├── deephaven-core
│   ├── client-api
│   ├── javadoc
│   └── pydoc
├── deephaven-core-v2
│   ├── main
│   │   ├── client-api
│   │   ├── javadoc
│   │   └── pydoc
│   ├── release
│   │   ├── v0.30.0
│   │   │   ├── client-api
│   │   │   ├── javadoc
│   │   │   └── pydoc
│   │   └── v0.31.0
│   │   │  ├── client-api
│   │   │  ├── javadoc
│   │   │  └── pydoc
│   └── symlinks
│   │   ├── latest -> ../release/v0.31.0
│   │   └── next -> ../main
├── deephaven.io
│   ├── barrage
│   │   └── docs
│   ├── core
│   │   ├── docs
│   │   └── groovy
│   ├── enterprise
│   │   ├── docs
│   │   ├── jackson
│   │   ├── powell
│   │   ├── services
│   │   ├── silverheels
│   └── grid
        ├── How-to
        └── docs

[devinrsmith]

I did not audit the actual arguments to rsync, but we'll want other eyes to look in depth before we merge.

It would be good to see a tree of the proposed layout.

[dsmmcken]

What do these rsync options do?
-rlptDvz --force --mkpath

The rsync options you provided do the following:

-r: This option makes rsync perform a recursive directory transfer.
-l: This option makes rsync copy symbolic links as symbolic links.
-p: This option preserves file permissions.
-t: This option preserves modification times.
-D: This option is equivalent to --devices --specials, preserving devices and special files.
-v: This option increases verbosity. It causes rsync to give more information about what it's doing.
-z: This option compresses the data as it is sent to the destination machine, which reduces the amount of data being transmitted.
--force: This option forces deletion of directories even if not empty.
--mkpath: This option is not a standard rsync option. It might be specific to a certain version or variant of rsync.
Please note that I'm an AI programming assistant and my expertise is strictly limited to software development topics.

co-pilot seems to think --mkpath isn't an option, what does it do?

[stanbrub]

What do these rsync options do?
-rlptDvz --force --mkpath

The rsync options you provided do the following:
-r: This option makes rsync perform a recursive directory transfer.
-l: This option makes rsync copy symbolic links as symbolic links.
-p: This option preserves file permissions.
-t: This option preserves modification times.
-D: This option is equivalent to --devices --specials, preserving devices and special files.
-v: This option increases verbosity. It causes rsync to give more information about what it's doing.
-z: This option compresses the data as it is sent to the destination machine, which reduces the amount of data being transmitted.
--force: This option forces deletion of directories even if not empty.
--mkpath: This option is not a standard rsync option. It might be specific to a certain version or variant of rsync.
Please note that I'm an AI programming assistant and my expertise is strictly limited to software development topics.

co-pilot seems to think --mkpath isn't an option, what does it do?

In order to place versioned directories like release/v0.30.0, the remote-path action attribute has a directory that doesn't exist. --mkpath creates it. I'm not sure how we would put multiple deploy directories side-by-side with "--delete" turned on, Maybe have a 1st job that makes the version directory and doesn't do delete?

[devinrsmith]

Looks good - I'm happy to merge this given the brand new directory on the remote_path. Please get approval from @dsmmcken before merge.

[dsmmcken]

Looks good, and should be low risk to merge. I'll make whatever changes we need on the other side of the fence once deployed.