[Jenkins-infra] Heads Up: JIRA DVCS integration disabled on issues.jenkins-ci.org

Ben Walding bwalding at cloudbees.com
Tue Nov 15 23:04:26 UTC 2016


Yes, against their written terms of service in that section.


But see this caveat:

https://developer.github.com/guides/managing-deploy-keys/ - bottom of the
page:

Tip: Our terms of service state:

Accounts registered by "bots" or other automated methods are not permitted.

This means that you cannot automate the creation of accounts. But if you
want to create a single machine user for automating tasks such as deploy
scripts in your project or organization, that is totally cool.

On 16 November 2016 at 06:51, R. Tyler Croy <tyler at monkeypox.org> wrote:

> (replies inline)
>
> On Tue, 15 Nov 2016, Oleg Nenashev wrote:
>
> > Cold we just use a separate GitHub account for JIRA?
> > This integration is generally useful.
>
>
> That would be against the GitHub terms of service
> https://help.github.com/articles/github-terms-of-service/#a-account-terms
>
>
>
> - R. Tyler Croy
>
> ------------------------------------------------------
>      Code: <https://github.com/rtyler>
>   Chatter: <https://twitter.com/agentdero>
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> ------------------------------------------------------
>
> _______________________________________________
> Jenkins-infra mailing list
> Jenkins-infra at lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>
>


-- 
Ben Walding
bwalding at cloudbees.com
Operations Manager

*CloudBees, Inc.*
www.cloudbees.com
<https://www.cloudbees.com/>
*software at the speed of ideas*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20161116/b3690efc/attachment.html>


More information about the Jenkins-infra mailing list