Skip to content

chore(build): add GCS upload of build artifacts#2946

Closed
alexeagle wants to merge 1 commit into
angular:masterfrom
alexeagle:travis_deploy
Closed

chore(build): add GCS upload of build artifacts#2946
alexeagle wants to merge 1 commit into
angular:masterfrom
alexeagle:travis_deploy

Conversation

@alexeagle
Copy link
Copy Markdown
Contributor

This copies the dist/ folder for each successful travis run
to a google cloud storage bucket, under the SHA of the commit.
We only upload for submitted changes, not PRs.
We can use this to fetch the dart sources for each SHA
without having to re-build them, which is hard to reproduce
since the environment might differ (eg. different Dart SDK)

This copies the dist/ folder for each successful travis run
to a google cloud storage bucket, under the SHA of the commit.
We only upload for submitted changes, not PRs.
We can use this to fetch the dart sources for each SHA
without having to re-build them, which is hard to reproduce
since the environment might differ (eg. different Dart SDK)
@alexeagle alexeagle added type: chore action: review The PR is still awaiting reviews from at least one requested reviewer labels Jul 8, 2015
Comment thread .travis.yml
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

technically not releases, just build artifacts.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

changed to angular2-snapshots

@rkirov rkirov added pr_state: LGTM action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Jul 8, 2015
@alexeagle
Copy link
Copy Markdown
Contributor Author

thanks, merged

@alexeagle alexeagle closed this Jul 8, 2015
@alexeagle alexeagle deleted the travis_deploy branch July 8, 2015 23:26
alexeagle added a commit to alexeagle/angular that referenced this pull request Jul 9, 2015
second attempt after rollback of angular#2946

After each successful build in the dart stable variant, this uploads just enough of the dart
artifacts to mirror what we would push to pub.
By uploading the files instead of a zip, this lets dart users depend on an unreleased snapshot
of angular2, and lets us easily fetch the dart artifacts for sync into google3
without having to re-build (potentially in a subtly different environment).
This doesn't upload anything for pull requests.
alexeagle added a commit to alexeagle/angular that referenced this pull request Jul 9, 2015
second attempt after rollback of angular#2946

After each successful build in the dart stable variant, this uploads just enough of the dart
artifacts to mirror what we would push to pub.
By uploading the files instead of a zip, this lets dart users depend on an unreleased snapshot
of angular2, and lets us easily fetch the dart artifacts for sync into google3
without having to re-build (potentially in a subtly different environment).
This doesn't upload anything for pull requests.
alexeagle added a commit that referenced this pull request Jul 9, 2015
second attempt after rollback of #2946

After each successful build in the dart stable variant, this uploads just enough of the dart
artifacts to mirror what we would push to pub.
By uploading the files instead of a zip, this lets dart users depend on an unreleased snapshot
of angular2, and lets us easily fetch the dart artifacts for sync into google3
without having to re-build (potentially in a subtly different environment).
This doesn't upload anything for pull requests.
@angular-automatic-lock-bot
Copy link
Copy Markdown

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.

@angular-automatic-lock-bot angular-automatic-lock-bot Bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker cla: yes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants