-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor [TeamCity] #2601
refactor [TeamCity] #2601
Conversation
|
pass: serverSecrets.teamcity_pass, | ||
} | ||
} else { | ||
qs.guest = 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TeamCity requires auth, so if explicit user/pass are not provided then we have to use guest auth
sendBadge(format, badgeData) | ||
} | ||
const buildStatusRegex = /SUCCESS|FAILURE|ERROR/ | ||
const buildStatusTextRegex = /^Success|Failure|Error|Tests( failed: \d+( \(\d+ new\))?)?(,)?( passed: \d+)?(,)?( ignored: \d+)?(,)?( muted: \d+)?$/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This covers everything that I've seen, but I have this suspicion that there are other potential values. The API spec does not enumerate those potential values so this is based on available info.
} | ||
} | ||
|
||
static get examples() { | ||
return [ | ||
{ | ||
title: 'TeamCity CodeBetter', | ||
previewUrl: 'codebetter/bt428', | ||
title: 'TeamCity Build Status (CodeBetter)', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CodeBetter was apparently merged with the main teamcity.jetbrains.com Open Source instance (see http://codebetter.jetbrains.com/) but maintaining the path and some nomenclature for backwards compatibility
Review app deployment is failing, heroku logs here:
|
Hmm, are there more logs further up? (Probably related to #2569.) |
Nope, at least not that I could see in the dashboard. Will check with the CLI to see if that offers any more insight |
From the CLI
|
Alright I think I've figured out what's going on here: In This results in It looks like there's a couple relatively easy fixes to this, but I'm hesitant to update this just yet as I'm not familiar with the server config/startup process. Any thoughts? |
I think this is unrelated to this PR. I tried to create a review app for #2598 and I've got the same issue: https://shields-staging-pr-2598.herokuapp.com/ Failing with Sounds like you're on the right lines for a fix, but given the issue isn't strictly related to this PR and is affecting other staging deploys, can we pull the fix out into a new PR so we can review it independently of the TeamCity refactor. Then we can merge it into other affected working branches. |
Proposed fix in #2607 for review |
Looks like the fix is working |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
Refactors TeamCity services to new service model and adds tests.
Refs #1358