You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 14, 2020. It is now read-only.
Describe what prompted this request
TeamCity will allow us to test our code and ensure that quality is maintained
Describe the solution you'd like
A clear and concise description of what you want to happen.
Who is the target user for this?
Lab managers and general infrastructure usage
Will it need to be maintained?
Yes, there will need to be an understanding of how it's role effects the lab and how to use it to the fullest
Who should have access?
Lab managers and possibly minions
Are these docs testable? (not all documentation will be testable)
Non
Will there be sensitive information in these docs?
possibly, this might describe weak points in our DevOps operations
Additional context
Add any other context or screenshots about the request here.
This is spike to identify the usage locations for TeamCity.
Currently this has been defined as:
GitHub CI/CD integration
possibly build testing
general CI/CD learning.
The text was updated successfully, but these errors were encountered:
DrJZoidberg
changed the title
[Spike] Document the understanding of TeamCity deployment and usage
[Spike] Identify usages and integration points for TeamCity in lab infrastructure/workflow
Oct 21, 2018
author is @DrJZoidberg
Describe what prompted this request
TeamCity will allow us to test our code and ensure that quality is maintained
Describe the solution you'd like
A clear and concise description of what you want to happen.
Who is the target user for this?
Lab managers and general infrastructure usage
Will it need to be maintained?
Yes, there will need to be an understanding of how it's role effects the lab and how to use it to the fullest
Who should have access?
Lab managers and possibly minions
Are these docs testable? (not all documentation will be testable)
Non
Will there be sensitive information in these docs?
possibly, this might describe weak points in our DevOps operations
Additional context
Add any other context or screenshots about the request here.
This is spike to identify the usage locations for TeamCity.
Currently this has been defined as:
The text was updated successfully, but these errors were encountered: