On your successful build, I see:
    [INFO] Building de.cognicrypt.crysl.handler 1.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] Downloading from xtend: http://build.eclipse.org/common/xtend/maven/de/darmstadt/tu/crossing/CryptSL/de.darmstadt.tu.crossing.CryptSL/1.0.0-SNAPSHOT/maven-metadata.xml
[WARNING] Checksum validation failed, expected <!doctype but is c143977810d6345b60e0d28515110a949a29a3a8 from xtend for http://build.eclipse.org/common/xtend/maven/de/darmstadt/tu/crossing/CryptSL/de.darmstadt.tu.crossing.CryptSL/1.0.0-SNAPSHOT/maven-metadata.xml
[WARNING] Could not validate integrity of download from http://build.eclipse.org/common/xtend/maven/de/darmstadt/tu/crossing/CryptSL/de.darmstadt.tu.crossing.CryptSL/1.0.0-SNAPSHOT/maven-metadata.xml: Checksum validation failed, expected <!doctype but is c143977810d6345b60e0d28515110a949a29a3a8
[WARNING] Checksum validation failed, expected <!doctype but is c143977810d6345b60e0d28515110a949a29a3a8 from xtend for http://build.eclipse.org/common/xtend/maven/de/darmstadt/tu/crossing/CryptSL/de.darmstadt.tu.crossing.CryptSL/1.0.0-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from xtend: http://build.eclipse.org/common/xtend/maven/de/darmstadt/tu/crossing/CryptSL/de.darmstadt.tu.crossing.CryptSL/1.0.0-SNAPSHOT/maven-metadata.xml (1.2 kB at 355 B/s)
[WARNING] The metadata /var/lib/jenkins/.m2/repository/de/darmstadt/tu/crossing/CryptSL/de.darmstadt.tu.crossing.CryptSL/1.0.0-SNAPSHOT/maven-metadata-xtend.xml is invalid: unexpected markup <!d (position: START_DOCUMENT seen <!d... @1:3) 
[WARNING] The metadata /var/lib/jenkins/.m2/repository/de/darmstadt/tu/crossing/CryptSL/de.darmstadt.tu.crossing.CryptSL/1.0.0-SNAPSHOT/maven-metadata-xtend.xml is invalid: unexpected markup <!d (position: START_DOCUMENT seen <!d... @1:3) 
Notice the Validation Failed and Unexpected Markup.
On the failed build, I see:
[INFO] Building de.cognicrypt.crysl.handler 1.0.0-SNAPSHOT               [4/10]
[INFO] ---------------------------[ eclipse-plugin ]---------------------------
[DEBUG] Using transporter WagonTransporter with priority -1.0 for http://build.eclipse.org/common/xtend/maven/
[INFO] Downloading from xtend: http://build.eclipse.org/common/xtend/maven/de/darmstadt/tu/crossing/CryptSL/de.darmstadt.tu.crossing.CryptSL/1.0.0-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata de.darmstadt.tu.crossing.CryptSL:de.darmstadt.tu.crossing.CryptSL:1.0.0-SNAPSHOT/maven-metadata.xml from/to xtend (http://build.eclipse.org/common/xtend/maven/): eclipse.org: Name or service not known
[WARNING] Failure to transfer de.darmstadt.tu.crossing.CryptSL:de.darmstadt.tu.crossing.CryptSL:1.0.0-SNAPSHOT/maven-metadata.xml from http://build.eclipse.org/common/xtend/maven/ was cached in the local repository, resolution will not be reattempted until the update interval of xtend has elapsed or updates are forced. Original error: Could not transfer metadata de.darmstadt.tu.crossing.CryptSL:de.darmstadt.tu.crossing.CryptSL:1.0.0-SNAPSHOT/maven-metadata.xml from/to xtend (http://build.eclipse.org/common/xtend/maven/): eclipse.org: Name or service not known
    
    
    In the end, this URL is a 404:
    http://build.eclipse.org/common/xtend/maven/de/darmstadt/tu/crossing/CryptSL/de.darmstadt.tu.crossing.CryptSL/1.0.0-SNAPSHOT/maven-metadata.xml
    
    
    I'm not sure why that succeeds on your end, because it never gets
      downloaded anyway. Perhaps one build job 
    
    At any rate, obtaining Xtend from build.eclipse.org has to be
      severely outdated.
    
    
    Denis
    
    
    
    
    
    On 2019-04-08 12:57 p.m., Karsten Thoms
      wrote:
    
    
      
      In the FAQ there is mentioned how to specify resource
      requests/limits
      
      
      
      Do you have recommendations what are reasonable
        settings for requests/limits for memory/CPU for „typical“ builds
        of kind
      - Gradle build & unit tests
      - „Plain“ Maven builds (e.g. building Maven plugins)
      - Tycho builds including UI Tests (i.e. 2 VMs)
      
      
      How could we deduce proper settings without wild
        guessing?
      
      
      ~Karsten
      
      
      _______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cbi-dev