-
Bug
-
Resolution: Fixed
-
Major
-
None
-
-
Evergreen - Milestone 2
Problem statement
It should be clear that the Evergreen Jenkins plugin is not designed to be installed on a non-evergreen Jenkins instance.
But currently for some reason, despite the fact I wrote
Jenkins Evergreen Plugin - Note: you should generally never install this plugin yourself.
In the plugin manager, it looks like:
Expected behavior
The end of that message should be visible. I suppose there's a tokenization that cuts after the hyphen or something. Probably we just remove it and that's enough.
- links to
[JENKINS-54167] Hide Evergreen Jenkins plugin for non-evergreen installs
| Attachment | New: screenshot-1.png [ 44822 ] |
| Description |
Original:
h3. Problem statement It should be clear that the Evergreen Jenkins plugin is not designed to be install on a non-evergreen Jenkins instance. But currently for some reason, despite the fact I wrote h4. Expected behavior |
New:
h3. Problem statement It should be clear that the Evergreen Jenkins plugin is not designed to be installed on a non-evergreen Jenkins instance. But currently for some reason, despite the fact I wrote {{Jenkins Evergreen Plugin - Note: you should generally never install this plugin yourself.}} In the plugin manager, it looks like: !screenshot-1.png! h4. Expected behavior The end of that message should be visible. I suppose there's a tokenization that cuts after the hyphen or something. Probably we just remove it and that's enough. |
| Description |
Original:
h3. Problem statement It should be clear that the Evergreen Jenkins plugin is not designed to be installed on a non-evergreen Jenkins instance. But currently for some reason, despite the fact I wrote {{Jenkins Evergreen Plugin - Note: you should generally never install this plugin yourself.}} In the plugin manager, it looks like: !screenshot-1.png! h4. Expected behavior The end of that message should be visible. I suppose there's a tokenization that cuts after the hyphen or something. Probably we just remove it and that's enough. |
New:
h3. Problem statement It should be clear that the Evergreen Jenkins plugin is not designed to be installed on a non-evergreen Jenkins instance. But currently for some reason, [despite the fact I wrote|https://github.com/jenkinsci/evergreen-plugin/blob/evergreen-0.9/pom.xml] {{Jenkins Evergreen Plugin - Note: you should generally never install this plugin yourself.}} In the plugin manager, it looks like: !screenshot-1.png! h4. Expected behavior The end of that message should be visible. I suppose there's a tokenization that cuts after the hyphen or something. Probably we just remove it and that's enough. |
| Assignee | Original: R. Tyler Croy [ rtyler ] | New: Baptiste Mathus [ batmat ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Remote Link | New: This issue links to "PR (Web Link)" [ 21940 ] |
| Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Note: again thanks to Daniel I finally chose an even better path: PR has been filed against the UC generation repo to hide evergreen Jenkins plugin.
As we're using anyway only incrementals releases on evergreen distribution, this is fine. This Jenkins plugin becomes invisible to standard installs, which if what we want.
Daniel just told me that now pom.xml is mostly ignored, so this is extracted from index.jelly. Fixing.