> On Dec 13, 2018, at 4:52 PM, Allen Wittenauer
> <[email protected]> wrote:
>
> a) create some Yetus-specific GitHub credentials (that the PMC will have
> access to)
> b) create a Github Branch Source-based Jenkins job
Since people may be curious as to the mechanics:
Jenkins is using an Oauth access token for this account for this job:
https://builds.apache.org/view/S-Z/view/Yetus/job/yetus-github-multibranch/
It currently does not write back to Github or JIRA since the credential
information isn’t given to test-patch. So I’ll file a bug to fix at least the
writing to JIRA portion. If we want it to write back to Github, we should
really create *another* account that we would never (potentially) give admin
privs to since this will test pull requests from the open Internet (just like
we do with JIRA, but with a higher barrier to entry). [Admin privs are needed
for GitHub to do some API calls that Jenkins and/or Yetus needs for full
functionality.]
I’ve got a blog post I’m working on that goes into a lot of these details (and
Travis CI. and Circle CI. and Gitlab CI) to publish post-0.9.0 release.
Sean, did you file the JIRA to INFRA to convert us over to Gitbox or did you
want me to do that?
