Post Status Updates to GitLab Commits about civet HOT 5 CLOSED

Our current Gitlab seems to be running 8.0.4, so we will have to wait awhile to do this.

from civet.

The version won't ever change unless we push on them. You should put in a request to have them update it.

from civet.

Actually the recently updated it without us asking. They are getting better
About these things.
On Mon, Nov 9, 2015 at 6:53 PM Derek Gaston [email protected]
wrote:

The version won't ever change unless we push on them. You should put in a
request to have them update it.

—
Reply to this email directly or view it on GitHub
#15 (comment).

from civet.

They upgraded to 8.4.2 last week and I put in the changes to update the commit statuses on merge requests.
Some notes:

1. It doesn't automatically update like GitHub so you have to keep hitting refresh.
2. Its doesn't always seem to show all the tested commits in the "Commits" section.
3. There is a description in the API for the status but it doesn't seem to be shown anywhere. This makes distinguishing "Success" from "Failed but allowed" impossible on the GitLab page.
4. It doesn't seem to be smart like GitHub where if a test fails then it marks the whole thing as failed even if there are jobs still pending. GitLab just leaves it as pending.

I left in the moosetest comments for now until I get some feedback on whether people think the status is sufficient.

from civet.

This seems to be working. Comments are still used but that can be a separate issue if people want to get rid of them.

from civet.