Hosting request for four new plugins

66 views
Skip to first unread message

Andrey Stroilov

unread,
Aug 26, 2015, 12:58:38 PM8/26/15
to Jenkins Developers

Repository names should not need to change:
google-health-check-plugin
google-persistent-master-plugin
google-git-notes-plugin
google-usage-report-plugin

My GitHub username: astroilov
My jenkins-ci.org username: astroilov

Plugin descriptions:
- Health Check: an extensible health check framework that works with Google Cloud Platform health checking.
- Persistent Master: an extensible backup-and-restore framework that supports autorestore, allowing "persistent" Jenkins masters that pull their configuration and state from backup automatically when they are restarted. Supports full and incremental backups, custom backup configurations, and on-demand backup when Jenkins is about to shut down. Uses Google Cloud Storage for backups, with extension points for additional upload/download mechanisms.
- Git Notes: logs Jenkins build results to Git notes in a JSON format intended for use as a tool-agnostic metadata format.
- Usage Report: allows Jenkins usage reporting via Google Analytics. Intended to allow organizations that release bundled Jenkins images or versions to receive more detailed usage info beyond "N downloads". Note that this plugin does not send any data without specific configuration by the system administrator or bundle administrator.

Oleg Nenashev

unread,
Aug 30, 2015, 5:58:33 AM8/30/15
to Jenkins Developers
I think that all plugins should be renamed to make them self-describable. I would update prefixes in order to reference the product. Examples:
  • google-cloud-health-check
  • google-cloud-backup
  • (google-?) git-notes-publisher (seems to be unrelated to Google, but sometimes companies use such approach for branding)
  • google-analytics-usage-reporter

среда, 26 августа 2015 г., 19:58:38 UTC+3 пользователь Andrey Stroilov написал:

Manuel Jesús Recena Soto

unread,
Aug 30, 2015, 7:17:48 AM8/30/15
to jenkin...@googlegroups.com
Thanks so much for including this
https://github.com/astroilov/google-usage-report-plugin/blob/master/checkstyle.xml

Regards,
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/70036200-14fe-4c70-b542-97fc99ceb670%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
Manuel Recena Soto
* manuelrecena.com [/blog]
* linkedin.com/in/recena

Andrey Stroilov

unread,
Sep 1, 2015, 4:45:39 PM9/1/15
to Jenkins Developers
On Sunday, August 30, 2015 at 2:58:33 AM UTC-7, Oleg Nenashev wrote:
I think that all plugins should be renamed to make them self-describable. I would update prefixes in order to reference the product. Examples:
  • google-cloud-health-check
  • google-cloud-backup
  • (google-?) git-notes-publisher (seems to be unrelated to Google, but sometimes companies use such approach for branding)
  • google-analytics-usage-reporter


Hi Oleg,

For the first two plugins: while they're designed to work well with the Cloud platform, they are not strictly cloud-only plugins; for example, someone could use the backup plugin on a local jenkins instance. Do you still think it should have the "cloud" prefix in the name when it's not restricted to those use cases?

Andrey Stroilov

unread,
Sep 1, 2015, 6:51:00 PM9/1/15
to Jenkins Developers
Generally speaking, whether or not we put in the "cloud" prefix, those names would be fine. Would you like us to update code before or after the new repos are created?

Oleg Nenashev

unread,
Sep 2, 2015, 4:48:11 AM9/2/15
to JenkinsCI Developers
Hi Andrey,

For the first two plugins: while they're designed to work well with the Cloud platform, they are not strictly cloud-only plugins; for example, someone could use the backup plugin on a local jenkins instance. 

From my POV "cloud" is related to the Google Cloud service, with which the plugins are being integrated. I agree that the name may have a double meaning, but hopefully the documentation will clarify it.

According to your comment, I'm going to proceed with the "cloud" prefix.  BTW we can rename repos before the release if we decide to do it..

Would you like us to update code before or after the new repos are created?


--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/lAk9JsXWQL0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ebd57461-c5f0-4e1b-9699-30b189ac77dd%40googlegroups.com.

Andrey Stroilov

unread,
Sep 2, 2015, 3:33:40 PM9/2/15
to Jenkins Developers
Hi Oleg,

Sorry, I wasn't sufficiently specific - with the git-notes plugin, we would prefer to maintain the "google-" prefix. Can we add that to the repo name?
I received the invite; I'll begin transferring the code. Thanks!

Oleg Nenashev

unread,
Sep 3, 2015, 4:49:36 PM9/3/15
to Jenkins Developers
I'll try to rename the repo tomorrow. I realized that IRC bot does not provide such command, so I'll ask somebody with proper permissions on the GitHub org.

среда, 2 сентября 2015 г., 22:33:40 UTC+3 пользователь Andrey Stroilov написал:

Daniel Beck

unread,
Sep 3, 2015, 5:21:30 PM9/3/15
to jenkin...@googlegroups.com
Done: https://github.com/jenkinsci/google-git-notes-publisher-plugin
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b2b983ad-ad4d-40de-a3aa-6e237cdc2f65%40googlegroups.com.

Andrey Stroilov

unread,
Sep 3, 2015, 7:46:06 PM9/3/15
to Jenkins Developers, m...@beckweb.net
Thanks!
Reply all
Reply to author
Forward
0 new messages