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 Thu, 18 Apr 2019 14:44:00 GMT


Fabio Utzig commented on INFRA-18229:

So I updated this build script to also clone the gitbox repo, and push there (I read somewhere
that it's not possible to push to GH, is that correct?).

But when trying to push the results it hangs on "git push", aparently with authorization fails,
logs follow. Any idea what is going on?

git push -v origin asf-site
Pushing to
* Couldn't find host in the .netrc file; using defaults
*   Trying
* Connected to ( port 443 (#0)
* found 133 certificates in /etc/ssl/certs/ca-certificates.crt
* found 399 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_256_GCM_SHA384
* 	 server certificate verification OK
* 	 server certificate status verification SKIPPED
* 	 common name: * (matched)
* 	 server certificate expiration date OK
* 	 server certificate activation date OK
* 	 certificate public key: RSA
* 	 certificate version: #3
* 	 subject: C=US,postalCode=21050-2747,ST=Maryland,L=Forest Hill,street=1901 Munsey Drive,O=The
Apache Software Foundation,OU=Infrastructure,CN=*
* 	 start date: Mon, 08 Oct 2018 00:00:00 GMT
* 	 expire date: Sat, 20 Jul 2019 23:59:59 GMT
* 	 issuer: C=US,,, High Assurance CA
* 	 compression: NULL
* ALPN, server accepted to use http/1.1
> GET /repos/asf/mynewt-site.git/info/refs?service=git-receive-pack HTTP/1.1
User-Agent: git/2.17.1
Accept: */*
Accept-Encoding: gzip
Accept-Language: en-US, *;q=0.9
Pragma: no-cache

< HTTP/1.1 401 Unauthorized
< Date: Thu, 18 Apr 2019 14:36:56 GMT
< Server: Apache/2.4.18 (Ubuntu)
< WWW-Authenticate: Basic realm="ASF Committers"
< Content-Length: 381
< Content-Type: text/html; charset=iso-8859-1
* Connection #0 to host left intact

> 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