Re: Integration Test Wiki

Thanks a lot Amila. It helps a lot. I will create the basic list of features and post it here. I got a good idea of what kind of tests you are looking for through this list. On Mon, Dec 16, 2013 at 11:15 PM, Amila Jayasekara wrote: > Hi Sachith, > > I am not sure what is expected from the page y

Re: Integration Test Wiki

Hi Sachith, I am not sure what is expected from the page you mentioned. But I have some idea what needs to be done. Let me explain briefly what I have in mind. We need to come up with an integration test for each feature we publish (We may not able to cover everything but needs to do as much as p

Jenkins build is still unstable: Apache Airavata #1267

See

Jenkins build is still unstable: Apache Airavata » Airavata Common Utilities #1267

See

Jenkins build is still unstable: Apache Airavata » Airavata Credential Store #1267

See

Re: [DISCUSS] Release Methodology

+1, please. - Thejaka Amila On Mon, Dec 16, 2013 at 2:05 PM, Suresh Marru wrote: > On Dec 16, 2013, at 1:51 PM, Saminda Wijeratne wrote: > > > I was thinking of an actual checklist where we can check-off/vote-off > once each test is done. Perhaps we can start with a simple spreadsheet with >

Re: [DISCUSS] Release Methodology

Heh--I started this on Rave, so I'm +1. Marlon On 12/16/13 2:05 PM, Suresh Marru wrote: > On Dec 16, 2013, at 1:51 PM, Saminda Wijeratne wrote: > >> I was thinking of an actual checklist where we can check-off/vote-off once >> each test is done. Perhaps we can start with a simple spreadsheet w

Re: [DISCUSS] Release Methodology

On Dec 16, 2013, at 1:51 PM, Saminda Wijeratne wrote: > I was thinking of an actual checklist where we can check-off/vote-off once > each test is done. Perhaps we can start with a simple spreadsheet with the > Tests specified by Raman added. + 1. Here is an example from Rave. Template for Qual

Re: [DISCUSS] Release Methodology

I was thinking of an actual checklist where we can check-off/vote-off once each test is done. Perhaps we can start with a simple spreadsheet with the Tests specified by Raman added. On Mon, Dec 16, 2013 at 10:24 AM, Chathuri Wimalasena wrote: > There is a general checklist added by Raman [1], wh

Integration Test Wiki

Added the For Each Test to the Wiki [1]. Can someone confirm whether this is correct and it's what is expected of the Wiki? [1] https://cwiki.apache.org/confluence/display/AIRAVATA/Integration+Tests -- Thanks, Sachith Withana

Re: [DISCUSS] Release Methodology

There is a general checklist added by Raman [1], which covers basic functionalities. Thanks.. Chathuri [1] https://cwiki.apache.org/confluence/display/AIRAVATA/Airavata+Release+Testing On Mon, Dec 16, 2013 at 12:56 PM, Saminda Wijeratne wrote: > > > > On Mon, Dec 16, 2013 at 9:28 AM, Suresh Ma

Re: [DISCUSS] Release Methodology

On Mon, Dec 16, 2013 at 9:28 AM, Suresh Marru wrote: > Thanks Amila for weighing in. Comments inline: > > On Dec 16, 2013, at 11:29 AM, Amila Jayasekara > wrote: > > > Hi Suresh, > > > > I have some comments inline. > > > > > > On Mon, Dec 16, 2013 at 10:53 AM, Suresh Marru > wrote: > > Hi All,

Re: [DISCUSS] Release Methodology

Thanks Amila for weighing in. Comments inline: On Dec 16, 2013, at 11:29 AM, Amila Jayasekara wrote: > Hi Suresh, > > I have some comments inline. > > > On Mon, Dec 16, 2013 at 10:53 AM, Suresh Marru wrote: > Hi All, > > This is a very good question. Lets discuss these options so we are con

Re: [DISCUSS] Release Methodology

Hi Suresh, I have some comments inline. On Mon, Dec 16, 2013 at 10:53 AM, Suresh Marru wrote: > Hi All, > > This is a very good question. Lets discuss these options so we are > consistent across releases. > > If we look at the way we are doing releases, we are calling a feature > freeze and co

[jira] [Commented] (AIRAVATA-965) Update Airavata JGLOBUS and Unicore jar

[ https://issues.apache.org/jira/browse/AIRAVATA-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849266#comment-13849266 ] Raminderjeet Singh commented on AIRAVATA-965: - I created a branch https://s

[jira] [Commented] (AIRAVATA-965) Update Airavata JGLOBUS and Unicore jar

[ https://issues.apache.org/jira/browse/AIRAVATA-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849246#comment-13849246 ] Suresh Marru commented on AIRAVATA-965: --- + 1. Branch or tag, but I would vote for

[jira] [Created] (AIRAVATA-969) GSISSH provider not fail on PBS Syntax errors

Raminderjeet Singh created AIRAVATA-969: --- Summary: GSISSH provider not fail on PBS Syntax errors Key: AIRAVATA-969 URL: https://issues.apache.org/jira/browse/AIRAVATA-969 Project: Airavata

[DISCUSS] Release Methodology

Hi All, This is a very good question. Lets discuss these options so we are consistent across releases. If we look at the way we are doing releases, we are calling a feature freeze and code freeze and cutting a release. Most of the time, our build is broken. Jenkins statistics for Airavata i

[jira] [Commented] (AIRAVATA-965) Update Airavata JGLOBUS and Unicore jar

[ https://issues.apache.org/jira/browse/AIRAVATA-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849203#comment-13849203 ] Raminderjeet Singh commented on AIRAVATA-965: - Can i create a branch with Jg