[Plugin Hosting Request] plugin for executing Tests with testing tool TPT
Joachim Kuhnert
Hello,
We like to host our Jenkins-Plugin on the official Jenkins-website. Here is the requested data:
GitHub-URL: https://github.com/PikeTec/tpt-jenkins
Repository-Name: piketec-tpt-plugin
jenkins-ci.org user name: piketec
Description:
TPT is a tool for testing and verifying model based control systems like ASCET, MATLAB/Simulink, AUTOSAR developed by PikeTec GmbH. Our customers are mainly from the automotive sector. The plugin enables Jenkins to execute tests and publish the test results from TPT. Please let me know if you need further information.
Best regards,
Joachim Kuhnert
---------------------------------------------------
Joachim Kuhnert
fon: +49 30 394 09 683 39
PikeTec GmbH, Waldenserstr 2-4, 10551 Berlin
Geschäftsführer: Eckard Bringmann, Andreas Krämer, Jens Lüdemann
Sitz der Gesellschaft: Berlin
Handelsregister: Amtsgericht Berlin HRB 105491 B
Joachim Kuhnert
Hello everybody,
I do not want to seem impatient but I would love to get any answer or a hint how long I should wait for one. I know, this plugin has a very small target group and I could totally understand if you do not want to host it, but then please just say so.
Best Regards,
Joachim
---------------------------------------------------
Joachim Kuhnert
fon: +49 30 394 09 683 39
PikeTec GmbH, Waldenserstr 2-4, 10551 Berlin
Geschäftsführer: Eckard Bringmann, Andreas Krämer, Jens Lüdemann
Sitz der Gesellschaft: Berlin
Handelsregister: Amtsgericht Berlin HRB 105491 B
Daniel Beck
I'm actually not sure how to proceed here.
I don't think we've considered the size of the target audience before, other than rejecting clearly 'private use' plugins (indicated by hardcoded non-public host names etc.). That's not what this is, but I still wonder if the installation count of this ever goes into the triple (double?) digits.
Additionally, I wonder how useful it is to have this part of an international open-source community. The documentation is in German, and I would expect all users of your plugin to work for traditionally less OSS-minded companies, so I don't know what to expect here wrt community involvement.
Could you give us some idea how much this plugin would be used and evolve? I'm not rejecting this (I don't think we have any requirements like what I'm asking above), just trying to understand your goal. It may turn out the best option for you would be hosting an update center yourself. It's basically a JSON file and the plugin HPI/JPI files you want to offer.
Daniel
> 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/601BB6FDC49648489C8BE0671860E03A0AD5F2%40VS2.piketec.local.
> For more options, visit https://groups.google.com/d/optout.
Joachim Kuhnert
thank you for your response. Our main goal would be that customers who already use Jenkins can find and install our plugin easily so it will get a wider distribution. If we were hosting our own update center we have to host all other interesting (however we decide which are interesting) plugins for our customers if I understand it right. I do not think, that the effort is justified, because we do not expect a very high installation count as said before. Additionally they have to configure Jenkins to use our update center.
To be honest, at the moment I would hope for a low double digit installation count.
You are right to question the usefulness of having this plugin in an open-source community. A small target group means that there are not much contributors to be expected and Jenkins and the community itself would only benefit by small reputation increase if at all. Personally I do not see benefits for other people than our customers. The code does not do something special others want to use.
If we are accepted the documentation would be translated into English and the code has to be revised because it is built against an outdated Jenkins version. The main contributor would be us and perhaps some of our customers. We are hoping that there will be more interested in our plugin if it is easier to access and therefore we get more change requests.
TL,DR
Goal: Easier access and therefore more interest in our plugin for and from our customers.
Questionable: Usefulness of and for Jenkins community.
Best regards,
---------------------------------------------------
Joachim Kuhnert
fon: +49 30 394 09 683 39
PikeTec GmbH, Waldenserstr 2-4, 10551 Berlin
Geschäftsführer: Eckard Bringmann, Andreas Krämer, Jens Lüdemann
Sitz der Gesellschaft: Berlin
Handelsregister: Amtsgericht Berlin HRB 105491 B
Von: jenkin...@googlegroups.com [mailto:jenkin...@googlegroups.com] Im Auftrag von Daniel Beck
Gesendet: Freitag, 10. Juli 2015 12:58
An: jenkin...@googlegroups.com
Betreff: Re: [Plugin Hosting Request] plugin for executing Tests with testing tool TPT
Daniel Beck
> If we were hosting our own update center we have to host all other interesting (however we decide which are interesting) plugins for our customers if I understand it right.
> I do not think, that the effort is justified, because we do not expect a very high installation count as said before. Additionally they have to configure Jenkins to use our update center.
Their example also shows you how small a supplementary update center can be: https://form.blackducksoftware.com/bdosvr-jenkins-update/update-center.json
> If we are accepted the documentation would be translated into English and the code has to be revised because it is built against an outdated Jenkins version. The main contributor would be us and perhaps some of our customers. We are hoping that there will be more interested in our plugin if it is easier to access and therefore we get more change requests.
Christopher Orr
When I first saw this request (plus similar requests recently, and
issues with closed-source plugins), it made me think that the Jenkins
Plugin Manager UI should support multiple update centres (UCs) out of
the box, rather than developers having to write a plugin just to add a
new UC.
Much like adding a third-party UC to IntelliJ or Eclipse, users could
just paste a URL directly into Jenkins. The UC metadata would be
fetched, Jenkins would then say something like "are you sure you want to
add the <name from metadata> update centre with certificate <UC public
certificate info>", and that would be it.
I guess that's basically a nicer, built-in version of the UpdateSites
Manager plugin.
That would prevent the project from having to host plugins that do
nothing other than point people at a closed source update centre
elsewhere, and would make it easier for people to host niche plugins.
Wishful thinking, I know :)
Regards,
Chris
evernat
If you do not want to create an update center, another way would be to just create a release and upload binary artifact there:
https://github.com/PikeTec/tpt-jenkins/releases
Then you can explain in README.md with screenshot how users can install your plugin in the Advanced tab of the Plugin Manager: that's easy for them and without restart.
For my part, I doubt that adding this niche plugin in the update center would do more good than harm:
- a lot of people would ask themselves if the plugin is useful for their needs,
- there are already 70% of the plugins in the update center which are used by less than 1% of the Jenkins installations.
My 2 cents,
Emeric
Joachim Kuhnert
Hello,
I do not think that the plugin in will do much harm by confusing people. They would figure out the usefulness of this plugin for them very fast, because its functionality is not hard to understand.
The second point that there are already 70% niche plugins let me wonder why this plugin should be rejected because it belongs to this group. If you do not like to host plugins with a very small target group anymore and want to introduce a new hosting requirement, ok I understand it and at some point you have to begin to handle it this way. I just want to make sure that this will not be the reason to reject this individual plugin after I had two (cautious) approvals. It will be just more convenient to have it in the update center.
I think the most harm our plugin would do is using up a little disk additional disk space and when a customer downloads it a bit traffic.
Kind Regards,
Joachim
---------------------------------------------------
Joachim Kuhnert
fon: +49 30 394 09 683 39
PikeTec GmbH, Waldenserstr 2-4, 10551 Berlin
Geschäftsführer: Eckard Bringmann, Andreas Krämer, Jens Lüdemann
Sitz der Gesellschaft: Berlin
Handelsregister: Amtsgericht Berlin HRB 105491 B
Von: jenkin...@googlegroups.com [mailto:jenkin...@googlegroups.com]
Im Auftrag von evernat
Gesendet: Samstag, 11. Juli 2015 11:40
An: jenkin...@googlegroups.com
Betreff: Re: [Plugin Hosting Request] plugin for executing Tests with testing tool TPT
Hi,
--
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/a7ed160e-d709-4ea7-8ce9-22d714808957%40googlegroups.com.
Daniel Beck
it looks like I was just overthinking this.
https://github.com/jenkinsci/piketec-tpt-plugin
Welcome aboard!
Daniel
evernat
I did not intend to reject your plugin, but to remind that:
- In my opinion, it's difficult to find which plugins could be used by people, among more than 1000 plugins in the update center (more is not always better). For once, you were honest to say that your plugin is a niche plugin.
- And your plugin could be distributed another way.
Anyway, you are in now.
Welcome !
- Emeric
Joachim Kuhnert
Thank you both for the warm welcome,
Just to clear it up I do not feel to be attacked by you, Emeric. Yours was just the most critical voice and so I felt I have to comment. After all my goal was to get the plugin accepted. ;-)
Kind Regards,
Joachim
---------------------------------------------------
Joachim Kuhnert
fon: +49 30 394 09 683 39
PikeTec GmbH, Waldenserstr 2-4, 10551 Berlin
Geschäftsführer: Eckard Bringmann, Andreas Krämer, Jens Lüdemann
Sitz der Gesellschaft: Berlin
Handelsregister: Amtsgericht Berlin HRB 105491 B
Von: evernat [mailto:eve...@free.fr]
Gesendet: Freitag, 17. Juli 2015 13:41
An: jenkin...@googlegroups.com
Cc: Joachim Kuhnert
Betreff: Re: [Plugin Hosting Request] plugin for executing Tests with testing tool TPT
Hi Joachim,