www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-11527) Connecting own build machines to Jenkins like Buildbot
Date Thu, 15 Sep 2016 00:01:42 GMT

     [ https://issues.apache.org/jira/browse/INFRA-11527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Lambertus updated INFRA-11527:
------------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

[~ipv6guru] has prototyped a method for this to work. It will require the following on your
end:

- A non-changing DNS entry or static IP address
- A 'jenkins' user created on the system
- Our jenkins ssh public key added to ~jenkins/.ssh/authorized_keys 

The current key can be found at https://github.com/apache/infrastructure-puppet/blob/deployment/data/ubuntu/1404.yaml#L261

Once this has been completed, let me know and we'll set up a test node on our end which will
connect to your system, install the appropriate agents, and add it to jenkins, then we'll
go from there.

> Connecting own build machines to Jenkins like Buildbot
> ------------------------------------------------------
>
>                 Key: INFRA-11527
>                 URL: https://issues.apache.org/jira/browse/INFRA-11527
>             Project: Infrastructure
>          Issue Type: Planned Work
>          Components: Jenkins
>            Reporter: Dmitry Blotsky
>            Assignee: Chris Lambertus
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> The Cordova project is improving its CI process and is planning to switch to the ASF
Jenkins instead of the ASF Buildbot. The Cordova build process requires custom tools like
mobile SDKs and emulators, and there are already machines connected to Buildbot that support
it. Is it possible to connect these build machines to Jenkins in a similar way to that of
Buildbot?
> Thank you in advance for investigating this use case!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message