Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-898

usage.jenkins.io access log should use hostname specific information in log file path

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Related to INFRA-896, in order to prevent issues with overlapping access log files when we migrate from EC2 to Azure, the access logs should use some hostname specific identifier in the access log file name in order to prevent conflicts.

      Puppet facts for $fqdn or $hostname} probably won't work because the hostnames will be the same when migrating (usage.jenkins.io in both places while DNS propagates). The {{ec2 specific facts are also out.

      $ip might be sufficiently unique however.

      cc Kohsuke Kawaguchi

        Attachments

          Activity

          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: R. Tyler Croy
          Path:
          dist/profile/manifests/usage.pp
          http://jenkins-ci.org/commit/jenkins-infra/c4d0c15b1171d732ccfa59ca3e671cbff74f3422
          Log:
          Include a unique fact (ip) in the access logs for disambiguation

          Fixes INFRA-898

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: R. Tyler Croy Path: dist/profile/manifests/usage.pp http://jenkins-ci.org/commit/jenkins-infra/c4d0c15b1171d732ccfa59ca3e671cbff74f3422 Log: Include a unique fact (ip) in the access logs for disambiguation Fixes INFRA-898

            People

            Assignee:
            rtyler R. Tyler Croy
            Reporter:
            rtyler R. Tyler Croy
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: