I know Sauce Connect pretty well from my days working at Sauce Labs :)

Not sure if appropriate for the dev list - if not, message me on slack
and I'd be happy to help any way I can.

On Wed, Jun 21, 2017 at 11:34 AM,  <[email protected]> wrote:
> Yeah, forgot to give a link to JIRA issue:
> https://issues.apache.org/jira/browse/CB-12935
>
> For now, I'm wrestling with Sauce Connect and jwt plugins for Travis in an 
> attempt to make secure variables work for PRs from external forks. Besides 
> that, there is nothing holding us from running these builds, so if you have 
> any insight on that, I'd be glad to hear it.
>
> -----Original Message-----
> From: Filip Maj [mailto:[email protected]]
> Sent: Wednesday, June 21, 2017 4:33 PM
> To: [email protected]
> Subject: Re: Cloudapp CI is down, builds moving to Travis
>
> Any JIRA issues we should look at to track progress?
>
> Alex, what can we do to assist? seems like a lot of work - let us know!
>
> On Wed, Jun 21, 2017 at 5:39 AM,  <[email protected]> wrote:
>> Our Plugins testing CI (Jenkins) is officially dead now.
>> We're migrating all the jobs to Travis and AppVeyor, but for the time
>> being, all PRs to the plugin repos are not being tested. I'm working
>> to enable Travis and AppVeyor builds as soon as possible, but there
>> are some unexpected hassle with encrypted env.variables.
>>
>> Will keep you posted.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to