You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "apupier (via GitHub)" <gi...@apache.org> on 2025/06/19 07:06:16 UTC
[PR] INFRA-26918 - Clean often corrupted folder on Jenkins [camel]
apupier opened a new pull request, #18404:
URL: https://github.com/apache/camel/pull/18404
The Jenkins slave is often corrupted failing the build with this error message:
```
Caused by: org.eclipse.aether.RepositoryException: Could not parse
metadata /home/jenkins/.m2/repository/org/apache/camel/camel-buildtools/maven-metadata-local.xml:
in epilog non whitespace content is not allowed but got a (position:
END_TAG seen ...</metadata>\na... @34:2)
```
So when cleaning the workspace, deleting the parent folder. Not deleting the whole .m2 as this would slow down too much the build. Deleting the whole folder to avoid having data not in phase inside the folder.
# Description
<!--
- Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
-->
# Target
- [ ] I checked that the commit is targeting the correct branch (Camel 4 uses the `main` branch)
# Tracking
- [ ] If this is a large change, bug fix, or code improvement, I checked there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it).
<!--
# *Note*: trivial changes like, typos, minor documentation fixes and other small items do not require a JIRA issue. In this case your pull request should address just this issue, without pulling in other changes.
-->
# Apache Camel coding standards and style
- [ ] I checked that each commit in the pull request has a meaningful subject line and body.
<!--
If you're unsure, you can format the pull request title like `[CAMEL-XXX] Fixes bug in camel-file component`, where you replace `CAMEL-XXX` with the appropriate JIRA issue.
-->
- [ ] I have run `mvn clean install -DskipTests` locally from root folder and I have committed all auto-generated changes.
<!--
You can run the aforementioned command in your module so that the build auto-formats your code. This will also be verified as part of the checks and your PR may be rejected if if there are uncommited changes after running `mvn clean install -DskipTests`.
You can learn more about the contribution guidelines at https://github.com/apache/camel/blob/main/CONTRIBUTING.md
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] INFRA-26918 - Clean often corrupted folder on Jenkins [camel]
Posted by "apupier (via GitHub)" <gi...@apache.org>.
apupier merged PR #18404:
URL: https://github.com/apache/camel/pull/18404
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] INFRA-26918 - Clean often corrupted folder on Jenkins [camel]
Posted by "apupier (via GitHub)" <gi...@apache.org>.
apupier commented on PR #18404:
URL: https://github.com/apache/camel/pull/18404#issuecomment-2986925957
so far I spotted that it was always on the same file so finger crossed that it is this specific file only.
And checked that the Clean workspace is called at the beginning so shoudl be able to try directly (I mean no need to first clean the workspace manually)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] INFRA-26918 - Clean often corrupted folder on Jenkins [camel]
Posted by "apupier (via GitHub)" <gi...@apache.org>.
apupier commented on PR #18404:
URL: https://github.com/apache/camel/pull/18404#issuecomment-2986900052
https://issues.apache.org/jira/browse/INFRA-26918?focusedCommentId=17983459&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17983459
even if it won't fix the root issue. This is currently failing too often to be sustainable. i tried to provide a PR to remove the mentioned parent folder https://github.com/apache/camel/pull/18404 but I do not know how to test that without commiting on main branch and waiting for a new build.
Is it possible to try to modify the job on the CI itself?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] INFRA-26918 - Clean often corrupted folder on Jenkins [camel]
Posted by "davsclaus (via GitHub)" <gi...@apache.org>.
davsclaus commented on PR #18404:
URL: https://github.com/apache/camel/pull/18404#issuecomment-2986899269
ah good idea thanks
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org