Plugin Hosting Request - drupal

[Fengtan]

Plugin Repo: https://github.com/fengtan/drupal-plugin

Plugin Name: drupal-plugin

Jenkins-Ci.org User: fengtan

Description: A plugin to review code and run tests on Drupal. Results can be published using Checkstyle and JUnit. It is already possible to do this using a Shell builder and/or the Phing Drush Task. What this plugin provides is a user-friendly interface to configure things in a few clicks right in the Jenkins interface.

[Oleg Nenashev]

Could you explain a use case of the plugin? Is it designed for the Drupal core development only or for the easy Drupal plugins CI? 

понедельник, 24 августа 2015 г., 20:22:52 UTC+3 пользователь Fengtan написал:

[Fengtan]

Here is a use case: you have developed a custom Drupal module for your client and you want to make sure that the code complies with Drupal standards and does not contain security flaws.

The plugin is designed for any Drupal module, whether they are core modules, contrib modules, or custom modules.

[Oleg Nenashev]

OK, thanks for the explanation!

I think it would make sense to rename the plugin to drupal-module-dev-plugin or something like that. I think that other Drupal plugins may appear later, hence the name seems to be too generic for me.

--
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/5ZKATly3T6o/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/c2a52e1a-bc99-4996-ad2d-63de8ffc5b9d%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Daniel Beck]

On 26.08.2015, at 23:16, Oleg Nenashev <o.v.ne...@gmail.com> wrote:

> OK, thanks for the explanation!
>
> I think it would make sense to rename the plugin to drupal-module-dev-plugin or something like that. I think that other Drupal plugins may appear later, hence the name seems to be too generic for me.

Like a plugin that publishes reports to Drupal or something? I agree.

'Drupal Developer Plugin' (or '… Development …) perhaps? Would be a slightly nicer name than what you suggest.

[Fengtan]

Sure, that makes sense.

The plugin is able to review code in modules but also in themes and installation profiles so maybe 'drupal-module-dev-plugin' is a bit too specific.

Maybe 'drupal-developer-plugin' as Daniel suggests ?

[Oleg Nenashev]

Agreed

--
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/5ZKATly3T6o/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/1dc74f52-dbd8-4915-a4d0-f61b267161bb%40googlegroups.com.

[Oleg Nenashev]

The repository has been forked + I’ve created a component on Jenkins JIRA.

You should receive an invitation to Jenkins CI organization soon.

https://github.com/jenkinsci/drupal-developer-plugin

Best regards,

Oleg

[Daniel Beck]

On 27.08.2015, at 14:37, Fengtan <fengt...@gmail.com> wrote:

> Maybe 'drupal-developer-plugin' as Daniel suggests ?

Remember to rename the plugin in the POM as well before your first release.

https://github.com/jenkinsci/drupal-developer-plugin/blob/master/pom.xml#L14 should be 'drupal-developer'.