[jbossws-issues] [JBoss JIRA] Commented: (JBWS-3007) Re-define QA phase leveraging staging repositories

[Alessio Soldano (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBWS-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12527113#action_12527113 ] 

Alessio Soldano commented on JBWS-3007:
---------------------------------------

I've been able to locally access the shared staging repository adding the following to my settings.xml
  <profile>
  ...
       <repository>
          <id>jboss-staging</id>
          <name>JBoss Staging</name>
          <url>https://repository.jboss.org/nexus/content/groups/staging</url>
          <releases>
            <enabled>true</enabled>
            <updatePolicy>true</updatePolicy>
          </releases>
          <snapshots>
            <enabled>false</enabled>
          </snapshots>
        </repository>
  ...
  </profile>
...
<mirrors>
    <mirror>
      <id>jboss-developer-repository-group</id>
      <mirrorOf>*,!jboss-deprecated,!jboss-staging</mirrorOf> <!-- need to also exclude the jboss-staging, to prevent that being looked for in the jboss-developer-repository-group -->
      <name>JBoss.org Developer Repository Group</name>
      <url>https://repository.jboss.org/nexus/content/groups/developer/</url>
    </mirror>
  </mirrors>

> Re-define QA phase leveraging staging repositories
> --------------------------------------------------
>
>                 Key: JBWS-3007
>                 URL: https://jira.jboss.org/jira/browse/JBWS-3007
>             Project: JBoss Web Services
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf, jbossws-metro, jbossws-native, productization
>            Reporter: Alessio Soldano
>             Fix For: jbossws-native-3.3.0,  jbossws-cxf-3.3.0, jbossws-metro-3.3.0
>
>
> Now that the new maven repository based on nexus is available, we can finally implement a better QA phase. I'm thinking about providing a proper maven profile for hudson to run against the staging repository. That would allow us to do what follows at code freeze:
> - verify all green (blue) on hudson against trunk
> - tag every changed components (spi, common, fw, ci, stacks) and mvn deploy them
> - close the temporary staging repository/repositories making the artifacts move to the shared staging repo
> - quickly re-start hudson against the staging repository
> - get a full clear run on hudson (starting with a local repository cleanup)
> - promote the artifacts to the release repository

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira