[Jenkins-infra] Proposal: Decommission demo.jenkins-ci.org

[R. Tyler Croy]

We have a Jenkins instance running on demo.jenkins-ci.org which I would like to
decommission entirely. It was originally provisioned to show-case some of the
Jenkins 2 features and now has become an increasing thorn in my side.

The two primary problems are:

 * Keeping it updated is tedious and manual in our current container
   infrastructure
 * It turns out to be using up *thousands* of GitHub API requests which is
   adversely affecting our rate-limiting on JIRA and ci.j.io, both of which
   have heavy GitHub integrations.


These /could/ be worked around, but I don't see good justification in
continuing the service and would like to hear any approving or contrary
opinions.


Cheers
- R. Tyler Croy

------------------------------------------------------
     Code: <https://github.com/rtyler>
  Chatter: <https://twitter.com/agentdero>

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20161005/8747eeb8/attachment.asc>