www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Heneveld (JIRA)" <j...@apache.org>
Subject [jira] [Created] (INFRA-8423) Jenkins pull-request builds use inconsistent version of code and fail spuriously - needs full rebuild?
Date Thu, 02 Oct 2014 08:05:33 GMT
Alex Heneveld created INFRA-8423:
------------------------------------

             Summary: Jenkins pull-request builds use inconsistent version of code and fail
spuriously - needs full rebuild?
                 Key: INFRA-8423
                 URL: https://issues.apache.org/jira/browse/INFRA-8423
             Project: Infrastructure
          Issue Type: Bug
          Components: Git, Jenkins
            Reporter: Alex Heneveld


Jenkins is building pull requests, but it appears to be merging the pull requests against
an inconsistent version of the codebase, rather than master.

I think it is attempting to optimize by only building branches which have changed in the pull
request itself.  But master may have changed in the meantime so that logic is flawed.  I think
it needs to do a full build.

For instance see:

    https://github.com/apache/incubator-brooklyn/pull/207

and

    https://builds.apache.org/job/incubator-brooklyn-pull-requests/8/io.brooklyn$brooklyn-core/console

Here, master builds fine, and PR 207 builds fine and the merge builds fine.  But Jenkins gives
compile errors.

I notice in this case it did not build the `api` subproject (no changes in PR?); and the errors
-- in the `core` project -- seem related to recent changes in upstream projects such as `api`.
 EG the errors referring to `HOT_STANDBY`; this was added recently in `api`, but not picked
up by the PR builder.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message