brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From geomacy <>
Subject [GitHub] brooklyn-server issue #719: Check versionedName to avoid NPE.
Date Tue, 06 Jun 2017 18:54:52 GMT
Github user geomacy commented on the issue:
    Looks like it is fetching the apache master instead of the branch from my fork, as below.
 Note `c545381152a22df29d16c063fd6cd2fab4ec7b33` is my change but it is fetching from 
    Checking out Revision 57b9d7270ba87486f311020bf62b37105d4ca0e4 (refs/remotes/origin/master)
    rather than from `refs/heads/pr/719`.
    From build log:
    GitHub pull request #719 of commit c545381152a22df29d16c063fd6cd2fab4ec7b33, no merge
    Setting status of c545381152a22df29d16c063fd6cd2fab4ec7b33 to PENDING with url
and message: 'Build started sha1 is merged.'
    Using context: Jenkins: brooklyn-server-pull-request
    [EnvInject] - Loading node environment variables.
    Building remotely on H14 (ubuntu xenial) in workspace /home/jenkins/jenkins-slave/workspace/brooklyn-server-pull-requests
     > git rev-parse --is-inside-work-tree # timeout=10
    Fetching changes from the remote Git repository
     > git config remote.origin.url git:// # timeout=10
    Fetching upstream changes from git://
     > git --version # timeout=10
     > git fetch --tags --progress git:// +refs/heads/*:refs/remotes/origin/*
     > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
     > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
    Checking out Revision 57b9d7270ba87486f311020bf62b37105d4ca0e4 (refs/remotes/origin/master)
     > git config core.sparsecheckout # timeout=10
     > git checkout -f 57b9d7270ba87486f311020bf62b37105d4ca0e4
    First time build. Skipping changelog.
    Parsing POMs

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message