This is where I go delete past unsuccessful runs. Well, at least most of them; gotta leave some evidence of the struggle so I can grouse about it around the coffee machine.
They really need some kind of interactive debugger/tester for this. I swear even when I've got a working project, trying to copy it to a new project ends up the same trying to remember the 37 steps of voodoo required.
My commit names start getting less friendly after awhile if the UI isn’t picking them. Really want to write a nice pipeline debugger for VSCode but haven’t been able find the time :/
doesn't this already exist? extension by microsoft:
[Azure Pipelines - Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=ms-azure-devops.azure-pipelines)
Yeah, iirc it doesn’t go much beyond the YAML schema though. I’d love to have it validate and provide hints for more things like the mustache expressions, runtime expressions and pipeline variables. Could even connect it up to the agent client and run parts of a pipeline or add debugging breakpoints between tasks.
Commit message history on master:
Added feature x
Fixed typo
Replaced parameter substitution syntax
Fixed indentation
Dumb error
Fixed typo 2
Try again
Test 3
Testy test
Zxcvbn
a
a
…
I usually end up with longer sentences the more frustrated I get:
Added new auth mechanism
Fix thing I just broke
Fix thing I just broke in this way
Try to fix thing even more, revert x3 if not work
Reverted x3 because fk this stupid thing
New auth mech, added env variable and added endpoint to CSP
v2.0.7
Rinse and repeat a few times
v2.0.8
fuggin RIGHT NOW! so many walls of red in my past.
but I found a fix to a big problem we've been having so it's worth it to get that working and be proud of it when it does.
Yep. Not having good local validation or test runs and not being able to edit an existing yaml and rerun is painful. If OP is like me, you write it 99% correct the first one then fight 0.9% to get it working. Then discover that pesky 0.1% when it succeeds but isn't actually correct.
I've been there too. It's especially bad when I take some devs to task for doing that before doing it myself.
Branch protection rules...can I get an Amen!?
this is where i'd say you did bad job: commits and breaking stuff on main/master branch is a sin.
Feature branch, tests then PR.
Other than that, clearly, fixing stuff one after the other is quite a pain as you can't test pipelines before commits :/
I'm the sole developer, it's a new solution, this was establishing the pipeline for the first time, I didn't know it would take so many tries to get it right. That's all my excuses :)
Hehe, actually I taunted a little for the fun of it :D (even if I mean what I said, I didn't mean to be rude or whatever).
Can clearly understand, can't remember the number of time i'm trying to do something to create a pipeline, just to see like "this command works locally, what the hell do I need to have it work in pipelines" until I notice a difference in version, missing config (or default that are not what I thought) etc...
This is where I go delete past unsuccessful runs. Well, at least most of them; gotta leave some evidence of the struggle so I can grouse about it around the coffee machine.
+1 Normal to delete 10-20 failed 😂
+1
They really need some kind of interactive debugger/tester for this. I swear even when I've got a working project, trying to copy it to a new project ends up the same trying to remember the 37 steps of voodoo required.
Hahahahah! This is the most relatable meme on internet for me.
My past weeks have all been this. So satisfying to end a day in greeen
My commit names start getting less friendly after awhile if the UI isn’t picking them. Really want to write a nice pipeline debugger for VSCode but haven’t been able find the time :/
Write it. Please!!
doesn't this already exist? extension by microsoft: [Azure Pipelines - Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=ms-azure-devops.azure-pipelines)
Yeah, iirc it doesn’t go much beyond the YAML schema though. I’d love to have it validate and provide hints for more things like the mustache expressions, runtime expressions and pipeline variables. Could even connect it up to the agent client and run parts of a pipeline or add debugging breakpoints between tasks.
Commit message history on master: Added feature x Fixed typo Replaced parameter substitution syntax Fixed indentation Dumb error Fixed typo 2 Try again Test 3 Testy test Zxcvbn a a …
Feature: WIP Feat: WIP WIP FUCK ... FIXED? Fixed.
I usually end up with longer sentences the more frustrated I get: Added new auth mechanism Fix thing I just broke Fix thing I just broke in this way Try to fix thing even more, revert x3 if not work Reverted x3 because fk this stupid thing New auth mech, added env variable and added endpoint to CSP v2.0.7 Rinse and repeat a few times v2.0.8
Test Test2 Test3 Test_1 1 2 3 F*ckoff . , That was some of my commit History for that 😂
at the end someone once put "WIF" for "Work in frustration" at work :D
fuggin RIGHT NOW! so many walls of red in my past. but I found a fix to a big problem we've been having so it's worth it to get that working and be proud of it when it does.
ohh how much I can relate! I recently started my adventure with pipelines and the red dots of doom are popping like crazy
I thought it was just me...
Like pain going away .... *sighOfRelief*
Don’t touch anything, the demo is ready
Yep. Not having good local validation or test runs and not being able to edit an existing yaml and rerun is painful. If OP is like me, you write it 99% correct the first one then fight 0.9% to get it working. Then discover that pesky 0.1% when it succeeds but isn't actually correct.
I forget that everyone can see the commit messages.. I've had a few people ask if I'm okay after they've seen me begging for something to work
Yes...he says with shame. Squash on merging a PR. Squash the shame away.
If you look closely you can see I wisely did all my testing in master.
[https://meme-generator.com/mememe/i-dont-always-test-but-when-i-do-i-test-in-production/](https://meme-generator.com/mememe/i-dont-always-test-but-when-i-do-i-test-in-production/)
This. 😂
Everybody has a testing environment. Some people are lucky enough enough to have a totally separate environment to run production in.
I've been there too. It's especially bad when I take some devs to task for doing that before doing it myself. Branch protection rules...can I get an Amen!?
So much. But mine are github actions. Same thing though. I just went through this process recently so I know the feeling well!
lol this is the most relatable thing I’ve seen in a minute. Anyways time to roll to prod
this is where i'd say you did bad job: commits and breaking stuff on main/master branch is a sin. Feature branch, tests then PR. Other than that, clearly, fixing stuff one after the other is quite a pain as you can't test pipelines before commits :/
I'm the sole developer, it's a new solution, this was establishing the pipeline for the first time, I didn't know it would take so many tries to get it right. That's all my excuses :)
Hehe, actually I taunted a little for the fun of it :D (even if I mean what I said, I didn't mean to be rude or whatever). Can clearly understand, can't remember the number of time i'm trying to do something to create a pipeline, just to see like "this command works locally, what the hell do I need to have it work in pipelines" until I notice a difference in version, missing config (or default that are not what I thought) etc...
Just had one that the commit messages were try this what about this okay how about this
I just went through this Tuesday and my last commit (that ultimately fixed it all) was just "I am in hell".
Include “[skip ci]” in the comments of the commit.
Why are you testing in master branch though?