Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CI] Creates nightly pipeline #2187

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[CI] Creates nightly pipeline #2187

wants to merge 1 commit into from

Conversation

zachgk
Copy link
Contributor

@zachgk zachgk commented Jul 17, 2024

This creates a full nightly pipeline for the build, test, and release.

First, it enables a full build through temp repo approach. The build will always go to the temp repo in docker_build.yml, and then the separate docker_publish.yml can be used for the actual release step.

Following this, it also enables the integration suite to test the temp repo similarly to the integration runner.

Finally, a new action "Nightly Pipeline" is enabled to pull it all together. Right now, it will publish regardless of the result of the test. This matches the current behavior. When it changes in the future, the testing can be enabled through un-commenting the line.

@tosterberg

This creates a full nightly pipeline for the build, test, and release.

First, it enables a full build through temp repo approach. The build will always
go to the temp repo in docker_build.yml, and then the separate
docker_publish.yml can be used for the actual release step.

Following this, it also enables the integration suite to test the temp repo
similarly to the integration runner.

Finally, a new action "Nightly Pipeline" is enabled to pull it all together.
Right now, it will publish regardless of the result of the test. This matches
the current behavior. When it changes in the future, the testing can be enabled
through un-commenting the line.
@tosterberg
Copy link
Contributor

I am good with the change, we can discuss approval and merge after 0.29.0 release has stabilized. My vote is that we set a task for the approval, merge, and cherry pick of this PR as well as the unified integration tests PR into the 0.26.0 branch through 0.29.0, and add a documentation maintenance step to update the related runbooks with the new action names and process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants