yes, access is restricted - not actually that we don't want you to access
the instance (if you need, I can grant you access) but this would be useful
only if you need to create a custom job (typically : for a ruby or
gradle-based plugin).

The plugin's jobs are set by a template, so that you only have to provide
the plugin name "email-ext-plugin" and everything is magically setup - so
creating CI jobs for plugin can be fully automated by infra jobs, crawling
the jenkinsci github organization for new plugins.

I've fixed the OOME issue, see
https://jenkins.ci.cloudbees.com/job/plugins/job/email-ext-plugin/105/console(and
related pull request)



2013/10/14 Mike Caspar <[email protected]>

> Hi Nicolas,
>
> I will read through those notes... I've been here only a month so still
> learning my way around.
>
> I'll adjust the POM to use the new CI settings and recommit a new version
> after some upgraded features.
>
> I've already gone and adjusted the WIKI page so it doesn't link to the
> hives location and show with errors.  (It had the badge for instance and a
> link to the old CI).
>
> When I try and login at the new CI location, I am denied access.  Should
> I to assume that access to our maintained apps is not available on the CI
> server and is restricted somehow?
>
> If just would like to know if I'm trying to do get access to something
> that's restricted or if something is wrong.
>
> Thanks for the guidance.
>
> Mike
>
>
>
> On Monday, October 14, 2013 11:43:14 AM UTC-4, nicolas de loof wrote:
>
>> Hi Mike,
>>
>> jenkins.ci.cloudbees.com instance is indeed designed to support plugin
>> development and other community jobs (to reduce load on ci.jenkins-ci.org
>> )
>>
>> This instance was set > 1 year ago, just got buildhive active as a
>> duplicate CI, I just disabled it this morning (see imod mail earlier on
>> jenkins-dev list)
>>
>> https://jenkins.ci.cloudbees.**com/job/plugins/job/ironmq-**
>> notifier-plugin/<https://jenkins.ci.cloudbees.com/job/plugins/job/ironmq-notifier-plugin/>is
>>  stable, so I think there's nothing much required here, isn't it ?
>>
>>
>> 2013/10/14 Mike Caspar <[email protected]>
>>
>>>  Hi there,
>>>
>>> I'm hoping someone can help.
>>>
>>> The other day, the builds got moved to https://jenkins.ci.**
>>> cloudbees.com <https://jenkins.ci.cloudbees.com>
>>>
>>> My project  ironmq-notifier got moved as part of that.
>>>
>>> A few things are going on and I'm looking for some help.
>>>
>>> 1 - I cannot login at 
>>> https://jenkins.ci.**cloudbees.com<https://jenkins.ci.cloudbees.com>with my 
>>> github account (or my email address)...
>>>
>>> 2 - The buildhive project that I've been using is completely gone (it
>>> has effected the WIKI page Logos and badges)..
>>>
>>> Can someone please allow me to authenticate to the plugin I'm
>>> maintaining.   I want to be able to fix up what's wrong now.
>>>
>>> Also, I'd like to know, do we need to change the CI section of our POMs
>>> now ?
>>>
>>> Can someone please help me out here ?
>>>
>>> Mike Caspar
>>>
>>>
>>>  --
>>> 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-de...@**googlegroups.com.
>>>
>>> For more options, visit 
>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
>>> .
>>>
>>
>>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Reply via email to