You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Bhuvan Arumugam (Created) (JIRA)" <ji...@apache.org> on 2012/02/02 01:31:53 UTC
[jira] [Created] (INFRA-4384) enable access to build machines
enable access to build machines
-------------------------------
Key: INFRA-4384
URL: https://issues.apache.org/jira/browse/INFRA-4384
Project: Infrastructure
Issue Type: Task
Security Level: public (Regular issues)
Components: Jenkins
Reporter: Bhuvan Arumugam
Priority: Minor
I'm validating the instructions in Jenkins wiki page. To confirm the instructions are accurate, I wish to login to builds.apache.org. For instance, the command to restart jenkins is: /etc/init.d/hudson restart. I wish to confirm if it's /etc/init.d/jenkins.
http://wiki.apache.org/general/Jenkins
I'm also interested to investigate the possibility to upgrade Jenkins periodically and setup yum based upgrade, if it's not already setup.
I had access in the past, but it seem to be broken now. I am able to login to people.apache.org using my LDAP password, but couldn't login to master and any slaves.
bhuvan@minotaur:~$ ssh builds.apache.org
Permission denied (publickey,keyboard-interactive).
bhuvan@minotaur:~$ ssh juno.apache.org
Permission denied (publickey,keyboard-interactive).
Can someone enable access to my account?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (INFRA-4384) enable access to build machines
Posted by "Niklas Gustavsson (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Niklas Gustavsson closed INFRA-4384.
------------------------------------
Resolution: Won't Fix
Assignee: Niklas Gustavsson
We do no longer provide access to the build master or slaves except to infra volunteers.
As for your questions. Yes, we still use /etc/init.d/hudson and no, we do not use yum. Since Jenkins runs on Ubuntu, apt would be more appropriate, and we use that where applicable, although not for Jenkins itself.
> enable access to build machines
> -------------------------------
>
> Key: INFRA-4384
> URL: https://issues.apache.org/jira/browse/INFRA-4384
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Jenkins
> Reporter: Bhuvan Arumugam
> Assignee: Niklas Gustavsson
> Priority: Minor
>
> I'm validating the instructions in Jenkins wiki page. To confirm the instructions are accurate, I wish to login to builds.apache.org. For instance, the command to restart jenkins is: /etc/init.d/hudson restart. I wish to confirm if it's /etc/init.d/jenkins.
> http://wiki.apache.org/general/Jenkins
> I'm also interested to investigate the possibility to upgrade Jenkins periodically and setup yum based upgrade, if it's not already setup.
> I had access in the past, but it seem to be broken now. I am able to login to people.apache.org using my LDAP password, but couldn't login to master and any slaves.
> bhuvan@minotaur:~$ ssh builds.apache.org
> Permission denied (publickey,keyboard-interactive).
> bhuvan@minotaur:~$ ssh juno.apache.org
> Permission denied (publickey,keyboard-interactive).
> Can someone enable access to my account?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira