You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when making changes to the ansible code base and testing them through the CI, we rely on existing workflows. These workflows include a step that automatically pushes validator artifacts to the branch, which is unnecessary during testing. This adds complexity for developers, as the artifacts are not required to be published for simple tests.
To bypass this current workaround, manually comment out the push step, run the workflow and later revert the changes if the CI passes. This process introduces unnecessary overhead, requiring an extra commit and a subsequent revert.
There should be a way to run the workflow fully, but make the push step optional, controlled via a variable or flag that can be set according to the need. This would streamline the testing process by eliminating unnecessary file changes and commits
The text was updated successfully, but these errors were encountered:
Currently, when making changes to the ansible code base and testing them through the CI, we rely on existing workflows. These workflows include a step that automatically pushes validator artifacts to the branch, which is unnecessary during testing. This adds complexity for developers, as the artifacts are not required to be published for simple tests.
To bypass this current workaround, manually comment out the push step, run the workflow and later revert the changes if the CI passes. This process introduces unnecessary overhead, requiring an extra commit and a subsequent revert.
There should be a way to run the workflow fully, but make the push step optional, controlled via a variable or flag that can be set according to the need. This would streamline the testing process by eliminating unnecessary file changes and commits
The text was updated successfully, but these errors were encountered: