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

Update explore-projects.md #5560

Merged
merged 14 commits into from
May 29, 2024
Merged

Update explore-projects.md #5560

merged 14 commits into from
May 29, 2024

Conversation

mirnawong1
Copy link
Contributor

update to say ci jobs aren't ingested in explorer.

raised in slack thread: https://dbt-labs.slack.com/archives/C01Q230T0E8/p1716478677606559?thread_ts=1716320321.880129&cid=C01Q230T0E8

update to say ci jobs aren't ingested in explorer.
@mirnawong1 mirnawong1 requested a review from a team as a code owner May 23, 2024 20:56
Copy link

vercel bot commented May 23, 2024

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

Name Status Preview Comments Updated (UTC)
docs-getdbt-com ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 29, 2024 7:04pm

@github-actions github-actions bot added content Improvements or additions to content Docs team Authored by the Docs team @dbt Labs size: x-small This change will take under 3 hours to fix. labels May 23, 2024
- You are on the dbt Explorer page. To do this, select **Explore** from the top navigation bar in dbt Cloud.


## Generate metadata

dbt Explorer uses the metadata provided by the [Discovery API](/docs/dbt-cloud-apis/discovery-api) to display the details about [the state of your project](/docs/dbt-cloud-apis/project-state). The metadata that's available depends on the [deployment environment](/docs/deploy/deploy-environments) you've designated as _production_ or _staging_ in your dbt Cloud project. dbt Explorer automatically retrieves the metadata updates after each job run in the production or staging deployment environment so it always has the latest results for your project.

To view a resource and its metadata, you must define the resource in your project and run a job in the production or staging environment. The resulting metadata depends on the [commands](/docs/deploy/job-commands) executed by the jobs.
Note that CI jobs do not update dbt Explorer. This is because they don't reflect the production state and don't provide the necessary metadata updates.
Copy link
Contributor Author

@mirnawong1 mirnawong1 May 24, 2024

Choose a reason for hiding this comment

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

note for this sentence, i purposely wrote it as 'do not' for a definitive tone while using contractions for readability in the second sentence. i felt that having the sentence as 'ci jobs don't update dbt explorer...' didn't sound as definitive or eye-catching. this is because i think it's important for users to know that ci jobs are excluded.

@matthewshaver matthewshaver merged commit f4f3bd4 into current May 29, 2024
11 checks passed
@matthewshaver matthewshaver deleted the mirnawong1-patch-26 branch May 29, 2024 19:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto update content Improvements or additions to content Docs team Authored by the Docs team @dbt Labs size: x-small This change will take under 3 hours to fix.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants