Repository: logging-log4net Updated Branches: refs/heads/develop 282279e85 -> fe147ac77
(doc) Contributing: improved the build job section Project: http://git-wip-us.apache.org/repos/asf/logging-log4net/repo Commit: http://git-wip-us.apache.org/repos/asf/logging-log4net/commit/fe147ac7 Tree: http://git-wip-us.apache.org/repos/asf/logging-log4net/tree/fe147ac7 Diff: http://git-wip-us.apache.org/repos/asf/logging-log4net/diff/fe147ac7 Branch: refs/heads/develop Commit: fe147ac7771355d2b8e65591b413c1bfc1006c51 Parents: 282279e Author: Dominik Psenner <dpsen...@apache.org> Authored: Thu Jul 20 13:58:50 2017 +0200 Committer: Dominik Psenner <dpsen...@apache.org> Committed: Thu Jul 20 13:58:50 2017 +0200 ---------------------------------------------------------------------- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/logging-log4net/blob/fe147ac7/CONTRIBUTING.md ---------------------------------------------------------------------- diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index caac719..faa6e49 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -33,7 +33,7 @@ For changes of a trivial nature to comments and documentation, it is not always * Push your changes to a topic branch in your fork of the repository. * Submit a pull request to the repository in the apache organization. * Update your JIRA ticket and include a link to the pull request in the ticket. -* The build system should automatically attempt to merge, build and test your pull request. Please navigate to [jenkins](https://builds.apache.org/job/logging-log4net) to check the outcome. +* A Jenkins [job](https://builds.apache.org/job/logging-log4net) should automatically attempt to merge, build and test your pull request and you can check the outcome [here](https://builds.apache.org/job/logging-log4net/view/change-requests/). # Additional resources
