Skip to content
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

Buildkite CI improvements #1617

Closed
3 of 10 tasks
Tracked by #2321
markov00 opened this issue Mar 3, 2022 · 1 comment
Closed
3 of 10 tasks
Tracked by #2321

Buildkite CI improvements #1617

markov00 opened this issue Mar 3, 2022 · 1 comment
Labels
:ci enhancement New feature or request internal Internal changes with no external impact meta ...meta issue

Comments

@markov00
Copy link
Member

markov00 commented Mar 3, 2022

Future enhancements

  • Create foundation of buildkite CI ci(buildkite): create foundation for ci and triggers #1733
  • Remove obsolete code and configurations ci: remove obsolete configurations #1803
  • git clone with depth 1 to avoid downloading the full repo see here
  • Enable better caching see link
  • Configure our own agents. Currently we are using a small instance from kibana that is suitable to all our jobs. But the wait times for these are between 1m and >3m for the job to even start, even with the job priority set very high. Not using our own agents also limits our ability to cache things specific to charts. I don't think this is a huge issue for the time being but should be considered later.
  • Optimize the buildkite upload script (see example run). This script, like all others, takes several minutes (~3) to wait, start and finish running. This is creates incredible flexibility for dynamic pipelines but blocks all other jobs from even starting. Having our own agent pool would help this.
  • Verify the reason why every job has a installing npm modules as part of their last command. In particular the Firebase deploy has a very long 1.4 minutes node module install process https://buildkite.com/elastic/datavis-ci/builds/646#_
  • expose logs at github level or link directly the status of a PR to the buildkite without passing for github
  • show the total CI time testing time on the PR message
  • When requesting to update the screenshot from a GH comment, just rerun the minimal required tasks
@markov00 markov00 added enhancement New feature or request :ci meta ...meta issue labels Mar 3, 2022
@nickofthyme nickofthyme added the internal Internal changes with no external impact label Jun 28, 2022
@markov00 markov00 changed the title Move CI to buildkite Buildkite CI improvements Jul 12, 2022
@markov00
Copy link
Member Author

markov00 commented May 7, 2024

Closing this because it's not planned to be resolved in the foreseeable future. It will be tracked in our Icebox and will be re-opened if our priorities change. Feel free to re-open if you think it should be melted sooner.

@markov00 markov00 closed this as not planned Won't fix, can't repro, duplicate, stale May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:ci enhancement New feature or request internal Internal changes with no external impact meta ...meta issue
Projects
None yet
Development

No branches or pull requests

2 participants