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

Arnaud Héritier aheritier at gmail.com
Wed Nov 16 10:16:47 UTC 2016


> We'd need a second user so we can split the tasks, and that is not
allowed.

But technically from what I understand jenkinsadmin isn't allowed too ?

Maybe we could ask the permission to github ?

Otherwise we can just move to a self-hosted GitLab on Azure :-)

On Wed, Nov 16, 2016 at 1:32 AM, Daniel Beck <ml at beckweb.net> wrote:

>
> > On 16.11.2016, at 00:04, Ben Walding <bwalding at cloudbees.com> wrote:
> >
> > 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.
>
> Yes, and that single user -- jenkinsadmin -- is used for both
> ci.jenkins.io and the JIRA integration, and reaches the API limit. So
> that doesn't help at all.
>
> We'd need a second user so we can split the tasks, and that is not allowed.
>
> _______________________________________________
> Jenkins-infra mailing list
> Jenkins-infra at lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>



-- 
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20161116/df084a40/attachment-0001.html>


More information about the Jenkins-infra mailing list