Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport the new doc framework with mkdocs and related build changes #10321

Merged
merged 17 commits into from
May 25, 2022

Conversation

travisn
Copy link
Member

@travisn travisn commented May 24, 2022

Description of your changes:
The stabilization of the new docs has been completed in master, now we can backport all the changes to the release-1.9 branch. This is done with the bulk manual backport so we don't have all the intermittent build issues that were experienced in master.

Checklist:

  • Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
  • Skip Tests for Docs: If this is only a documentation change, add the label skip-ci on the PR.
  • Reviewed the developer guide on Submitting a Pull Request
  • Pending release notes updated with breaking and/or notable changes for the next minor release.
  • Documentation has been updated, if necessary.
  • Unit tests have been added, if necessary.
  • Integration tests have been added, if necessary.

galexrt and others added 17 commits May 24, 2022 15:24
Signed-off-by: Alexander Trost <galexrt@googlemail.com>
(cherry picked from commit 7443144)
Deploying a custom CSI image is more of a standalone topic
under the CSI configuration docs. There is no need for the
upgrade guide to have the details about CSI images.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit b6c2b99)
The ceph upgrade guide is factored out into a separate document
to help simplify the flow and make the different types of
upgrades more easily discoverable.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit 3e0f26a)
The requirements_docs.txt is expected by the build.docs
build target in build/release. Since the txt file was at
the root of the repo, the build was failing to be pubished
when it didn't find the file in build/release.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit 557feb2)
Signed-off-by: Alexander Trost <galexrt@googlemail.com>
(cherry picked from commit a17575f)
Signed-off-by: Alexander Trost <galexrt@googlemail.com>
(cherry picked from commit 0d815c0)
The doc build generation script is failing to install
the needed dependencies for mkddocs.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit 03a091e)
The docs failed to publish with the mkdocs.yml in the root
folder instead of where the docs are being built.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit c375bbd)
Signed-off-by: Gaurav Sitlani <gaurav@koor.tech>
(cherry picked from commit 84c53d1)
The push image build CI action is mistakenly running on
arm64 instead of amd64, which is failing the build since
it only expects amd64.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit 5793582)
The setup tools package and libgit2 are required on
ubuntu 18.04 in order to install the mkdocs framework
and publish the docs. After we move to ubuntu 20.04
this should no longer be necessary.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit 2404fe1)
Resolves rook#10282

Signed-off-by: Alexander Trost <galexrt@googlemail.com>
(cherry picked from commit a156dc3)
Signed-off-by: Alexander Trost <galexrt@googlemail.com>
(cherry picked from commit 2f75104)
Signed-off-by: Alexander Trost <galexrt@googlemail.com>
(cherry picked from commit 46fa71c)
Signed-off-by: Alexander Trost <galexrt@googlemail.com>
(cherry picked from commit 548f723)
Signed-off-by: Alexander Trost <galexrt@googlemail.com>
(cherry picked from commit c149d87)
Signed-off-by: Alexander Trost <galexrt@googlemail.com>
(cherry picked from commit de5777c)
@travisn travisn requested review from galexrt and BlaineEXE May 24, 2022 21:35
@travisn travisn marked this pull request as ready for review May 24, 2022 21:35
@mergify
Copy link

mergify bot commented May 24, 2022

Hi @travisn, this pull request was opened against a release branch, is it expected? Normally patches should go in the master branch first and then be backported to release branches.

@travisn
Copy link
Member Author

travisn commented May 24, 2022

@galexrt If this looks good, please go ahead and merge so we can watch closely and iterate again on the build if anything is still needed.

Copy link
Member

@galexrt galexrt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM Let's get the new docs design out for 1.9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants