Improve information when Compiling from a git repository

Description

Currently if you compile a query from a git repository, and that compile fails for some reason, then the work unit does not appear to contain any details of the git repositories that were used, or which branches.

I suspect it will also not contain an archive of the query either - which will make debugging tricky.

At a minimum we need to

  • tag the workunit with all githooks and branches used for those

  • ensure archives are registered if they are generated, but the compile fails.

  • ensure that errors are preserved. There was an instance I looked at where the only error was "Attempting to execute a workunit that hasn't been compiled" I'm not sure how that could have occurred.

Conclusion

None

Activity

Show:

Richard Chapman April 25, 2016 at 3:53 PM

The commit used is added to the application values of the workunit already:

-a${repo}_commit=${last_commit}

I will add the branch too.

Richard Chapman April 25, 2016 at 12:15 PM

Most of the options controlling branches/commits etc will typically come from the WU in the first place. We could I suppose modify the git.sh to add -f options for all relevant env variables used by the script.

Richard Chapman April 25, 2016 at 12:14 PM

I suspect the archive question is a more general one, that if eclccserver is in use but reading ECL server side, there will be no archive.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Compatibility

Minor

Fix versions

Created April 1, 2016 at 8:43 AM
Updated April 28, 2016 at 3:42 PM
Resolved April 28, 2016 at 3:42 PM

Flag notifications