![]() I currently have YAML triggers overridden for the pipeline, but I did also define the same trigger in the YAML to see if that would help (it did not). Nothing is broken and no further details are given about the supposed issue. ![]() The odd part here is that the pipeline works completely fine, including triggers. The pipelines run perfectly fine, however I get a "Some recent issues detected related to pipeline trigger." warning at the top of the pipeline summary page and viewing details only states: "Configuring the trigger failed, edit and save the pipeline again." Use a password manager like LastPass to save your passwords, it keeps your information protected from attacks or snooping.I have run in to an odd problem after converting a bunch of my YAML pipelines to use templates for holding job logic as well as for defining my pipeline variables.Update passwords after every three months.Avoid using similar passwords that change only a single word or character. ![]() Share your sensitive information with friends and family through LastPass’ secure password sharing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |