Skip to content

build: exclude devserver targets from ci test jobs #17990

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

Merged

Conversation

devversion
Copy link
Member

We don't want to build the runfile tree's for the executable
devserver targets. In the CI, we are only interested in building
the actual "ng_module" target to ensure the dev-app/e2e-app are
not broken. Building the devserver runfiles is just wasteful.

I looked for more targets that we could exclude, but didn't find any..

We don't want to build the runfile tree's for the executable
devserver targets. In the CI, we are only interested in building
the actual "ng_module" target to ensure the dev-app/e2e-app are
not broken. Building the devserver runfiles is just wasteful.
@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Dec 17, 2019
@devversion devversion requested a review from jelbourn as a code owner December 17, 2019 14:47
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Dec 17, 2019
additional_root_paths = [
"npm/node_modules",
],
# Name of the AMD module that should be required on page load.
entry_module = "angular_material/src/e2e-app/main",
port = 4200,
# Scripts which will be included in the serving_path bundle after "require.js" has been
# loaded.
# TODO(jelbourn): remove UMDs from here once we don't have to manually include them
Copy link
Member Author

Choose a reason for hiding this comment

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

I removed this TODO since it makes sense to exclude them manually (and we already made this less hard-coded). Also removed a few comments that were not necessary since it's obvious and we don't do it for other devserver targets.

Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Dec 17, 2019
@mmalerba mmalerba merged commit 093d007 into angular:master Dec 17, 2019
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jan 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants