Commit Graph
100 Commits
Author SHA1 Message Date
Sébastien Han 6fb67a297d build: only produce binary for linux
We now build rook to build only for linux platforms and not darwin nor
windows anymore.

Signed-off-by: Sébastien Han <seb@redhat.com>
2021-11-04 15:13:40 +01:00
Travis Nielsen 8715964fd5 docs: update release process for github actions
Jenkins has been decommissioned so the release instructions are
updated to work more clearly with the new processes around
the github actions.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
2021-10-20 12:10:21 -06:00
Travis Nielsen fee7e82416 docs: publish master docs to latest path
Rename the master docs to latest. This will be easier
to understand for users who are new to the project.
The url will also contain latest, which will be more
clear to reference instead of the master path. This
also follows the pattern of the ceph docs site.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
2021-09-10 17:55:14 -06:00
Blaine Gardner 7febd4e303 ci: add debugging to release build script
Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>
2021-09-01 13:58:21 -06:00
Sébastien Han 18b1477352 ci: remove jenkins from master branch
Thank you Jenkins for all those years, but it's to retire.

Signed-off-by: Sébastien Han <seb@redhat.com>
2021-06-10 15:34:15 +02:00
Travis Nielsen 043f947321 build: remove yugabytedb operator
The YugabyteDB team has decided to move support of their operator
to a new repo at https://github.com/yugabyte/yugabyte-operator.
The operator in Rook is no longer needed. Further usage of
the YugabyteDB operator is recommended at the new location.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
2021-02-06 00:03:41 -07:00
Travis Nielsen 2294851ca3 build: remove the cockroachdb operator from rook
The cockroachDB operator has not had community support in Rook.
Therefore, the time has come to deprecate and remove it.
If the sources are still needed, there is always git history.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
2021-01-20 17:28:58 -07:00
Artur 0754695655 build: switch to new aws buckets
Signed-off-by: Artur <artur@upbound.io>
2021-01-15 23:58:23 -08:00
Alexander Trost e5ba1fa7a8 build: update manifest-tools version to v1.0.2
This updates the manifest-tools from v1.0.0 to v1.0.2 to
pickup the following fix
https://github.com/estesp/manifest-tool/pull/90.

This currently prevents the build to push images to Docker
hub.

Resolves #5194

Signed-off-by: Alexander Trost <galexrt@googlemail.com>
2020-04-07 19:47:50 +02:00
moricho 7d0215d820 ci: switch to use go.mod.check target
This switches to use `go.mod.check` target instead of `go.vendor.check` target.

Signed-off-by: moricho <ikeda.morito@gmail.com>
2020-03-17 16:48:43 +09:00
moricho 2beb731a7e go: move to gomodules
This switches Rook to use `go mod` instead of `dep` for
dependencies management.

Signed-off-by: moricho <ikeda.morito@gmail.com>
2020-03-17 16:47:53 +09:00
Travis Nielsen de06c5c2ec build: update manifest tool version to v1.0.0
The manifest tool is needed for pushing images to dockerhub.
The tool has been failing the past two days due to running
an old version.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
2020-03-06 11:59:27 -07:00
Travis Nielsen 67c0b02848 Merge pull request #3078 from travisn/no-extra-release-tags
No longer generate "release" docker tag during release build promotion
2019-12-12 12:55:04 -07:00
Travis Nielsen eb1dadccb2 build: always use the version suffix from tag pipeline
The version suffix such as alpha.0, beta.0, or rc.0 only apply
when running the tag pipeline or the release build. Otherwise,
we don't want to use the suffix from the master build.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
2019-12-09 17:43:29 -07:00
travisn 1d97a6089d build: sanitize the master tag
The master branch uses the first tag from the last release
to create the version tag. Since the 1.1 release this tag
can include the alpha, beta, or rc tags, which only make
sense for the release tags, but not the master tag. This
change removes the suffix from the master tag.

