[sling-site] branch master updated: SLING-12052 - use Node 16 to avoid 'GLIBC_2.28 not found' error

[bdelacretaz]

This is an automated email from the ASF dual-hosted git repository.

bdelacretaz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 39b068c30 SLING-12052 - use Node 16 to avoid 'GLIBC_2.28 not found' 
error
39b068c30 is described below

commit 39b068c30920de924a66fe0ec6fcda91c5c7f345
Author: Bertrand Delacretaz <bdelacre...@apache.org>
AuthorDate: Mon Oct 2 10:51:43 2023 +0200

    SLING-12052 - use Node 16 to avoid 'GLIBC_2.28 not found' error
---
 pom.xml | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/pom.xml b/pom.xml
index d1db2a820..d2120e662 100644
--- a/pom.xml
+++ b/pom.xml
@@ -41,6 +41,9 @@
 
     <!-- pagefind needs to run after compile and before package... -->
     <pagefind.maven.phase>test</pagefind.maven.phase>
+
+    <!-- getting GLIBC_2.28 not found on Jenkins with Node > 16 -->
+    <pagefind.node.version>v16.6.0</pagefind.node.version>
   </properties>
 
   <build>
@@ -237,7 +240,7 @@
                                 </goals>
                                 <phase>${pagefind.maven.phase}</phase>
                                 <configuration>
-                                    <nodeVersion>v20.7.0</nodeVersion>
+                                    
<nodeVersion>${pagefind.node.version}</nodeVersion>
                                 </configuration>
                             </execution>
                             <execution>