-
Notifications
You must be signed in to change notification settings - Fork 73
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
[DOP-3911]: Check project path for monorepo #894
Conversation
… have been changed if head_commit is included
…ctories for organization
@@ -46,7 +46,7 @@ jobs: | |||
cd cdk-infra/ | |||
npm ci | |||
npm run deploy:feature:stack -- -c env=stg -c customFeatureName=enhancedApp-stg-${{github.head_ref}} \ | |||
auto-builder-stack-enhancedApp-stg-${{github.head_ref}}-webhook | |||
auto-builder-stack-enhancedApp-stg-${{github.head_ref}}-webhooks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixes bug with feature branch update.
|
||
const docSetCollectionName = process.env.DOCS_SET_COLLECTION_NAME || 'docset'; | ||
|
||
export class DocSetRepository extends BaseRepository { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently not used since the docset
collection in Atlas is not yet configured, but we will need this functionality in the future.
|
||
// TODO: Populate these more. For DOP-3911, they are | ||
// being added for testing purposes. | ||
export interface DocSetEntry { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently incomplete, but this contains some of the type information that will be needed for the docset
collection once it is created.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! I like the test cases provided
tests/unit/monorepo/monorepo.test.ts
Outdated
expect(paths).toContain('server-docs/source/datalake'); | ||
}); | ||
|
||
it('Returns an empty array if there is no snooty.toml at in point in the file path', async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
at in point in the file path
Should this be "at any point" ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope! It should be in point, lol jk!! good catch, I'll update that 👍
Ticket
DOP-3911
Description
Adds logic to find the project's path within the monorepo based on given file changes. This change supports detecting nested projects as well.
This PR also includes the functionality to check whether or not the project paths detected from GitHub match what is configured within the corresponding
docset
entry.This PR also includes small bugfixes/improvements:
Testing
https://3kxa3rkxf8.execute-api.us-east-2.amazonaws.com/prod/webhook/githubEndpoint/trigger/build
and the secret for pre-prod GitHub push jobs found on Parameter Store.docs-landing
directoryNOTE: You will receive an error message stating that the build has failed. This is due to the autobuilder not having permission to clone the
docs-monorepo
repository.