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

Move documentation from Wiki to GitHub #122

Merged
merged 3 commits into from Oct 23, 2019
Merged

Move documentation from Wiki to GitHub #122

merged 3 commits into from Oct 23, 2019

Conversation

oleg-nenashev
Copy link
Member

@oleg-nenashev oleg-nenashev commented Jul 25, 2019

subj

@oleg-nenashev oleg-nenashev added the documentation A PR that adds to documentation - used by Release Drafter label Jul 25, 2019
README.md Outdated Show resolved Hide resolved
(This refers only to additional messages printed to console, not to a failure stack trace).
Such output is always kept if the test failed, but by default lengthy output from passing tests is truncated to save space.
Check this option if you need to see every log message from even passing tests, but beware that Jenkins's memory consumption can substantially increase as a result, even if you never look at the test results!
* **Health report amplification factor:** The amplification factor to apply to test failures when computing the test result contribution to the build health score.
Copy link
Member

Choose a reason for hiding this comment

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

I think this sort of detailed help is best left in help*.html files in the product. Will just go stale here. The online docs should focus on higher-level guidelines and suggestions.

Copy link
Member

Choose a reason for hiding this comment

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

... but this is just a port of the Wiki page, so fine for now.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah, did not want to spend much time rewording. Subject for contributions

@olivergondza
Copy link
Member

What would happen with the user documentation on plugin wiki? I prefer to have user-docs there...

@zbynek
Copy link
Contributor

zbynek commented Sep 3, 2019

@olivergondza the first paragraph in the wiki tells users to go to the plugin site instead (I assume the plugin site is easier to scale/customize). So the plugin site is preferred as source for the users. Until now wiki was the only way to edit the content served on the plugin site, but now with https://issues.jenkins-ci.org/browse/WEBSITE-406 released you can use GitHub as the editor as well.

@oleg-nenashev
Copy link
Member Author

@olivergondza @zbynek Sorry, missed the ping there. Updated POM.xml.
With the new version the Plugin site will take docs from GitHub

@olivergondza
Copy link
Member

Thanks, was not aware of the WEBSITE-406 effort.

@oleg-nenashev
Copy link
Member Author

oleg-nenashev commented Sep 5, 2019

FTR https://groups.google.com/forum/#!topic/jenkinsci-dev/VSdfVMDIW-A . It was just announced 2 days ago, and I forgot to link it in my last comment

@tiger5226
Copy link

Its also probably a good idea to include the format of the junit xml files https://llg.cubic.org/docs/junit/

@oleg-nenashev
Copy link
Member Author

@olivergondza would it be possible to merge it so that the improvements get submitted as follow-ups?

@olivergondza olivergondza merged commit 18f7099 into master Oct 23, 2019
@zbynek zbynek moved this from Needs-release to Merged in Plugin documentation Migration (Wiki=>GitHub) Jan 16, 2020
@zbynek zbynek moved this from Merged to Released in Plugin documentation Migration (Wiki=>GitHub) May 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation A PR that adds to documentation - used by Release Drafter
Development

Successfully merging this pull request may close these issues.

None yet

5 participants