Task #407

maven repository upgrade

Added by Claudio Atzori over 4 years ago. Updated about 2 years ago.

Status:NewStart date:Jul 22, 2015
Priority:ImmediateDue date:
Assignee:Tommaso Piccioli% Done:

0%

Category:System Application
Sprint:UnSprintable
Infrastructure:Development
Milestones:
Duration:

Description

The current version of nexus 2.0.4-1 is quite outdated and runs on ubuntu 10.04 (maven.research-infrastructures.eu), we need a newer version based on maven >= 3.2.5.

As the maven repository is used by D4S, DNet, and the resp. partners, we must ensure the service availability. For this reason it would be preferable to create a new VM, install the latest version of nexus and migrate the data.

The artifacts migration is not a requirement, as we might delegate to a new jenkins slave (running maven >= 3.2.5 as well) the burden to build and deploy them.


Subtasks

History

#1 Updated by Pasquale Pagano over 4 years ago

I am fine with the upgrade but the migration is required for gCube since we not use jenkins yet.

#2 Updated by Pasquale Pagano over 4 years ago

Should the new server be named nexus.d4science.org? I am not sure but the repository is based on Nexus ... am i wrong?

#3 Updated by Claudio Atzori over 4 years ago

Pasquale Pagano wrote:

I am fine with the upgrade but the migration is required for gCube since we not use jenkins yet.

I'm not sure about the "cost" of a migration, as different versions of nexus might organise the artifact repository in different ways. I didn't read the documentation nor the changelogs yet.

Anyway although this task was proposed ~1h ago on the OpenAIRE issue tracker, we got back to it as some newer tools and libraries require newer maven versions (gRPC+Protobuf3 btw).

I guess we could create the VM, install the newer version of nexus, and start playing with it. Then the migration will come in a later stage.

Pasquale Pagano wrote:

Should the new server be named nexus.d4science.org? I am not sure but the repository is based on Nexus ... am i wrong?

Any name is fine with me. I just copied the task content from the other issue tracker. I'd go for nexus as we already know the tool.

#4 Updated by Andrea Dell'Amico over 4 years ago

Claudio Atzori wrote:

Pasquale Pagano wrote:

I am fine with the upgrade but the migration is required for gCube since we not use jenkins yet.

I'm not sure about the "cost" of a migration, as different versions of nexus might organise the artifact repository in different ways. I didn't read the documentation nor the changelogs yet.

Anyway although this task was proposed ~1h ago on the OpenAIRE issue tracker, we got back to it as some newer tools and libraries require newer maven versions (gRPC+Protobuf3 btw).

I guess we could create the VM, install the newer version of nexus, and start playing with it. Then the migration will come in a later stage.

That could be the plan: play with the new VM first, and then choose to migrate the artifacts if it's needed. In that case another subtask can be opened.

Pasquale Pagano wrote:

Should the new server be named nexus.d4science.org? I am not sure but the repository is based on Nexus ... am i wrong?

Any name is fine with me. I just copied the task content from the other issue tracker. I'd go for nexus as we already know the tool.

Yes, the hostname comes from the old tasks that predate the research-infrastructures.eu dismissal.

#5 Updated by Andrea Dell'Amico almost 4 years ago

  • Tracker changed from Support to Task

#6 Updated by Claudio Atzori over 2 years ago

  • Assignee changed from Andrea Dell'Amico to Tommaso Piccioli

The recent incident involving the nexus repository (https://issue.openaire.research-infrastructures.eu/issues/3219) makes me think that we should move on with this task.

Tom can we come up with a plan?

#7 Updated by Andrea Dell'Amico about 2 years ago

We need to move on with this activity.

#8 Updated by Luca Frosini about 2 years ago

Any news about this?

Also available in: Atom PDF