Opened 2 years ago

Last modified 6 months ago

#16871 new task

Infrastructure migration

Reported by: michael2402 Owned by: team
Priority: normal Milestone: Longterm
Component: Core Version:
Keywords: hack-weekend-2018-10 Cc:

Description (last modified by simon04)

Meta-Ticket to coordinate the timeline of infrastructure conversion (build system, ci, GIT, dependencies, ...)

I (michael2402) will work on creating some more smaller tickets and linking all the tickets here as soon as Jenkins is done.

Legend: yellow=todo, green=done, blue=optional

Mermaid code for generating above graph using

graph TD
gitlab[setup GitLab server]:::todo
gitlabCi[setup GitLab CI or Jenkins for Git]:::todo
ciArtifcat[use CI to create artefacts]:::done
git[move to Git]:::todo

gradle[move to Gradle]:::todo
dropAnt[drop Ant and Eclipse]:::todo
gradleSubproject[move to Gradle subprojects]:::todo

gitSvgSalamander[clone svgSalamander to Git]:::optional
patchSvgSalamander[patch svgSalamander with our changes]:::optional
ciArtifcatSvgSalamander[use CI to create svgSalamander artifacts]:::optional
ivySvgSalamander[use svgSalamander via Ivy]:::optional

ivyJMapViewer[use JMapViewer via Ivy]:::done
gitJMapViewer[move JMapViewer to Git]:::todo
gradleJMapViewer[move JMapViewer to Gradle]:::todo
ivyApacheCommons[use Apache Commons via Ivy]:::done
ivyTools[use compile/test tools via Ivy]:::done

gitSvgSalamander --> patchSvgSalamander --> ciArtifcatSvgSalamander --> ivySvgSalamander --> gradle
ciArtifcat --> ciArtifcatSvgSalamander
gitlab --> gitlabCi --> ciArtifcat --> gradle
gitlab --> gitJMapViewer
gitlab --> git --> gradle --> dropAnt --> gradleSubproject
ivyJMapViewer --> gitJMapViewer --> gradleJMapViewer --> ciArtifcat
ivyJMapViewer --> ivyApacheCommons --> ivyTools --> git

dropGetopt[drop getopt]:::done

classDef todo fill:#ffd92f;
classDef done fill:#a6d854;

Attachments (3)

workflow.png (69.3 KB) - added by michael2402 2 years ago.
mermaid-diagram-20200408143202.svg (39.3 KB) - added by simon04 6 months ago.
mermaid-diagram-20200408143810.svg (37.2 KB) - added by simon04 6 months ago.

Download all attachments as: .zip

Change History (9)

Changed 2 years ago by michael2402

Attachment: workflow.png added

comment:1 Changed 2 years ago by Don-vip

Thanks Michael for this graph! :)

comment:2 Changed 2 years ago by simon04

Description: modified (diff)

Changed 6 months ago by simon04

Changed 6 months ago by simon04

comment:3 Changed 6 months ago by simon04

Description: modified (diff)
Milestone: Longterm

I've updated the dependency graph using mermaid.

For now, we're pretty good on the Java part (Ant, Ivy, Maven). The next steps would involve the Git part.

comment:4 Changed 6 months ago by GerdP

What is meant by dropping Eclipse?

comment:5 Changed 6 months ago by simon04

I guess (not written by me) removing source:trunk/.settings since that can be generated automatically from the Gradle configuration, see #8269.

comment:6 Changed 6 months ago by Don-vip

The "move to Gradle" part won't happen as such. I'm ok to add Gradle support for those who want to use it, but I really don't like it, and prefer Maven by far. I would rather see a common shared between Ant/Ivy, Maven and Gradle builds. I talked to some Linux package maintainers and heard similar feedback: Gradle is not their favorite piece of meat.

Modify Ticket

Change Properties
Set your email in Preferences
as new The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to michael2402
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.