When I add a new Build Definition in Azure Pipelines the GUI is no longer available. The YAML tool appears.
My team needs to gradually move over to YAML. I know the GUI works for existing pipelines but we would like to create new pipelines with the GUI too.
N/A
Click on the Use the classic editor link when creating a new pipeline:
Related
I am trying to use Azure Function class to generate a template for AzureQueueTrigger function in IntelliJ. However, when I click on the package -> new -> Azure Function Class:
I see templates for only three types of triggers:
Blob trigger and Queue trigger options are missing. However when I create a new project, I see all the 5 trigger options for azure functions.
Any one else is facing this issue? Kindly let me know if any one has found a solution (to see all the 5 options to add the desired template in an existing project) for this issue?
My environment:
Windows 11
IntelliJ IDEA 2022.3.1 (Community Edition)
Azure toolkit plugin version: 3.73.0-2022.3
In IntelliJ IDE, I have experienced the Same that cannot see more than 3 types of Triggers when adding the additional Azure Function Class to the Java Azure Functions Project but can be able to see most of the trigger types in IntelliJ IDE.
For the temporary workaround/fix, you can use VS Code where I experienced same but able to see all types of triggers and add them to existing Java Azure Functions Projects by using template filter field:
Regarding the IntelliJ IDE Issue, I have raised a ticket #105223 in the official Issues Tracking GitHub Repository of the Azure Java Functions Project - IntelliJ IDE Development.
Is it possible to set the TestCafé Studio so that after a test run an automatic report in the desired format (for me e.g. Xunit) is exported?
The summarized reports that can be manually exported from the view would be great for my DevOps purposes if they could somehow be automatically exported after the test was completed! The report.json file in the Test-CaféStudio directory is unfortunately less helpful for my purposes.
I have already been told that it is not possible to call the software via cmd in another question. But I think in the context of the DevOps tests it should at least be possible to create automatic reports with it.
There's no automatic export option. However, you can take any existing reporter plug-in (they are all open-source and hosted on Github) and create your own custom reporter that will do what you want. TestCafe Studio will find your custom reporter and use it.
Refer to the Reporter Plugin topic to learn how to create your own reporter plug-in.
I am moving from "XAML" builds to DevOps YAML builds and trying to replicate what I had in TFS 2012. In the XAML build I had several "Solutions" in the "Items to build" and this build was triggered on any checkin. From what I can tell the Pipeline was designed to build a single solution. I've "unlinked" the Pipeline from a single solution and was planning on adding additional Build Tasks for each solution to build. Is this the proper way? If this is not the best way to do this I'm open to suggestions. Using Azure DevOps 2019 and Visual Studio 2017.
Theoretically, you are able to do this. If you manage to do this with if's or something like that, you have to add multiple tasks - to each solution. You have to deal with triggers, finally your yaml file would be unmaintainable. YAML script would be huge and difficult to understand the dependencies.
I would suggest you just use a single file for each solution build. You are able to have many of .yml files all targeting different solutions.
Multiple YAML build pipelines in Azure DevOps
Can I have multiple build pipelines for the same repository?
Besides, since you are moving from "XAML" and not familiar with this build process. You can always use the Designer approach and pull out the system generated YAML if you are new to the system. Here's the YAML schema reference that might help you!!!
I have an MVC 5 application we're moving from on-premise to the Azure cloud. Currently, we have several publish profiles, one per environment, which we determine using a powershell script. One of our goals is to make the building scripts and infrastructure as simple as possible, so I was wondering if I could make it so that using only my appveyor.yml file I could set the publish profile to be used, so
Is there a way to set the publish profile from the appveyor.yml file?
If not what are my choices?
You can run your PowerShell script as part of desired build step in pipeline. It is possible can run commands right from YAML file or UI or check-in your PowerShell script into repository and run .ps1 file. You might consider using secure variables to avoid checking in things like connection strings into repo in clear text.
However this custom script/profiles approach will not allow you to use built-in WAP artifacts packaging and you will be also needed to use custom script instead of automatic MSBuild mode. Which is OK, but a little bit more scripting. Also you will be needed to publish artifacts so it will be available for deployment.
Maybe easier option is to let AppVeyor do all build and WAP artifacts packaging/publishing automatically, and then use built-in Web Deployment with Web Deploy parametrization instead of multiple publishing profiles.
But if you decide to go with custom scripts, and multiple publishing profiles, you still can use use built-in Web Deployment with artifacts created by your scripts.
I want to know how we can create different build like distribution, debug, release or development build using titanium studio.
Can we create custom build profile such that each of my build profile have different settings like if resource filters are applied on my project.
I don't think something similar exist, you need to build a custom tool. What about using git and its branches? Or write a script with a list of all your files and rename all the unnecessary with a ".disabled" extension?
I like scripting and automating things, if you want we can create some kind of project on github. :)