Signed-off-by: travisn <tnielsen@redhat.com>
2019-10-14 10:58:51 -06:00
travisn 82b5c0d48d allow git tags to be added for alpha, beta, or rc releases
The tag pipeline currently only allows a strict versioning tag to be
applied with the major, minor, and patch numbers such as v1.1.0.
This change allows adding a suffix to the tag to support alpha,
beta, or rc releases. For example, the version can now be
v1.1.0-alpha.0 or v1.1.0-beta.1 or v1.1.0-rc.2

Signed-off-by: travisn <tnielsen@redhat.com>
2019-08-27 16:18:26 -06:00
Sameer Kulkarni dd9e51286e yugabytedb: rook/yugabutedb image build
Signed-off-by: Sameer Kulkarni <samkulkarni20@gmail.com>
2019-08-27 22:45:14 +05:30
travisn 0dd62eb56f build: do not add generic release docker tag
To support upgrades, the operator relies on a changing tag
between versions so that when a pod spec is updated, k8s will
restart the pod due to the new image name. If the image name
does not change, the operator cannot control the upgrade deployment.
Therefore, we do not support a generic docker tag such as
rook/ceph:release and we expect specific version tags to be
specified in the operator such as rook/ceph:v1.0.0.
The master build is tagged with a generic tag for convenience
of testing the latest builds, but it is important to note that
upgrades are not supported between master builds.

Signed-off-by: travisn <tnielsen@redhat.com>
2019-08-26 14:24:05 -06:00
travisn 81f55a12eb build: promote builds only to master and release
The alpha, beta, and stable channels do not match the rook release process.
Each storage provider defines their own stability based on the CRDs
rather than defining it with the release process. Rook really
only has two release streams: master and the official releases.
Master is published with each merge, while releases go through
a signoff process to ensure quality. Thus, the alpha, beta,
and stable channels are removed and replaced with a
single release channel.

Signed-off-by: travisn <tnielsen@redhat.com>
2019-04-27 22:49:11 -06:00
Michael Goff f88a9b78ba docs: Update the build process to use the new docs build process
Signed-off-by: Michael Goff <thephred@gmail.com>
2019-02-13 11:20:41 -08:00
travisn efd581e7ed start toolbox pod with the ceph image instead of a separate image
Signed-off-by: travisn <tnielsen@redhat.com>
2018-10-02 15:43:53 -06:00
Bassam Tabbara e2fd1eb8e6 Merge pull request #2054 from SUSE/ceph-makefiles-skip-image-save
Image build/release: do not save image for builds; save only for release
2018-08-23 10:09:19 -07:00
Blaine Gardner 60b4a1e4d3 Image make: Move save image step to release builds
The image save step in the image build makefiles takes half or more of
the time of builds, and this step is not necessary for development
builds. Move this functionality to the `build/release/Makefile` so that
images are saved during release builds but not during dev builds. This
will allow developers to iterate more quickly on their builds.

Signed-off-by: Blaine Gardner <blaine.gardner@suse.com>
2018-08-23 09:49:56 -06:00
Jared Watts dd948b155a build: remove support for quay.io
Signed-off-by: Jared Watts <jbw976@gmail.com>
2018-08-17 14:03:55 -07:00
Jared Watts 31d29fe4e7 release: update release approval policy to be in accordance with governance
Signed-off-by: Jared Watts <jbw976@gmail.com>
2018-08-02 16:24:44 -07:00
Blaine Gardner 483163fc21 make: Allow building select images
Raise the scope of the `IMAGES` config variable in the
`build/release/Makefile` to the `build/makelib/common.mk` file, and use
the `IMAGES` variable in the `images/Makefile` to allow users to build
only select images.

Examples of new use:
  make IMAGES='ceph ceph-toolbox' build
  make -C build/release IMAGES='ceph ceph-toolbox' publish

The 'images/image.mk' clean.build target was changed to use
`CLEAN_IMAGES` instead of `IMAGES`, as it was conflicting with use of
the parameter in image builds.

Added IMAGES option to top-level make's help text. The text for this
option exceeded 80 lines in the `Makefile` itself, so the help text was
refactored to eliminate `    @echo '<text>'`. The `Makefile` text should
now match exactly what is output to the user including line length.

Added IMAGES option to `INSTALL.md` file's "Build" section and also
moved some text around and added a few extra points of clarification
there to hopefully improve readability, especially for first-time
readers.

Signed-off-by: Blaine Gardner <blaine.gardner@suse.com>
2018-07-20 15:49:46 -06:00
Jared Watts 088278d28e Define release criteria and checklist
Signed-off-by: Jared Watts <jbw976@gmail.com>
2018-07-11 17:40:54 -07:00
Tony Allen 7442f8713b Implement Minio operator w/ tests.
Signed-off-by: Tony Allen <tony@upbound.io>
2018-06-21 16:41:30 -07:00
Jared Watts a80f05cf51 cockroachdb: rook/cockroachdb image build
Signed-off-by: Jared Watts <jbw976@gmail.com>
2018-06-18 17:09:45 -07:00
Jared Watts e48e951d1c Rename toolbox to make it Ceph specific, short names for CRDs, upgrade guide tweaks
Signed-off-by: Jared Watts <jbw976@gmail.com>
2018-05-22 12:31:38 -07:00
Jared Watts 3a2a2d2021 build: rook/ceph image build
Signed-off-by: Jared Watts <jbw976@gmail.com>
2018-05-18 14:25:39 -07:00
travisn 9e4baf4c96 (ichekrygin) Remove the rook api service from production code
Remove controller api component and api daemon
Remove rookctl and  endpoints from Docker image

Signed-off-by: travisn <tnielsen@redhat.com>
2018-03-16 08:30:54 -07:00
Bassam Tabbara 6b89a8feda build: use new S3 buckets
Signed-off-by: Bassam Tabbara <bassam@upbound.io>
2018-02-26 08:55:50 -08:00
Bassam Tabbara 07463fa0dd images: disable armhf image builds
While ceph can build fine on armhf it is not a tested configuration
today nor are debian packages for ceph published. Also ceph requires
more horsepower than is typically available on armhf machines.

We are dropping armhf support for now. arm64 is still supported.
2018-01-08 21:06:11 -08:00
Jared Watts 64e88253af docs: update release readme instructions and clear out pending release notes 2017-11-08 15:44:35 -08:00
Bassam Tabbara 14dc8e39ea build: update manifest tool 2017-10-24 15:38:50 -07:00
Bassam Tabbara 2568e8b679 build: fix helm pre-req 2017-08-15 12:09:15 -07:00
Bassam Tabbara ab5d89fff7 build: fix chart merging 2017-08-14 16:26:01 -07:00
Bassam Tabbara 9f6d3798e5 build: publish and promote helm charts
we now support charts.rook.io
2017-08-10 13:26:45 -07:00
Bassam Tabbara dfd8ff7c36 build: remove empty recipe lines 2017-08-09 12:16:13 -07:00
Ian Lovett b4cc7523b8 changes required for building and publishing docs through ci 2017-08-04 15:21:16 -07:00
Bassam Tabbara b7bc840c89 build: update release docs 2017-08-04 08:34:35 -07:00
Bassam Tabbara b9c504bca3 build: add pipeline options to promote and tag 2017-08-03 16:19:44 -07:00
Bassam Tabbara 695eac60be build: create tools dir before installing manifest-tool 2017-08-03 16:19:44 -07:00
Bassam Tabbara 072cb5fbd5 build: update release docs 2017-08-03 10:08:09 -07:00
Bassam Tabbara 82b10d1cdc build: pass the BRANCH_NAME to promote 2017-08-03 10:08:09 -07:00
Bassam Tabbara fbf9650c16 build: dont tag release inside container 2017-08-02 21:17:16 -07:00
Bassam Tabbara 4e1b4fbec9 build: add promote jenkinsfile 2017-08-02 17:24:36 -07:00
Bassam Tabbara 103fb39f11 build: add support for tagging a release
added a new make target that will tag a release and create a release branch if needed
2017-08-02 17:24:36 -07:00
Bassam Tabbara 3b948e0901 build: write version file during build not release 2017-07-24 13:27:16 -07:00