search

eclipse-ee4j / glassfish-fighterfish

FighterFish project
Other
6 stars 11 forks source link

Release CI/CD pipeline #14

Closed m0mus closed 6 years ago

m0mus commented 6 years ago

This task is for creating a project release CI/CD pipeline.

Use these documents as a reference:

jayasheelankumar commented 6 years ago

Created the jobs for all the artifacts in figtherfish.

Tomas-Kraus commented 6 years ago

Those jobs are not working, I see

gpg: signing failed: Not a tty
gpg: signing failed: Not a tty

in console output. This is caused by old parent pom. Made PR to update pareent to 1.0.2: https://github.com/eclipse-ee4j/glassfish-fighterfish/pull/18 https://github.com/eclipse-ee4j/glassfish-fighterfish/pull/19

Tomas-Kraus commented 6 years ago

Well, looks like you have to release modules parent first and update versions to make rest of the jobs working too. Another option is to do everything in a single job where parent is installed and all modules are updated to this new parent. But I have no idea how release process should work properly in this project.

romain-grecourt commented 6 years ago

Sahoo did things that way but he was releasing modules individually from command line. IMO you should refactor the pom files and make it a single reactor that you can release in one shot.

Tomas-Kraus commented 6 years ago

Yes, it's another option to go. But there is one more thing - versioning. If you check https://github.com/javaee/fighterfish/releases, we have versions from 1.0.1 up to 2.0.1 for various modules. Single reactor solution would mean releasing everything with a single shot and if possible, with the same version numbers. I'm even not commiter here so I won't do such a change without others agreement.