[GitHub] [spark-website] maropu commented on a change in pull request #286: Add descriptions about GitHub Actions in the "Useful Developer Tools" page
maropu commented on a change in pull request #286: URL: https://github.com/apache/spark-website/pull/286#discussion_r475145735 ## File path: developer-tools.md ## @@ -228,6 +228,25 @@ Getting logs from the pods and containers directly is an exercise left to the re Kubernetes, and more importantly, minikube have rapid release cycles, and point releases have been found to be buggy and/or break older and existing functionality. If you are having trouble getting tests to pass on Jenkins, but locally things work, don't hesitate to file a Jira issue. +Running tests in your forked repository using GitHub Actions + +GitHub Actions is a functionality within GitHub that enables continuous integration and a wide range of automation. +We have already started using some action scripts and one of them is to run tests for Pull Requests. Review comment: Looks like we don't have the direct link to the secion, so I added the link to the page. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@spark.apache.org For additional commands, e-mail: commits-h...@spark.apache.org
[GitHub] [spark-website] maropu commented on a change in pull request #286: Add descriptions about GitHub Actions in the "Useful Developer Tools" page
maropu commented on a change in pull request #286: URL: https://github.com/apache/spark-website/pull/286#discussion_r475139695 ## File path: developer-tools.md ## @@ -228,6 +228,25 @@ Getting logs from the pods and containers directly is an exercise left to the re Kubernetes, and more importantly, minikube have rapid release cycles, and point releases have been found to be buggy and/or break older and existing functionality. If you are having trouble getting tests to pass on Jenkins, but locally things work, don't hesitate to file a Jira issue. +Running tests in your forked repository using GitHub Actions + +GitHub Actions is a functionality within GitHub that enables continuous integration and a wide range of automation. +We have already started using some action scripts and one of them is to run tests for Pull Requests. Review comment: Sure! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@spark.apache.org For additional commands, e-mail: commits-h...@spark.apache.org
[GitHub] [spark-website] maropu commented on a change in pull request #286: Add descriptions about GitHub Actions in the "Useful Developer Tools" page
maropu commented on a change in pull request #286: URL: https://github.com/apache/spark-website/pull/286#discussion_r475099316 ## File path: developer-tools.md ## @@ -228,6 +228,25 @@ Getting logs from the pods and containers directly is an exercise left to the re Kubernetes, and more importantly, minikube have rapid release cycles, and point releases have been found to be buggy and/or break older and existing functionality. If you are having trouble getting tests to pass on Jenkins, but locally things work, don't hesitate to file a Jira issue. +Running tests in your forked repository using GitHub Actions + +GitHub Actions is a functionality within GitHub that enables continuous integration and a wide range of automation. +We have already started uing some action scripts and one of them is to run tests for Pull Requests. +If you are planning to create a new Pull Reques, it is important to check if tests can pass on your branch before creating it. +This is because our GitHub Acrions script automatically run tests for your Pull Request/following commits and Review comment: Yea, in the following commit, I've updated it. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@spark.apache.org For additional commands, e-mail: commits-h...@spark.apache.org
[GitHub] [spark-website] maropu commented on a change in pull request #286: Add descriptions about GitHub Actions in the "Useful Developer Tools" page
maropu commented on a change in pull request #286: URL: https://github.com/apache/spark-website/pull/286#discussion_r475099245 ## File path: developer-tools.md ## @@ -228,6 +228,25 @@ Getting logs from the pods and containers directly is an exercise left to the re Kubernetes, and more importantly, minikube have rapid release cycles, and point releases have been found to be buggy and/or break older and existing functionality. If you are having trouble getting tests to pass on Jenkins, but locally things work, don't hesitate to file a Jira issue. +Running tests in your forked repository using GitHub Actions + +GitHub Actions is a functionality within GitHub that enables continuous integration and a wide range of automation. +We have already started uing some action scripts and one of them is to run tests for Pull Requests. +If you are planning to create a new Pull Reques, it is important to check if tests can pass on your branch before creating it. +This is because our GitHub Acrions script automatically run tests for your Pull Request/following commits and +this can burden our limited resources of GitHub Actions. Review comment: I saw the max number, 180, in https://issues.apache.org/jira/browse/SPARK-32264?focusedCommentId=17170040=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17170040 But, this number might change in future, so I think it the current statement is okay for most developers. ## File path: developer-tools.md ## @@ -228,6 +228,25 @@ Getting logs from the pods and containers directly is an exercise left to the re Kubernetes, and more importantly, minikube have rapid release cycles, and point releases have been found to be buggy and/or break older and existing functionality. If you are having trouble getting tests to pass on Jenkins, but locally things work, don't hesitate to file a Jira issue. +Running tests in your forked repository using GitHub Actions + +GitHub Actions is a functionality within GitHub that enables continuous integration and a wide range of automation. +We have already started uing some action scripts and one of them is to run tests for Pull Requests. +If you are planning to create a new Pull Reques, it is important to check if tests can pass on your branch before creating it. +This is because our GitHub Acrions script automatically run tests for your Pull Request/following commits and +this can burden our limited resources of GitHub Actions. Review comment: I saw the max number, 180, in https://issues.apache.org/jira/browse/SPARK-32264?focusedCommentId=17170040=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17170040 But, this number might change in future, so I think it the current statement is okay for most developers. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@spark.apache.org For additional commands, e-mail: commits-h...@spark.apache.org
[GitHub] [spark-website] maropu commented on a change in pull request #286: Add descriptions about GitHub Actions in the "Useful Developer Tools" page
maropu commented on a change in pull request #286: URL: https://github.com/apache/spark-website/pull/286#discussion_r475097900 ## File path: developer-tools.md ## @@ -228,6 +228,25 @@ Getting logs from the pods and containers directly is an exercise left to the re Kubernetes, and more importantly, minikube have rapid release cycles, and point releases have been found to be buggy and/or break older and existing functionality. If you are having trouble getting tests to pass on Jenkins, but locally things work, don't hesitate to file a Jira issue. +Running tests in your forked repository using GitHub Actions + +GitHub Actions is a functionality within GitHub that enables continuous integration and a wide range of automation. +We have already started uing some action scripts and one of them is to run tests for Pull Requests. +If you are planning to create a new Pull Reques, it is important to check if tests can pass on your branch before creating it. +This is because our GitHub Acrions script automatically run tests for your Pull Request/following commits and +this can burden our limited resources of GitHub Actions. + +Our script enables you to run tests for a branch in your forked repository. +Let's say that you have a branch named "your_branch" for a Pull Request. +To run tests on "your_branch" and check test reuslts: + +- Clicks a "Actions" tab in your forked repository. +- Selects a "Build and test" workfolow in a "All workflows" list. +- Pushs a "Run workflow" button and enters "your_branch" in a "Target branch to run" field. +- When a "Build and test" workflow finished, clicks a "Report test results" workfolow to check test results. Review comment: Ah, thanks! I forgot to run a typo checker This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@spark.apache.org For additional commands, e-mail: commits-h...@spark.apache.org
[GitHub] [spark-website] maropu commented on a change in pull request #286: Add descriptions about GitHub Actions in the "Useful Developer Tools" page
maropu commented on a change in pull request #286: URL: https://github.com/apache/spark-website/pull/286#discussion_r475097900 ## File path: developer-tools.md ## @@ -228,6 +228,25 @@ Getting logs from the pods and containers directly is an exercise left to the re Kubernetes, and more importantly, minikube have rapid release cycles, and point releases have been found to be buggy and/or break older and existing functionality. If you are having trouble getting tests to pass on Jenkins, but locally things work, don't hesitate to file a Jira issue. +Running tests in your forked repository using GitHub Actions + +GitHub Actions is a functionality within GitHub that enables continuous integration and a wide range of automation. +We have already started uing some action scripts and one of them is to run tests for Pull Requests. +If you are planning to create a new Pull Reques, it is important to check if tests can pass on your branch before creating it. +This is because our GitHub Acrions script automatically run tests for your Pull Request/following commits and +this can burden our limited resources of GitHub Actions. + +Our script enables you to run tests for a branch in your forked repository. +Let's say that you have a branch named "your_branch" for a Pull Request. +To run tests on "your_branch" and check test reuslts: + +- Clicks a "Actions" tab in your forked repository. +- Selects a "Build and test" workfolow in a "All workflows" list. +- Pushs a "Run workflow" button and enters "your_branch" in a "Target branch to run" field. +- When a "Build and test" workflow finished, clicks a "Report test results" workfolow to check test results. Review comment: Ah, thanks! I forgot to run a typo checker. I run it by myself and pushed it. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@spark.apache.org For additional commands, e-mail: commits-h...@spark.apache.org
