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
This is a question: which file serves as a source of configuration for Drone CI, .drone.yml or .drone.jsonnet?
If some of it is legacy, we need to drop it to avoid confusion and duplication of efforts. If the one of it is somehow generated from the other one, it should be documented how to make this conversion.
Also it appears that after the changes was made to the CI configs, all subsequent builds require manual approval from authorized person to kick off the build.
Description of Issue/Question
This is a question: which file serves as a source of configuration for Drone CI,
.drone.yml
or.drone.jsonnet
?If some of it is legacy, we need to drop it to avoid confusion and duplication of efforts. If the one of it is somehow generated from the other one, it should be documented how to make this conversion.
Also it appears that after the changes was made to the CI configs, all subsequent builds require manual approval from authorized person to kick off the build.
@s0undt3ch, could we change the CI behavior somehow to allow config changes applied automatically once being propagated to the
develop
? Because for now the build for the tip ofdevelop
is stuck:https://drone.saltstack.com/saltstack/salt-bootstrap/282
The text was updated successfully, but these errors were encountered: