On Wed, Nov 5, 2014 at 12:20 PM, Jonathan McAllister <[email protected]> wrote: > The repo/target folder contains the compiled HPI and JAR thats the size > majority. I wasnt sure the methodology of how users would consume the plugin > in its final state.
You would run mvn release:prepare release:perform to deploy it, where the Jenkins update center would pick it up. It is quite reasonable to request that repos forked to @jenkinsci be free of major build products in the history. Many people (myself included) do clone _all_ plugin repos and they need to stay free of large binaries. Anyway this is quite easy to do: http://rtyley.github.io/bfg-repo-cleaner/ (Looks like ‘--delete-folders target’ is what you want here.) -- 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.
