Skip to content

Fail-fast checking and workflow reporting in tarantool/doc #3085

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
1 of 2 tasks
NickVolynkin opened this issue Aug 12, 2022 · 0 comments · Fixed by #3086
Closed
1 of 2 tasks

Fail-fast checking and workflow reporting in tarantool/doc #3085

NickVolynkin opened this issue Aug 12, 2022 · 0 comments · Fixed by #3086
Assignees
@NickVolynkin
Labels
doc pipelines [area] related to CI/CD builds

Comments

@NickVolynkin
Copy link
Contributor

NickVolynkin commented Aug 12, 2022 •
edited
Loading

Definition of done
@NickVolynkin NickVolynkin added doc pipelines [area] related to CI/CD builds internal Technical debt in the docs teamX and removed internal Technical debt in the docs labels Aug 12, 2022
NickVolynkin added a commit that referenced this issue Aug 12, 2022
@NickVolynkin
Report workflow failures to VK Teams
6fabc53 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Resolves #3085
@NickVolynkin NickVolynkin mentioned this issue Aug 12, 2022
Merged
NickVolynkin added a commit that referenced this issue Aug 12, 2022
@NickVolynkin
Report workflow failures to VK Teams
8cade7d 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 12, 2022
@NickVolynkin
Report workflow failures to VK Teams
9944411 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 12, 2022
@NickVolynkin
Report workflow failures to VK Teams
b5e7b96 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 12, 2022
@NickVolynkin
Report workflow failures to VK Teams
419fc87 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 12, 2022
@NickVolynkin
Report workflow failures to VK Teams
ab42799 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 12, 2022
@NickVolynkin
Report workflow failures to VK Teams
524ee5e 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 12, 2022
@NickVolynkin
Report workflow failures to VK Teams
5240931 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 12, 2022
@NickVolynkin
Report workflow failures to VK Teams
600ea5c 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 12, 2022
@NickVolynkin
Report workflow failures to VK Teams
2b57f6a 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Resolves #3085
@NickVolynkin NickVolynkin self-assigned this Aug 15, 2022
NickVolynkin added a commit that referenced this issue Aug 16, 2022
@NickVolynkin
Report workflow failures to VK Teams
c07f365 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Also, extract webhooks into separate scripts to
make separate steps for them. This way, we'll know
which step failed: uploading to S3 or running a webhook.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 16, 2022
@NickVolynkin
Report workflow failures to VK Teams
9730dd6 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Also, extract webhooks into separate scripts to
make separate steps for them. This way, we'll know
which step failed: uploading to S3 or running a webhook.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 16, 2022
@NickVolynkin
Report workflow failures to VK Teams
d00b0da 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Also, extract webhooks into separate scripts to
make separate steps for them. This way, we'll know
which step failed: uploading to S3 or running a webhook.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 16, 2022
@NickVolynkin
Report workflow failures to VK Teams
50fa0bb 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Also, extract webhooks into separate scripts to
make separate steps for them. This way, we'll know
which step failed: uploading to S3 or running a webhook.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 16, 2022
@NickVolynkin
Report workflow failures to VK Teams
97c3747 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Also, extract webhooks into separate scripts to
make separate steps for them. This way, we'll know
which step failed: uploading to S3 or running a webhook.

Rename BRANCH_NAME to DEPLOYMENT_NAME in scripts and
workflows, becase it makes more sense in workflows
deploy-custom and destroy-deployment-manually.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 16, 2022
@NickVolynkin
Report workflow failures to VK Teams
611c6e6 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Also, extract webhooks into separate scripts to
make separate steps for them. This way, we'll know
which step failed: uploading to S3 or running a webhook.

Rename BRANCH_NAME to DEPLOYMENT_NAME in scripts and
workflows, becase it makes more sense in workflows
deploy-custom and destroy-deployment-manually.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 16, 2022
@NickVolynkin
Report workflow failures to VK Teams
082f941 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Also, extract webhooks into separate scripts to
make separate steps for them. This way, we'll know
which step failed: uploading to S3 or running a webhook.

Rename BRANCH_NAME to DEPLOYMENT_NAME in scripts and
workflows, becase it makes more sense in workflows
deploy-custom and destroy-deployment-manually.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 16, 2022
@NickVolynkin
Report workflow failures to VK Teams
8d84be3 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Also, extract webhooks into separate scripts to
make separate steps for them. This way, we'll know
which step failed: uploading to S3 or running a webhook.

Rename BRANCH_NAME to DEPLOYMENT_NAME in scripts and
workflows, becase it makes more sense in workflows
deploy-custom and destroy-deployment-manually.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 16, 2022
@NickVolynkin
Report workflow failures to VK Teams
23129bb 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Also, extract webhooks into separate scripts to
make separate steps for them. This way, we'll know
which step failed: uploading to S3 or running a webhook.

