Build failed in Jenkins: brooklyn-master-windows #179

2016-07-01 Thread Apache Jenkins Server 
See 

--
Started by upstream project "brooklyn-master-build" build number 284
originally caused by:
 Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-1 (Windows) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/brooklyn.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/brooklyn.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/brooklyn.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse "origin/master^{commit}" # timeout=10
Checking out Revision e9ea4570b82ae6d41a9197d45ba576a173c1d275 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f e9ea4570b82ae6d41a9197d45ba576a173c1d275
 > git rev-list e9ea4570b82ae6d41a9197d45ba576a173c1d275 # timeout=10
 > git remote # timeout=10
 > git submodule init # timeout=10
 > git submodule sync # timeout=10
 > git config --get remote.origin.url # timeout=10
 > git submodule update --init --recursive --remote
[brooklyn-master-windows] $ cmd /c call 
C:\Windows\TEMP\hudson2841056726912856099.bat

git> submodule 
foreach "git checkout master & git pull origin master" 
Entering 'brooklyn-client'
Your branch is up-to-date with 'origin/master'.
Already on 'master'
>From https://github.com/apache/brooklyn-client
 * branchmaster -> FETCH_HEAD
Already up-to-date.
Entering 'brooklyn-dist'
Your branch is up-to-date with 'origin/master'.
Already on 'master'
>From https://github.com/apache/brooklyn-dist
 * branchmaster -> FETCH_HEAD
Already up-to-date.
Entering 'brooklyn-docs'
Your branch is behind 'origin/master' by 2 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)
Previous HEAD position was ed10f42... This closes #84
Switched to branch 'master'
>From https://github.com/apache/brooklyn-docs
 * branchmaster -> FETCH_HEAD
warning: fetch updated the current branch head.
fast-forwarding your working tree from
commit ed10f420b062b98f0beeebce89574baedcbcc9ba.
error: Your local changes to the following files would be overwritten by merge:
guide/ops/locations/_byon.md
guide/ops/locations/_clouds.md
guide/ops/locations/_localhost.md
Please, commit your changes or stash them before you can merge.
Aborting
fatal: Cannot fast-forward your working tree.
After making sure that you saved anything precious from
$ git diff ed10f420b062b98f0beeebce89574baedcbcc9ba
output, run
$ git reset --hard
to recover.
Stopping at 'brooklyn-docs'; script returned non-zero status.

exit> 1 
Build step 'Execute Windows batch command' marked build as failure

[GitHub] brooklyn-server issue #227: Fixes BrooklynFeatureEnablement setting defaults

2016-07-01 Thread nakomis 
Github user nakomis commented on the issue:

https://github.com/apache/brooklyn-server/pull/227
  
One comment unrelated to this PR. Other than that, code looks good. Is 
there an documentation that explains the explicit precedence?


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (BROOKLYN-311) Problems with RiakCluster on Centos 7

2016-07-01 Thread Geoff Macartney (JIRA) 

[ 
https://issues.apache.org/jira/browse/BROOKLYN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15358797#comment-15358797
 ] 

Geoff Macartney commented on BROOKLYN-311:
--

Also of interest  
http://developerblog.redhat.com/2014/05/05/running-systemd-within-docker-container/

> Problems with RiakCluster on Centos 7
> -
>
> Key: BROOKLYN-311
> URL: https://issues.apache.org/jira/browse/BROOKLYN-311
> Project: Brooklyn
>  Issue Type: Bug
>Reporter: Geoff Macartney
>Priority: Minor
>
> I tried to get a RiakCluster entity going on a Centos 7 Docker image based on 
> centos:7 and ran into problems.  
> The immediate cause of failure was in the launch stage
> {code}
> d4HlHNpa   ssh: launching RiakNodeImpl{id=t02d2i...   Mon Jun 20 04:53:30 CDT 
> 2016   Failed  env,stderr,stdin,stdout 
> ...
> $ br app riak-on-swarm-master ent t02d2ihg3z activity d4HlHNpa stderr
> sh: service: command not found
> {code}
> I worked around that manually by installing 'initscripts' in order to get the 
> service command, but Riak still failed to start, with a less immediately 
> obvious error:
> {code}
> # service riak start
> Failed to get D-Bus connection: Operation not permitted
> Failed to get D-Bus connection: Operation not permitted
> Starting riak (via systemctl):  Failed to get D-Bus connection: Operation not 
> permitted
>[FAILED]
> {code}



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

[jira] [Commented] (BROOKLYN-311) Problems with RiakCluster on Centos 7

2016-07-01 Thread Svetoslav Neykov (JIRA) 

[ 
https://issues.apache.org/jira/browse/BROOKLYN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15358771#comment-15358771
 ] 

Svetoslav Neykov commented on BROOKLYN-311:
---

https://github.com/docker-library/docs/tree/master/centos#systemd-integration

> Problems with RiakCluster on Centos 7
> -
>
> Key: BROOKLYN-311
> URL: https://issues.apache.org/jira/browse/BROOKLYN-311
> Project: Brooklyn
>  Issue Type: Bug
>Reporter: Geoff Macartney
>Priority: Minor
>
> I tried to get a RiakCluster entity going on a Centos 7 Docker image based on 
> centos:7 and ran into problems.  
> The immediate cause of failure was in the launch stage
> {code}
> d4HlHNpa   ssh: launching RiakNodeImpl{id=t02d2i...   Mon Jun 20 04:53:30 CDT 
> 2016   Failed  env,stderr,stdin,stdout 
> ...
> $ br app riak-on-swarm-master ent t02d2ihg3z activity d4HlHNpa stderr
> sh: service: command not found
> {code}
> I worked around that manually by installing 'initscripts' in order to get the 
> service command, but Riak still failed to start, with a less immediately 
> obvious error:
> {code}
> # service riak start
> Failed to get D-Bus connection: Operation not permitted
> Failed to get D-Bus connection: Operation not permitted
> Starting riak (via systemctl):  Failed to get D-Bus connection: Operation not 
> permitted
>[FAILED]
> {code}



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