On 31/07/2024 19:15, Phillip Ross wrote:
Hi Andy, I'd been periodically building the main branch of jena in a
container for awhile now and only recently bumped into problems with
the fuseki e2e tests consistently not working. I actually took the
time to patch in a maven profile which allows me to toggle e2e tests
on and off when invoking maven. It was much quicker for me to add
this patch than trying to troubleshoot why the tests aren't working
in-container, but it would be great to run down the root cause and
have it all working properly in containers on an ongoing basis!
That's an option. Did you set <testFailureIgnore> to true?
Having a docker container would be useful investment generally, not just
for ASF Jenkins.
Andy
On Wed, Jul 31, 2024 at 9:46 AM Andy Seaborne <a...@apache.org> wrote:
The Jenkins build still isn't fixed. I have a container+maven experiment
using a simple script to build a container then running the maven build
in the container but Cypress/networking isn't working properly. If it
did work, it could be converted to a Jenkins pipeline and/or put the
script into git and run that instead of maven directly.
It's only on Jenkins and it's because the servers don't have the Cypress
prerequisites. While getting them added might be possible, I think
having a container-hosted build is itself desirable in the long term.
The Jena builds works in github actions (Linux, Windows, macOS).
For now - and temporarily! - I've made the deploy build run without
tests so development builds are available on
://repository.apache.org/content/groups/snapshots/org/apache/jena/
Andy
On 15/07/2024 17:09, Andy Seaborne wrote:
> Marco - thank you. That's good news.
>
> The plan is to have a Jenkins pipeline that makes a docker container
> which gets cached on the ASF Jenkins nodes, not built from scratch each
> run, then run the Jena build in that container. We can configure the
> container appropriately.
>
> The Dockerfile file will be in the jena code repo.
>
> I don't know what we can do about other systems except document the
> situation.
>
> Much reading the Jenkins documentation!
>
> Andy
