chore: [VIO-3010] Transition from jenkins to Github Actions #474
Conversation
This file contains 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
This commit removes the `.jenkins` file, disabling builds through Jenkins, in favor of Github Actions.
This is a first pass at implementing a release workflow.
schoterson
reviewed
Jul 14, 2023
This is an attempt to enable the use of private workflows.
This reverts commit e004c20.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This commit disables builds through Jenkins, in favor of Github Actions.
Prior to merge, the vio-build/branch webhook will need to be disabled.
This also adds a new, untested
releaseworkflow. When a new release tag is created, it should run thereleasejob which will, create a pull request to update thesynse-serverhelm chart.