New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adam-submit buildinfo is confused #880

Closed
heuermh opened this Issue Nov 11, 2015 · 4 comments

Comments

Projects
None yet
3 participants
@heuermh
Member

heuermh commented Nov 11, 2015

On 0.18.2 release distribution tarball, the buildinfo command seems to be describing a commit to the utils repository

$ ./adam-distribution_2.10-0.18.2/bin/adam-submit buildinfo
Using ADAM_MAIN=org.bdgenomics.adam.cli.ADAMMain
Using SPARK_SUBMIT=/usr/local/bin/spark-submit
Build information:
git.commit.id.abbrev: a27af8f
git.commit.message.full: [maven-release-plugin] prepare release utils-parent_2.10-0.2.3

git.commit.id: a27af8f0c60343b98d187d05dcb06258fbab4b1d
git.commit.message.short: [maven-release-plugin] prepare release utils-parent_2.10-0.2.3
git.commit.id.describe: utils-parent_2.10-0.2.3
git.branch: a27af8f0c60343b98d187d05dcb06258fbab4b1d
git.commit.time: 23.08.2015 @ 09:07:48 PDT
git.remote.origin.url: git@github.com:bigdatagenomics/utils.git
git.build.time: 23.08.2015 @ 09:11:53 PDT
@fnothaft

This comment has been minimized.

Show comment
Hide comment
@fnothaft

fnothaft Jan 7, 2016

Member

Closed by #888.

Member

fnothaft commented Jan 7, 2016

Closed by #888.

@fnothaft fnothaft closed this Jan 7, 2016

@heuermh

This comment has been minimized.

Show comment
Hide comment
@heuermh

heuermh Jan 7, 2016

Member

If we're fixing this by using --version instead, the buildinfo command should probably be removed.

Member

heuermh commented Jan 7, 2016

If we're fixing this by using --version instead, the buildinfo command should probably be removed.

@fnothaft

This comment has been minimized.

Show comment
Hide comment
@fnothaft

fnothaft Jan 7, 2016

Member

Oh, sorry, I thought this was completely resolved. I would +1 your suggestion.

Member

fnothaft commented Jan 7, 2016

Oh, sorry, I thought this was completely resolved. I would +1 your suggestion.

@fnothaft fnothaft reopened this Jan 7, 2016

@massie

This comment has been minimized.

Show comment
Hide comment
@massie

massie Feb 1, 2016

Member

+1

Member

massie commented Feb 1, 2016

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment