infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <>
Subject [jira] [Resolved] (INFRA-17787) Incubator Zipkin: Jenkins-GitHub integration
Date Wed, 20 Feb 2019 06:42:00 GMT


Chris Lambertus resolved INFRA-17787.
    Resolution: Information Provided
      Assignee: Chris Lambertus

> Incubator Zipkin: Jenkins-GitHub integration
> --------------------------------------------
>                 Key: INFRA-17787
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Github, Jenkins
>            Reporter: Zoltán Nagy
>            Assignee: Chris Lambertus
>            Priority: Minor
> Dear INFRA,
> We're in the process of setting up Jenkins jobs for incubator-zipkin-brave-karaf, the
first Zipkin project we're planning to release under our ASF incubation.
> is a multi-branch
pipeline job that currently runs tests, and does nothing else. I'm asking for your assistance
on three things.
> 1) Delete the Jenkins-global credential I mistakenly created when setting all this up
(it's junk, noise, and overall badness):
(I've created a job-level credential instead)
> 2) Advise on the best way to authenticate from Jenkins to GitHub for reporting build
results to commits and pull requests. Currently the job linked above uses my personal access
token I created for this purpose, but if there's a better way (like some shared service token),
we'd be happy to adopt that.
> 3) It appeared to me that pull requests weren't discovered by the multi-branch pipeline
job on creation, only when I clicked Scan Repository. Branches / commits did seem to be picked
up, so I'm confused, and have no way to investigate further given I have no admin access to If possible, it'd be best to have
admin access to the repo. If that's against policy, please set up the relevant webhook so
that pushes and pull-requests notify Jenkins.
> Thank you!

This message was sent by Atlassian JIRA

View raw message