Build failed in Jenkins: JClouds » jclouds #103

[Apache Jenkins Server]

See 


Changes:

[Andrew Gaul] JCLOUDS-1629: Upgrade to Guice 7.0.0


--
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on builds26 (ubuntu) in workspace 

The recommended git tool is: NONE
No credentials specified
 > git rev-parse --resolve-git-dir 
 >  # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://gitbox.apache.org/repos/asf/jclouds.git 
 > # timeout=10
Fetching upstream changes from https://gitbox.apache.org/repos/asf/jclouds.git
 > git --version # timeout=10
 > git --version # 'git version 2.34.1'
 > git fetch --tags --force --progress -- 
 > https://gitbox.apache.org/repos/asf/jclouds.git 
 > +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
Checking out Revision 107741f786a6aabfd68617b4e2e4ff59efac675d 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 107741f786a6aabfd68617b4e2e4ff59efac675d # timeout=10
Commit message: "JCLOUDS-1629: Upgrade to Guice 7.0.0"
 > git rev-list --no-walk b5e4e1d0fd466dffcbb0fb7921e52732145cc732 # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LC_ALL=en_US.UTF-8
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
Parsing POMs
Modules changed, recalculating dependency graph
Established TCP socket on 44933
maven35-agent.jar already up to date
maven35-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[jclouds] $ /home/jenkins/tools/java/latest1.8/bin/java -cp 
/home/jenkins/jenkins-agent/maven35-agent.jar:/home/jenkins/tools/maven/apache-maven-3.5.4/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/apache-maven-3.5.4/conf/logging
 jenkins.maven3.agent.Maven35Main /home/jenkins/tools/maven/apache-maven-3.5.4 
/home/jenkins/jenkins-agent/agent.jar 
/home/jenkins/jenkins-agent/maven35-interceptor.jar 
/home/jenkins/jenkins-agent/maven3-interceptor-commons.jar 44933
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
hudson/remoting/Launcher has been compiled by a more recent version of the Java 
Runtime (class file version 55.0), this version of the Java Runtime only 
recognizes class file versions up to 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:473)
at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:401)
at 
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
at jenkins.maven3.agent.Maven35Main.main(Maven35Main.java:136)
at jenkins.maven3.agent.Maven35Main.main(Maven35Main.java:66)
ERROR: Failed to parse POMs
java.io.EOFException: unexpected stream termination
at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:459)
at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:404)
at hudson.slaves.Channels.forProcess(Channels.java:121)
at 
hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:298)
at hudson.maven.ProcessCache.get(ProcessCache.java:237)
at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:802)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:526)
at hudson.model.Run.execute(Run.java:1841)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
at hudson.model.ResourceController.execute(ResourceController.java:101)
at hudson.model.Executor.run(Executor.java:442)

[jira] [Commented] (JCLOUDS-1629) Upgrade to Guice 7

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820562#comment-17820562
 ] 

ASF subversion and git services commented on JCLOUDS-1629:
--

