kubernetes-retired/kube-aws

Deploy step failed

chenrui333 opened this issue · 4 comments

The latest master build seems failed in the deploy step:

https://travis-ci.org/kubernetes-incubator/kube-aws/jobs/641090197#L704-L721

NODE_DEBUG=gh-pages gh-pages -d _book -r git@github.com:kubernetes-incubator/kube-aws.git -o origin
GH-PAGES 15991: Cloning git@github.com:kubernetes-incubator/kube-aws.git into ../../../../../.nvm/versions/node/v13.3.0/lib/node_modules/gh-pages/.cache/git@github.com!kubernetes-incubator!kube-aws.git
GH-PAGES 15991: Cleaning
GH-PAGES 15991: Fetching origin
GH-PAGES 15991: Checking out origin/gh-pages 
GH-PAGES 15991: Removing files
GH-PAGES 15991: Copying files
GH-PAGES 15991: Adding all
GH-PAGES 15991: Committing
GH-PAGES 15991: Pushing
remote: error: GH006: Protected branch update failed for refs/heads/gh-pages.        
remote: error: 2 of 2 required status checks are expected.        
To github.com:kubernetes-incubator/kube-aws.git
 ! [remote rejected] gh-pages -> gh-pages (protected branch hook declined)
error: failed to push some refs to 'git@github.com:kubernetes-incubator/kube-aws.git'
Makefile:47: recipe for target 'publish-docs' failed
make: *** [publish-docs] Error 1

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.