I reckon we can get quite far with just a nice bash script (or a couple of scripts). Things like branching, mvn version, tagging and pushing could all be done with a bash script. Also a lot simpler now that we have a single repo.
I would love to give it a go. Håvard On 10 Oct 2019, at 12:35, Jeen Broekstra <jeen.broekstra@xxxxxxxxx> wrote:
So where we're at: I've set up the Jenkins pipeline to do releases for 2.5 again (using the multi-repo setup), so that we can do a 2.5.5 release. I haven't started the actual release process yet though.
Jenkins is currently working on deploying 3.0.1 artifacts. I am signing off for the evening, so I'll take care of the rest (upload of SDK/onejar and announcements) this weekend.
Cheers,
Jeen
PS still struggling a little with the fact that the release process is very manual and involves so many steps. Would be keen to hear bright ideas on how to simplify things (including changes to our branch model if necessary).
Thanks Bart, that should make things a lot easier.
I'll try and get both releases out the door later today. If things don't go as smooth as hoped I'll finish up during the weekend.
Cheers,
Jeen
_______________________________________________rdf4j-dev mailing listrdf4j-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://www.eclipse.org/mailman/listinfo/rdf4j-dev
|