github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/hack/jenkins/README.md

55 lines
2.7 KiB
Markdown
Raw Normal View History

Initial commit of Jenkins script + README And a config description. This doesn't yet have much - first want to make sure I can do the build job. Next I'll submit the e2e script with its twiddles and switch those over. (After going to 3 e2es, I think it's finally time for version control.)
2015-01-09 16:02:11 +00:00
# Jenkins
[Jenkins](http://jenkins-ci.org/) is a pluggable continuous
integration system. The Google team is running a Jenkins server on a
private GCE instance for the Kubernetes project in order to run longer
integration tests, continuously, on different providers. Currently, we
Allow source-controlled Jenkins job configs. Job configs are stored in YAML files in hack/jenkins/job-configs in the format used by Jenkins Job Builder. A docker container running on Jenkins fetches job configs every fifteen minutes and updates Jenkins.
2015-12-05 00:23:30 +00:00
are running tests on GCE, GKE, and AWS.
Initial commit of Jenkins script + README And a config description. This doesn't yet have much - first want to make sure I can do the build job. Next I'll submit the e2e script with its twiddles and switch those over. (After going to 3 e2es, I think it's finally time for version control.)
2015-01-09 16:02:11 +00:00
## General flow
The flow of the Google Jenkins server:
Allow source-controlled Jenkins job configs. Job configs are stored in YAML files in hack/jenkins/job-configs in the format used by Jenkins Job Builder. A docker container running on Jenkins fetches job configs every fifteen minutes and updates Jenkins.
2015-12-05 00:23:30 +00:00
* Under the `kubernetes-build` job: Every 2 minutes, Jenkins polls for a batch
of new commits, after which it runs the `build.sh` script (in this directory)
on the latest tip. This results in build assets getting pushed to GCS and the
`latest.txt` file in the `ci` bucket being updated.
* On trigger, and every half hour (which effectively means all the time, unless
we're failing cluster creation), e2e variants run, on the latest build assets
in GCS:
* `kubernetes-e2e-gce`: Standard GCE e2e.
* `kubernetes-e2e-gke`: GKE provider e2e, with head k8s client and GKE
creating clusters at its default version.
* `kubernetes-e2e-gke-ci`: GKE provider e2e, with head k8s client and GKE
creating clusters at the head k8s version.
* `kubernetes-e2e-aws`: AWS provider e2e.
Initial commit of Jenkins script + README And a config description. This doesn't yet have much - first want to make sure I can do the build job. Next I'll submit the e2e script with its twiddles and switch those over. (After going to 3 e2es, I think it's finally time for version control.)
2015-01-09 16:02:11 +00:00
* Each job will not run concurrently with itself, so, for instance,
Jenkins executor will only ever run one `kubernetes-build`
job. However, it may run the jobs in parallel,
i.e. `kubernetes-build` may be run at the same time as
`kubernetes-e2e-gce`. For this reason, you may see your changes
pushed to our GCS bucket rapidly, but they may take some time to
fully work through Jenkins. Or you may get lucky and catch the
train in 5 minutes.
Allow source-controlled Jenkins job configs. Job configs are stored in YAML files in hack/jenkins/job-configs in the format used by Jenkins Job Builder. A docker container running on Jenkins fetches job configs every fifteen minutes and updates Jenkins.
2015-12-05 00:23:30 +00:00
* There are many jobs not listed here, including upgrade tests, soak tests, and
tests for previous releases.
Initial commit of Jenkins script + README And a config description. This doesn't yet have much - first want to make sure I can do the build job. Next I'll submit the e2e script with its twiddles and switch those over. (After going to 3 e2es, I think it's finally time for version control.)
2015-01-09 16:02:11 +00:00
## Scripts
The scripts in this directory are directly used by Jenkins, either by
curl from githubusercontent (if we don't have a git checkout handy) or
by executing it from the git checkout. Since Jenkins is an entity
outside this repository, it's tricky to keep documentation for it up
to date quickly. However, the scripts themselves attempt to provide
color for the configuration(s) that each script runs in.
Add ga-beacon analytics to gendocs scripts hack/run-gendocs.sh puts ga-beacon analytics link into all md files, hack/verify-gendocs.sh verifies presence of link.
2015-05-14 22:12:45 +00:00
Allow source-controlled Jenkins job configs. Job configs are stored in YAML files in hack/jenkins/job-configs in the format used by Jenkins Job Builder. A docker container running on Jenkins fetches job configs every fifteen minutes and updates Jenkins.
2015-12-05 00:23:30 +00:00
## Job Builder
New jobs should be specified as YAML files to be processed by [Jenkins Job
Builder](http://docs.openstack.org/infra/jenkins-job-builder/). The YAML files
live in `job-configs` and its subfolders. Jenkins runs Jenkins Job Builder
in a Docker container defined in `job-builder-image`, and triggers it using
`update-jobs.sh`. Jenkins Job Builder uses a config file called
[jenkins_jobs.ini](http://docs.openstack.org/infra/jenkins-job-builder/execution.html)
which contains the location and credentials of the Jenkins server.
Add ga-beacon analytics to gendocs scripts hack/run-gendocs.sh puts ga-beacon analytics link into all md files, hack/verify-gendocs.sh verifies presence of link.
2015-05-14 22:12:45 +00:00
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/hack/jenkins/README.md?pixel)]()