[JIRA] [build-name-setter-plugin] (JENKINS-21270) Add licenses to jenkins core and plugins
Title: Message Title Tom Van Eyck updated an issue Jenkins / JENKINS-21270 Add licenses to jenkins core and plugins Change By: Tom Van Eyck Component/s: build-name-setter-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-name-setter-plugin] (JENKINS-21270) Add licenses to jenkins core and plugins
Title: Message Title Tom Van Eyck updated an issue Jenkins / JENKINS-21270 Add licenses to jenkins core and plugins Change By: Tom Van Eyck Hi all,we use Jenkins and quite a few of its plugins in our organization. Due to legal reasons we are required to keep track of which licenses any software we use falls under. Generally this is pretty easy.However, I'd estimate that less than half of the Jenkins core and plugin components that we use has clear license info (e.g. a license file in a github repo or a license mentioned on http://maven-repository.com). Would it be possible to have a look at this? Or is there perhaps an implicit license that applies when no license is specified?The following plugins are ones that I'm having trouble finding a license for:ruby-runtime plugin https://github.com/jenkinsci/ruby-runtime-plugingit plugin https://github.com/jenkinsci/git-pluginemail-ext pluginhttps://github.com/jenkinsci/email-ext-pluginrvm plugin https://github.com/jenkinsci/rvm-plugingithub api plugin https://github.com/jenkinsci/github-api-plugingit client plugin https://github.com/jenkinsci/git-client-pluginhtml publisher plugin https://github.com/jenkinsci/htmlpublisher-pluginmaven project pluginhttps://github.com/jenkinsci/maven-plugin/tree/mastermultijob plugin https://github.com/jenkinsci/tikal-multijob-pluginparameterized trigger pluginhttps://github.com/jenkinsci/parameterized-trigger-plugintimestamper plugin https://github.com/jenkinsci/timestamper-plugintoken macro plugin https://github.com/jenkinsci/token-macro-plugin build name setter plugin https://github.com/jenkinsci/build-name-setter-plugin What would be the correct way to go about collecting license information for these? I've opened a few pull requests on github with licensing info for these, but was told that writing a JIRA ticket like this might yield better results.Many thanks,Tom Add Comment
[JIRA] [email-ext] (JENKINS-21270) Add licenses to jenkins core and plugins
Tom Van Eyck created JENKINS-21270 Add licenses to jenkins core and plugins Issue Type: Improvement Assignee: Alex Earl Components: email-ext, git, git-client, github-api, htmlpublisher, maven, maven2, next-build-number, parameterized-trigger, ruby-runtime, rvm, timestamper, token-macro Created: 08/Jan/14 11:55 AM Description: Hi all, we use Jenkins and quite a few of its plugins in our organization. Due to legal reasons we are required to keep track of which licenses any software we use falls under. Generally this is pretty easy. However, I'd estimate that less than half of the Jenkins core and plugin components that we use has clear license info (e.g. a license file in a github repo or a license mentioned on http://maven-repository.com). Would it be possible to have a look at this? Or is there perhaps an implicit license that applies when no license is specified? The following plugins are ones that I'm having trouble finding a license for: ruby-runtime plugin https://github.com/jenkinsci/ruby-runtime-plugin git plugin https://github.com/jenkinsci/git-plugin email-ext pluginhttps://github.com/jenkinsci/email-ext-plugin rvm plugin https://github.com/jenkinsci/rvm-plugin github api plugin https://github.com/jenkinsci/github-api-plugin git client plugin https://github.com/jenkinsci/git-client-plugin html publisher plugin https://github.com/jenkinsci/htmlpublisher-plugin maven project pluginhttps://github.com/jenkinsci/maven-plugin/tree/master multijob plugin https://github.com/jenkinsci/tikal-multijob-plugin parameterized trigger pluginhttps://github.com/jenkinsci/parameterized-trigger-plugin timestamper plugin https://github.com/jenkinsci/timestamper-plugin token macro plugin https://github.com/jenkinsci/token-macro-plugin What would be the correct way to go about collecting license information for these? I've opened a few pull requests on github with licensing info for these, but was told that writing a JIRA ticket like this might yield better results. Many thanks, Tom Project: Jenkins Priority: Major Reporter: Tom Van Eyck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13590) Trigger build when new pull request occurs in github
Tom Van Eyck commented on JENKINS-13590 Trigger build when new pull request occurs in github I've also written a Ruby app that does the same thing as Travis does: https://github.com/vaneyckt/Jently This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
