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

CI Update apify connector #31380

Closed
wants to merge 9 commits into from
Closed

CI Update apify connector #31380

wants to merge 9 commits into from

Conversation

flash1293
Copy link
Contributor

CI PR for #31333

@vercel
Copy link

vercel bot commented Oct 13, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
airbyte-docs ⬜️ Ignored (Inspect) Visit Preview Oct 13, 2023 0:55am

@github-actions
Copy link
Contributor

Before Merging a Connector Pull Request

Wow! What a great pull request you have here! 🎉

To merge this PR, ensure the following has been done/considered for each connector added or updated:

  • PR name follows PR naming conventions
  • Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
  • Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
  • You've updated the connector's metadata.yaml file any other relevant changes, including a breakingChanges entry for major version bumps. See metadata.yaml docs
  • Secrets in the connector's spec are annotated with airbyte_secret
  • All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
  • Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
  • Migration guide updated in docs/integrations/<source or destination>/<name>-migrations.md with an entry for the new version, if the version is a breaking change. See migration guide example
  • If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

  1. Check for hidden checklists in your PR description

  2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.

@airbyte-oss-build-runner
Copy link
Collaborator

source-apify-dataset test report (commit 061f622f46) - ❌

⏲️ Total pipeline duration: 01mn04s

Step Result
Build source-apify-dataset docker image for platform(s) linux/x86_64
Acceptance tests
Code format checks
Validate metadata for source-apify-dataset
Connector version semver check
Connector version increment check
QA checks

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=source-apify-dataset test

@octavia-squidington-iii octavia-squidington-iii added area/connectors Connector related issues area/documentation Improvements or additions to documentation labels Oct 13, 2023
@airbyte-oss-build-runner
Copy link
Collaborator

source-apify-dataset test report (commit 1f70a5b0f8) - ✅

⏲️ Total pipeline duration: 41.97s

Step Result
Build source-apify-dataset docker image for platform(s) linux/x86_64
Acceptance tests
Code format checks
Validate metadata for source-apify-dataset
Connector version semver check
Connector version increment check
QA checks

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=source-apify-dataset test

@airbyte-oss-build-runner
Copy link
Collaborator

source-apify-dataset test report (commit 19fc17144e) - ✅

⏲️ Total pipeline duration: 01mn31s

Step Result
Build source-apify-dataset docker image for platform(s) linux/x86_64
Acceptance tests
Code format checks
Validate metadata for source-apify-dataset
Connector version semver check
Connector version increment check
QA checks

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=source-apify-dataset test

@airbyte-oss-build-runner
Copy link
Collaborator

source-apify-dataset test report (commit a298adee87) - ✅

⏲️ Total pipeline duration: 53.05s

Step Result
Build source-apify-dataset docker image for platform(s) linux/x86_64
Acceptance tests
Code format checks
Validate metadata for source-apify-dataset
Connector version semver check
Connector version increment check
QA checks

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=source-apify-dataset test

@flash1293 flash1293 closed this Oct 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connectors Connector related issues area/documentation Improvements or additions to documentation connectors/source/apify-dataset
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants