Jenkins build is back to normal : airavata-dev #850

2016-10-19 Thread Apache Jenkins Server 
See

Build failed in Jenkins: airavata-dev #849

2016-10-19 Thread Apache Jenkins Server 
See 

--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on ubuntu-us1 (Ubuntu ubuntu docker) in workspace 
/home/jenkins/jenkins-slave/workspace/airavata-dev
 > 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/airavata.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/airavata.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/airavata.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
Checking out Revision 08e306e01085e7c3b6003e1f771922683cd4c0f1 
(refs/remotes/origin/develop)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 08e306e01085e7c3b6003e1f771922683cd4c0f1
 > git rev-list 08e306e01085e7c3b6003e1f771922683cd4c0f1 # timeout=10
ERROR: Processing failed due to a bug in the code. Please report this to 
jenkinsci-us...@googlegroups.com
hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
at hudson.remoting.Request.abort(Request.java:303)
at hudson.remoting.Channel.terminate(Channel.java:847)
at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1080)
at hudson.remoting.Channel$1.handle(Channel.java:501)
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:83)
at ..remote call to ubuntu-us1(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
at hudson.remoting.Request.call(Request.java:172)
at hudson.remoting.Channel.call(Channel.java:780)
at hudson.FilePath.act(FilePath.java:1102)
at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:629)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
at hudson.model.Run.execute(Run.java:1741)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: hudson.remoting.Channel$OrderlyShutdown
at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1080)
at hudson.remoting.Channel$1.handle(Channel.java:501)
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:83)
Caused by: Command close created at
at hudson.remoting.Command.(Command.java:56)
at hudson.remoting.Channel$CloseCommand.(Channel.java:1074)
at hudson.remoting.Channel$CloseCommand.(Channel.java:1072)
at hudson.remoting.Channel.close(Channel.java:1156)
at hudson.remoting.Channel.close(Channel.java:1138)
at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1079)
... 2 more
project=hudson.maven.MavenModuleSet@757623a9[airavata-dev]
project.getModules()=[hudson.maven.MavenModule@36f49bb[airavata-dev/org.apache.airavata:airavata][airavata-dev/org.apache.airavata:airavata][relativePath:],
 
hudson.maven.MavenModule@53084561[airavata-dev/org.apache.airavata:airavata-api][airavata-dev/org.apache.airavata:airavata-api][relativePath:airavata-api],
 
hudson.maven.MavenModule@31c94b29[airavata-dev/org.apache.airavata:airavata-api-server][airavata-dev/org.apache.airavata:airavata-api-server][relativePath:airavata-api/airavata-api-server],
 
hudson.maven.MavenModule@74ccc7b4[airavata-dev/org.apache.airavata:airavata-api-stubs][airavata-dev/org.apache.airavata:airavata-api-stubs][relativePath:airavata-api/airavata-api-stubs],
 
hudson.maven.MavenModule@d177a07[airavata-dev/org.apache.airavata:airavata-client-configuration][airavata-dev/org.apache.airavata:airavata-client-configuration][relativePath:modules/configuration/client],
 
hudson.maven.MavenModule@1ca50589[airavata-dev/org.apache.airavata:airavata-client-samples][airavata-dev/org.apache.airavata:airavata-client-samples][relativePath:airavata-api/airavata-client-sdks/java-client-samples],
 
hudson.maven.MavenModule@674e9537[airavata-dev/org.apache.airavata:airavata-client-sdks][airavata-dev/org.apache.airavata:airavata-client-sdks][relativePath:airavata-api/airavata-client-sdks],
 
hudson.maven.MavenModule@75ad0f0d[airavata-dev/org.apache.airavata:airavata-commons][airavata-dev/org.apache.airavata:airavata-commons][relativePath:modules/commons],
 
hudson.maven.MavenModule@435c84fd[airavata-dev/org.apache.airavata:airavata-configuration][airavata-dev/org.apache.airavata:airavata-configuration][relativePath:modules/configuration],

Jenkins build is back to normal : airavata-dev #848

2016-10-19 Thread Apache Jenkins Server 
See

Build failed in Jenkins: airavata-dev » Airavata API Server #847

2016-10-19 Thread Apache Jenkins Server 
See 


Changes:

[scnakandala] fixing entity conversion issue

--
[INFO] 
[INFO] 
[INFO] Building Airavata API Server 0.17-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ airavata-api-server 
---
[INFO] Deleting 

[INFO] 
[INFO] --- maven-resources-plugin:2.5:copy-resources (copy-resources) @ 
airavata-api-server ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] 
[INFO] --- gitdescribe-maven-plugin:3.0:gitdescribe (git-describe) @ 
airavata-api-server ---
[INFO] Setting Git Describe: airavata-0.16-280-g61d7b68
[INFO] 
[INFO] --- templating-maven-plugin:1.0.0:filter-sources 
(filtering-java-templates) @ airavata-api-server ---
[INFO] Request to add 
'
 folder. Not added since it does not exist.
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
airavata-api-server ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
airavata-api-server ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
airavata-api-server ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 24 source files to 

[INFO] -
[WARNING] COMPILATION WARNING : 
[INFO] -
[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 2 warnings 
[INFO] -
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
:[115,13]
 cannot find symbol
  symbol:   class Domain
  location: class org.apache.airavata.api.server.handler.AiravataServerHandler
[ERROR] 
:[115,33]
 cannot find symbol
  symbol:   class Domain
  location: class org.apache.airavata.api.server.handler.AiravataServerHandler
[ERROR] 
:[121,13]
 cannot find symbol
  symbol:   class User
  location: class org.apache.airavata.api.server.handler.AiravataServerHandler
[ERROR] 
:[121,29]
 cannot find symbol
  symbol:   class User
  location: class org.apache.airavata.api.server.handler.AiravataServerHandler
[ERROR] 
:[128,13]
 cannot find symbol
  symbol:   class EntityType
  location: class org.apache.airavata.api.server.handler.AiravataServerHandler
[ERROR] 
:[128,41]
 cannot find symbol
  symbol:   class EntityType
  location: class org.apache.airavata.api.server.handler.AiravataServerHandler

[jira] [Commented] (AIRAVATA-2152) UI for to add compute resource/storage allocations

2016-10-19 Thread Marcus Christie (JIRA) 

[ 
https://issues.apache.org/jira/browse/AIRAVATA-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15589832#comment-15589832
 ] 

Marcus Christie commented on AIRAVATA-2152:
---

[~shameera],

Can you review Anuj's pull request? https://github.com/apache/airavata/pull/56

> UI for to add compute resource/storage allocations
> --
>
> Key: AIRAVATA-2152
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2152
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>




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

Jenkins build is back to stable : airavata-dev #846

2016-10-19 Thread Apache Jenkins Server 
See

Jenkins build is back to stable : airavata-dev » Airavata Registry Core #846

2016-10-19 Thread Apache Jenkins Server 
See

Jenkins build is still unstable: airavata-dev » Airavata Registry Core #845

2016-10-19 Thread Apache Jenkins Server 
See

Jenkins build is still unstable: airavata-dev #845

2016-10-19 Thread Apache Jenkins Server 
See

[jira] [Commented] (AIRAVATA-2177) Changes to "Data is Staged?" are not persisted in Application Interface

2016-10-19 Thread Marcus Christie (JIRA) 

[ 
https://issues.apache.org/jira/browse/AIRAVATA-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15589701#comment-15589701
 ] 

Marcus Christie commented on AIRAVATA-2177:
---

Do you think we should look into why it isn't getting persisted? Or should we 
just remove it from the UI?

> Changes to "Data is Staged?" are not persisted in Application Interface
> ---
>
> Key: AIRAVATA-2177
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2177
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>
> In the Application Interface part of PGA, changing the "Data is Staged?" 
> setting doesn't persist.



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

Jenkins build is still unstable: airavata-dev #844

2016-10-19 Thread Apache Jenkins Server 
See

Jenkins build is still unstable: airavata-dev » Airavata Registry Core #844

2016-10-19 Thread Apache Jenkins Server 
See

[jira] [Created] (AIRAVATA-2179) Ansible script for Airavata installation fails at TASK [common : Run maven build] ********

2016-10-19 Thread Eroma (JIRA) 
Eroma created AIRAVATA-2179:
---

 Summary: Ansible script for Airavata installation fails at TASK 
[common : Run maven build] 
 Key: AIRAVATA-2179
 URL: https://issues.apache.org/jira/browse/AIRAVATA-2179
 Project: Airavata
  Issue Type: Bug
Reporter: Eroma
Assignee: Shameera Rathnayaka


Ansible script fails at TASK [common : Run maven build] 






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

[jira] [Commented] (AIRAVATA-2177) Changes to "Data is Staged?" are not persisted in Application Interface

2016-10-19 Thread Eroma (JIRA) 

[ 
https://issues.apache.org/jira/browse/AIRAVATA-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15589635#comment-15589635
 ] 

Eroma commented on AIRAVATA-2177:
-

Currently data is staged irrespective of the 'true' 'false' we enter in 
application interface.
As per my understanding staging is having the files available in the working 
directory of each experiment

> Changes to "Data is Staged?" are not persisted in Application Interface
> ---
>
> Key: AIRAVATA-2177
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2177
> Project: Airavata
>  Issue Type: Bug
>Reporter: Marcus Christie
>
> In the Application Interface part of PGA, changing the "Data is Staged?" 
> setting doesn't persist.



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

[GitHub] airavata pull request #59: uploading initial project structure

2016-10-19 Thread anujbhan 
GitHub user anujbhan opened a pull request:

https://github.com/apache/airavata/pull/59

uploading initial project structure

* Minimum bare bones implementation of thrift interface. 
* Next task would be to add the initial data-models 

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

$ git pull https://github.com/anujbhan/airavata allocation-manager

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

https://github.com/apache/airavata/pull/59.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 #59


commit fd42b790bcc403405127c1bb9785c6e1708a13b6
Author: Anuj Bhandar 
Date:   2016-10-19T19:08:16Z

uploading initial project structure




---
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.
---

[GitHub] airavata issue #58: Initial Project Structure

2016-10-19 Thread anujbhan 
Github user anujbhan commented on the issue:

https://github.com/apache/airavata/pull/58
  
I did a git rebase, but thought of pulling the develop branch changes as 
well, But now I realized, it is not needed.

Doing a proper rebase.


---
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.
---

[GitHub] airavata issue #58: Initial Project Structure

2016-10-19 Thread smarru 
Github user smarru commented on the issue:

https://github.com/apache/airavata/pull/58
  
@anujbhan this one will be hard to review. Can you do a git rebase instead 
of git merge so we can only look at your commits? 


---
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] [Created] (AIRAVATA-2178) GFAC changes for user specific compute resource preferences

2016-10-19 Thread Eroma (JIRA) 
Eroma created AIRAVATA-2178:
---

 Summary: GFAC changes for user specific compute resource 
preferences
 Key: AIRAVATA-2178
 URL: https://issues.apache.org/jira/browse/AIRAVATA-2178
 Project: Airavata
  Issue Type: Sub-task
  Components: GFac
Reporter: Eroma
Assignee: Shameera Rathnayaka






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

Jenkins build became unstable: airavata-dev #843

2016-10-19 Thread Apache Jenkins Server 
See

[jira] [Commented] (AIRAVATA-2174) Allow sharing an experiment irrespective of the experiment's status

2016-10-19 Thread Marcus Christie (JIRA) 

[ 
https://issues.apache.org/jira/browse/AIRAVATA-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588677#comment-15588677
 ] 

Marcus Christie commented on AIRAVATA-2174:
---

I think this task is basically done. I just want to do a little more testing.  
Waiting on dev seagrid Airavata to come back up.

> Allow sharing an experiment irrespective of the experiment's status
> ---
>
> Key: AIRAVATA-2174
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2174
> Project: Airavata
>  Issue Type: Sub-task
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>




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

[jira] [Commented] (AIRAVATA-2170) When editing a project, only the owner can change the sharing settings

2016-10-19 Thread Marcus Christie (JIRA) 

[ 
https://issues.apache.org/jira/browse/AIRAVATA-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588665#comment-15588665
 ] 

Marcus Christie commented on AIRAVATA-2170:
---

I talked with [~scnakandala] and he is going to add the OWNER 
ResourcePermissionType to the sharing API. Then I'll be able to call 
getAllAccessibleUsers with the OWNER permission type.

> When editing a project, only the owner can change the sharing settings
> --
>
> Key: AIRAVATA-2170
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2170
> Project: Airavata
>  Issue Type: Sub-task
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>




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

Jenkins build is back to stable : airavata-dev #840

2016-10-19 Thread Apache Jenkins Server 
See

Jenkins build is back to stable : airavata-dev » Airavata Registry Core #840

2016-10-19 Thread Apache Jenkins Server 
See

Jenkins build is still unstable: airavata-dev » Airavata Registry Core #839

2016-10-19 Thread Apache Jenkins Server 
See

Jenkins build is still unstable: airavata-dev #839

2016-10-19 Thread Apache Jenkins Server 
See

Jenkins build is still unstable: airavata-dev » Airavata Registry Core #838

2016-10-19 Thread Apache Jenkins Server 
See

Jenkins build is still unstable: airavata-dev #838

2016-10-19 Thread Apache Jenkins Server 
See

Jenkins build is unstable: airavata-dev #837

2016-10-19 Thread Apache Jenkins Server 
See

Jenkins build became unstable: airavata-dev » Airavata Registry Core #837

2016-10-19 Thread Apache Jenkins Server 
See