https://github.com/jenkinsci/logstash-plugin/pull/96 has started the migration from wiki to github. It would be much better if you provided help to that pull request rather than creating a new pull request to update the wiki content or to migrate the existing content.

If you don't receive a response from the plugin maintainer in 1-2 weeks, then you can propose to adopt the plugin, complete the documentation migration, and release a new version of the plugin with the updated documentation

I never got any reply from OP after that PR was posted. If you can pick it up jinwookh that would be nice, if you prefer to start from scratch that's OK too

Thanks for the comment.
I will begin from original PR at first.

markewaite Would it be okay to link this issue to the epic INFRA-2328?
Or should I create a new issue for it?

PR #111 is merged, so the task is done except the last step(creating an INFRA Jenkins JIRA ticket to replace the content).

markewaite  Thanks for the reply.
Then there is no step that I need to further proceed, right?
I am asking this because plugin migration guide says that creating new issue is required.
https://www.jenkins.io/doc/developer/publishing/wiki-page/#migrating-from-wiki-to-github

The most important step is yet to be performed. The plugin needs to be released with the updated pom.xml .

Opening a ticket at https://github.com/jenkins-infra/helpdesk is fine, once the plugin has released with the change.

Got it. Thanks for the guide.

I thought the releases should happen automatically now since I added that .github/workflows/cd.yaml file
But I don't think it worked... any help finding out whats wrong?

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:

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.

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.