https://github.com/cgwalters/fedora-silverblue-pipeline

Fork of fedora-coreos-pipeline for FSBCOS
https://github.com/cgwalters/fedora-silverblue-pipeline

Last synced: about 24 hours ago
JSON representation

Fork of fedora-coreos-pipeline for FSBCOS

• Host: GitHub
• URL: https://github.com/cgwalters/fedora-silverblue-pipeline
• Owner: cgwalters
• License: other
• Created: 2020-01-04T16:41:17.000Z (almost 5 years ago)
• Default Branch: master
• Last Pushed: 2020-10-16T21:24:06.000Z (about 4 years ago)
• Last Synced: 2024-11-16T21:42:01.376Z (about 1 month ago)
• Language: Python
• Size: 344 KB
• Stars: 1
• Watchers: 4
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: COPYING

Awesome Lists containing this project

README

        
# Fedora CoreOS Pipeline

This is the Jenkins pipeline configuration for

[Fedora CoreOS](https://github.com/coreos/fedora-coreos-config).

The pipeline is built around

[coreos-assembler](https://github.com/coreos/coreos-assembler).

It uses the OpenShift Jenkins template and is meant to be

fully compatible with the local dev `oc cluster up`

workflow. For more information on getting started, see

[HACKING](HACKING.md).

The production instance is running in

[CentOS CI](https://jenkins-fedora-coreos.apps.ocp.ci.centos.org)

(though note anonymous view is blocked by default). Its raw

build output can be seen in the

[build browser](https://builds.coreos.fedoraproject.org/browser)

(but note that the latest ***supported*** version of FCOS must

be downloaded from

[the official page](https://getfedora.org/en/coreos/download/)).

To operate the production Jenkins (or more generally to access the

production namespace), you must have access to the cluster

at https://console.apps.ci.centos.org:8443 and to the projects

"fedora-coreos" and "fedora-coreos-devel".

For more information on CentOS CI, see these resources:

  - https://github.com/centosci/ocp4-docs (the "new" OCP 4.4 cluster)

  - https://wiki.centos.org/QaWiki/CI (out of date)

If you need access, you can open a bug request at

https://bugs.centos.org/ against the `Buildsys` project and

`Ci.centos.org Ecosystem Testing` category.

Do note that the bug-tracker and OpenShift use different

authentication backends, so you will have separate credentials

for each.

Please specify the requested username, RBAC for projects

`fedora-coreos` and `fedora-coreos-devel`, and your GPG key

fingerprint.

You also need one of the project admins as a sponsor, please

reach out on Freenode `#fedora-coreos` channel.

You should also be able to run this pipeline and run it in any

OpenShift cluster that supports (potentially nested)

virtualization.

### Terminology

This repo tries to maintain a consistent set of words to

avoid confusion around different concepts with similar

names:

- `production/development/mechanical streams`: refers to the

  Fedora CoreOS streams as defined in

  https://github.com/coreos/fedora-coreos-tracker/blob/master/stream-tooling.md

- `official pipeline`: the *single* official instance of

  this pipeline code, which runs in the `fedora-coreos`

  namespace on the CentOS CI OpenShift cluster and pushes to

  the `fcos-builds` bucket.

- `developer pipeline`: a pipeline stood up by a developer

  running in a separate cluster/namespace

So for example, a developer pipeline may perform e.g. a

production or development stream build, but release tooling

only cares about builds performed by the official pipeline

pushed to the official locations.

Avoid using the naked word `devel`. Always either use

`development` (if talking about the streams) or `developer`

(if talking about the pipeline).

Similarly, avoid using the word `production` alone, in

favour of `production stream` or `official pipeline`.