You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Kay Kay (JIRA)" <ji...@apache.org> on 2010/04/13 02:17:50 UTC
[jira] Created: (INFRA-2609) Nexus/Hudson - apache.snapshot.https -
build username for org.apache.hbase ?
Nexus/Hudson - apache.snapshot.https - build username for org.apache.hbase ?
-----------------------------------------------------------------------------
Key: INFRA-2609
URL: https://issues.apache.org/jira/browse/INFRA-2609
Project: Infrastructure
Issue Type: Task
Security Level: public (Regular issues)
Components: Hudson, Nexus
Reporter: Kay Kay
INFRA-2461 specifies about nexus access for hbase committers, for the groupID - org.apache.hbase .
We are trying to set up a hudson build to automatically deploy to snapshots for every successful build.
What are some of the best practices here (other than hardcoding the committer username/password in ~/.m2/settings.xml ) ?
Can there be a build user - who can get to publish to snapshot of org.apache.hbase . Any suggestions much appreciated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-2609) Nexus/Hudson - apache.snapshot.https
- build username for org.apache.hbase ?
Posted by "Kay Kay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856323#action_12856323 ]
Kay Kay commented on INFRA-2609:
--------------------------------
Great. That works.
So - how many snapshot builds are retained by nexus , at any given time. Can there be a limit specified (latest 5 builds, say) to restrict the number of snapshots retained ?
> Nexus/Hudson - apache.snapshot.https - build username for org.apache.hbase ?
> -----------------------------------------------------------------------------
>
> Key: INFRA-2609
> URL: https://issues.apache.org/jira/browse/INFRA-2609
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: Kay Kay
> Assignee: Brian Fox
>
> INFRA-2461 specifies about nexus access for hbase committers, for the groupID - org.apache.hbase .
> We are trying to set up a hudson build to automatically deploy to snapshots for every successful build.
> What are some of the best practices here (other than hardcoding the committer username/password in ~/.m2/settings.xml ) ?
> Can there be a build user - who can get to publish to snapshot of org.apache.hbase . Any suggestions much appreciated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-2609) Nexus/Hudson - apache.snapshot.https
- build username for org.apache.hbase ?
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856243#action_12856243 ]
Brian Fox commented on INFRA-2609:
----------------------------------
We create machine specific accounts that are able to deploy snapshots of org.apache.*....so unless you're using a new hudson install, it's likely that the machine is already configured for you.
> Nexus/Hudson - apache.snapshot.https - build username for org.apache.hbase ?
> -----------------------------------------------------------------------------
>
> Key: INFRA-2609
> URL: https://issues.apache.org/jira/browse/INFRA-2609
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Hudson, Nexus
> Reporter: Kay Kay
>
> INFRA-2461 specifies about nexus access for hbase committers, for the groupID - org.apache.hbase .
> We are trying to set up a hudson build to automatically deploy to snapshots for every successful build.
> What are some of the best practices here (other than hardcoding the committer username/password in ~/.m2/settings.xml ) ?
> Can there be a build user - who can get to publish to snapshot of org.apache.hbase . Any suggestions much appreciated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-2609) Nexus/Hudson - apache.snapshot.https
- build username for org.apache.hbase ?
Posted by "Kay Kay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856247#action_12856247 ]
Kay Kay commented on INFRA-2609:
--------------------------------
Brian: The hudson url under discussion is available here - http://hudson.zones.apache.org/hudson/view/HBase/job/HBase-Patch/ .
The server id - apache.snapshots.https .
So - this should take care of automatic deploy to org.apache.hbase namespace ?
> Nexus/Hudson - apache.snapshot.https - build username for org.apache.hbase ?
> -----------------------------------------------------------------------------
>
> Key: INFRA-2609
> URL: https://issues.apache.org/jira/browse/INFRA-2609
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Hudson, Nexus
> Reporter: Kay Kay
> Assignee: Brian Fox
>
> INFRA-2461 specifies about nexus access for hbase committers, for the groupID - org.apache.hbase .
> We are trying to set up a hudson build to automatically deploy to snapshots for every successful build.
> What are some of the best practices here (other than hardcoding the committer username/password in ~/.m2/settings.xml ) ?
> Can there be a build user - who can get to publish to snapshot of org.apache.hbase . Any suggestions much appreciated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (INFRA-2609) Nexus/Hudson - apache.snapshot.https -
build username for org.apache.hbase ?
Posted by "Kay Kay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kay Kay updated INFRA-2609:
---------------------------
Component/s: (was: Hudson)
> Nexus/Hudson - apache.snapshot.https - build username for org.apache.hbase ?
> -----------------------------------------------------------------------------
>
> Key: INFRA-2609
> URL: https://issues.apache.org/jira/browse/INFRA-2609
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: Kay Kay
> Assignee: Brian Fox
>
> INFRA-2461 specifies about nexus access for hbase committers, for the groupID - org.apache.hbase .
> We are trying to set up a hudson build to automatically deploy to snapshots for every successful build.
> What are some of the best practices here (other than hardcoding the committer username/password in ~/.m2/settings.xml ) ?
> Can there be a build user - who can get to publish to snapshot of org.apache.hbase . Any suggestions much appreciated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (INFRA-2609) Nexus/Hudson - apache.snapshot.https -
build username for org.apache.hbase ?
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed INFRA-2609.
----------------------------
Resolution: Fixed
Snapshots are retained for 10 days, always keeping at least 1. When a release is detected of the matching version, then all snapshots for that version are removed. The cleanup runs once a week.
> Nexus/Hudson - apache.snapshot.https - build username for org.apache.hbase ?
> -----------------------------------------------------------------------------
>
> Key: INFRA-2609
> URL: https://issues.apache.org/jira/browse/INFRA-2609
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: Kay Kay
> Assignee: Brian Fox
>
> INFRA-2461 specifies about nexus access for hbase committers, for the groupID - org.apache.hbase .
> We are trying to set up a hudson build to automatically deploy to snapshots for every successful build.
> What are some of the best practices here (other than hardcoding the committer username/password in ~/.m2/settings.xml ) ?
> Can there be a build user - who can get to publish to snapshot of org.apache.hbase . Any suggestions much appreciated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-2609) Nexus/Hudson - apache.snapshot.https
- build username for org.apache.hbase ?
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856249#action_12856249 ]
Brian Fox commented on INFRA-2609:
----------------------------------
Yes, that machine should be all set.
> Nexus/Hudson - apache.snapshot.https - build username for org.apache.hbase ?
> -----------------------------------------------------------------------------
>
> Key: INFRA-2609
> URL: https://issues.apache.org/jira/browse/INFRA-2609
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Hudson, Nexus
> Reporter: Kay Kay
> Assignee: Brian Fox
>
> INFRA-2461 specifies about nexus access for hbase committers, for the groupID - org.apache.hbase .
> We are trying to set up a hudson build to automatically deploy to snapshots for every successful build.
> What are some of the best practices here (other than hardcoding the committer username/password in ~/.m2/settings.xml ) ?
> Can there be a build user - who can get to publish to snapshot of org.apache.hbase . Any suggestions much appreciated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (INFRA-2609) Nexus/Hudson - apache.snapshot.https
- build username for org.apache.hbase ?
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox reassigned INFRA-2609:
--------------------------------
Assignee: Brian Fox
> Nexus/Hudson - apache.snapshot.https - build username for org.apache.hbase ?
> -----------------------------------------------------------------------------
>
> Key: INFRA-2609
> URL: https://issues.apache.org/jira/browse/INFRA-2609
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Hudson, Nexus
> Reporter: Kay Kay
> Assignee: Brian Fox
>
> INFRA-2461 specifies about nexus access for hbase committers, for the groupID - org.apache.hbase .
> We are trying to set up a hudson build to automatically deploy to snapshots for every successful build.
> What are some of the best practices here (other than hardcoding the committer username/password in ~/.m2/settings.xml ) ?
> Can there be a build user - who can get to publish to snapshot of org.apache.hbase . Any suggestions much appreciated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira