[
https://issues.apache.org/jira/browse/JAMES-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18055546#comment-18055546
]
Jean Helou commented on JAMES-3894:
-----------------------------------
Hello,
As you have noticed I have worked a bit on the documentation lately, however my
changes were not published and there were failing jobs on the james website CI
The error was similar to the one reported by benoit
{code:java}
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to check-in
files to SCM: The git-push command failed. remote: To
github:apache/james-site.git
remote: ! [rejected] 602676487c61b16c3155b9e03c14b004cee01544 ->
asf-staging (fetch first)
remote: error: failed to push some refs to 'github:apache/james-site.git'
remote: hint: Updates were rejected because the remote contains work that you
do not
remote: hint: have locally. This is usually caused by another repository
pushing to
remote: hint: the same ref. If you want to integrate the remote changes, use
remote: hint: 'git pull' before pushing again.
remote: hint: See the 'Note about fast-forwards' in 'git push --help' for
details.
remote: Syncing refs/heads/asf-staging...
remote: Could not sync with GitHub:
remote: Error running update hook: /x1/gitbox/hooks/update.d/01-sync-repo.py
remote: error: hook declined to update refs/heads/asf-staging
To https://gitbox.apache.org/repos/asf/james-site.git
! [remote rejected] asf-staging -> asf-staging (hook declined)
error: failed to push some refs to
'https://gitbox.apache.org/repos/asf/james-site.git'{code}
I searched 01-sync-repo.py in jira and only found this Jira :D
I don't fully understand the setup but it appears the gitbox repository is
supposed to be synced automatically with the github repo
I cloned the james site repo locally added the gitbox remote and compared
various branches
It appeared that the asf-staging branch on gitbox was lagging behind the one on
github
{code:java}
* 6f03a3c79 (2025-01-17 23:24:05 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N (origin/asf-staging)
* e854d285b (2025-01-17 23:23:29 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 747c81d27 (2025-01-17 07:52:15 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 16c2a8826 (2025-01-17 07:51:46 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* e34cf8771 (2025-01-16 21:09:57 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 54d6a2099 (2025-01-16 21:07:57 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* a3527aa43 (2025-01-14 11:57:27 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* cf0a38a98 (2025-01-13 14:14:59 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* ed634cdf7 (2025-01-13 14:14:17 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 0c42bd47e (2025-01-13 08:55:25 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* c2043c54d (2025-01-13 08:54:03 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 01a6dde28 (2025-01-08 07:40:45 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 08f75a887 (2025-01-08 07:40:14 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 6e85fdf3a (2025-01-06 13:52:18 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 5ec6f75cd (2025-01-06 08:26:22 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* d03193065 (2025-01-06 08:25:40 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 26cc86a6e (2024-12-28 10:55:00 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 4212eee53 (2024-12-28 10:54:21 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 2ee6258f3 (2024-12-26 06:32:59 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 819a9722a (2024-12-26 06:27:14 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 018419859 (2024-12-26 01:21:15 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 42b440d5d (2024-12-26 01:20:30 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 41983e7e2 (2024-12-24 13:09:46 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* aecd3f5b2 (2024-12-24 13:08:42 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* e1a479f5c (2024-12-22 14:13:57 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N (HEAD -> foo, gitbox/asf-staging)
* 08cb3c9cf (2024-12-22 14:13:14 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 69d1c9a6d (2024-12-21 02:24:58 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* cfc73d5f5 (2024-12-21 02:24:31 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 75b8ae45e (2024-12-20 18:34:10 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N {code}
on a hunch ( and because I was quite sure I could revert it as i had the
references) I tried to sync both branches
{code:java}
git push gitbox origin/asf-staging:asf-staging {code}
bringing both histories in sync
{code:java}
* 6f03a3c79 (2025-01-17 23:24:05 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N (origin/asf-staging, gitbox/asf-staging)
* e854d285b (2025-01-17 23:23:29 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 747c81d27 (2025-01-17 07:52:15 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 16c2a8826 (2025-01-17 07:51:46 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* e34cf8771 (2025-01-16 21:09:57 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* 54d6a2099 (2025-01-16 21:07:57 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N
* a3527aa43 (2025-01-14 11:57:27 +0000) Site checkin for project Apache James:
Jenkins Tools (jenkins) N {code}
I ran a [build
again|[https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/staging/849/cloudbees-pipeline-explorer/]]
and it succeeded !
So the latest version of hte documentation is now indeed deployed on staging.
Maybe it solves this issue too
> Antora build mis-fonctionning - Distributed server
> --------------------------------------------------
>
> Key: JAMES-3894
> URL: https://issues.apache.org/jira/browse/JAMES-3894
> Project: James Server
> Issue Type: Bug
> Components: site
> Reporter: Benoit Tellier
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The Antora build for the distributed server randomly fails, leading to
> missing online docimentation.
> Investigate "why" it fails and propose a fix.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