Rename BRANCH_NAME to DEPLOYMENT_NAME in scripts and
workflows, becase it makes more sense in workflows
deploy-custom and destroy-deployment-manually.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 16, 2022
@NickVolynkin
Report workflow failures to VK Teams
ad42aa2 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This won't work
with forks unless fork's owner adds the bot token
in the VKTEAMS_BOT_TOKEN secret.

Also, extract webhooks into separate scripts to
make separate steps for them. This way, we'll know
which step failed: uploading to S3 or running a webhook.

Rename BRANCH_NAME to DEPLOYMENT_NAME in scripts and
workflows, becase it makes more sense in workflows
deploy-custom and destroy-deployment-manually.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 16, 2022
@NickVolynkin
Report workflow failures to VK Teams
772c8c9 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This will only work
with PRs from original repository, but not from forks.

Also, extract webhooks into separate scripts to
make separate steps for them. This way, we'll know
which step failed: uploading to S3 or running a webhook.

Rename BRANCH_NAME to DEPLOYMENT_NAME in scripts and
workflows, becase it makes more sense in workflows
deploy-custom and destroy-deployment-manually.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 16, 2022
@NickVolynkin
Report workflow failures to VK Teams
9fe83b9 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This will only work
with PRs from original repository, but not from forks.

Also, extract webhooks into separate scripts to
make separate steps for them. This way, we'll know
which step failed: uploading to S3 or running a webhook.

Rename BRANCH_NAME to DEPLOYMENT_NAME in scripts and
workflows, becase it makes more sense in workflows
deploy-custom and destroy-deployment-manually.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 16, 2022
@NickVolynkin
Report workflow failures to VK Teams
6cd75d7 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This will only work
with PRs from original repository, but not from forks.

Also, extract webhooks into separate scripts to
make separate steps for them. This way, we'll know
which step failed: uploading to S3 or running a webhook.

Rename BRANCH_NAME to DEPLOYMENT_NAME in scripts and
workflows, becase it makes more sense in workflows
deploy-custom and destroy-deployment-manually.

Update bobheadxi/deployments to version 1,
which supports deleting deployments entirely.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 16, 2022
@NickVolynkin
Report workflow failures to VK Teams
1cca012 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This will only work
with PRs from original repository, but not from forks.

Also, extract webhooks into separate scripts to
make separate steps for them. This way, we'll know
which step failed: uploading to S3 or running a webhook.

Rename BRANCH_NAME to DEPLOYMENT_NAME in scripts and
workflows, becase it makes more sense in workflows
deploy-custom and destroy-deployment-manually.

Update bobheadxi/deployments to version 1,
which supports deleting deployments entirely.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 17, 2022
@NickVolynkin
Report workflow failures to VK Teams
91d1582 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This will only work
with PRs from original repository, but not from forks.

Also, extract webhooks into separate scripts to
make separate steps for them. This way, we'll know
which step failed: uploading to S3 or running a webhook.

Rename BRANCH_NAME to DEPLOYMENT_NAME in scripts and
workflows, becase it makes more sense in workflows
deploy-custom and destroy-deployment-manually.

Update bobheadxi/deployments to version 1,
which supports deleting deployments entirely.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 17, 2022
@NickVolynkin
Report workflow failures to VK Teams
0ec5f58 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This will only work
with PRs from original repository, but not from forks.

Also, extract webhooks into separate scripts to
make separate steps for them. This way, we'll know
which step failed: uploading to S3 or running a webhook.

Rename BRANCH_NAME to DEPLOYMENT_NAME in scripts and
workflows, becase it makes more sense in workflows
deploy-custom and destroy-deployment-manually.

Update bobheadxi/deployments to version 1,
which supports deleting deployments entirely.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 17, 2022
@NickVolynkin
Report workflow failures to VK Teams
dc071d3 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This will only work
with PRs from original repository, but not from forks.

Also, extract webhooks into separate scripts to
make separate steps for them. This way, we'll know
which step failed: uploading to S3 or running a webhook.

Rename BRANCH_NAME to DEPLOYMENT_NAME in scripts and
workflows, becase it makes more sense in workflows
deploy-custom and destroy-deployment-manually.

Update bobheadxi/deployments to version 1,
which supports deleting deployments entirely.

Resolves #3085
NickVolynkin added a commit that referenced this issue Aug 17, 2022
@NickVolynkin
Report workflow failures to VK Teams
9334be1 
When a workflow fails, a message will be sent to
VK Teams, @tt_docs_cicd_reports. This will only work
with PRs from original repository, but not from forks.

Also, extract webhooks into separate scripts to
make separate steps for them. This way, we'll know
which step failed: uploading to S3 or running a webhook.

Rename BRANCH_NAME to DEPLOYMENT_NAME in scripts and
workflows, becase it makes more sense in workflows
deploy-custom and destroy-deployment-manually.

Update bobheadxi/deployments to version 1,
which supports deleting deployments entirely.

Resolves #3085
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@NickVolynkin NickVolynkin

Labels
doc pipelines [area] related to CI/CD builds
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Report workflow failures to VK Teams tarantool/doc
1 participant
@NickVolynkin