Home → Suggestions →

Cooperate with other CI in same Gihub repo

• Edit

Bart van der Schoor

24 Apr, 2014 11:52 PM

Looks like Travis and Appveyor override each-others status updates when used on the same (Gihub) repo.

I was curious to use both and cover Linux as well as Windows.

On a Pull Request both trigger and try to update the same status: Travis is faster:

All is well — The Travis CI build passed

Then later the same widget changes (Github does a fancy UI live-update thing):

All is well — AppVeyor build succeeded

I'm not quite sure what I expected, it is an experiment. Is it even possible to see multiple statuses on same github repos?

If your use-case covers open project with possibly some existing Linux based CI this could be worth smooting out somehow:

As a windows user I see a nice angle: it is a recurring problem that many open source devs work and deploy on Unixy platforms. This is fine for most servers, but don't catch platform bugs in tools intended to be used on local machine (like grunt plugins or package managers).

Wouldn't it be nice if AppVeyor could offer those projects a simple way to do secondary Windows tests? It is not quite the same as full main CI builds, but a safety net.

I vaguely remember some code-coverage service that does a simple comment as status update: https://github.com/coveralls?tab=activity

Using that and some creative UIX can make it easy for users to propose AppVeyor windows test enviroment to existing projects without requiring full project change. Could be a nice angle to get a foothold on Linux builds crowd.

1. Support Staff 1 Posted by Feodor Fitsner on 25 Apr, 2014 05:27 PM

   

   Hi Bart,

   Sounds interesting of course! I've been asking GitHub team about Travis/AV statuses overlapping and got this response (i was asking about Combined Status API):

   While the status contexts are a preview feature, no changes have been made to what a branch shows as on a pull request page. So the pull request page still shows the last-status-wins behavior.

   Are you saying placing comment instead of status might work?

   • Edit

2. 2 Posted by Bart van der Sc... on 25 Apr, 2014 05:43 PM

   

   Do yo mean this is supposed to work already? "Combined Status API" ( https://developer.github.com/changes/2014-03-27-combined-status-api/ ) ?

   I did see one green widget on PR page, with a name that changed so I guess it is Github's play to fix a multi-reporter UI thing?

   The comment notion was just an alternative angle of adding the test feedback (interesting because it won't block the PR).

   • Edit

3. Support Staff 3 Posted by Feodor Fitsner on 25 Apr, 2014 05:50 PM

   

   As far as I understand it's only kind of "internal" change available via API, but GitHub UI will stay the same (for now). The rest of response from them:

   However, any potential changes to that will use the context field, so we want to get people using it. That's part of the reason for the preview period. If we can measure how many people are using multiple statuses, it helps us decide if a change is warranted, and if so, exactly how.

   A really big reason for the context field is to help integrators like AppVeyor and Travis work together. I'm happy to hear any feedback, issues, or requests you have while we're in the preview period, so please keep the messages coming. In the meantime, I'll take this email as a vote to change the behavior of the pull request button.

   • Edit

4. 4 Posted by Bart van der Sc... on 25 Apr, 2014 05:56 PM

   

   Oh cool, makes sense, glad they are already exploring this. I'll send them a feedback note too asking for this too.

   • Edit

5. 5 Posted by Steve on 09 Dec, 2014 11:35 PM

   

   Looks like internal has gone external.. https://github.com/blog/1935-see-results-from-all-pull-request-status-checks
   Nice!

   • Edit

6. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:50 AM.