May be very simple question for you guys. But I just want to clear my doubt.
I have seen option "Enable Version Control" while creating repository service. Can somebody tell me, what is the use of version control there?
Thanks in advance.
Nothing tricky here - if you choose this option, the repository will support versioning for all the objects, e.g. reusable transformations, mappings, sessions, workflows. You will have to check out the objects to edit them and then check them in, you will be able to view object's history, compare the revisions, revert changes, etc.
Related
Often during development designs get updated and we want to avoid this. Interesting how other people freeze figma version and whether it's possible. We need somekind of snapshot link which can't be changed neither by designers nor by developers.
when you give the link, you have the options to set the permission. change permisiion to view only for other users that see your screens created in Figma.
Currently, there is no such way to share the file version wise. What I do in this situation, export the Figma document & rename it something like "app_design_v1.0_02_feb.fig".
And then share the file with devs and other stakeholders. Telling them to import the file on their own.
Another solution is to use "Pages". Though it's not very handy for large design projects. You can name your pages as "app_design_v1","app_design_v2" etc. So that everyone knows what they have on which version.
What is a good learning resource for TFS and how to use TFS with Visual Studio?
Specifically, I want to know two things.
Exactly what are the step-by-steps procedures of checking in code. I know that I am required to do a code review. So, after the code review is done by a peer, I understand that this is not enough and the original developer has to click to do something to submit the code into the TFS system. I mean, I want to know precisely what buttons to click on.
I also want to know how to use Visual Studio to look up the actual version. How do I determine the details of what is already checked in?
There are many blogs videos in google. If you want a full detail resource, suggest you directly take a look at our official doc here -- Azure DevOps Server Documentation
A suggested learn order for your reference:
Installation (you could skip this if your company already done this)--
Code -- Build&Release -- Packages-- Test-- Work-- Analysis-- Admin
Tool
TFS supports two types of version control: Git and Team Foundation Version Control (TFVC). One centralized and one distributed. As for which version control system should you use, you could take a look at this thread: Choosing the right version control for your project
For your case, you could easy check the history in server side. It's called changeset in TFVC and commit in Git.
For example, when you check in your changes, they are stored on the server as a changeset. Changesets contain the history of each item in version control.
You can view a changeset to see what the exact file changes were, discover the owner's comments, find linked work items, and see if any policy warnings were triggered.
The same as Git, actually you could find the answer for both question 1&2 in Code part. Hope it helps.
I am new to apache NIFI. I was kind of wondering where is the save button. I tried a sample from a tutorial that I saw on youtube. I would like to save all the processors that I created for future reference. I don't see any save button. Is is possible to save my work open later.? Or open in another machine.?
Please Help.
Apache NiFi automatically saves your flow for you. The flow configuration file is stored in ./conf/flow.xml.gz by default. NiFi also maintains an archive of previous versions in ./conf/archive. See the Core Properties settings for changing these settings. It is possible to backup and restore the flow configuration through these files.
Apache NiFi also has a Templates feature that makes it easy to save a selection from your flow, export it from the UI, and share it with other NiFi installations. Templates may be a closer approximation of a "save" button.
The Apache Nifi Registry is another option. You can version processor groups, commit changes to the registry, revert back, add comments, etc. I see it as similar to version control such as Git. It's helpful in collaborative settings as well as promoting changes from development to production.
Does anyone know of a way to view entire source of a build via TeamCity - Jenkins has a nice feature whereby you can get to the workspace really easily. Hope this is possible out-of-the-box or via some other method.
Thanks.
I don't know if there is a way to directly get to the source through the Team City interface, but I do know that as you inspect problems, you can get a stack dump. It wouldn't surprise me if you can.
But, I use a different work flow instead, since the CI's working environment should only be a checkout from your source. Therefore if you have your revision information, you can view the source from your repository:
Use the %build.vcs.number.1% property in your "Build Number Format" field; this will place the revision ID into the build's name. You can then view that source exactly in the repository.
You can configure where the checkouts go, but either way you can navigate to "Team City's" working directory if you have access to that box.
You can get the temporary WC directory through the %system.teamcity.build.checkoutDir% property if you want to see the directory on disk where the checkouts etc. happened at.
see this TeamCity article for more information on changing it.
You can turn on VCS Labeling under the VCS Settings, where a build is auto-labeled in your repository. That naming convention is also configurable.
see this blog for more information.
Hope that helps.
I am using the embedded version of RavenDb and have put the physical database in the App_Data folder, based on this article http://msdn.microsoft.com/en-us/magazine/hh547101.aspx. My first question is, what portions of the db need to be committed to the SCM repo?
The second question is, My workflow is such that I'll also use web publishing directly from my laptop, are there any concerns using this methodology?
Thank you,
Stephen
There's no need to put your database under source-control since your documents have no particular schema. They will be created on the fly when serialized into json. So as long as you check in your C# classes, you're all fine.
First, are you aware that RavenDB uses the AGPL license? This license requires that you publish your project as open source if you are not paying for a commercial license.
They do offer free licensing in some cases but you must contact them and get a license. Check their licensing page for more details.
Second, You proably shouldn't check your database into your SCM. Databases change frequently, and SCM is designed for files that not constantly changing. You might want to check in your database schema as it changes... but not the database itself.
Regarding your second question, i'm not sure what concerns you're talking about. Can you be more clear about what your concerns are?