[self-hosted] Update install guide for semantically versioned cloud#255
Merged
aimichelle merged 1 commit intopixie-io:mainfrom May 9, 2023
Merged
[self-hosted] Update install guide for semantically versioned cloud#255aimichelle merged 1 commit intopixie-io:mainfrom
aimichelle merged 1 commit intopixie-io:mainfrom
Conversation
Signed-off-by: James Bartlett <jamesbartlett@pixielabs.ai>
|
| Name | Link |
|---|---|
| 🔨 Latest commit | ac411aa |
aimichelle
pushed a commit
to pixie-io/pixie
that referenced
this pull request
May 8, 2023
Summary: Updates `scripts/create_release_tag.sh` to also work with `cloud` as an artifact type. Updates `ci/cloud_build_release.sh` to only push to `latest` if its not an RC build. Once we create the first semantically versioned release we should land and deploy pixie-io/docs.px.dev#255. Type of change: /kind cleanup Test Plan: Built a cloud RC using these changes (deleted the tag from the repo so that the current docs.px.dev self-hosted instructions still work until this lands). Ran through the self-hosted deploy instructions (including the changes in pixie-io/docs.px.dev#255) and everything worked. Saw the expected version string in the cloud pods: `time="2023-05-08T20:29:31Z" level=info msg="Starting service" service=api-service version=0.1.0-pre-cloud-semver.5+Distribution.2551dc3.20230508201452.1.jenkins` (as an aside: I will fix the jenkins vs github actions BUILT_BY separately). Changelog Message: ```release-note Pixie Cloud now follows semantic versioning for release versioning. The first semantic versioned release of cloud will be `release/cloud/v0.1.0`. ``` Signed-off-by: James Bartlett <jamesbartlett@pixielabs.ai>
aimichelle
approved these changes
May 9, 2023
ddelnano
pushed a commit
to k8sstormcenter/pixie
that referenced
this pull request
Feb 25, 2026
Summary: Updates `scripts/create_release_tag.sh` to also work with `cloud` as an artifact type. Updates `ci/cloud_build_release.sh` to only push to `latest` if its not an RC build. Once we create the first semantically versioned release we should land and deploy pixie-io/docs.px.dev#255. Type of change: /kind cleanup Test Plan: Built a cloud RC using these changes (deleted the tag from the repo so that the current docs.px.dev self-hosted instructions still work until this lands). Ran through the self-hosted deploy instructions (including the changes in pixie-io/docs.px.dev#255) and everything worked. Saw the expected version string in the cloud pods: `time="2023-05-08T20:29:31Z" level=info msg="Starting service" service=api-service version=0.1.0-pre-cloud-semver.5+Distribution.2551dc3.20230508201452.1.jenkins` (as an aside: I will fix the jenkins vs github actions BUILT_BY separately). Changelog Message: ```release-note Pixie Cloud now follows semantic versioning for release versioning. The first semantic versioned release of cloud will be `release/cloud/v0.1.0`. ``` Signed-off-by: James Bartlett <jamesbartlett@pixielabs.ai>
ddelnano
pushed a commit
to k8sstormcenter/pixie
that referenced
this pull request
Feb 25, 2026
Summary: Updates `scripts/create_release_tag.sh` to also work with `cloud` as an artifact type. Updates `ci/cloud_build_release.sh` to only push to `latest` if its not an RC build. Once we create the first semantically versioned release we should land and deploy pixie-io/docs.px.dev#255. Type of change: /kind cleanup Test Plan: Built a cloud RC using these changes (deleted the tag from the repo so that the current docs.px.dev self-hosted instructions still work until this lands). Ran through the self-hosted deploy instructions (including the changes in pixie-io/docs.px.dev#255) and everything worked. Saw the expected version string in the cloud pods: `time="2023-05-08T20:29:31Z" level=info msg="Starting service" service=api-service version=0.1.0-pre-cloud-semver.5+Distribution.2551dc3.20230508201452.1.jenkins` (as an aside: I will fix the jenkins vs github actions BUILT_BY separately). Changelog Message: ```release-note Pixie Cloud now follows semantic versioning for release versioning. The first semantic versioned release of cloud will be `release/cloud/v0.1.0`. ``` Signed-off-by: James Bartlett <jamesbartlett@pixielabs.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary: Updates commands in the self-hosted install guide to work with semantically versioned cloud. This PR shouldn't be landed until the semantically versioned cloud PR lands on the main Pixie side.
Type of change: /kind cleanup.
Test Plan: Tested that the new
LATEST_CLOUD_RELEASEcommand works by adding a bunch of fake tags in the repo and seeing that they were sorted correctly and the correct latest tag was found.