Nikolay helped me set up the AWS account and the tests were green after the
upgrade. No regressions after 3 local runs. I'll merge to master.

The problem with the tests may be that the env variables include dots (.) –
which are invalid in Linux machines. I had to change these to underscores
to test in my Mac.

I can have a quick look at this in TeamCity, but first I need to know how
and where to manage secret parameters in TeamCity? The build configurations
reference parameters with prefix "secret:" =>
%secure:teamcity.password.env.test.amazon.access.key%.

Regards,

*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

On Thu, Oct 29, 2015 at 2:04 PM, Nikolay Tikhonov <ntikho...@gridgain.com>
wrote:

> Raul,
>
> AWS build on TC is broken by another reason. Admin investigates this issue.
> For local testing you could use AWS Free Tier. (
> https://aws.amazon.com/free/
> )
>
> On Thu, Oct 29, 2015 at 4:25 PM, Denis Magda <dma...@gridgain.com> wrote:
>
> > Nick, should know the credentials.
> >
> > Nick, please help Raul with the setup.
> >
> >
> > --
> > Denis
> >
> >
> > On 10/29/2015 4:16 PM, Raul Kripalani wrote:
> >
> >> I'm working on upgrading the dependencies of ignite-aws, as we need the
> >> upgrade for OSGi integration.
> >>
> >> Unfortunately, it seems the AWS builds on TeamCity are failing because
> the
> >> AWS API params cannot be resolved:
> >>
> >> %secure:teamcity.password.env.test.amazon.access.key%
> >> %secure:teamcity.password.env.test.amazon.secret.key%
> >>
> >> Could someone please have a look?
> >>
> >> If you can provide me the keys in private, I'd be grateful. That way I
> >> won't have to push the changes to test them.
> >>
> >> Regards,
> >>
> >> *Raúl Kripalani*
> >> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data
> and
> >> Messaging Engineer
> >> http://about.me/raulkripalani |
> http://www.linkedin.com/in/raulkripalani
> >> http://blog.raulkr.net | twitter: @raulvk
> >>
> >>
> >
>

Reply via email to