Azure DevOps Task Control Option: Cannot Change "Run this task" dropdown - azure-devops

I'm new to Azure DevOps, so please forgive me if my query seems a tad silly.
I'm trying to change our build definition so that it will miss certain steps based on the value of a Pipeline variable. So, if I'm correct, I believe that I first must change the Run this task selection (found under Control Options) to Custom conditions (its current value is Only when all previous tasks have succeeded). However, everytime I try this, the original is reinstated. It's as though I don't have the proper permissions, but I'm certainly able to change and save other properties. I'd be grateful for any suggestions!
Thanks,
David.

Thanks to those who responded. I've just tried again, and got it working. The "trick" involved is to make the selection using the arrow keys, and not the mouse. A colleague has also verified this quite odd behaviour.
The browser we are using is Chrome.
Regards,
David.

Related

VSC command palette (too narrow)

Is there any possibility to make command palette wider?
When looking for symbol (e.g. same functions with different set of arguments) to less characters are shown to choose proper definition.
Is there any possibility to mitigate this problem?
Using standard VS Code settings looks like you can't do this, which I agree should be possible. The strange thing is that I can't find an extension too that does this, so there may be a specific reason why this can't be done at the moment. By the way you can open an Issue on the VSCode Github and ask the developers themself to add this feature or why seems to be missing at the moment

Scheduled tasks are being queued on windows server 2012

I have scheduled few tasks in "Scheduled Tasks", but tasks are being queued instead of executing. When I run the tasks manually tasks being executed correctly. I tried all the possible configuration/properties suggested after Google search. Below are screenshots of the task properties.
This post is a litle bit old, but i had the same issue and a found a funny solution. I don't know if this is your case, but i using a Notebook that was not connected from the power. Well... Just disable the option "Start the task only if the computer is on AC power"
(or just put it on the power) and have fun!
Task Conditions
I had faced the same issue and after making a small setting change it worked! Screenshot is attached. When I selected red tick option from X option, it did the trick.
Initially, I selected "Do not start a new instance" and the job was going in "Queued" state. When I changed it to "Stop the existing instance" it worked for me!
Hope it could help.
Unfortunately I was not able to find the reason for this. I had to delete all tasks and add again to solve the issue.
Too bad I only found this post now, we encountered the same issue.
What solved it for us was to run a sysprep (without generalize), reboot the machine and rejoin it into the domain.
Hope it will help you / someone in the future.

vscode: Automatically save all on build

In Visual Studio when I trigger a build it automatically saves all files first. I want the same behavior in vscode, but couldn't find a way to do it short of writing my own extension. Is there any simple method I'm missing?
It's not exactly what you're asking, but will also accomplish what you want: you could enable the auto-save feature:
"files.autoSave": "afterDelay"
After using IntelliJ for a while, I managed to get rid of my habit of pressing Ctrl+S after every second typed-out word, for the most part (since it has auto-save by default). I was happy to find out that VSCode support this somewhat less stressful workflow too.
Other than that, there's also a Files: Save All command you've probably already found.
I'm actually not sure you can do this with the extension API right now - you can definitely trigger the "save all" command easily, but you'd need to be notified of when a build occurs, and I couldn't find any events for this. I think it will definitely be possible after #15179 is resolved though, which should allow extensions to participate in builds.

TeamCity Use Credentials of User Currently Logged In

Here is my problem. I have a build step in TeamCity that fires a powershell which updates a configuration parameter in another TC sub-project and resets the build counter via an API call. To do so, I have to pass valid credentials, which I am setting up as a parameter to be entered when the a custom build is run. This works great, however, for some reason if the password is typo'd even once(and I am using TC's password type parameter so it is masked, making this easy to do), the user's windows account is locked immediately. I assume this is something TC is doing to send the request multiple times, but regardless of why it is happening and is obviously not ideal.
The most ideal solution would simply be able to run the build using the credentials of the user who is kicking it off. So far as I can tell, there is no 'Run As' option, so is there a way for me to retrieve and use the password of the current user logged in to TeamCity, perhaps as a system variable? I've read through the documentation and have not had any luck finding what I need. Maybe there is a way to do this through powershell?
Any ideas/suggestions would be greatly appreciated.
JetBrains is working on https://github.com/JetBrains/teamcity-runas-plugin
I hope it will appear soon

Track code changes to specific functions

Not sure how to even search for this topic so I'm just going to ask. I have a couple places in my code where changes to one function have to be also made to a similar function. Basically the operations in the functions are very similar but the data being worked on is different.
I don't like it but for now that's how it is. My question is anyone knows of a way or a tool that will notify me if a certain function has changed. If I get the notification I know to confirm the changes were made to other function.
Please don't tell me to change my code. I know this isn't ideal and thought has been put into alternatives, but nothing elegant has popped up.
Thanks,
Gunner
Here is an idea I have. Maybe it will set the train of thought...
I can add a special comment in my code for a block that I want to be tracked. The comment will have opening and closing syntax:
my_code.php...
//track-start-1234
[CODE]
//track-end-1234
//track-start-5678
[CODE]
//track-end-5678
I will then have a script that I tell to check a list of files, my_code.php, for now. It will look for the special comment syntax. "1234" will represent a file that holds the last modified code for that function, so 1234.php. If the contents between the comments do not match the code stored in the file then an alert is fired. Also I might add a relationship to the other code so the alert says something like
Code 1234 has changed. Please make sure code 5678 has been updated as well.
I think I can add this script to GIT somehow so it either is part of the core git commands like "push" or maybe just another command I have to run as part of our deployment process. A second option might be adding it to phpstorm's code inspector or something like that.
When the code has been modified and everything is good I will just manually copy the new code into the comparison file. There will not be a ton of updates so this will not be too tedious.
For now this is probably the route I'll go, but any critiques or suggestions are definately welcome.