Details
-
Task
-
Status: In Progress (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
Description
Is there ongoing task for migrating wiki to github?
I was trying to fix wiki about elasticsearch(related to JENKINS-67546), but I found that fixing wiki by contribution is not possible unless wiki is migrated.
Would it be okay if I change a wiki a bit to make migration, and request a PR for it?
Attachments
Issue Links
- links to
Activity
jinwookh han
added a comment - Failing CI has been solved, but still documentation in plugins.jenkins.io is outdated.
It seems new plugin release is not generated automatically, so the documentation is not synced with github wiki.
markewaite Could you figure out why the new release is not generated?
The release page shows that latest release was done 10 months ago.(https://github.com/jenkinsci/logstash-plugin/releases)
jinwookh han
added a comment - Failing CI has been solved, but still documentation in plugins.jenkins.io is outdated.
It seems new plugin release is not generated automatically, so the documentation is not synced with github wiki.
markewaite Could you figure out why the new release is not generated?
The release page shows that latest release was done 10 months ago.( https://github.com/jenkinsci/logstash-plugin/releases)
I suspect that the continuous delivery process is detecting that none of the pull requests merged since the last releases have a label that indicates they are interesting enough to justify a release. When I look at the list of merged pull requests, they appear to be mostly dependency updates and they have no label.
If you label one of the recent pull requests as an enhancement, that should be enough to trigger the release.
Jakub Bochenski
added a comment - I thought the release is triggered, unless a commit is specially marked as uninteresting. How do I mark one as an enhancement?
Jakub Bochenski
added a comment - I thought the release is triggered, unless a commit is specially marked as uninteresting. How do I mark one as an enhancement? Apply a label to one or more of the pull requests. In the platformlabeler and schedule build plugins, it would be "feature".
You can check that from the "Actions" tab on GitHub. Here is a screenshot of the actions tab for a plugin that I maintain:
You should probably modify the version numbering in the pom.xml file before the next release. Do a detailed review of the instructions at https://www.jenkins.io/doc/developer/publishing/releasing-cd/ especially the part about manually controlled prefix. Currently the plugin seems to use a 3 part version number as the manually controlled prefix then it appends the generated number. Usually you want at most one or two components to be manually controlled.
Automatic releases require that the master branch on ci.jenkins.io must pass automated tests.
Merge pull request 113 to fix the failing test on the master branch and the plugin release should be generated automatically.
Thanks for maintaining the plugin jbochenski!
In case it helps, someone once showed me the location on github.com where the status of the master branch CI job is reported. Here's a screenshot: