Expanded browser scraping#521
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds two new data sources to the existing release_scraping job:
User-facing content: blog post feeds (Chrome, Edge, Brave, Opera, Vivaldi) and Firefox user-facing release notes (from the Mozilla product-details API). Stored at MARKET_RESEARCH/BLOGS/ and MARKET_RESEARCH/STRUCTURED/Firefox/user_release_*.
Job postings: Mozilla and Brave via the Greenhouse API, Opera via Teamtailor HTML scraping. Captures full descriptions for hiring-signal analysis. Stored as date-partitioned snapshots at MARKET_RESEARCH/JOBS/{Company}/{YYYYMMDD}/.
Checklist for reviewer:
Commits should reference a bug or github issue, if relevant (if a bug is referenced, the pull request should include the bug number in the title)
Scan the PR and verify that no changes (particularly to
.circleci/config.yml) will cause environment variables (particularly credentials) to be exposed in test logsEnsure the container image will be using permissions granted to telemetry-airflow responsibly.