Skip to content
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.

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

fix(ci): use different image for smoke base image #5607

Merged
merged 1 commit into from
Aug 10, 2022

Conversation

anshbansal
Copy link
Collaborator

@anshbansal anshbansal commented Aug 10, 2022

Going to use https://hub.docker.com/r/acryldata/datahub-ingestion-smoke so we have separate tags for each build

Checklist

  • The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
  • Links to related issues (if applicable)
  • Tests for the changes have been added/updated (if applicable)
  • Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
  • For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@anshbansal anshbansal added the devops PR or Issue related to DataHub backend & deployment label Aug 10, 2022
@github-actions
Copy link

Unit Test Results (build & test)

499 tests  ±0   499 ✔️ ±0   8m 24s ⏱️ +5s
115 suites ±0       0 💤 ±0 
115 files   ±0       0 ±0 

Results for commit 2315a70. ± Comparison against base commit 3aa74e0.

Copy link
Contributor

@treff7es treff7es left a comment

Choose a reason for hiding this comment

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

lgtm

@anshbansal anshbansal merged commit fedf451 into datahub-project:master Aug 10, 2022
@anshbansal anshbansal deleted the aseem-image-tag-smoke branch August 10, 2022 09:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops PR or Issue related to DataHub backend & deployment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants