| Re: [leshan-dev] Release Process |
I actually do not know whether we are required to also deploy to the eclipse repos. But you are right, we can add that later as well. The most important thing to do is to get the PGP keys created for signing the leshan artifacts and get deploy keys for committing to github from hudson.
Let me know if I can help with defining the build job(s). However, I think that we can use the Californium build jobs as a blueprint.
Kai
Good question :).
For this first step, I just plan to automate the current release
process. (without modification)
Next, I don't know. Does it exist needs ? I'm not sure, but if somebody
needs this I suppose we can do that.
Simon
Le 19/11/2015 10:57, Hudalla Kai (INST/ESY) a écrit :
> Simon,
>
> sounds good to me :-) One question though: don't you plan to deploy to eclipse repo as well?
>
> Regards,
> Kai
>
> ________________________________________
> Von: leshan-dev-bounces@xxxxxxxxxxx [leshan-dev-bounces@xxxxxxxxxxx]" im Auftrag von "Simon Bernard [contact@xxxxxxxxxxxxxxx]
> Gesendet: Mittwoch, 18. November 2015 18:11
> An: leshan developer discussions
> Betreff: [leshan-dev] Release Process
>
> Hi,
> I would like to create a new hudson task to simplify the release process.
> I will take inspiration from the great job done for californium.
>
> This new task should be started manually and will take 2 parameters
> (RELEASE_VERSION and NEXT_VERSION).
> The task description :
> * Checks out current master's HEAD
> * Change version to RELEASE_VERSION
> mvn versions:set -DnewVersion=${RELEASE_VERSION} -Pall
> * Builds and tests it
> mvn clean install javadoc:javadoc
> -DsnapshotDependencyAllowed=false -Pall
> * Tags it with ${RELEASE_VERSION}
> git add **/pom.xml
> git commit -m "Bump version to ${RELEASE_VERSION}"
> git tag leshan-${RELEASE_VERSION}
> * Deploys artifacts to Maven Central's staging repo with
> autoReleaseAfterClose=true (no staging step)
> mvn clean deploy -Prelease,all
> * Change version to NEXT_VERSION
> mvn versions:set -DnewVersion=${NEXT_VERSION} -Pall
> * Pushes newly created tags to GitHub
> git add **/pom.xml
> git commit -m "Bump version to ${NEXT_VERSION}"
> git push repo.git && git push --tags repo.git
>
> Does it sounds good ?
> I create an issue[1] on bugzilla to ask to eclipse admins to make
> this possible.
>
> Maybe we could also automatically create the new release entry in
> github releases[2] and send a mail on the mailing list too?
>
> Simon
>
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=482493
> [2] https://developer.github.com/v3/repos/releases/#create-a-release
> _______________________________________________
> leshan-dev mailing list
> leshan-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/leshan-dev
> _______________________________________________
> leshan-dev mailing list
> leshan-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/leshan-dev
_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/leshan-dev