jieryn found an e-mail from Tyler that explains why he disabled that
job. I understand that your change of making it use authenticated token
would help us around the rate limitation.
I haven't looked at the code carefully, but I wonder if using our "all"
repository [1] is going to help us further reduce the GitHub API call
and make the report that much faster to run.
[1] http://git.jenkins-ci.org/?p=all.git;a=summary
On 08/05/2013 11:54 AM, Kohsuke Kawaguchi wrote:
My apologies for letting this fall through the cracks.
I've changed the job configuration to use RepoInfo.txt, I've added the
github token, and I've also tweaked the permission so that you have the
write access to this job's configuration. We shouldn't be getting in
your way or making changes!
If there are more things you need to prevent us from getting in your
way, please let me know.
On 08/05/2013 11:31 AM, Kohsuke Kawaguchi wrote:
Oops, let me resurrect the job.
I'm not sure why it was disabled, but I suspect it was unintended.
I'm getting to your "Re: Backend: Unreleased Plugin Changes" thread now.
On 08/05/2013 10:17 AM, Jan Ruzicka wrote:
Hi
Can somebody delete the Unreleased Plugin Changes page[1]?
Apparently there is no interest about keeping this information and it is
getting outdated.
The job on ci.jenkins-ci.otg responsible for generating this page was disabled
without any explanation last week.
Requests for configuration changes were ignored since March.
Rather then just confusing users/developers with outdated information, that
nobody looks at anyway, delete the page and related job.
Sincerely
Jan
[1] https://wiki.jenkins-ci.org/display/JENKINS/Unreleased+Plugin+Changes
Jan Ruzicka
Senior Software Engineer
Comtech Mobile Datacom Corporation
20430 Century Blvd, Germantown, MD 20874
Office: 240-686-3300
Fax: 240-686-3301
The information contained in this message may be privileged and/or
confidential. If you are not the intended recipient, or responsible for
delivering this message to the intended recipient, any review, forwarding,
dissemination, distribution or copying of this communication or any
attachment(s) is strictly prohibited. If you have received this message in
error, please so notify the sender immediately, and delete it and all
attachments from your computer and network.
--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins
--
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.
--- Begin Message ---
_______________________________________________
Jenkins-infra mailing list
[email protected]
http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
<https://ci.jenkins-ci.org/job/infra_plugin_changes_report/>
I disabled it, it appears that
(https://ci.jenkins-ci.org/job/infra_plugin_changes_report/253/console) it was
getting rate limited/screwed by the GitHub API.
I'm not sure who's responsible for that job, but it's going to get our IPs
banned from GitHub...
- R. Tyler Croy
--------------------------------------
Code: https://github.com/rtyler
Chatter: https://twitter.com/agentdero
[email protected]
signature.asc
Description: Digital signature
--- End Message ---
