openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Santana <>
Subject Re: Travis runs for test involving access to Cloud Services requiring secret access key
Date Fri, 20 Apr 2018 11:14:58 GMT
Hi Chetan

I proposed a new option 3 :-)

We can configure Travis to skip this tests when the build is on PR and run the tests when
build is on master branch. 

So creating a new gradle task for it testLeanPR

The same for doing the decryption of the secret will be done only when is not a PR build.

We already do this and I can work with you to setup I know I have some repos doing this for
ibmfunctions and I think wskdeploy also has similar Travis setup using credentials

If you do this configuration your PR will be green and will be able to merge it into master.

In terms running the tests on your branch on your fork for the PR, you can setup your fork
to run the Travis tests and share the link as comment on the PR pointing to the Travis build
passing and running the tests. 

With that then I think we can feel confident and merge the PR and the tests will run again
in master branch in main repo. 

- Carlos Santana

> On Apr 20, 2018, at 5:21 AM, Chetan Mehrotra <> wrote:
> Hi Team,
> For some of the work I am doing (CosmosDB integration [1], S3
> AttachmentStore) the test need to be run against a remote cloud
> service and thus requires access to access keys.
> For CosmosDB PR I tried to read them from environment variables [2]
> and have them configured in the Travis settings for the repo. However
> it appears that those environment variables are not exposed for PR
> runs (for good reason) and instead are only accessible to PR which
> originate from same origin repo [3]. Due to this the build failed [4]
> for PR but passed on the build from fork [5]
> So I see following options
> 1. Have a branch in incubator-openwhisk repo and then create a PR from that.
> 2. Keep working on a branch in fork and then reviewers can run the
> test on there setup by providing the credentials directly.
> So any thoughts on how  to proceed on this work? I prefer #1 but that
> would require me to work on a branch in incubator-openwhisk repo and
> create PR from that
> Chetan Mehrotra
> [1]
> [2]
> [3]
> [4]
> [5] (see
> status for artifact-store-cosmos)

View raw message