2014-05-02 01:05:15 +00:00
|
|
|
# Jenkins Account Management/Sign-up App
|
|
|
|
|
[](http://ci.jenkins-ci.org/view/Infrastructure/job/infra_accountapp/)
|
|
|
|
|
|
|
|
|
|
## Testing locally
|
2012-12-22 17:33:07 +00:00
|
|
|
First, set up a tunnel to Jenkins LDAP server. Run the following command and keep the terminal open:
|
|
|
|
|
|
|
|
|
|
ssh -L 9389:localhost:389 cucumber.jenkins-ci.org
|
|
|
|
|
|
|
|
|
|
Create `config.properties` in the same directory as `pom.xml`. See the `Parameters` class for the details,
|
|
|
|
|
but it should look something like the following:
|
|
|
|
|
|
|
|
|
|
server=ldap://localhost:9389/
|
|
|
|
|
managerDN=cn=admin,dc=jenkins-ci,dc=org
|
|
|
|
|
newUserBaseDN=ou=people,dc=jenkins-ci,dc=org
|
|
|
|
|
smtpServer=localhost
|
|
|
|
|
recaptchaPublicKey=6Ld--8ASAAAAANHmHaM1sdSYshtmXTin1BNtaw86
|
|
|
|
|
recaptchaPrivateKey=*****
|
|
|
|
|
managerPassword=*****
|
2015-12-15 18:36:13 +00:00
|
|
|
circuitBreakerFile=./circuitBreaker.txt
|
|
|
|
|
url=http://localhost:8080/account/
|
2012-12-22 17:33:07 +00:00
|
|
|
|
|
|
|
|
Finally, run the application with Jetty, then access `http://localhost:8080/`:
|
|
|
|
|
|
|
|
|
|
mvn jetty:run
|
|
|
|
|
|
|
|
|
|
(As you can see above, this connects your test instance to the actual LDAP server, so the data you'll be seeing
|
2014-05-01 18:16:21 +00:00
|
|
|
is real.
|
|
|
|
|
|
|
|
|
|
|
2014-05-02 01:05:15 +00:00
|
|
|
## Packaging
|
2014-05-01 18:16:21 +00:00
|
|
|
For deploying to production, this app gets containerized. The container expects to see `/etc/accountapp` mounted
|
|
|
|
|
from outside that contains the abovementioned `config.properties`
|
|
|
|
|
|
