Request to host plugin: delphix-jenkins-plugin

[Peter Vilim]

Hello everyone!

First time doing this, and I'm doing this based off the wiki.  I have
a plugin that I would like to be hosted on jenkins-ci.org.

The plugin interacts with the Delphix Engine which is the core product
that my company sells.  Our product allows for customers to spin up
virtual copies of their production databases that take no additional
space and changes to those databases are stored as a diff.  The
virtual databases can be rewound, fast forwarded, in a manner somewhat
similar to source control.  As a result a lot of our customers like to
use our product with Jenkins and have Jenkins spin up virtual
databases as part of test runs that can be tested against and then
destroyed when the run completes.

This plugin adds a couple build steps that give Jenkins the ability to
make API calls to our engines deployed at customer sites to perform
some of the operations that I just described.  It also has niceties
such as including log output from our engine in the Jenkins logs so
that if a job on our engine fails the logs can be inspected in Jenkins
to figure out what went wrong as well as clean up on our engine if a
Jenkins job gets aborted mid-run.

The plugin is located here and having the same repository name is fine
with me: https://github.com/delphix/delphix-jenkins-plugin

It is licensed under the open source Apache 2.0 license.

My github id is: peterlvilim.  My jenkins-ci.org username is: peterlvilim

Happy to answer any questions.

[Daniel Beck]

Hi Peter,

I suggest renaming this (both display name and artifact ID) to delphix-plugin -- 'jenkins' is redundant in this context.

Also, you should probably make the license you're publishing this under explicit.

Daniel

> -Peter
>
> --
> 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/fd9a32b4-3f38-4b37-ab68-443cd23cd530%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Peter Vilim]

That makes sense.  Could I get the name to be delphix-plugin for the repository in the jenkinsci organization and keep the current name for the repository on our company github since it does make sense on our company github?

I have the LICENSE folder in the root of the git repository, and I mentioned in my previous post that it was Apache 2.0.  Was there something else you were looking for?

Thanks.

-Peter

[Daniel Beck]

On 19.10.2015, at 20:44, Peter Vilim <peter...@gmail.com> wrote:

> That makes sense. Could I get the name to be delphix-plugin for the repository in the jenkinsci organization and keep the current name for the repository on our company github since it does make sense on our company github?

Yes. Note that in Gradle (at least regular Java builds, haven't looked into Gradle for Jenkins plugins) the folder name is the project name, unless overridden in settings.gradle -- so you need to make sure that's always delphix-plugin.

> I have the LICENSE folder in the root of the git repository, and I mentioned in my previous post that it was Apache 2.0. Was there something else you were looking for?

My bad, I missed those. Maybe adapt the license header in the source files?

Daniel

[Peter Vilim]

I have updated the source files to include the Apache 2.0 copyright header.

I also modified the shortName in the build.gradle which overrides the directory name and set it to be delphix-plugin.  I also verified that the plugin that was produced had the name delphix-plugin.hpi after building.

[Peter Vilim]

Thought I'd bump this and check if I should do anything else since I haven't heard anything for about a week.  Thanks!

[Peter Vilim]

Bumping this again since there hasn't been any activity in over a week and it has been a couple weeks since I submitted the request.  Should I email someone about this?  Thanks.

[Daniel Beck]

On 03.11.2015, at 02:29, Peter Vilim <peter...@gmail.com> wrote:

> Bumping this again since there hasn't been any activity in over a week and it has been a couple weeks since I submitted the request. Should I email someone about this? Thanks.

Sorry about the delay! We're working on a new process that should prevent requests from falling through the cracks, but it's not done yet.

I forked the repo to https://github.com/jenkinsci/delphix-plugin and create delphix-plugin in issues.jenkins-ci.org and made you lead/default assignee.

By convention, plugin IDs skip the '-plugin' suffix. E.g. 'Git Plugin' -> 'git'; 'Subversion Plugin' -> 'subversion', etc. ... so 'delphix' would be better. It's just the repo and JIRA component that get the suffix.

Remember to point the build.gradle to the jenkinsci repo as well.

Ideally, the wiki page gets a less 'technical' title once you create it, e.g. "Delphix Plugin". Note that without the wiki page referenced in the pom, the plugin will not show on the update center.

Daniel

[Peter Vilim]

Thanks!  I went through the publish steps and am waiting for it to show up in the list of plugins (says it could take up to 8 hours in docs).  Will let you know if I run into any problems.

-Peter