chore(ci): cleanup artifact upload

[alexeagle]

This is no longer needed for g3sync. Also, it frees up a travis worker.

[IgorMinar]

The build only job is also used for payload size analytics and continuous delivery to npm and pub.

Can you keep it and just remove the upload to gcs?

[alexeagle]

Sure, done.
It still seems like we ought to be able to save a travis worker. We already do these build steps in other builds. A small change in publish-build-artifacts.sh seems sufficient. Is that worth doing?

[IgorMinar]

discussed offline... let's move the work to other works in a new PR.

Can you also create an issue to audit our CI jobs and document what's
running where in a similar fashion as we document our bundles:
https://github.com/angular/angular/blob/d116861c8e884d911f15b8caabeefc6f049c775d/modules/angular2/docs/bundles/overview.md#es5-and-ngupgrade-users
or
maybe even create a DSL for job splitup similar to how we will soon test
angular on various browsers:
https://github.com/angular/angular/pull/5795/files#diff-6c156334b18015a66bc1bb55cedd6838R5

On Mon, Jan 4, 2016 at 9:28 AM Alex Eagle notifications@github.com wrote:

Sure, done.
It still seems like we ought to be able to save a travis worker. We
already do these build steps in other builds. A small change in
publish-build-artifacts.sh seems sufficient. Is that worth doing?

—
Reply to this email directly or view it on GitHub
#6232 (comment).

[alexeagle]

filed #6256 for the follow-up

[alexeagle]

ready to merge

[mary-poppins]

Merging PR #6232 on behalf of @alxhub to branch presubmit-alxhub-pr-6232.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}