[
https://issues.apache.org/jira/browse/DISPATCH-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16227259#comment-16227259
]
Ganesh Murthy edited comment on DISPATCH-862 at 11/1/17 2:48 PM:
-----------------------------------------------------------------
The echo statement (echo $(echo "Current proton checkout:") $(git rev-parse
HEAD)) only prints properly in the *script* section of travis. In other
sections it literally prints "echo $(echo "Current proton checkout:") $(git
rev-parse HEAD)"
So, I had to put it in the script section. Does that soiund good?
[~gemmellr] can I raise a PR for you to look at?
was (Author: ganeshmurthy):
The echo statement (echo $(echo "Current proton checkout:") $(git rev-parse
HEAD)) only prints properly in the *script* section of travis. In other
sections it literally prints "echo $(echo "Current proton checkout:") $(git
rev-parse HEAD)"
So, I had to put it in the script section.
> 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: [email protected]
For additional commands, e-mail: [email protected]
