-
Bug
-
Resolution: Unresolved
-
Major
-
None
As described by multiple users in stack-overflow
It seems like the CORS plugin doesn't work anymore. I ran into the same issue, tried solving it from all kinds of directions but I think it still broken.
If this could be fixed, that's amazing. But if it's not being maintained maybe it's possible to add a warning to the plugin page?
[JENKINS-67488] CORS plugin isn't working
Effi Qurer
created issue -
Effi Qurer
made changes -
| Description |
Original:
As described by multiple users in stack-overflow ([1|http://example.com]https://stackoverflow.com/questions/63604874/jenkins-cors-plugin-not-enabling-access-control-allow-header , [2|[http://example.com]https://stackoverflow.com/questions/56962278/jenkins-cors-filter-plugin-not-adding-access-control-allow-origins-header),|http://example.com]https//stackoverflow.com/questions/56962278/jenkins-cors-filter-plugin-not-adding-access-control-allow-origins-header),] It seems like the CORS plugin doesn't work anymore. I ran into the same issue, tried solving it from all kinds of directions but I think it still broken.
If this could be fixed, that's amazing. But if it's not being maintained maybe it's possible to add a warning to the plugin page? |
New:
As described by multiple users in stack-overflow
[https://stackoverflow.com/questions/63604874/jenkins-cors-plugin-not-enabling-access-control-allow-header] [https://stackoverflow.com/questions/56962278/jenkins-cors-filter-plugin-not-adding-access-control-allow-origins-header] It seems like the CORS plugin doesn't work anymore. I ran into the same issue, tried solving it from all kinds of directions but I think it still broken. If this could be fixed, that's amazing. But if it's not being maintained maybe it's possible to add a warning to the plugin page? |
Effi Qurer
made changes -
| Attachment | New: Screen Shot 2022-01-02 at 14.15.56.png [ 57023 ] |
Effi Qurer
added a comment - Hi Mark, thanks for the quick response.
I tried looking at the issues page but it was infinitely loading:
Unfortunately I don't have the knowledge and experience for development at this level, I hope that in the future I'll be able to contribute.
Effi Qurer
added a comment - Hi Mark, thanks for the quick response.
I tried looking at the issues page but it was infinitely loading:
Unfortunately I don't have the knowledge and experience for development at this level, I hope that in the future I'll be able to contribute. Click the link to "Issues" on the right hand column. I believe that halkeye plans to remove the issues tab and rely solely on the issues link that is on the right hand column
Effi Qurer
added a comment - Do you mean the Open Issues (Jira) link? it took me to https://issues.jenkins.io/browse/JENKINS-67488?jql=resolution%20is%20EMPTY%20and%20component%3D20629
It's showing me only this ticket we're in, do you mean a different link?
In any case, I thought it could be helpful if there's some kind of communication about the status of the plugin, otherwise people spending hours on configurations without knowing it's not maintained anymore.
Effi Qurer
added a comment - Do you mean the Open Issues (Jira) link? it took me to https://issues.jenkins.io/browse/JENKINS-67488?jql=resolution%20is%20EMPTY%20and%20component%3D20629
It's showing me only this ticket we're in, do you mean a different link?
In any case, I thought it could be helpful if there's some kind of communication about the status of the plugin, otherwise people spending hours on configurations without knowing it's not maintained anymore. Plugins that are not maintained are generally not marked with any special indicator unless the maintainer specifically lists them as "up for adoption". I don't see why the CORS plugin would deserve different treatment than other plugins.
Effi Qurer
added a comment - Well, I'm new to Jenkins plugins, but it's pretty common for people to reflect on the status of software especially , e.g many github projects have a workflow status badge and so on. In any case this isn't done in Jenkins plugins that's fine, thank you again for the responses.
Effi Qurer
added a comment - Well, I'm new to Jenkins plugins, but it's pretty common for people to reflect on the status of software especially , e.g many github projects have a workflow status badge and so on. In any case this isn't done in Jenkins plugins that's fine, thank you again for the responses. 
Markus Winter
added a comment - For me it works fine.
I used the latest weekly Jenkins and deployed a locally built CORS plugin with some debug output, then using Postman to send a request and analyze the response.
Maybe you write more details about your setup especially the configuration of the plugin and the URL in your browser window to ensure it is not a configuration issue.
Markus Winter
added a comment - For me it works fine.
I used the latest weekly Jenkins and deployed a locally built CORS plugin with some debug output, then using Postman to send a request and analyze the response.
Maybe you write more details about your setup especially the configuration of the plugin and the URL in your browser window to ensure it is not a configuration issue. 
The plugins page includes a link to the issues reported for the plugin. This issue appears in that report.
If you'd like to adopt the CORS plugin, that would be great. It was last released five years ago.
There is a "Contributing to Open Source" tutorial document that includes many small steps that a new contributor can take to modernize a plugin and prepare to adopt it. Many of those steps are supported by segments from the five tutorial videos that are linked in that document.