Commit 107741f786a6aabfd68617b4e2e4ff59efac675d in jclouds's branch 
refs/heads/master from Andrew Gaul
[ https://gitbox.apache.org/repos/asf?p=jclouds.git;h=107741f786 ]

JCLOUDS-1629: Upgrade to Guice 7.0.0

This also changes from javax to jakarta annotations.


> Upgrade to Guice 7
> --
>
> Key: JCLOUDS-1629
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1629
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-core
>Affects Versions: 2.5.0
>Reporter: Andrew Gaul
>Assignee: Andrew Gaul
>Priority: Major
>  Labels: guice
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> [~basil] JCLOUDS-1627 upgrading some of the packages to jakarta but not the 
> important annotations one for Guice.  When changing these to Jakarta I could 
> get Guice 7 working but not 6.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [PR] JCLOUDS-1629: Upgrade to Guice 7.0.0 [jclouds]

[via GitHub]

gaul merged PR #197:
URL: https://github.com/apache/jclouds/pull/197


-- 
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: notifications-unsubscr...@jclouds.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (JCLOUDS-1606) Cannot upload more than 32 parts to GCS

[Lari Hotari (Jira)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820546#comment-17820546
 ] 

Lari Hotari commented on JCLOUDS-1606:
--

Thanks for fixing this!

> Cannot upload more than 32 parts to GCS
> ---
>
> Key: JCLOUDS-1606
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1606
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 2.5.0
>Reporter: Lari Hotari
>Assignee: Andrew Gaul
>Priority: Major
>  Labels: google-cloud-storage
> Fix For: 2.6.0
>
>
> There's currently a limitation in JClouds that it cannot upload more than 32 
> parts to GCS.
> {code:java}
> org.jclouds.http.HttpResponseException: command: POST 
> https://www.googleapis.com/storage/v1/b/somebucket/o/ff553922-1fa3-4ceb-abcd-60106603b5c8-object-123456/compose
>  HTTP/1.1 failed with response: HTTP/1.1 400 Bad Request; content: [{
>   "error": {
> "code": 400,
> "message": "The number of source components provided (35) exceeds the 
> maximum (32)",
> "errors": [
>   {
> "message": "The number of source components provided (35) exceeds the 
> maximum (32)",
> "domain": "global",
> "reason": "invalid"
>   }
> ]
>   }
> } {code}
> The limitation of 32 parts is per API call to the compose endpoint.
>  
> When there are more than 32 parts, the endpoint should be called multiple 
> times. The total limit is 1 parts in GCS.
> [https://cloud.google.com/storage/docs/composite-objects]
>  
> {quote}When you perform a composition:
>  * The source objects are unaffected.
>  * You can use between {*}1 and 32 source objects{*}.
>  * {*}Source objects can themselves be composite objects{*}.{quote}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Closed] (JCLOUDS-1606) Cannot upload more than 32 parts to GCS

[Lari Hotari (Jira)]

 [ 
https://issues.apache.org/jira/browse/JCLOUDS-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lari Hotari closed JCLOUDS-1606.

Resolution: Fixed

> Cannot upload more than 32 parts to GCS
> ---
>
> Key: JCLOUDS-1606
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1606
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 2.5.0
>Reporter: Lari Hotari
>Assignee: Andrew Gaul
>Priority: Major
>  Labels: google-cloud-storage
> Fix For: 2.6.0
>
>
> There's currently a limitation in JClouds that it cannot upload more than 32 
> parts to GCS.
> {code:java}
> org.jclouds.http.HttpResponseException: command: POST 
> https://www.googleapis.com/storage/v1/b/somebucket/o/ff553922-1fa3-4ceb-abcd-60106603b5c8-object-123456/compose
>  HTTP/1.1 failed with response: HTTP/1.1 400 Bad Request; content: [{
>   "error": {
> "code": 400,
> "message": "The number of source components provided (35) exceeds the 
> maximum (32)",
> "errors": [
>   {
> "message": "The number of source components provided (35) exceeds the 
> maximum (32)",
> "domain": "global",
> "reason": "invalid"
>   }
> ]
>   }
> } {code}
> The limitation of 32 parts is per API call to the compose endpoint.
>  
> When there are more than 32 parts, the endpoint should be called multiple 
> times. The total limit is 1 parts in GCS.
> [https://cloud.google.com/storage/docs/composite-objects]
>  
> {quote}When you perform a composition:
>  * The source objects are unaffected.
>  * You can use between {*}1 and 32 source objects{*}.
>  * {*}Source objects can themselves be composite objects{*}.{quote}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (JCLOUDS-1606) Cannot upload more than 32 parts to GCS

[Lari Hotari (Jira)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820545#comment-17820545
 ] 

Lari Hotari commented on JCLOUDS-1606:
--

[~gaul] Yes, that should be fine. I'll close this issue.

> Cannot upload more than 32 parts to GCS
> ---
>
> Key: JCLOUDS-1606
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1606
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 2.5.0
>Reporter: Lari Hotari
>Assignee: Andrew Gaul
>Priority: Major
>  Labels: google-cloud-storage
> Fix For: 2.6.0
>
>
> There's currently a limitation in JClouds that it cannot upload more than 32 
> parts to GCS.
> {code:java}
> org.jclouds.http.HttpResponseException: command: POST 
> https://www.googleapis.com/storage/v1/b/somebucket/o/ff553922-1fa3-4ceb-abcd-60106603b5c8-object-123456/compose
>  HTTP/1.1 failed with response: HTTP/1.1 400 Bad Request; content: [{
>   "error": {
> "code": 400,
> "message": "The number of source components provided (35) exceeds the 
> maximum (32)",
> "errors": [
>   {
> "message": "The number of source components provided (35) exceeds the 
> maximum (32)",
> "domain": "global",
> "reason": "invalid"
>   }
> ]
>   }
> } {code}
> The limitation of 32 parts is per API call to the compose endpoint.
>  
> When there are more than 32 parts, the endpoint should be called multiple 
> times. The total limit is 1 parts in GCS.
> [https://cloud.google.com/storage/docs/composite-objects]
>  
> {quote}When you perform a composition:
>  * The source objects are unaffected.
>  * You can use between {*}1 and 32 source objects{*}.
>  * {*}Source objects can themselves be composite objects{*}.{quote}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Build failed in Jenkins: JClouds » jclouds-with-credentials » jclouds-google-compute-engine-live-tests #183

[Apache Jenkins Server]

See 


Changes:


--
Started by timer
Running as SYSTEM
No JDK named ‘JDK 1.8 (latest)’ found
[EnvInject] - Loading node environment variables.
Building remotely on builds23 (ubuntu) in workspace 

No JDK named ‘JDK 1.8 (latest)’ found
ERROR: A Maven installation needs to be available for this project to be 
built.Either your server has no Maven installations defined, or the requested 
Maven version does not exist.
No JDK named ‘JDK 1.8 (latest)’ found
No JDK named ‘JDK 1.8 (latest)’ found