Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kube API Test dependency not resolvable #5898

Closed
ivanchuchulski opened this issue Apr 15, 2024 · 12 comments · Fixed by #5899
Closed

Kube API Test dependency not resolvable #5898

ivanchuchulski opened this issue Apr 15, 2024 · 12 comments · Fixed by #5899
Assignees
Milestone

Comments

@ivanchuchulski
Copy link

Describe the bug

Hello, I'm trying to use the Kube API Test artifact in a project, but Maven is unable to resolve the dependency.

I see that in the New Features section of the release notes of 6.11.0 the Kube API Test is mentioned, but nonetheless the artifact isn't available in the Maven central repositoty. I've found this issue in which it was also mentioned the the feature should come in 6.11.0.

I also tried to use the 6.12.0 version, but the same problematic behavior is observed.

Fabric8 Kubernetes Client version

6.12.0

Steps to reproduce

  1. Add the following dependency to a pom.xml file:
        <dependency>
            <groupId>io.fabric8</groupId>
            <artifactId>kube-api-test</artifactId>
            <version>6.12.0</version>
            <scope>test</scope>
        </dependency>
  1. Run mvn clean install
  2. The following error is observed from the command output:
[ERROR] Failed to execute goal on project kube-api-server-test: Could not resolve dependencies for project org.example:kube-api-server-test:jar:1.0-SNAPSHOT: Could not find artifact io.fabric8:kube-api-test:jar:
6.12.0 in central (https://repo.maven.apache.org/maven2) -> [Help 1]

Expected behavior

Dependency is downloaded and project build is successful.

Runtime

Kubernetes (vanilla)

Kubernetes API Server version

other (please specify in additional context)

Environment

Windows, other (please specify in additional context)

Fabric8 Kubernetes Client Logs

No response

Additional context

K8s version: irrelevant

@manusa
Copy link
Member

manusa commented Apr 15, 2024

You're right, the release pipelines were not modified and the module has not been released 😞.

@manusa manusa moved this to In Progress in Eclipse JKube Apr 15, 2024
@manusa manusa self-assigned this Apr 15, 2024
@manusa manusa added this to the 6.13.0 milestone Apr 15, 2024 — with automated-tasks
@ivanchuchulski
Copy link
Author

Hello, thank you for the fast reply!

In the previous issue I've linked it was mentioned that somewhere you also have nightly builds I suppose from the current state of main branch. How those could be referenced/used?

@manusa
Copy link
Member

manusa commented Apr 15, 2024

Yes, I suggested that, but despite asking for feedback, apparently nobody tested the nightly build because the SNAPSHOT module isn't released either.

I'll try to merge #5898 today which should allow the nightly build pipeline to release the module in a few hours.

@ivanchuchulski
Copy link
Author

Alright, thank you for the effort. I'm just asking again how can I use this nightly build, what you be put as artifact version? Maybe just 6.13.0-SNAPSHOT or something else?

Thanks and regards.

@manusa
Copy link
Member

manusa commented Apr 15, 2024

You need to add this to your project's pom.xml or m2 settings.xml

      <repositories>
        <repository>
          <id>sonatype-snapshots</id>
          <url>https://oss.sonatype.org/content/repositories/snapshots</url>
          <releases><enabled>false</enabled></releases>
          <snapshots><enabled>true</enabled></snapshots>
        </repository>
      </repositories>

Then, set the Kubernetes Client version to the latest SNAPSHOT ---> 6.13-SNAPSHOT

@manusa manusa moved this from In Progress to Review in Eclipse JKube Apr 15, 2024
@github-project-automation github-project-automation bot moved this from Review to Done in Eclipse JKube Apr 15, 2024
@ivanchuchulski
Copy link
Author

Hello, I added the settings you've mentioned, but the dependency is still not resolvable:
[ERROR] Failed to execute goal on project kube-api-test-tryout: Could not resolve dependencies for project org.example:kube-api-test-tryout:jar:1.0-SNAPSHOT: The following artifacts could not be resolved: io.fabric8:kube-api-test:jar:6.13-SNAPSHOT (absent): Could not find artifact io.fabric8:kube-api-test:jar:6.13-SNAPSHOT in sonatype-snapshots (https://oss.sonatype.org/content/repositories/snapshots) -> [Help 1]

@rohanKanojia
Copy link
Member

rohanKanojia commented Apr 16, 2024

something is odd... I only see kube-api-test-parent being uploaded here https://oss.sonatype.org/content/repositories/snapshots/io/fabric8/kube-api-test-parent/

@manusa
Copy link
Member

manusa commented Apr 16, 2024

Yes, I was worried about that.
We need to manually add the child repositories too.

@manusa manusa reopened this Apr 16, 2024
@github-project-automation github-project-automation bot moved this from Done to Planned in Eclipse JKube Apr 16, 2024
@manusa manusa moved this from Planned to Review in Eclipse JKube Apr 16, 2024
@manusa
Copy link
Member

manusa commented Apr 16, 2024

I have just released the SNAPSHOTS manually with the updated CI pipeline fix, could you please confirm if it's working now?

@ivanchuchulski
Copy link
Author

Yes, now I've managed to resolve it. Thank you very much!

@manusa
Copy link
Member

manusa commented Apr 16, 2024

Awesome, I'll try to release a 6.12.1 patch version to make the module GA.

@manusa manusa modified the milestones: 6.13.0, 6.12.1 Apr 16, 2024
@manusa manusa moved this from Review to In Progress in Eclipse JKube Apr 17, 2024
@manusa
Copy link
Member

manusa commented Apr 18, 2024

@manusa manusa closed this as completed Apr 18, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in Eclipse JKube Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants