Create travis jobs for taskcluster repos that have no CI set up yet

RESOLVED FIXED

Status

RESOLVED FIXED
3 years ago
9 months ago

People

(Reporter: pmoore, Assigned: pmoore)

Tracking

(Blocks: 1 bug)

Details

The full list of projects that have travis jobs set up can be seen here:
  1) https://travis-ci.org/taskcluster

The full list of github repos we have can be seen here:
  2) https://github.com/taskcluster

For repos listed in 2) that are not listed in 1) we should either:
  a) set up a travis job
  b) deprecate the repository

If the repository is actively used (regardless of whether it is currently undergoing change) it should have a working, reliable CI.
Affected repositories:

  * apidesign
  * aws-lambda
  * aws-provisioner
  * azure-blobstream
  * buildbot-step
  * bunyan-env-config
  * cloud-mirror
  * dind
  * dind-service
  * docker-bootstrap
  * docker-exec-websocket-server
  * docker-experiments
  * docker-image-builder
  * docker-registry-v2-proxy
  * docker-services
  * docker-worker
  * docker-worker-ci
  * dockerode-process
  * dockerode-promise
  * example-worker
  * gaia-taskcluster
  * gecko-images
  * github-graph-example
  * heroku-grafana
  * index-browser
  * jsonschema
  * logconsumer
  * logserver
  * logstream
  * mozilla-hg-pushlog
  * mozilla-taskcluster
  * nginx-s3-proxy
  * npm-cache
  * packer-boxes
  * provisioner-hub
  * rust-hawk
  * s3-copy-proxy
  * stateless-dns-server
  * task-factory
  * taskcluster-babel
  * taskcluster-bot
  * taskcluster-cli
  * taskcluster-cli-go
  * taskcluster-diagnostics
  * taskcluster-docs
  * taskcluster-github
  * taskcluster-hooks
  * taskcluster-https-proxy
  * taskcluster-lib-loader
  * taskcluster-lib-rules
  * taskcluster-lib-scopes
  * taskcluster-log
  * taskcluster-login
  * taskcluster-loop
  * taskcluster-manifest
  * taskcluster-monitor
  * taskcluster-pulse
  * taskcluster-purge-cache
  * taskcluster-registry
  * taskcluster-scheduler
  * taskcluster-secrets
  * taskcluster-skeleton
  * taskcluster-stats
  * taskcluster-stats-collector
  * taskcluster-status
  * taskcluster-tools
  * taskcluster-treeherder
  * taskcluster-try
  * taskcluster-utils
  * taskcluster-vpn-proxy
  * taskcluster-worker
  * taskcluster-worker-bind9
  * tc-vcs-repo-test
  * testdroid-proxy
  * testrepo
  * worker-stats
Assignee: nobody → pmoore
I've not looked into this any further since raising the bug. Adding 'good first bug' as might be interesting for a contributor to set up CI for projects which have documented how they should be tested.
Whiteboard: [good first bug]
For the repos that we use, this is done.  We're moving toward using taskcluster-github instead of travis, but otherwise yes.  Services are all already tested, and will be checked in the work on RFC0110.  Libraries all use Travis to release, which implicitly runs tests.

Things like testdroid-proxy and worker-stats (to pick a few) are leftovers that we should archive, but that's another projects.
Status: NEW → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → FIXED
Whiteboard: [good first bug]
You need to log in before you can comment on or make changes to this bug.