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
track "warnings" or "additional information" and attach them to builds, steps, pipelines, etc throughout a build's lifecycle. the idea came from v0.25 breaking changes to the yaml compiler. it would be ideal if the user could get a heads up that the behavior of their pipeline may have changed in a recent release. a user will never know unless you track it and put it right in front of their face ⚠️
the idea is track things that are relevant/helpful, then render these warnings to the user in the form of UI enhancements, CLI output, etc.
other example warnings might be:
using unsupported yaml keys (ports)
using deprecated yaml syntax
using features that are subject to change
referencing secrets that arent pulled in
referencing a secret inside the environment block
referencing an org/repo secret in the wrong org/repo
here's a screenshot of what i'm thinking a "Pipeline Warnings" view might look like. the warning is just an example based on anchor merge changes from v0.25
The text was updated successfully, but these errors were encountered:
Description
track "warnings" or "additional information" and attach them to builds, steps, pipelines, etc throughout a build's lifecycle. the idea came from⚠️
v0.25
breaking changes to the yaml compiler. it would be ideal if the user could get a heads up that the behavior of their pipeline may have changed in a recent release. a user will never know unless you track it and put it right in front of their facethe idea is track things that are relevant/helpful, then render these warnings to the user in the form of UI enhancements, CLI output, etc.
other example warnings might be:
environment
blockhere's a screenshot of what i'm thinking a "Pipeline Warnings" view might look like. the warning is just an example based on anchor merge changes from
v0.25
The text was updated successfully, but these errors were encountered: