Skip to content
This repository was archived by the owner on Nov 6, 2020. It is now read-only.

ci: publish docs debug #10638

Merged
merged 1 commit into from
May 8, 2019
Merged

ci: publish docs debug #10638

merged 1 commit into from
May 8, 2019

Conversation

gabreal
Copy link
Contributor

@gabreal gabreal commented May 8, 2019

No description provided.

@gabreal gabreal requested review from kirushik and TriplEight May 8, 2019 14:57
@parity-cla-bot
Copy link

It looks like this contributor signed our Contributor License Agreement. 👍

Many thanks,

Parity Technologies CLA Bot

@@ -51,8 +51,11 @@ commit_files() {

upload_files() {
echo "__________Upload files__________"
git push -q origin HEAD
git push -q -f --tags
# this version of git (2.7.4) will dump the token on failure
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why do we even use token instead of a deploy SSH key?

git push -q -f --tags
# this version of git (2.7.4) will dump the token on failure
git push -q origin HEAD 2>&1 \
| sed -r "s|(${GITHUB_USER}):[a-f0-9]+@|\1:REDACTED@|g"
Copy link
Collaborator

Choose a reason for hiding this comment

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

I find it possible that git will change the failure format and this regexp will stop redacting the secret...
And this failure will be terribly hard to notice in advance...

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's the most simple pattern username:token

Copy link
Collaborator

@kirushik kirushik left a comment

Choose a reason for hiding this comment

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

I don't mind this as a hotfix — but in later iterations I would prefer us redesigning system to follof the "fail closed" principle: like deployment-only SSH key which is only authorized to push in this particular repo, or even migrating to just using Github/Gitlab pages without resorting to manual pushes.

@TriplEight
Copy link
Collaborator

LGTM, also I'd vote moving to gitlab/github pages later

@gabreal
Copy link
Contributor Author

gabreal commented May 8, 2019

thanks, I don't mind at all moving to something else when there is time to plan.

@gabreal gabreal merged commit e91eb33 into master May 8, 2019
@gabreal gabreal deleted the docs-job-debug branch May 8, 2019 15:58
@soc1c
Copy link
Contributor

soc1c commented May 14, 2019

labels!

@soc1c soc1c added this to the 2.6 milestone May 14, 2019
@soc1c soc1c added A8-looksgood 🦄 Pull request is reviewed well. B0-patch-stable 🕷 Pull request should also be back-ported to the stable branch. B1-patch-beta 🕷🕷 M1-ci 🙉 Continuous integration. labels May 14, 2019
soc1c pushed a commit that referenced this pull request May 14, 2019
soc1c pushed a commit that referenced this pull request May 14, 2019
soc1c added a commit that referenced this pull request May 14, 2019
soc1c added a commit that referenced this pull request May 14, 2019
soc1c added a commit that referenced this pull request May 14, 2019
* ci: publish docs debug (#10638)

* ci: backport missing diff from master
soc1c added a commit that referenced this pull request May 14, 2019
* ci: publish docs debug (#10638)

* ci: backport missing diff from master
ordian added a commit that referenced this pull request May 16, 2019
* master:
  docs: Add ProgPoW Rust docs to ethash module (#10653)
  fix: Move PR template into .github/ folder (#10663)
  docs: Add PR template (#10654)
  Trivial journal for private transactions (#10056)
  fix(compilation warnings) (#10649)
  [whisper] Move needed aes_gcm crypto in-crate (#10647)
  Adds parity_getRawBlockByNumber, parity_submitRawBlock (#10609)
  Fix rinkeby petersburg fork (#10632)
  ci: publish docs debug (#10638)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A8-looksgood 🦄 Pull request is reviewed well. B0-patch-stable 🕷 Pull request should also be back-ported to the stable branch. M1-ci 🙉 Continuous integration.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants