[jira] [Commented] (DISPATCH-862) have the CI build log detal which commit is being used from the Proton repo

["Ganesh Murthy (JIRA)" <ji...@apache.org>]

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

Ganesh Murthy commented on DISPATCH-862:
----------------------------------------

[~gemmellr] can you please look at this sample output from my branch travis build - https://travis-ci.org/ganeshmurthy/qpid-dispatch/builds/295336910#L2022

It prints out the sha of the qpid-proton checkin using the following command from the qpid-proton folder which is inside the qpid-dispatch folder 

- echo $(echo "Current proton checkout:") $(git rev-parse HEAD)


> have the CI build log detal which commit is being used from the Proton repo
> ---------------------------------------------------------------------------
>
>                 Key: DISPATCH-862
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-862
>             Project: Qpid Dispatch
>          Issue Type: Task
>          Components: Tests
>            Reporter: Robbie Gemmell
>            Assignee: Ganesh Murthy
>            Priority: Minor
>
> Not release-specific, just saving a thought I've had a couple times now.
> The Travis CI build job for Dispatch uses git submodules to pull in the proton repo and then builds it locally before building Dispatch. Other than estimating it based on the build times, I didn't see a way to establish what commit is actually used when this occurs. It might be nice if the build printed the commit details after setting up the submodule so that they are just available in the log without investigation work.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org