Hi, Jenkins is not only a tool. It also an ecosystem and infrastructure see https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document . We host plugin sources in github and built from them binaries in binary repository to have available plugins in jenkins Update Center. Committed /target and any binary files in VCS (especially in git) is a poor indicator of development knowledge. If you want host final .hpi - you may create separate github repo and pollute it with binaries (or GH created something for releases some time ago?). Not all plugins makes sense to host under jenkins infra, many things maybe and must be extended in current plugins. If you have some generic part, then create "Extension point".
Artifactory support multiple repositories... btw have somebody asked jfrog about input plugin for jenkins? Maybe they want develop and support it...? On Wednesday, November 5, 2014 8:26:22 PM UTC+3, Jonathan McAllister wrote: > > Im not sure i see value in that train of thought. Most Jenkins users > (myself included) dont want to spend hours trying to hack something to > almost work the way they want. Ill post this as an added improvement to the > artifactory jfrog company directly then. > > On Nov 05, 2014, at 09:17 AM, "Larry Shatzer, Jr." <[email protected] > <javascript:>> wrote: > > Mine has a default regex, it just allows you to override it (there was a > specific use case that I can't remember). > > I'm not rejecting it, I was just bringing up mine, since there are a few > people who want to keep the number of plugins that are similar to a low > number. > > On Wed, Nov 5, 2014 at 10:07 AM, Jonathan McAllister <[email protected] > <javascript:>> wrote: > >> ArtifactoryDownloadLinks dosent require any regex or special searching it >> just works OOB. Either way its not a big deal to me. Feel free to merge the >> two if you like. I am content with what I implemented is very simplistic >> and i thought it might help others. Thats the ONLY reason i offered it up >> as opensource. If the community wishes to reject it thats their decision. >> >> >> >> On Nov 05, 2014, at 09:01 AM, "Larry Shatzer, Jr." <[email protected] >> <javascript:>> wrote: >> >> Mine links to them on the build info page (in my case, in a Nexus >> repository). That was the first use case, others added the ability to use >> for input for dependency management type activities. >> >> I just thought I'd bring up mine, to see if the two could be merged, and >> avoid an explosion of plugins. >> >> On Wed, Nov 5, 2014 at 9:56 AM, Jonathan McAllister <[email protected] >> <javascript:>> wrote: >> >>> This plugin executes as a post build task. With no options specifically >>> for reg-ex it simply searches for published modules/packages to artifactory >>> (as part of the post build execution) and links to those directly in the >>> build info page. This is not designed for dependency management (input) >>> but rather serves a similar function to 'Archive Artifacts' but instead of >>> copying the files to some random location on the jenkins server it links >>> directly to those that were uploaded to Artifactory.. >>> >>> I wrote this plugin as a need for a business and thought id share. If >>> the community wishes to reject such no problem with me as this filled a >>> need I had.. >>> >>> It looks like yours is for resolving dependencies not build output >>> packages. >>> >>> On Nov 05, 2014, at 08:37 AM, "Larry Shatzer, Jr." <[email protected] >>> <javascript:>> wrote: >>> >>> While my plugin has Maven in the name, it will also accept a regex to >>> scan for. I would rather see any improvements made to my plugin to support >>> more usecases then seeing multiple plugins doing effectively the same >>> thing, just in a slightly different way. >>> >>> On Wed, Nov 5, 2014 at 9:28 AM, Jonathan McAllister <[email protected] >>> <javascript:>> wrote: >>> >>>> Its similar yes. Although the artifacts at the places I am at are not >>>> java dependencies. They are deb packages or tar balls or zips. This simply >>>> puts a link directly in Jenkins build info (each build) to the artifactory >>>> packages that were uploaded as part of the build. This removes the need >>>> for the user to navigate through to artifactory to download the build >>>> output . >>>> >>>> On Nov 05, 2014, at 07:57 AM, "Larry Shatzer, Jr." <[email protected] >>>> <javascript:>> wrote: >>>> >>>> This looks a lot like my Maven Deployment Linker plugin, but specific >>>> for Artifactory? >>>> >>>> https://wiki.jenkins-ci.org/display/JENKINS/Maven+Deployment+Linker >>>> >>>> >>>> >>>> On Wed, Nov 5, 2014 at 8:20 AM, Jonathan McAllister <[email protected] >>>> <javascript:>> wrote: >>>> >>>>> Hello would like to get my plugin hosted: >>>>> >>>>> - Artifactory Download Links >>>>> - GitHub ID: KineticX >>>>> - Author: Jonathan McAllister >>>>> - >>>>> https://github.com/KineticX/Jenkins.Plugin.ArtifactoryDownloadLinks.git >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> 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 [email protected] <javascript:>. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>>> -- >>>> 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 [email protected] <javascript:>. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>>> >>>> -- >>>> 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 [email protected] <javascript:>. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> -- >>> 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 [email protected] <javascript:>. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- >>> 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 [email protected] <javascript:>. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> -- >> 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 [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> 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 [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > 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 [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
