I have started using Bluemix devops insights service available as part of Bluemix toolchain. I am not able to see any documentation on integration of SonarQube with the tool. The one available in the service is a bit misleading as it only talks about UT, code cov. & FVT but not on how to publish SonarQube static code analysis reports to Devops insight, can someone pl. help?
Check the documentation pages on Publishing Test Results. If you're using DevOps Pipelines, go into the scripts for your builds, and integrate in the idra command as shown in the example. Also spend some time reading that npm package, which goes over how to do this within a Continuous delivery pipeline, or from the CLI.
Related
I am following the steps outlined here. I am using the Deploy to Azure Extension
https://learn.microsoft.com/en-us/azure/devops/pipelines/targets/deploy-to-azure-vscode?view=azure-devops#github--azure-pipelines
I have done the following steps.
I have managed to create a simple react app and then got the GitHub + GitHub Actions portion to work no problem.
Now, I want to get GitHub Plus Azure Pipeline to work. So, I deleted the GitHub Actions/Workflow files, and starting over with the CICD setup.
Next, I have enabled Use Azure Pipelines for GitHub in the extension.
Then, as per the steps/pictures outlined in the above microsoft documentation link, I have begun the configure CICD option from the command palette.
Selected the Visual Studio Subscription
Selected the target web app
Now, at this point, as per the linked tutorial, it is supposed to ask me to choose a azure devops organization, so that the azure pipeline YAML file can kick in. This step never happens.
instead, VS Code will proceed to generate a GitHub Actions Workflow just as it did before.
What should I do to the GitHub to Azure Pipeline working from this extension?
Update 1
In case anyone is curious, I have raised a issue on the visual studio community forum. You can find that here
https://developercommunity.visualstudio.com/content/problem/1182952/github-azure-pipelines-falls-back-to-github-github.html
As of now, there is an ongoing discussion but no solution yet.
You can try reinstalling Deploy to Azure Extension and enable Use Azure Pipelines for GitHub, and then configure CI/CD option again. If the issue persists, you can report this issue here.
You can create a pipeline directly in your azure devops project. Check out below tutorial
Build, test, and deploy JavaScript and Node.js apps
You will also need to create an Azure Resource Manager service connection to deploy to your azure resource from azure devops pipeline.
Deploy an Azure Web App (Linux)
I am doing some research for Powerapps integration with Azure DevOps.
However there is limitated information for it.
It is possible to integrate powerapps inside a Task for AzureDevops?
Based on, that we have a .zip file with the Powerapp, and we want to create a Build and Release/Deploy for several environments.
Thank You.
It is possible to integrate powerapps inside a Task for AzureDevops?
Yes it is.
You can leverage the Solution concept of the Microsoft Power Platform and the Power Apps BuildTools (preview) extension for Azure DevOps.
Update 11/2020: This is now GA and called Power Platform Build Tools
I've written a complete step-by-step guide on this topic:
A Continuous Delivery Approach for No-Code Solutions in Microsoft’s Power Platform
Bottom line:
With this build tool, you can automatically check-in a Solution into source control and deploy it using a continuous delivery approach with the help of Azure DevOps. See the screenshot for a sample configuration of the Export and Import Solution Task.
It works for everything you can organize inside a Solution, e.g.:
Power Apps
Power Automate Flows
AI Builder Models
Common Data Service Entities
It is possible to integrate powerapps inside a Task for AzureDevops?
I am afraid there is no such Task integrate powerapps for AzureDevops at this moment.
If you want to integrate powerapps with azure devops, you can follow the guide step by step:
Microsoft Teams – Integration with Visual Studio Team Services using PowerApps.
Besides, AFAIK, PowerApps should not be "Build/Deployed" through Azure Devops.
When you are developing with PowerApps, there is no way to do Source
Control. There are no source files. The only artifact you can version
control is the .zip file that you can export.
And
In PowerApps, you don’t have to build your code. Any change you make
to the application is live for you to test it. In that way it is very
productive. To publish the application you just click on the publish
button and it is live.
Check this great blog: PowerApps From A DevOps Perspective for some more details.
Hope this helps.
Solutions are a way to package your components in a single zip file and use Powerapps build tools to import your solution on to a different environment or tenant.
It is still a an improvement from manually importing each app or environment variable and then import it on to target system, but it lacks what we call as automation of deployment.
To provide an eg, I will explain what I have done, and what still constitutes of a manual task:
I created an enterprise level app using powerapp canvas model. My app consumes data from around 20 APIs. These API calls are implemented in power automate.
We have 4 environments, dev, sit, uat and prod. Now I cant keep on importing flows in each environment and change their api URLs to point to the deployed environment. So I used environment variables for each environment which stores api URLs for each environment. This can be done under solution.
Under the same solution, I added my app. So now my solution has 2 things, my app and the environment variable which consists of api URLs.
I then use powerapps build tools to move this solution from dev to sit.
Steps: use build tools tasks to perform the following
Export solution
Unpack it in git
Pack it
Import the solution.
This successfully moves my solution to sit.
But the solution environment variable still points to the dev url.
So I have to override environment variables to store sit URLs.
This manual intervention to edit environment variable is as good as doing all the tasks manually.
This was the case when PowerApps was first announced; however, this is no longer the case.
While it is technically true that there is no actual code that would be managed and deployed with a PowerApp or Flow but that doesn't mean that you can not use the power of Azure DevOps. Additionally, when creating a PowerApp / flow you would also be creating entities and even Model Driven apps - and these uses solutions - which naturally work well to deplooy within Azure DevOps.
Microsoft is building out this whole construct to enable all these to deploy...
While the whole incorporation of PowerApps and flows into Solutions is not fully baked yet - they are targeting to have this ready around the October time frame this year.
We have been talking to Microsoft about also enabling PowerApps and flows to follow the same expansion that solutions do so that they can take advantage of the full branching strategy.
So even though you would be simply exporting out zip files into your repo - you can still take advantage of the full devops pipeline which is highly recommended.
Use this component, it still on preview mode but is working fine on my side
https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerApps-BuildTools
Summary
Recently migrated PB126 apps to PB2017 and changed source control to Azure DevOps Git.
Now, I'd like to integrate Azure DevOps CI/CD Build Pipeline to the app dev life-cycle.
jenkins
I know it's feasible to configure jenkins CI server so it builds PB2017 projects.
Continuous Integration with PowerBuilder 2017, Bonobo Git and Jenkins
My problem here's I can't get it to work on a local Docker container and make it accessible to the outside world (Internet) so Azure DevOps can trigger its build action. Supposedly, it's a Docker for Windows thing which Docker handles differently from the Linux-based Docker.
Azure DevOps Pipeline
As per this link, Azure Pipelines is the CI/CD solution for any language, any platform, any cloud, it says any language, which makes me believe it's feasible to build PB2017 projects using Azure DevOps Pipelines.
The fact is that I'm totally new to CI/CD in terms of implementing it myself. I've experienced it in many projects where I wasn't responsible to implement it. Now I am. I've been on it since a few days now, and I do want it to work.
Any help appreciated.
The Appeon offical user forum: https://community.appeon.com/index.php/qna/q-a
The tool we are trying to integrate with vsts(Azure DevOps) is Cognos Framework Manager. Is Cognos Framework Manager anyway compatible to integrate with vsts. In what way will i be able to acheive this. I was just trying to get ideas from PowerBI to understand workflow of BI projects. But its quite different from Cognos Framework Manager. This is in regards to testing the workflow of Cognos projects & their CI/CD pipeline.
One of FM's selling points used to be it's native integration with source control but that feature was taken out when it was no longer in a competitors feature list.
Having said that, Framework manager is just a bunch of files. Just commit those files to a DevOps github repository using for example git command line.
With regards to automatic deployment from DevOps to your environment, you'd need to work out how to use the FM API. Some info here but I'm not going to take the time to decipher it
https://www.ibm.com/support/knowledgecenter/en/SSEP7J_10.2.2/com.ibm.swg.ba.cognos.dg_fm_sdk.10.2.2.doc/c_sdk_overview.html
In the very least you'd need to install FM in your DevOps deployment agent
We are used to running Java development projects, typically using Atlassian products including Stash. We're now trying to use Bluemix Devops Services instead.
One limitation we have found is that you cannot create Pull Requests, meaning we can't review changes to source code before it is merged.
Is this the case? And what do others do for source code review workflow in Bluemix Devops?
At this time no you can not do code reviews through Bluemix. You can however attached the DevOps pipeline to a Github project though.