-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
Use antsibull 0.40.1 for docsite build #76675
Conversation
0.40.0 crashed during the test docsite build; 0.40.1 fixes the crash (antsibull now has tests to prevent this kind of crash). |
The test
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
verified on jenkins and local build that this works.
fwiw I changed max_threads to 1 on my vm to get the build to work w/o timeouts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Forgot one more place this needs to change I think. We need to keep the docs_build requirements file in sync with this.
https://github.com/ansible/ansible/blob/devel/test/sanity/code-smell/docs-build.requirements.txt#L7
Hmm top of that file (docs-build.requirements.txt sez to generate it w/ another file so might need edits somewhere else? or maybe just regenerate the file?? |
@samccann I think changing that file prevents this from being backported to any stable branch. |
On the other hand, the code-smell test is internal to ansible/ansible, so maybe this doesn't block backporting. |
I don't know if we want to backport this or not really. I know I'd like to keep this on devel only 'for a time' so we can get any feedback from users. I can put it in the bullhorn and on reddit etc once it's on devel. I was thinking it would go live on /latest/ with Ansible 6? |
...or are you thinking of updating that docs-build.requirements in a separate PR? I'm still not sure we'd want our docs requirements out of sync with the sanity test... |
I've now updated it in this PR. I'm not sure whether this is a problem, but now the dependencies for the docs build differ partially from the dependencies for the changelog test (https://github.com/ansible/ansible/blob/devel/test/lib/ansible_test/_data/requirements/sanity.changelog.txt). @mattclay is this a problem (and do the requirements have to match), or is it ok if they differ? |
Yeah it's picking up a lot of changes, most of which I don't know where they come from etc. Notice the ansible sphinx theme also got updated from what we use - https://github.com/ansible/ansible/pull/76675/files#diff-4cc37de5fc6a320124546ce84589725b60cf05237e02a49a19eaeda2f8f87fe2R37 Not sure what to do... |
The test
The test
|
Manually update the pinned requirements in It should be safe to do so as long as those package versions are compatible with the other pinned packages in that file. Once this is merged I'll rebuild the test container used for the If it does get backported, there will be merge conflicts and I'll need to rebuild the container used in the |
@@ -18,9 +18,9 @@ class ModuleDocFragment(object): | |||
env: | |||
- name: DISPLAY_SKIPPED_HOSTS | |||
deprecated: | |||
why: environment variables without "ANSIBLE_" prefix are deprecated | |||
why: environment variables without C(ANSIBLE_) prefix are deprecated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the quote fixes be done in a separate PR so they can be independently backported?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I see you've already opened a PR for that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, didn't mention it here, but I created a separate PR (#76698). I've now rebased after that one was merged.
…rce." (This needs to be done in a separate PR, since it also needs to modify the docs build sanity test. Backporting it follows different rules than pure docs build backports, so let's keep it separate.) This reverts commit 649a349.
adcaea8
to
cea1f1f
Compare
SUMMARY
Use the latest release of antsibull to build the docsite. It uses RST tables instead of HTML blobs for option and return value tables, and these tables are responsive.
ISSUE TYPE
COMPONENT NAME
docsite