Build failed in Jenkins: JClouds » jclouds-with-credentials » jclouds-chef-live-tests #182

2024-02-20 Thread Apache Jenkins Server 
See 


Changes:

[Andrew Gaul] Bump bcprov-ext-jdk18on from 1.71 to 1.74 in /drivers/bouncycastle

[Andrew Gaul] Bump ch.qos.logback:logback-core from 1.2.9 to 1.2.13 in /project

[Andrew Gaul] Upgrade netty to 3.10.6.Final

[github] JCLOUDS-1519: Fix the authorization error with b2 application keys

[Andrew Gaul] Correct testName

[Andrew Gaul] Bump testng from 7.5 to 7.5.1 in /project


--
Started by timer
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on builds48 (tmp-22 ubuntu) in workspace 

The recommended git tool is: NONE
No credentials specified
Cloning the remote Git repository
Cloning repository https://gitbox.apache.org/repos/asf/jclouds.git
 > git init 
 > 
 >  # 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 config remote.origin.url https://gitbox.apache.org/repos/asf/jclouds.git 
 > # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
Avoid second fetch
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
Checking out Revision a983eaced90287d428beb81501f128f6d5113d86 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f a983eaced90287d428beb81501f128f6d5113d86 # timeout=10
Commit message: "Bump testng from 7.5 to 7.5.1 in /project"
 > git rev-list --no-walk 6455fd8518f3158c7bb1693f7489896a24bd88fa # timeout=10
[EnvInject] - Mask passwords that will be passed as build parameters.
Parsing POMs
Modules changed, recalculating dependency graph
Established TCP socket on 38325
maven35-agent.jar already up to date
maven35-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[jclouds-chef-live-tests] $ /home/jenkins/tools/java/latest1.8/bin/java -cp 
/home/jenkins/maven35-agent.jar:/home/jenkins/tools/maven/latest/boot/plexus-classworlds-2.7.0.jar:/home/jenkins/tools/maven/latest/conf/logging
 jenkins.maven3.agent.Maven35Main /home/jenkins/tools/maven/latest 
/home/jenkins/agent.jar /home/jenkins/maven35-interceptor.jar 
/home/jenkins/maven3-interceptor-commons.jar 38325
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.findClassInternal(ClassRealm.java:313)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:432)
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

Build failed in Jenkins: JClouds » jclouds #100

2024-02-20 Thread Apache Jenkins Server 
See 


Changes:

[Andrew Gaul] Correct testName

[Andrew Gaul] Bump testng from 7.5 to 7.5.1 in /project


--
Started by an SCM change
Started by an SCM change
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on EC2 (ec2-Jenkins Ephemeral Node User-CLI) - Jenkins 
Ephemeral Node - ubuntu label (i-041e445dc907413b8) (ubuntu ephemeral) in 
workspace 
The recommended git tool is: NONE
No credentials specified
Cloning the remote Git repository
Cloning repository https://gitbox.apache.org/repos/asf/jclouds.git
 > git init  # 
 > 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 config remote.origin.url https://gitbox.apache.org/repos/asf/jclouds.git 
 > # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
Avoid second fetch
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
Checking out Revision a983eaced90287d428beb81501f128f6d5113d86 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f a983eaced90287d428beb81501f128f6d5113d86 # timeout=10
Commit message: "Bump testng from 7.5 to 7.5.1 in /project"
 > git rev-list --no-walk 41d842d449e125411709613e27ca01c8fc5c4a4f # 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 34155
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/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 
/tmp/remoting.jar /home/jenkins/maven35-interceptor.jar 
/home/jenkins/maven3-interceptor-commons.jar 34155
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

Re: [PR] Upgrade to Netty 4.1.107 [jclouds]

2024-02-20 Thread via GitHub 


gaul commented on PR #195:
URL: https://github.com/apache/jclouds/pull/195#issuecomment-1954042627

   This has a bunch of API changes.


-- 
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

Re: [PR] Upgrade to Netty 4.1.107 [jclouds]

2024-02-20 Thread via GitHub 


gaul closed pull request #195: Upgrade to Netty 4.1.107
URL: https://github.com/apache/jclouds/pull/195


-- 
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

Re: [PR] Bump testng from 7.5 to 7.5.1 in /project [jclouds]

2024-02-20 Thread via GitHub 


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


-- 
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-1519) Support for Backblaze application keys

2024-02-20 Thread ASF subversion and git services (Jira) 


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

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

Commit 41d842d449e125411709613e27ca01c8fc5c4a4f in jclouds's branch 
refs/heads/dependabot/maven/project/org.testng-testng-7.5.1 from davidsenk
[ https://gitbox.apache.org/repos/asf?p=jclouds.git;h=41d842d449 ]

JCLOUDS-1519: Fix the authorization error with b2 application keys



> Support for Backblaze application keys
> --
>
> Key: JCLOUDS-1519
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1519
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 2.1.2
>Reporter: Elton Carneiro
>Assignee: Andrew Gaul
>Priority: Major
> Fix For: 2.6.0
>
>
> The current implementation of the B2 API in JClouds only supports Master Keys 
> and not application keys. 
> When using the Master Key, the Key ID and the Account ID are the same. 
> However, when using Application Keys, the Key ID of the application key is 
> not the same as the account ID. The account ID is what is needed to make 
> certain calls such as bucket operations.
> The response of the 
> [b2_authorize_account|https://www.backblaze.com/b2/docs/b2_authorize_account.html]
>  contains the account ID.
> If you look at the 
> [b2_list_buckets|https://www.backblaze.com/b2/docs/b2_list_buckets.html] 
> endpoint, it takes in an account ID. This Account ID is returned in the 
> authorize call.
> Looking at the source code, It seems that the account ID is being pulled from 
> the credentials that the user entered versus the response from the authorize 
> call.
> This issue prevents users from using Application keys when using JClouds. 
>  
>  



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

Re: [PR] Bump testng from 7.5 to 7.5.1 in /project [jclouds]

2024-02-20 Thread via GitHub 


gaul commented on PR #171:
URL: https://github.com/apache/jclouds/pull/171#issuecomment-1954002794

   @dependabot rebase


-- 
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