Rewrite 'Jenkins Development Environment with Nexus', add to dev docs

[getJv]

trafficstars

Essential information

Rewrite the Nexus caching instructions from https://wiki.jenkins.io/display/JENKINS/Jenkins+Development+Environment+with+Nexus Insert the updated / replacement content as a new page under destination: https://www.jenkins.io/doc/developer/guides/ as a new "How-to Guide: Using Nexus as a Repository Cache for Development"

Terminology updates

Please consider updating some old terminologies:

• Change ‘master’ to ‘controller’
• Change ‘slave’ to ‘agent’
• Change ‘blacklist’ to ‘denylist’ or better phrase in context
• Change ‘whitelist’ to ‘allowlist’ or better phrase in context

Migration tutorial

Watch the tutorial to learn more about each page migration process:

Additional information

Note: check jenkins.io first to see if there's content for this already, possibly there's some useful content on the wiki that should be pulled in

It should be improved on and cleaned up, not just imported,

You can use the wiki-exporter to save some time: https://jenkins-wiki-exporter.jenkins.io/

Redirecting pages

After it has been migrated a redirect should be setup, by sending a PR to this file: https://github.com/jenkins-infra/jenkins-infra/blob/staging/dist/profile/templates/confluence/vhost.conf, see past PRs for examples, or just take a look.

[timja]

I think we can just delete the page @MarkEWaite ?

[MarkEWaite]

Agreed @timja that the page could be deleted or could be redirected to https://github.com/jenkinsci/jenkins/blob/master/CONTRIBUTING.md . I confirmed that the Nexus repository configuration steps are not required for Jenkins development. If someone is running a local caching Nexus or Artifactory, they'll learn how to configure settings.xml from the Nexus or Artifactory documentation and it will be better suited to the artifact repository than if we try to document it.