You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@drill.apache.org by cg...@apache.org on 2021/05/12 13:58:50 UTC
[drill] branch gh-pages updated: DRILL-7923 Add a section to
Contribution Guidelines page (#2223)
This is an automated email from the ASF dual-hosted git repository.
cgivre pushed a commit to branch gh-pages
in repository https://gitbox.apache.org/repos/asf/drill.git
The following commit(s) were added to refs/heads/gh-pages by this push:
new 49ad1a2 DRILL-7923 Add a section to Contribution Guidelines page (#2223)
49ad1a2 is described below
commit 49ad1a204c7d17f3f3f08e2d844a5af0e669bead
Author: Martin Grigorov <ma...@users.noreply.github.com>
AuthorDate: Wed May 12 16:58:36 2021 +0300
DRILL-7923 Add a section to Contribution Guidelines page (#2223)
... about CI at Github Actions and TravisCI
---
.../010-apache-drill-contribution-guidelines.md | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/_docs/developer-information/contribute-to-drill/010-apache-drill-contribution-guidelines.md b/_docs/developer-information/contribute-to-drill/010-apache-drill-contribution-guidelines.md
index f7cbeec..a55e564 100644
--- a/_docs/developer-information/contribute-to-drill/010-apache-drill-contribution-guidelines.md
+++ b/_docs/developer-information/contribute-to-drill/010-apache-drill-contribution-guidelines.md
@@ -74,7 +74,7 @@ This section describes the GitHub pull request-based review process for Apache D
The following steps outline the code review and commit process required to contribute new code to the Apache Drill project:
1. The contributor writes the code that addresses a specific JIRA report as a contribution to the Apache Drill project.
-2. The contributor organizes (squashes) their code into commits that segregate out refactoring/reorg, as necessary, to enable efficient review. The following list identifies how to combine code into commits:
+2. The contributor organizes (squashes) their code into commits that segregate out refactoring/reorg, as necessary, to enable efficient review. The following list identifies how to combine code into commits:
* Combine WIP and other small commits together.
* Address multiple JIRAs, for smaller bug fixes or enhancements, with a single commit.
* Use separate commits to allow efficient review, separating out formatting changes or simple refactoring from core changes or additions.
@@ -102,6 +102,11 @@ This information can be found in the [component owners](https://issues.apache.or
* The committer pushes the commit(s) to the Apache repo (the GitHub repo is just a read-only mirror).
* The committer resolves the JIRA with a message like `"Fixed in <Git commit SHA>"`.
+### Continuous Integration
+
+All Pull requests at Github are automatically tested:
+* On Linux x86_64 at [Github Actions](https://github.com/apache/drill/actions) with JDK 8, 11 and 14
+* on Linux ARM64 at [Travis CI](https://travis-ci.com/github/apache/drill) with JDK 8
## Additional Information