Hi Marcus,
Strange I checked and only saw through 11/15
Then I did https://openoffice-org.staged.apache.org/stats/aoo-downloads.txt
directly
It was correct and also when I revisited the downloads page.
Something with browser cache on the downloads page …
Regards,
Dave
> On Dec 2, 2020, at
Am 02.12.20 um 20:07 schrieb Marcus:
Am 02.12.20 um 20:02 schrieb Dave Fisher:
https://openoffice-org.staged.apache.org/feed.xml
Shows the last staging build.
yes, however it seems that the stage site hasn't got the page I expect:
http://ooo-site.staging.apache.org/stats/downloads.html
Am 02.12.20 um 20:01 schrieb Matthias Seidel:
Am 02.12.20 um 19:54 schrieb Marcus:
The second time that a commit goes not through to the staging site.
- git pull, git commit, git push
- Then waititng / watching that the Jenkins job is finished
- Then updating the website in the browser
--> And
Am 02.12.20 um 20:02 schrieb Dave Fisher:
https://openoffice-org.staged.apache.org/feed.xml
Shows the last staging build.
yes, however it seems that the stage site hasn't got the page I expect:
http://ooo-site.staging.apache.org/stats/downloads.html
Marcus
On Dec 2, 2020, at 11:01 AM,
Hi -
https://openoffice-org.staged.apache.org/feed.xml
Shows the last staging build.
Regards,
Dave
> On Dec 2, 2020, at 11:01 AM, Matthias Seidel
> wrote:
>
> Hi Marcus,
>
> Am 02.12.20 um 19:54 schrieb Marcus:
>> The second time that a commit goes not through to the staging site.
>>
>> -
Hi Marcus,
Am 02.12.20 um 19:54 schrieb Marcus:
> The second time that a commit goes not through to the staging site.
>
> - git pull, git commit, git push
> - Then waititng / watching that the Jenkins job is finished
> - Then updating the website in the browser
> --> And still the old page
>
> Is
The second time that a commit goes not through to the staging site.
- git pull, git commit, git push
- Then waititng / watching that the Jenkins job is finished
- Then updating the website in the browser
--> And still the old page
Is there something I'm doing wrong? Or something missing?