https://plugins.jenkins.io/github-branch-source/ and
https://plugins.jenkins.io/cloudbees-folder/ both still have
documentation hosted on cloudbees.com.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and
One example of content that might help (but would need modifications to fit
into the jenkins.io structure) is the Jenkins command line interface
documentation
at
https://docs.cloudbees.com/docs/admin-resources/latest/cli-guide/cli-guide-intro
.
A technical writer would need to evaluate that
I concur with all of Oleg's statements. I think this sounds great, but we
need to make sure the content is not copyrighted in such a way that would
cause the Jenkins project issues.
On Wed, Jun 24, 2020 at 4:00 AM Oleg Nenashev
wrote:
> Hi Mark,
>
> Thanks a lot for starting this discussion. I
Hi Mark,
Thanks a lot for starting this discussion. I see no problem with such
initiative in general. If someone is willing to donate the documentation
content, it is always appreciated. There are many vendors and users who
created their own documentation for Jenkins, and it would be great to
Hi Mark
Have you got any examples of documentation that would be good to migrate?
Sounds great though
Thanks
Tim
On Tue, 23 Jun 2020 at 22:39, Mark Waite wrote:
> The documentation team at CloudBees has asked if the community would be
> interested in reworking or adjusting documentation that
The documentation team at CloudBees has asked if the community would be
interested in reworking or adjusting documentation that CloudBees has
created for their product to describe similar use cases on
www.jenkins.io. The documentation team at CloudBees does not have the
capacity to perform
