@dblandin we are using Circle 2.0 where the docker host is remote, so mounting volumes doesn't work for much since the machine you are running the command on is not where the volume is created.

However, I still don't think this would fix the issue. committed_at is only set if the git binary is available or if the value is in the payload from the CI reporter.

You can see the code where this value is set here ->

ruby-test-reporter/lib/code_climate/test_reporter/git.rb

Lines 21 to 23 in 4bfe8f6

    
           def committed_at_from_git_or_ci 
        
             committed_at_from_git || committed_at_from_ci 
        
           end

There is no other way to set it in the CI reporter other than pretending to be CodeShip.

You can see where it is set in the CodeShip branch of the conditional in Ci.service_data here ->

ruby-test-reporter/lib/code_climate/test_reporter/ci.rb

Line 74 in 4bfe8f6

committed_at: env["CI_TIMESTAMP"],

You can see where your PayloadValidator requires that it be set here ->

ruby-test-reporter/lib/code_climate/test_reporter/payload_validator.rb

Line 16 in 925d5b2

    
           raise InvalidPayload, "A git commit timestamp was not found in the test report payload" unless committed_at

The issue I pointed out is a legitimate bug (and an easily fixable one) in the library if the intended behavior is to be able to run without git, which, like I mentioned, we are successfully doing by pretending to send from CodeShip.

	def committed_at_from_git_or_ci
	committed_at_from_git \|\| committed_at_from_ci
	end

command not found: git #171

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions