I have created https://github.com/jenkins-infra/jenkins.io/pull/2589 to
document the service usage.
Also, created few tickets in
https://github.com/halkeye/jenkins-wiki-exporter so that we can fix exposrt
for some plugins and support non-plugin issues.
But overall it works great, thanks Gavin!
-
> Asciidoc format can be used as well, with the .adoc extension.
- I can add that pretty easily
-
- > Remove the macro references in the top of the document.
-
- Totally done
> If the document includes "Table of contents", remove this section in
Markdown or replace it by :toc: macros in
Okay~~~
https://jenkins-wiki-exporter.g4v.dev/ is now updated to support markdown,
or a zip of markdown + images
Gavin
On Sun, Oct 20, 2019 at 2:11 PM Gavin Mogan wrote:
> Thanks for the PR, I've deployed the change, and started to get prepped
> for straight up markdown, markdown + zip with
Thanks for the PR, I've deployed the change, and started to get prepped for
straight up markdown, markdown + zip with images, and eventually adoc
I'm totally up for forking it to infra or something, I have no idea how to
do that though.
On Sun, Oct 20, 2019 at 1:50 AM Oleg Nenashev
wrote:
>
Thanks Gavin!
I submitted the pull request for truncating RAW HTML which should improve
the layout. More pull requests to come soon. I would suggest hosting this
service on jenkinsci or jenkins-infra. I think we can get a lot of
contributions. Also, I think we should reserve opportunities to
Last night I started a little web app to make the migration easier for
people
https://jenkins-wiki-md.g4v.dev/ (for example, try out "blueocean")
I have to incorporate some of the items oleg mentioned in the doc, but its
a start.
Gavin
On Sat, Oct 19, 2019 at 12:53 AM Oleg Nenashev
wrote:
>
Do we have any information on the Wiki pages that get the most hits, that
way we could target specific pages to migrate to github / jenkins.io?
A quick google suggests the below, but they may not be enabled:
First version of the plugin Wiki=>GitHub migration guide is available here:
https://jenkins.io/doc/developer/publishing/wiki-page/#migrating-from-wiki-to-github
Later it will be improved once I finish the migration tool on the top of
Pandoc
Could use GitHub topics? Or just add to the readme
>
Could use GitHub topics? Or just add to the readme
On Fri, 18 Oct 2019 at 15:24, Robert Sandell wrote:
> And how do I mark a plugin as up for adoption without the wiki labels?
>
> /B
>
> Den fre 18 okt. 2019 kl 14:52 skrev Jesse Glick :
>
>> On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck wrote:
And how do I mark a plugin as up for adoption without the wiki labels?
/B
Den fre 18 okt. 2019 kl 14:52 skrev Jesse Glick :
> On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck wrote:
> > I propose that we restore write access for plugin maintainers at least
> for a time, to allow them to clear out
On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck wrote:
> I propose that we restore write access for plugin maintainers at least for a
> time, to allow them to clear out wiki pages after migrating the content
> elsewhere.
Makes sense, but is there some plan to notify maintainers of plugins
who have
> On 17. Oct 2019, at 17:05, Olblak wrote:
>
>> Don't we have a feature in Confluence to add a big warning in top of pages,
>> for people logged in, to point them to this thread or so?
>
> I added that warning message
It shows for everyone, but that way it prepares everyone for the
> I don't know how much longer we can keep Confluence alive.
I've seen some links in jenkins.io still pointing to confluence (ie.
https://jenkins.io/doc/developer/views/).
If confluence is going down, those should be migrated, I think.
On Thu, 17 Oct 2019 at 07:36, Oleg Nenashev wrote:
>
GitHub documentation support is available thanks to Zbynek, I am just
facilitating things and helping PRs to land. Anyway, I agree we should
consider moving content to GitHub and jenkins.io where possible.
Some useful links:
* Plugin Documentation (including GitHub):
14 matches
Mail list logo
