[infinispan-issues] [JBoss JIRA] Commented: (ISPN-942) Add an (automatic) validation process to infinispan releases

[Manik Surtani (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585964#comment-12585964 ] 

Manik Surtani commented on ISPN-942:
------------------------------------

I've added a check for the XSD in the release script.

Testing for binaries on SF needs to be done manually since SF takes "a few minutes" to make artefacts available.

As for wrong binaries/branches, the release script asks you to confirm this before you start the process:

{{Releasing Infinispan version 4.2.1.CR4 from branch 4.2.x}}
{{Are you sure you want to continue?}}

> Add an (automatic) validation process to infinispan releases 
> -------------------------------------------------------------
>
>                 Key: ISPN-942
>                 URL: https://issues.jboss.org/browse/ISPN-942
>             Project: Infinispan
>          Issue Type: Task
>    Affects Versions: 4.2.1.CR3
>            Reporter: Mircea Markus
>            Assignee: Manik Surtani
>             Fix For: 4.2.1.FINAL
>
>
> In order to avoid problems with releases a release validation process should be created. The following problems were encountered in the past and should be checked by this release process:
> - incorrect XSD (ISPN-934)
> - upload problems to SF (e.g. today the release script silently failed to upload the binaries to SF as they changed their certificate)
> - wrong binaries being deployed under the "right" name(e.g. a 4.x release was performed from trunk and not from the 4.2.x branch)
> Any others?
> All these cause a lot of community frustration and time to debug and fix. 
> These can potentially be automated.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira