Skip to content

Conversation

@ezyang
Copy link
Contributor

@ezyang ezyang commented Jan 29, 2018

Putting these scripts here has a few benefits:

  1. PyTorch developers can easily update the scripts without
    having to ask for permissions to ossci-job-dsl

  2. You can test changes in the scripts by opening a PR to
    PyTorch (functionality is ossci-job-dsl is not easily testable.)

  3. If you get one of our stock Docker images, you can run these scripts
    to trigger a build identical to what would occur in Jenkins (not
    entirely true yet, but we can make it so.)

Signed-off-by: Edward Z. Yang ezyang@fb.com

Putting these scripts here has a few benefits:

1. PyTorch developers can easily update the scripts without
having to ask for permissions to ossci-job-dsl

2. You can test changes in the scripts by opening a PR to
PyTorch (functionality is ossci-job-dsl is not easily testable.)

3. If you get one of our stock Docker images, you can run these scripts
to trigger a build identical to what would occur in Jenkins (not
entirely true yet, but we can make it so.)

Signed-off-by: Edward Z. Yang <ezyang@fb.com>
@ezyang
Copy link
Contributor Author

ezyang commented Jan 29, 2018

@pytorchbot retest this please

1 similar comment
@ezyang
Copy link
Contributor Author

ezyang commented Jan 29, 2018

@pytorchbot retest this please

@apaszke
Copy link
Contributor

apaszke commented Jan 29, 2018

Why not keep them in pytorch/builder? That's where we used to keep all our scripts

@soumith
Copy link
Contributor

soumith commented Jan 29, 2018

then we cant open a PR and test script changes

@ezyang ezyang merged commit e93ece9 into pytorch:master Jan 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants