You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Marshall Schor (JIRA)" <ji...@apache.org> on 2011/03/02 17:34:37 UTC
[jira] Created: (INFRA-3484) Add plugin to conditionally deploy
SNAPSHOTs (only) to Apache Nexus snapshot repo
Add plugin to conditionally deploy SNAPSHOTs (only) to Apache Nexus snapshot repo
---------------------------------------------------------------------------------
Key: INFRA-3484
URL: https://issues.apache.org/jira/browse/INFRA-3484
Project: Infrastructure
Issue Type: Improvement
Security Level: public (Regular issues)
Components: Hudson
Reporter: Marshall Schor
Priority: Minor
There currently is a post-build setting for maven projects which, if checked, deploys the results to a repository. We want to do this only for Snapshots. Because of the way the Maven release plugin works (it updates the POMs in trunk from Snapshot to not-snapshot, tags that, and then updates the poms to the next development level), there is a (quite small) chance that the Hudson build could be triggered right after the poms were updated to the non-snapshot version, and the build would be done with this.
If this happened, we would like the deploy (of this non-snapshot build) to *not* happen to the Apache Nexus snapshot directory.
If this already is prevented (perhaps by the Nexus configuration?) then please indicate, and close this issue.
Otherwise, googling found a plugin for Hudson which checks to insure builds are snapshot builds, and won't deploy if they are non-snapshot builds; the plugin is here: http://code.google.com/p/maven-hudson-ext-plugin/
If possible, see if installing this plugin adds a post-build item to deploy SNAPSHOTs (only) to the list of actions, and works appropriately.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (INFRA-3484) Add plugin to conditionally deploy
SNAPSHOTs (only) to Apache Nexus snapshot repo
Posted by "Marshall Schor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor reopened INFRA-3484:
-----------------------------------
First try after configure to use this plugin caused failure the first time this plugin was invoked - seems to be missing a library. Here's the link to the console output:
https://hudson.apache.org/hudson/job/UIMA-AS/39/console
Also, I cannot "uncheck" this in the configuration, because for some reason the configuration GUI is missing the bottom set of controls, including this checkbox (and all the other post build action specs). Here's a link to that GUI:
https://hudson.apache.org/hudson/job/UIMA-AS/configure
> Add plugin to conditionally deploy SNAPSHOTs (only) to Apache Nexus snapshot repo
> ---------------------------------------------------------------------------------
>
> Key: INFRA-3484
> URL: https://issues.apache.org/jira/browse/INFRA-3484
> Project: Infrastructure
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Hudson
> Reporter: Marshall Schor
> Assignee: Niklas Gustavsson
> Priority: Minor
>
> There currently is a post-build setting for maven projects which, if checked, deploys the results to a repository. We want to do this only for Snapshots. Because of the way the Maven release plugin works (it updates the POMs in trunk from Snapshot to not-snapshot, tags that, and then updates the poms to the next development level), there is a (quite small) chance that the Hudson build could be triggered right after the poms were updated to the non-snapshot version, and the build would be done with this.
> If this happened, we would like the deploy (of this non-snapshot build) to *not* happen to the Apache Nexus snapshot directory.
> If this already is prevented (perhaps by the Nexus configuration?) then please indicate, and close this issue.
> Otherwise, googling found a plugin for Hudson which checks to insure builds are snapshot builds, and won't deploy if they are non-snapshot builds; the plugin is here: http://code.google.com/p/maven-hudson-ext-plugin/
> If possible, see if installing this plugin adds a post-build item to deploy SNAPSHOTs (only) to the list of actions, and works appropriately.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (INFRA-3484) Add plugin to conditionally deploy
SNAPSHOTs (only) to Apache Nexus snapshot repo
Posted by "Niklas Gustavsson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Niklas Gustavsson closed INFRA-3484.
------------------------------------
Resolution: Fixed
Assignee: Niklas Gustavsson
Plugin installed
> Add plugin to conditionally deploy SNAPSHOTs (only) to Apache Nexus snapshot repo
> ---------------------------------------------------------------------------------
>
> Key: INFRA-3484
> URL: https://issues.apache.org/jira/browse/INFRA-3484
> Project: Infrastructure
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Hudson
> Reporter: Marshall Schor
> Assignee: Niklas Gustavsson
> Priority: Minor
>
> There currently is a post-build setting for maven projects which, if checked, deploys the results to a repository. We want to do this only for Snapshots. Because of the way the Maven release plugin works (it updates the POMs in trunk from Snapshot to not-snapshot, tags that, and then updates the poms to the next development level), there is a (quite small) chance that the Hudson build could be triggered right after the poms were updated to the non-snapshot version, and the build would be done with this.
> If this happened, we would like the deploy (of this non-snapshot build) to *not* happen to the Apache Nexus snapshot directory.
> If this already is prevented (perhaps by the Nexus configuration?) then please indicate, and close this issue.
> Otherwise, googling found a plugin for Hudson which checks to insure builds are snapshot builds, and won't deploy if they are non-snapshot builds; the plugin is here: http://code.google.com/p/maven-hudson-ext-plugin/
> If possible, see if installing this plugin adds a post-build item to deploy SNAPSHOTs (only) to the list of actions, and works appropriately.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-3484) Add plugin to conditionally deploy
SNAPSHOTs (only) to Apache Nexus snapshot repo
Posted by "Marshall Schor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002846#comment-13002846 ]
Marshall Schor commented on INFRA-3484:
---------------------------------------
I've temporarily disabled the build until this issue gets resolved.
> Add plugin to conditionally deploy SNAPSHOTs (only) to Apache Nexus snapshot repo
> ---------------------------------------------------------------------------------
>
> Key: INFRA-3484
> URL: https://issues.apache.org/jira/browse/INFRA-3484
> Project: Infrastructure
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Hudson
> Reporter: Marshall Schor
> Assignee: Niklas Gustavsson
> Priority: Minor
>
> There currently is a post-build setting for maven projects which, if checked, deploys the results to a repository. We want to do this only for Snapshots. Because of the way the Maven release plugin works (it updates the POMs in trunk from Snapshot to not-snapshot, tags that, and then updates the poms to the next development level), there is a (quite small) chance that the Hudson build could be triggered right after the poms were updated to the non-snapshot version, and the build would be done with this.
> If this happened, we would like the deploy (of this non-snapshot build) to *not* happen to the Apache Nexus snapshot directory.
> If this already is prevented (perhaps by the Nexus configuration?) then please indicate, and close this issue.
> Otherwise, googling found a plugin for Hudson which checks to insure builds are snapshot builds, and won't deploy if they are non-snapshot builds; the plugin is here: http://code.google.com/p/maven-hudson-ext-plugin/
> If possible, see if installing this plugin adds a post-build item to deploy SNAPSHOTs (only) to the list of actions, and works appropriately.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (INFRA-3484) Add plugin to conditionally deploy
SNAPSHOTs (only) to Apache Nexus snapshot repo
Posted by "Niklas Gustavsson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Niklas Gustavsson closed INFRA-3484.
------------------------------------
Resolution: Fixed
Plugin has been disabled
> Add plugin to conditionally deploy SNAPSHOTs (only) to Apache Nexus snapshot repo
> ---------------------------------------------------------------------------------
>
> Key: INFRA-3484
> URL: https://issues.apache.org/jira/browse/INFRA-3484
> Project: Infrastructure
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Hudson
> Reporter: Marshall Schor
> Assignee: Niklas Gustavsson
> Priority: Minor
>
> There currently is a post-build setting for maven projects which, if checked, deploys the results to a repository. We want to do this only for Snapshots. Because of the way the Maven release plugin works (it updates the POMs in trunk from Snapshot to not-snapshot, tags that, and then updates the poms to the next development level), there is a (quite small) chance that the Hudson build could be triggered right after the poms were updated to the non-snapshot version, and the build would be done with this.
> If this happened, we would like the deploy (of this non-snapshot build) to *not* happen to the Apache Nexus snapshot directory.
> If this already is prevented (perhaps by the Nexus configuration?) then please indicate, and close this issue.
> Otherwise, googling found a plugin for Hudson which checks to insure builds are snapshot builds, and won't deploy if they are non-snapshot builds; the plugin is here: http://code.google.com/p/maven-hudson-ext-plugin/
> If possible, see if installing this plugin adds a post-build item to deploy SNAPSHOTs (only) to the list of actions, and works appropriately.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira