You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (Jira)" <ji...@apache.org> on 2021/07/06 16:17:00 UTC

[jira] [Comment Edited] (OAK-9486) Build all modules on GitHub PR

    [ https://issues.apache.org/jira/browse/OAK-9486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17375822#comment-17375822 ] 

Marcel Reutegger edited comment on OAK-9486 at 7/6/21, 4:16 PM:
----------------------------------------------------------------

Added a Jenkinsfile with the following two commits:
- https://github.com/apache/jackrabbit-oak/commit/28700284e449907d5373ce9241459d91ede4a4ce
- https://github.com/apache/jackrabbit-oak/commit/ccc2a77ee65496b9fb7db4734879cfac8bf2fcf9

The multibranch pipeline is here: https://ci-builds.apache.org/job/Jackrabbit/job/oak-trunk-pr/

The pipeline is currently only able to build branches and PR on origin but not on forks. But this may be the better/safer option anyway. Otherwise anyone can trigger a build on Apache infrastructure and execute arbitrary code.


was (Author: mreutegg):
Added a Jenkinsfile with the following two commits:
- https://github.com/apache/jackrabbit-oak/commit/28700284e449907d5373ce9241459d91ede4a4ce
- https://github.com/apache/jackrabbit-oak/commit/ccc2a77ee65496b9fb7db4734879cfac8bf2fcf9

The multibranch pipeline is here: https://ci-builds.apache.org/job/Jackrabbit/job/oak-trunk-pr/

> Build all modules on GitHub PR
> ------------------------------
>
>                 Key: OAK-9486
>                 URL: https://issues.apache.org/jira/browse/OAK-9486
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: continuous integration
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>
> With the migration from SVN to GitHub pull requests became the primary way how changes go into the Oak codebase. Currently a pull requests triggers a build on travis-ci, but does not cover all modules. Historically the travis-ci build was introduced to get better test coverage on MongoDB and was not meant to test all modules.
> This task is about building all modules and potentially move from travis-ci to Apache build infrastructure. Frequently travis-ci resources that can be used by Apache projects are very scarce and PR builds have to wait for hours until the check/build completes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)