infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fabio Utzig (JIRA)" <>
Subject [jira] [Commented] (INFRA-18229) Publishing the mynewt-site
Date Wed, 24 Apr 2019 10:53:00 GMT


Fabio Utzig commented on INFRA-18229:

Thanks, everything works now. Before I close this... our builds are running on Python2 but
I would really like to run on Python3, does anyone have instructions on how to install dependencies
on Python3? Or could you install python-pip3 (if it's available)?

> Publishing the mynewt-site
> --------------------------
>                 Key: INFRA-18229
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Jenkins
>            Reporter: Fabio Utzig
>            Priority: Major
> I am trying to publish the documentation for Mynewt which is pushed to `asf-site` branch
on `mynewt-site` repo. The pages are built from multiple repos, and are already setup here:
> The process we had before on a private Jenkins instance was:
> ```
> git remote add fork
> git add .
> git commit -m "asf-site update $(date)"
> git push --force fork asf-site
> curl -X POST -u runtime-bot:$GITHUB_TOKEN -d '{"title":"automated asf-site build","head":"runtime-bot:asf-site","base":"asf-site"}'
> ```
> As can be seen we had this runtime-bot user that would send a PR to the rasf-site branch
with the built results. I tried to understand to understand the CloudBees Pull Request Builder
for GitHub (
but it's not obvious to me what I am missing to achieve the same behavior as described above.
> Also there is "Add asfbot as a Collaborator and set it to Admin". I obviously have no
admin access to the repo but is this user there, can I used this user to push stuff? What
about the credentials for it?

This message was sent by Atlassian JIRA

View raw message