How to work around HG https Authentication limitations

Continua CI Discussion
1

I looks like HTTPS authentication for HG is a lot harder that expected as it's still an known issue.  If Final Builder projects include all those actions, can we configure continua to use those to execute those actions until it's integrated into the continua?

How would this work, practically in continua. Would you

  1. Have one configuration that was just executing the FB project to "pull" changes to the server periodically. 
  2. Have a second configuration that did a file monitor on the local repo and detect changes and then trigger off all the normal build + Unit test + Package + distribute stages?

I must admit to re-think the way I've put together all my FB projects actions when it comes to Continua. Essentially I can see that continua will allow those projects to be cut up into small "stages" of work due to the greater flexibility within Continua CI over FB CI Server.

2

Hi Jamie

I just created a trial kiln account so I’ll try getting it working with Continua. You should just be able treat it like a normal repository.

3

Ok, I have https working and working great using kiln access tokens. Build 892 is running now… should be uploaded in 30 minuts or so.

4

Build 892 uploaded.

5

Sweet.

6

Confirm build 892 connects to HG over SSL and validates with Kiln via AccessTokens. Thanks.

7

Oh yeah, I forgot to mention that I tested kiln with access tokens.