Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server application written in PHP for plug-in compatibility feedback from Jenkins users #1

Closed
wants to merge 4 commits into from

Conversation

kinow
Copy link

@kinow kinow commented Apr 28, 2012

This is a simple server application for storing user feedback about plug-in compatibility. It reports whether the plug-in is working or not with a certain Jenkins version. This way we can create the jelly/java part in Jenkins.

This application was written with Slim (for RESTful + Logging) and ActiveRecord (for ORM).

You can see the server running at http://www.tupilabs.com/infra-rating/ (try /ratings or /pluginStatus for JSON output).

And a sample application with a form to submit plug-in feedback and query the plug-in statuses is available at http://www.tupilabs.com/infra-rating/sample_app/.

This server application seems to be quite different than the previous plugin rating application. Not sure if it would be better to create a separate repository for this application, or replace it with this pull request.

…from

PG to MySQL or vice versa. It is also easier to communicate with database
and to query.

Included Slim for a small and simple RESTful server with logging support.

ActiveRecord has been patched as it had no way to output/serialize
entities as JSON.

Created a server application to handle /ratings, /pluginStatus GET resources
and /ratings POST.

There is also a sample application that shows how to use this application
for keeping status of plug-in compatibility. This sample uses only Twitter
bootstrap and Backbone.js/JQuery.

The database model was created based on the existing code of infra-rating,
and it is not normalized. There is a simple index, but it is not clear
whether that will be enough or not.

Before running the application, check the database connection, Slim mode
(development, production, etc) and if the log leves are fine.
@jenkinsadmin
Copy link

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

@kohsuke
Copy link
Member

kohsuke commented Mar 19, 2014

OMG, 40K LoC addition!

I feel really bad that we left this unattended for 2 years. Since this isn't compatible with the current version, I think it's best to put this in a separate repository. Are you still interested in taking this forward? Does it help if we set you up with the system access so that you can deploy this by yourself?

@jakesylvestre
Copy link

I'd think it would need updates with the incompatibilty

@kinow
Copy link
Author

kinow commented Jun 9, 2015

Hi, the code can be simplified and polished, use newer PHP, updated UI, etc. I'll try to update the PR, fix the broken link and attach some screenshots.

@daniel-beck
Copy link
Contributor

@kinow I'm planning to look into integrating user feedback into Jenkins itself. We should probably coordinate our efforts.

@kinow
Copy link
Author

kinow commented Jun 10, 2015

Sure thing @daniel-beck. Let me know (here or in the dev-list) about what you have in mind, and I'll be happy if I can help in some way 👍

@kinow
Copy link
Author

kinow commented Jan 8, 2019

Uh, probably won't have time to ever look at this code. I barely remembered creating the PR. Closing to avoid confusion 😬

@kinow kinow closed this Jan 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants