I know that in Author & Deploy draft we can create objects one by one, like data sets, linked service, pipelines etc. But what if you have all those JSONs stored in a single file, why can't you just copy and paste it all to draft and deploy them all in one shot? I know there will be dependency of objects on one another, but that ADF should be able to determine. As of now, copying individual objects one by one and deploying individually is a pain. I know there are programmatic ways to do it easily. But I am specifically asking about Author & Deploy feature.
I would assume the biggest reason they do not handle this is as you mention the dependency checking they would have to perform.
An alternative idea, if you use visual studio you can download Microsoft Azure DataFactory Tools, another link. This will give you a DataFactory project template inside visual studio. You can then store all of your JSON files in the Data Factory project and then "Publish" the project to a DataFactory in azure from visual studio. You also get the benefit of being able to check in the files into source control.
Hope this helps.
Related
Azure Synapse saves all our sql scripts as Json - which is fine - but when I want to look at a changeset for a code review for instance, in azure devops it's very hard to see where all the changes are, because it all ends up in one long row (see picture in link).
Are there any easy fixes for this? Or do I need to copy the before and after into some text editor to find what lines all the changes are on?
Azure Devops/Synapse changeset
There is an extension for DevOps which may help. Install the Synapse artifact native view extension. It only helps in the pull request screen and it reformats a limited list of artifact types like SQL scripts. Hopefully it will help your scenario.
Im happy with the Kanban side of Devops along with dashboards etc. The team is looking to try to roll out multiple projects, but all with the same Epics, Features, Backlog and Tasks etc etc ie a repeatable project. Although im fairly sure the answer is no, is there a way to build out a project with all the work items, and then copy this as a file, and when creating a new one, use this as the basis??
is there a way to build out a project with all the work items, and then copy this as a file, and when creating a new one, use this as the basis??
When you create new projects, you can use the same Process.
For copy the work items as the basis, I suggest that you can export Work items to excel , then when you can import the exported work items to new projects.
For more detailed info, you can refer to this doc: Bulk import or update work items using CSV files
I'm evaluating GitHub as a way to keep under version control and share some excel files containing basically financial models.
The issue I'm facing is this one: I need to share the Release artifacts (a bunch of xlsx files) with people outside GitHub, so I'd like to include the version number in the filename to be sure that, even when the files will be further shared by business people through email or other non-GitHub means, that information won't be lost.
Is there a way to rename the artifacts automatically? GitHub Actions seemed to be the right way to address this thing, but unfortunately they're still unavailable on the Enterprise Server my company is using (v 2.19.13, I don't have any administrative access to it, btw), and adding some CI toolchain just to rename some files is probably too much.
Thank you in advance for any response!
Michele
I am working on a requirement where I have to generate the load test report using artillery tool and publish the report stats into our Azure DevOps pipeline.
Artillery generates the report into html format and same I want to show into Azure DevOps pipeline. How can i do it?
I know Azure pipeline supports only Junit reports but still is there a way I can publish the artillery HTML report?
If without any plugin or extension support, until now, the HTML report would not be compiled successfully, then map corresponding attributes into pipeline directly. As you know, until now, it only support the format: TRX, JUnit, NUnit2, NUnit3, xUnit2, CTest.
As work around, you can define your customized extension. With this extension, add one new section into pipeline first, use task to publish this HTML report into this new section, then map and display its attributes into this section.
There has a sample extension can for you refer to: vsts-publish-html-artifact.
Note:
Since this extension programmed 4 years ago and no longer maintained now, also most of our official doc content has been updated with the latest grammar, such as categories and etc. I modify johnwalley's script, thus you can directly use it now. Due to my github repository: Merlin-Extension.
You can also extend the functionality of this extension by adding scripts based on your individual needs. Refer to this doc for extension script written: https://learn.microsoft.com/en-us/azure/devops/extend/get-started/node?view=azure-devops
The work around I provide above can only consider as a temporarily method. Since Xml reports are too basic and html is more useful in many cases/ tools, I also looking forward to the feature for HTML report Published in pipeline can be expanded into Azure Devops.
Here has a feature suggestion ticket exists on our official forum. We can vote and comment it there to make it has a broad community impact, also will improve the Azure Devops experience. Thus our product group will consider to take this feature into our develop roadmap.
Management would like to migrate all teams using Azure DevOps (VSTS) to a single project to make reporting and work roll-ups easier. if this is done can the individual teams still utilize templates customized to their specific needs or would they need to use the default template for the project.
Thanks
We are being asked to migrate to a "standard" company project but don't know if we will be able to have customization for our process
No. One team project has one process template. You can customize that process template however you wish, of course.
What you could do is create an inherited process in order to make your customizations, and change every Team Project to that Process.
You have to take into account that the customizations you have made to your Team Project could be affected when you change to a inherited process.
Test carefully with some test Team Projects before.