Update from 9.x to 2017.2 --> MacBuild agent is not behaving as expected

Yesterday I finally updated our TC server to the 2017.2. In the process our Mac build agent, on which I build iOS Xamarin apps, changed its behaviour in an unexpected way.

I'm using fastlane match to mange our certs and after the update it stopped working as expected. I update the fastlane match settings using a command step that looks just like: 

 

/Users/example/.fastlane/bin/match adhoc --username build@example.com --force_for_new_devices --team_id XXXXXXX --app_identifier com.example.test --readonly false

That started failing after the update. 

When I run the same command from the terminal on the machine I have no troubles. 

If I run the command with the --verbose argument I find the following difference in my logs. On Teamcity I have: 

[19:35:31]INFO [2017-12-06 16:35:31.90]: $ security list-keychains -d user
[19:35:31]INFO [2017-12-06 16:35:31.91]: ▸ "/Library/Keychains/System.keychain"

but if I run it interactively I have

INFO [2017-12-06 16:58:32.77]: $ security list-keychains -d user
INFO [2017-12-06 16:58:32.78]: ▸     "/Users/example/Library/Keychains/login.keychain-db"

If I run the command over ssh from my local machine to the build server I also the user's specific keychain. 

Any idea?

0
1 comment
Avatar
Permanently deleted user

I think deleting all the expired certificates from the keychain, running security list-keychains -s /path/to/keychain *and* restarting solved the problem. One of those or all of those, I don't know. 

0

Please sign in to leave a comment.