Yes, I added them using the GitHub UI. Somehow the bot produces the new error 
„User isn't a member of this organization. Please invite them first“. Or is 
this a change in the GitHub API? You already noted that in 
https://issues.jenkins-ci.org/browse/INFRA-142.

Am 08.10.2014 um 08:35 schrieb Oleg Nenashev <o.v.nenas...@gmail.com>:

> Ulli,
> 
> Did you add users to the organization manually?
> //I'm waiting for a test project to start working on 
> https://issues.jenkins-ci.org/browse/INFRA-142
> 
> Best regards,
> Oleg Nenashev
> 
> 
> 
> 
> 2014-10-08 1:59 GMT+04:00 Ulli Hafner <ullrich.haf...@gmail.com>:
> Done.
> 
> Am 07.10.2014 um 15:57 schrieb Anthony DeMartini <anthony.demart...@avi.com>:
> 
>> Currently I don’t have access to the code dx plugin on github:
>> 
>>  
>> https://github.com/jenkinsci/codedx-plugin
>> 
>>  
>> 
>> My username is ademartini.  In addition to myself, please add the following 
>> other users:
>> 
>>  
>> 
>> dylemma
>> 
>> KenProle
>> 
>> leRadwan
>> 
>> baffles
>> 
>>  
>> Thank You,
>> 
>>  
>> Anthony
>> 
>> From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] 
>> On Behalf Of Anthony DeMartini
>> Sent: Monday, October 06, 2014 5:53 PM
>> To: jenkinsci-dev@googlegroups.com
>> Subject: RE: New Plugin Request
>> 
>>  
>> 
>> Oleg,
>> 
>>  
>> Thank you!  But it looks like I don’t have write access to the repo.
>> 
>>  
>> Kind Regards,
>> 
>>  
>> Anthony
>> 
>>  
>> From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] 
>> On Behalf Of Oleg Nenashev
>> Sent: Monday, October 06, 2014 5:47 PM
>> To: JenkinsCI Developers
>> Subject: Re: New Plugin Request
>> 
>>  
>> 
>> The repository has been created: https://github.com/jenkinsci/codedx-plugin
>> 
>> Please confirm you got group membership invitations (Just2check the behavior)
>> 
>>  
>> 
>> 2014-10-07 0:21 GMT+04:00 Anthony DeMartini <anthony.demart...@avi.com>:
>> 
>> We would like to setup hosting for our plugin:
>> 
>>  
>> 
>> GroupId: org.jenkins-ci.plugins
>> 
>>  
>> 
>> ArtifactId: codedx
>> 
>> GitHub: https://github.com/secdec/codedx-jenkins-plugin
>> 
>> User: ademartini
>> 
>>  
>> 
>>  
>> 
>> Thank You,
>> 
>>  
>> 
>> Anthony DeMartini
>> 
>>  
>> 
>> From: Anthony DeMartini 
>> Sent: Monday, September 29, 2014 10:15 AM
>> To: 'Oleg Nenashev'; jenkinsci-dev@googlegroups.com
>> Subject: RE: New Plugin Request
>> 
>>  
>> 
>> Oleg,
>> 
>>  
>> 
>> Yes there are other possible use cases.  We are exploring getting data from 
>> the server to show statistics inside of Jenkins, as well as other possible 
>> usages.
>> 
>>  
>> 
>> Thank You,
>> 
>>  
>> 
>> Anthony
>> 
>>  
>> 
>> From: Oleg Nenashev [mailto:o.v.nenas...@gmail.com] 
>> Sent: Saturday, September 27, 2014 12:56 PM
>> To: jenkinsci-dev@googlegroups.com
>> Cc: Anthony DeMartini
>> Subject: Re: New Plugin Request
>> 
>>  
>> 
>> Hello Anthony,
>> 
>> Are there any other possible use-cases excepting the pyblishing to your 
>> server?
>> If no, what about changing the plugin's name to codedx-publisher?
>> 
>> Best regards,
>> Oleg Nenashev
>> 
>> пятница, 26 сентября 2014 г., 22:50:58 UTC+4 пользователь Anthony DeMartini 
>> написал:
>> 
>> Greetings,
>> 
>>  
>> 
>> I’m with the CodeDx development team at Secure Decisions 
>> (http://codedx.com/) and we are developing a plugin for Jenkins to publish 
>> builds to our software assurance analysis tool.  Our current plugin is 
>> located here:
>> 
>>  
>> 
>> https://github.com/secdec/codedx-jenkins-plugin
>> 
>>  
>> 
>> and my github handle is ademartini.
>> 
>>  
>> 
>> We have chosen a groupid of org.jenkins-ci.plugins and an artifactid of 
>> codedx.  From the documentation it looks like the next step would be to move 
>> our code into the Jenkins github area.  We are not necessarily opposed to 
>> this but want to know if there are any limitations if we were to keep our 
>> code in its current github repo.  Would we still be able to publish it and 
>> have a wiki page and be listed as an official plugin?
>> 
>>  
>> 
>> Thank You,
>> 
>> Anthony DeMartini 
>> 
>> --
>> 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/jenkinsci-dev/9eo-3-5pD2A/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-dev+unsubscr...@googlegroups.com.
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to