Linaro Android Build Tools

Merge lp://staging/~pfalcon/linaro-android-build-tools/migrate-new-pub into lp://staging/linaro-android-build-tools

migrate-new-pub
Merge into trunk

Proposed by Paul Sokolovsky on 2012-05-17

Status:	Merged
Merged at revision:	472
Proposed branch:	lp://staging/~pfalcon/linaro-android-build-tools/migrate-new-pub
Merge into:	lp://staging/linaro-android-build-tools
Diff against target:	82 lines (+11/-11) 1 file modified utils/mangle-jobs/builders.xml (+11/-11)
To merge this branch:	bzr merge lp://staging/~pfalcon/linaro-android-build-tools/migrate-new-pub
Related bugs:	Link a bug report

Reviewer	Date Requested	Status
Fathi Boudra	2012-05-17	Approve on 2012-05-17
Linaro Infrastructure	2012-05-17	Pending
Review via email: mp+106174@code.staging.launchpad.net

This proposal supersedes a proposal from 2012-05-17.

Description of the change

Migration script (actually, only updated data) to switch to new publishing script consistently on android-build.

Revision history for this message

Fathi Boudra (fboudra) wrote on 2012-05-17:

Approved.

"snapshots.linaro.org file-move new" is using linaro-android-build-publish account.
Does it still make sense to have 2 accounts (linaro-ci-publish) duplicating the same thing?
We deploy linaro-license-protection on both accounts and use them in the same way.

review: Approve

Revision history for this message

Paul Sokolovsky (pfalcon) wrote on 2012-05-18:

> Does it still make sense to have 2 accounts (linaro-ci-publish) duplicating the same thing?

AFAIK, it's IS thing, and done for security reasons. They have accounts config tight - e.g., check the exact source address for connections. So, let's start with tearing off 3rd account we have there (for sh-based publisher script) which we no longer need.

Revision history for this message

Paul Sokolovsky (pfalcon) wrote on 2012-05-18:

Deployed.