Hi, Personally I'm +1 on moving to GitHub. Confluence is error-prone and unstable. It also has capture/spam problems. So such migration may solve all the issues and allow to keep docs up to date.
FYI we also keep the documentation centralization in mind. E.g. there is a project idea for GSoC2016 <https://wiki.jenkins-ci.org/display/JENKINS/Google+Summer+Of+Code+2016>, which covers publishing of the documentation to the Jenkins website. It should solve the usage limitations for common users. BR, Oleg среда, 9 марта 2016 г., 21:36:38 UTC+1 пользователь Jesse Glick написал: > > On Wed, Mar 9, 2016 at 12:11 PM, Rafael Rezende <[email protected] > <javascript:>> wrote: > > is there any documentation > > about the Jenkins release process behind the scenes? For example, when > > someone wants to contribute with a new plugin, a whole environment is > > created around it (github repo, confluence page, a jenkins job to build > the > > plugin, Jira etc). Is everything triggered by scripts? > > https://wiki.jenkins-ci.org/display/JENKINS/IRC+Bot > > is used by admins to create the GitHub repo and JIRA component. Wiki > page creation is up to the plugin creator (be sure to add beneath the > Plugins page, add one or more `plugin-*` tags, and include the macro > that produces plugin summary information—view source of another plugin > page to see). The Jenkins job is created automatically. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/28d8f4c7-4441-479e-b597-890e56edbb58%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
