Details
-
Type:
Epic
-
Status: In Review (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: plugin-site
-
Labels:
-
Epic Name:PluginSite-GitHub-Integration
-
Similar Issues:
Description
Jenkins plugins steadily move to GitHub in order to enable Documentation-as-Code. Also, release Drafter changelog automation or CHANGELOG.md are pretty popular across plugins. It would be great to enable Jenkins Plugin Site to pull plugin information from the locations there so that Jenkins users get a better experience.
Goals:
- Plugin site can pull README.md from GitHub instead of Wiki for plugins
- Plugin site can reference changelog URLs and, ideally, display the changelogs
- Plugin site can display logos supplied by plugin metadata
- + other topics TBD at the sub-project meeting
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
This is a wannabe-EPIC ticket Jenkins plugins steadily move to GitHub in order to enable Documentation-as-Code. Also, release Drafter changelog automation or CHANGELOG.md are pretty popular across plugins. It would be great to enable Jenkins |
| Description |
This is a wannabe-EPIC ticket Jenkins plugins steadily move to GitHub in order to enable Documentation-as-Code. Also, release Drafter changelog automation or CHANGELOG.md are pretty popular across plugins. It would be great to enable Jenkins |
This is a wannabe-EPIC ticket Jenkins plugins steadily move to GitHub in order to enable Documentation-as-Code. Also, release Drafter changelog automation or CHANGELOG.md are pretty popular across plugins. It would be great to enable Jenkins Plugin Site to pull plugin information from the locations there so that Jenkins users get a better experience. |
| Description |
This is a wannabe-EPIC ticket Jenkins plugins steadily move to GitHub in order to enable Documentation-as-Code. Also, release Drafter changelog automation or CHANGELOG.md are pretty popular across plugins. It would be great to enable Jenkins Plugin Site to pull plugin information from the locations there so that Jenkins users get a better experience. |
This is a wannabe-EPIC ticket Jenkins plugins steadily move to GitHub in order to enable Documentation-as-Code. Also, release Drafter changelog automation or CHANGELOG.md are pretty popular across plugins. It would be great to enable Jenkins Plugin Site to pull plugin information from the locations there so that Jenkins users get a better experience. Goals: * Plugin site can pull README.md from GitHub instead of Wiki for plugins * Plugin site can reference changelog URLs and, ideally, display the changelogs * Plugin site can display logos supplied by plugin metadata * + other topics TBD at the sub-project meeting |
| Summary | Plugin Site GitHub: Documentation and Changelogs from GitHub | Plugin Site Update: Documentation and Changelogs from GitHub |
| Assignee | Michael McCaskill [ mmccaskill ] | Oleg Nenashev [ oleg_nenashev ] |
This is also another step towards not needing to host confluence
| Issue Type | Task [ 3 ] | Epic [ 10001 ] |
| Epic Child |
|
| Epic Child | WEBSITE-383 [ 183942 ] |
| Epic Child |
|
| Labels | docs-sig documentation |
| Priority | Minor [ 4 ] | Major [ 3 ] |
| Description |
This is a wannabe-EPIC ticket Jenkins plugins steadily move to GitHub in order to enable Documentation-as-Code. Also, release Drafter changelog automation or CHANGELOG.md are pretty popular across plugins. It would be great to enable Jenkins Plugin Site to pull plugin information from the locations there so that Jenkins users get a better experience. Goals: * Plugin site can pull README.md from GitHub instead of Wiki for plugins * Plugin site can reference changelog URLs and, ideally, display the changelogs * Plugin site can display logos supplied by plugin metadata * + other topics TBD at the sub-project meeting |
Jenkins plugins steadily move to GitHub in order to enable Documentation-as-Code. Also, release Drafter changelog automation or CHANGELOG.md are pretty popular across plugins. It would be great to enable Jenkins Plugin Site to pull plugin information from the locations there so that Jenkins users get a better experience. Goals: * Plugin site can pull README.md from GitHub instead of Wiki for plugins * Plugin site can reference changelog URLs and, ideally, display the changelogs * Plugin site can display logos supplied by plugin metadata * + other topics TBD at the sub-project meeting |
| Epic Child | INFRA-2225 [ 201424 ] |
| Epic Name | PluginSite-GitHub-Integration |
| Epic Child | INFRA-2228 [ 201448 ] |
| Epic Child | INFRA-2229 [ 201463 ] |
| Epic Child |
|
| Epic Child | INFRA-2240 [ 201544 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child | INFRA-2248 [ 201637 ] |
| Epic Child |
|
| Epic Child | WEBSITE-644 [ 201649 ] |
| Epic Child | WEBSITE-645 [ 201651 ] |
| Epic Child | WEBSITE-646 [ 201653 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child | INFRA-2255 [ 201705 ] |
| Epic Child | INFRA-2256 [ 201706 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child | JENKINS-59467 [ 202067 ] |
| Epic Child |
|
| Epic Child | JENKINS-59555 [ 202187 ] |
| Epic Child | JENKINS-59572 [ 202208 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Labels | docs-sig documentation | docs-sig documentation hacktoberfest |
| Epic Child |
|
| Epic Child | JENKINS-59712 [ 202419 ] |
| Epic Child |
|
| Epic Child | INFRA-2297 [ 202603 ] |
| Epic Child |
|
| Link | This issue is related to INFRA-2328 [ INFRA-2328 ] |
| Epic Child | JENKINS-59555 [ 202187 ] |
| Epic Child | JENKINS-59572 [ 202208 ] |
| Epic Child |
|
| Epic Child | WEBSITE-646 [ 201653 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child | JENKINS-59467 [ 202067 ] |
| Status | To Do [ 10003 ] | In Progress [ 3 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child | WEBSITE-728 [ 204629 ] |
| Status | In Progress [ 3 ] | In Review [ 10005 ] |
CC Zbynek Konecny Gavin Mogan. Once INFRA-2220 is done, I will move the related tickets under the EPIC so that we can coordinate the multiple Work streams we have at the moment. If you are fine with that, I suggest using Documentation SIG as a base for the project. CC Mark Waite