ci,cdash: rename cdash workflow to external #260
Conversation
|
@lindstro the status check works! |
|
It appears that it is posting the status as comming from your account. Make sure that it is using the robot token. |
Hmm, that's odd. I created another token from the robot account and updated. Of course, the robot is not admin, so I had to update the token through my personal account. Not sure if that has anything to do with it. |
It should not be |
vicentebolea
force-pushed
the
test-cdash-status
branch
from
cb55f43 to
4325f7c
Compare
|
@lindstro oh the new token is not associated to your account! I think that we completed this task! :) |
|
Actually Ill go ahead and change the cdash job to another name so that it is not confusing. |
vicentebolea
force-pushed
the
test-cdash-status
branch
from
4325f7c to
5ee9745
Compare
vicentebolea
changed the title
|
@lindstro I reused this PR to rename the cdash workflow to external and the cdash job to generate_statuses. This will avoid the confusion of having two status checks named cdash. |
3 participants
No description provided.