[jbosstools-issues] [JBoss JIRA] (JBIDE-13408) investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Mon Mar 11 09:44:42 EDT 2013
[ https://issues.jboss.org/browse/JBIDE-13408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760192#comment-12760192 ]
Nick Boldt commented on JBIDE-13408:
------------------------------------
So you want to introduce a "mandatory waiting period" between ['new TP available' announcement in mailing list] and [update jobs to point explicitly to new version] during which time all devs will magically find time to run their local builds w/ the -DTARGET_PLATFORM_VERSION=<new version>.
How will we enforce that everyone has done that? Will we expect signoffs? Or just wait x days before changing the jobs, assuming that after x days any problems will have been reported?
> investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-13408
> URL: https://issues.jboss.org/browse/JBIDE-13408
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: target-platform
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.1.0.Alpha2
>
>
> investigate using `mvn deploy` from Jenkins CI job of non-SNAPSHOT target platforms to JBoss Public Nexus so that we can have *final* versions rather than ongoing snapshots.
> Last time I attempted to deploy something without a -SNAPSHOT suffix in its version, I got this error:
> {quote}
> {code:title=https://github.com/nickboldt/jbosstools-target-platforms/tree/d14d79e71d62b77f73d19d96e6bb1a03db90d5f1}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project multiple: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools.target-platforms.jbdevstudio:multiple:pom:4.21.3.Final from/to jboss-releases-repository (https://repository.jboss.org/nexus/content/repositories/releases/): Failed to transfer file: https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/target-platforms/jbdevstudio/multiple/4.21.3.Final/multiple-4.21.3.Final.pom. Return code is: 502, ReasonPhrase:Proxy Error. -> [Help 1]
> {code}
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list