[CI] Initial TeamCity implementation #81043
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
brianseeders
added
Team:Operations
| root(Kibana) | ||
|
|
||
| checkoutDir = "kibana" | ||
| // checkoutDir = "/dev/shm/%system.teamcity.buildType.id%/%system.build.number%/kibana" |
There was a problem hiding this comment.
Was this swapped for testing?
There was a problem hiding this comment.
"/dev/shm/%system.teamcity.buildType.id%/%system.build.number%/kibana" puts the workspace for the job in memory, but I had some issues when I tried it initially. It's on my TODO list to revisit. It has pretty good performance without being in-memory (probably since a ton of stuff isn't all running on one machine), so it's not a huge concern at the moment.
tylersmalley
approved these changes
Oct 26, 2020
|
Pinging @elastic/kibana-operations (Team:Operations) |
patrykkopycinski
approved these changes
Nov 19, 2020
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
brianseeders
added a commit
that referenced
this pull request
Nov 20, 2020
gmmorris
added a commit
to rudolf/kibana
that referenced
this pull request
Nov 23, 2020
* master: (67 commits) [Observability] Load hasData call asynchronously (elastic#80644) Implement AnonymousAuthenticationProvider. (elastic#79985) Deprecate `visualization:colorMapping` advanced setting (elastic#83372) [TSVB] [Rollup] Table tab not working with rollup indexes (elastic#83635) Revert "[Search] Search batching using bfetch (elastic#83418)" (elastic#84037) skip flaky suite (elastic#83772) skip flaky suite (elastic#69849) create kbn-legacy-logging package (elastic#77678) [Search] Search batching using bfetch (elastic#83418) [Security Solution] Refactor Timeline flyout to take a full page (elastic#82033) Drop use of console-stamp (elastic#83922) skip flaky suite (elastic#84011 , elastic#84012) Fixed usage of `isReady` for usage collection of alerts and actions (elastic#83760) [maps] support URL drilldowns (elastic#83732) Revert "Added default dedupKey value as an {{alertInstanceId}} to provide grouping functionality for PagerDuty incidents. (elastic#83226)" [code coverage] Update jest config to collect more data (elastic#83804) Added default dedupKey value as an {{alertInstanceId}} to provide grouping functionality for PagerDuty incidents. (elastic#83226) [Security Solution] Give notice when endpoint policy is out of date (elastic#83469) [Security Solution] Sync url state on any changes to query string (elastic#83314) [CI] Initial TeamCity implementation (elastic#81043) ...
kibanamachine
added
the
backport missing
|
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
kibanamachine
removed
the
backport missing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR provides TeamCity implementations of most of our primary CI pipelines currently running in Jenkins. Namely: Hourly builds for tracked branches, baseline builds, pull requests, and Elasticsearch snapshot build/verify.
See .teamcity/README.md for diagrams and information on how these pipelines are structured.
We reviewed much of this PR as a team during a two-hour video conference.
These pipelines are close to being ready to run, but we need to wait until TeamCity at Elastic is generally available, both to run them and to finalize some of the details. It is likely to be at least two more months before that happens. As such, we discussed merging this PR, and submitting any changes between now and then as separate, smaller PRs.