couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kxepal <...@git.apache.org>
Subject [GitHub] couchdb pull request: Use cluster setup in dev run
Date Sat, 04 Apr 2015 23:21:54 GMT
GitHub user kxepal opened a pull request:

    https://github.com/apache/couchdb/pull/313

    Use cluster setup in dev run

    Since `/_cluster_setup`  requires Admin Party to be fixed it's not suitable for running
our JavaScript test suite which requires Admin Party to be on. So the old way to make a cluster
is provided now as an option.
    
    Also I a bit modified output to make it nicer and show all possible issues without making
a look that it's hanged:
    
    ```
    [ * ] Setup environment ... ok
    [ * ] Ensure CouchDB is built ... ok
    [ * ] Prepare configuration files ... ok
    [ * ] Start node node1 ... ok
    [ * ] Start node node2 ... ok
    [ * ] Start node node3 ... ok
    [ * ] Check node at http://127.0.0.1:15984/ ... failed: <urlopen error [Errno 111]
Connection refused>
    [ * ] Check node at http://127.0.0.1:25984/ ... failed: <urlopen error [Errno 111]
Connection refused>
    [ * ] Check node at http://127.0.0.1:35984/ ... ok
    [ * ] Check node at http://127.0.0.1:15984/ ... ok
    [ * ] Check node at http://127.0.0.1:25984/ ... ok
    [ * ] Running cluster setup ... ok
    [ * ] Developers cluster is set up at http://127.0.0.1:15984.
    Admin username: root
    Password: AaqFj+kO
    Time to hack! ... 
    ```
    
    cc @janl @robertkowalski

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kxepal/couchdb use-cluster-setup-in-dev-run

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb/pull/313.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #313
    
----
commit bfe1e3abec60ee34e88e691685510f1a49a7aba6
Author: Alexander Shorin <kxepal@apache.org>
Date:   2015-04-04T20:33:09Z

    More verbose check nodes for being alive

commit ab6e67d46a0a811184433a66def205fe5f677779
Author: Alexander Shorin <kxepal@apache.org>
Date:   2015-04-04T21:08:00Z

    Fulfill /_cluster_setup requirements
    
    - bind_address shouldn't be 127.0.0.1
    - admin party should be fixed

commit 20f74d945cd95624faf1474e803122920afed4e9
Author: Alexander Shorin <kxepal@apache.org>
Date:   2015-04-04T21:47:17Z

    Use /_cluster_setup

commit 42b504a4b947dbea3d40c32383d58c0b539e282b
Author: Alexander Shorin <kxepal@apache.org>
Date:   2015-04-04T22:18:01Z

    Print dev/run steps nicer

commit 07f8d760d8cb189af3be503725dd6b97100c3d09
Author: Alexander Shorin <kxepal@apache.org>
Date:   2015-04-04T22:54:51Z

    Add option to run dev cluster with Admin Party state

commit e7fc7f41e4e03aebd5bc13a8891d7c6ccde1eb76
Author: Alexander Shorin <kxepal@apache.org>
Date:   2015-04-04T22:55:27Z

    JavaScript tests are need in Admin Party

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message