We need to have the ablity to roll back to a previous version of a published tag, much like the way Google Tag Manager has versioning.
For instance, if we go through the publication authentication, then find that a bug exists and need to drop back to the most recent known working version.
Adobe does not provide any documentation on the subject. Implying the feature does not exist.
What is the correct process to provide roll back?
DTM versioning isn't completely non-existent but I will agree that (IMO) it falls embarrassingly short of the mark compared to other tag managers.
If you have the permissions to see it, you should see a History tab where the other main tabs for your Property are located (e.g. Overview,Rules). This tab will list a history of when and what things were published. From there, you can click the Edit link for an entry and go to the editing page for the entry (e.g. the tool config or a rule).
Up at the top right of the editing page for whatever tool config/rule, etc. is a blue box that shows the current Revision # and date, e.g. Revision 1 Feb 16, 2015. If you click on it, you can select a previous revision from the dropdown (Oddly, it does not autoselect/show the revision you selected when selected from the History page).
When you select a revision from the dropdown, it will show a side-by-side of the revision you selected vs. the current revision, and at the bottom of the page, you can choose which revision to select.
Select the one you want to revert to, and it will now show the editing page but with the selected revision. Save it and Approve/Publish.
Note: DTM currently has no way to roll everything back to a previous revision all at once, so you will need to individually go through each tool, rule, etc. to make sure they are rolled back to the desired revision.
Note: You do not have to go through the History tab to see the revision dropdown for a given tool/rule editing page; you can just navigate to any tool or rule and see it. However, the History tab will help determine which items actually need to be reverted.
Related
After upgrading to IntelliJ IDEA 2021.2.2 Ultimate Edition, I've noticed now that when I go to the Commit pane and select Show Diff on a file in the Default Changelist, that it includes the Unversioned Files in the set of files for the diff comparison.
That is, say I only change one line of code in pom.xml but I also have some un-versioned file, let's say called temp.sql. If I open the Show Diff tool by select Show Diff from pom.xml in the Default Changelist, then the Compare to Next File button is still enabled. Clicking it takes me to temp.sql`, though I have no desire to look at it since I don't even have it in source control.
For example, here I have a Default Changelist with a change to one file in source control, pom.xml. And I have an un-versioned file called temp.sql.
When I select Show Diff on a file in the Default Changlist, it should, in my opinion, and in my previous version of IntelliJ, only show you...the Default Changelist, which is pom.xml. Instead it is giving me pom.xml and temp.sql.
Is this a new feature? It seems like a bug to me. I can't seem to find any documentation for it. I can't find any way to turn it off.
I see there is a "Show unversioned files" check box in the Version Control > Commit section of Preferences, but clicking it doesn't seem to change anything.
If I choose Show Diff on the Default Changelist object, rather than on a file in the Default Changelist, that it restricts navigation to the files in the change list as I want. It's only if I select Show Diff from a file in the Default Changelist that includes all files in all change lists, including un-versioned files.
Ruslan Kuleshov made a comment that this seems like a known issue, https://youtrack.jetbrains.com/issue/IDEA-237528.
New commit tool: don't jump to other changelist's changes
I always review all changes on the current changelist before commit. I focus the diff preview and use F7 to jump through all changes on all files. Previously, when I reached the last file F7 stopped jumping to other files. But after enabling the new tool, when I press F7 on the last changed file on the current changelist, it jumps to the first change on the next changelist. That's a problem since I can begin reviewing changes which are not intended for commiting right now, loosing time, confusing me and even risking to mix files from different changesets.
I had failed to find that issue on https://youtrack.jetbrains.com because I hadn't yet tried having files in source control with changes in a non-default change list. I was only searching YouTrack for the fact that Show Diff now includes un-versioned files.
So, it seems that if you choose Show Diff from a file in a change list, then the diff comparison tool will now include all files in the set of files, regardless which change list they are in and regardless whether they are in source control yet.
I think that this is a bug and have voted for the issue. I encourage others to do so as well.
The CLion Version Control Window (cmd+9 on Mac) is a disaster of overlapping columns and way-too-many-windows. I do, however, prefer their diff presentation to that of GitLab.
Is there a way to remove or collapse columns from at least the Log / branch window? For example, if I wanted to remove author, tag, and date, and just see the branches and their commit messages?
In next major version (2019.2, will be released soon) you can customize VCS Log columns.
From https://blog.jetbrains.com/idea/2019/05/intellij-idea-starts-the-2019-2-early-access-program/
Ability to customize VCS Log columns
You will be able to choose the columns that will be displayed in the VCS Log tab. Simply click on the eye icon, select the ‘Show Columns’ item from the context menu, and then select the columns you want to see: Author, Date, or commit hash.
Is there a way to hide a field in TFS2015? We just needed to hide an unused field since it doesn't server us purpose anymore but we don't want to delete it.
If you just mean you don't want to see the filed in your workitem.
You could delete the control in layout page (Need TFS Power Tools installed).
After this your teams won't be able to see the field in work item page any more.
However this filed still could be used/filtered in work item query. If the hide in your question means this. Unfortunately, no this function for now. You may have to delete the filed instead.
One of the features I love in Visual Studio is that it notes, with color-coded bars in the left margin, which lines I've changed in the program I'm editing.
Is it possible to get something similar in IntelliJ IDEA?
I'm aware that it has a "change markers" feature for files that are under version control, but that's not applicable for me. I've also seen this question which seems to imply that it should be possible, although that guy had the opposite problem.
The gutter marks that you are asking about only appear when you are using a VCS with the project.
IDEA will track local history, but does not show the changes in the gutter (most likely because this local history is temporary and is overwritten when the cache is invalidated or when an upgrade is done).
To view the completely history, right click on the file in the Project view, and under Local History select Show History:
The above image is taken from the online documentation, where it describes the Local History feature:
This section describes how to use Local History, which is your
personal real-time version control system. Local History is
independent of external version control systems and works with the
directories of your project even when they are not under any VCS
control.
If you want local history changes to be shown in the gutter, you can raise this as a feature request at the bug tracker.
How can I access previous checked in versions of workspace repository?
I just seem to be able to compare against the latest changes sets delivered to the stream. Can I also view/compare previous version of a file which has been checked into my repository workspace ?
You can display the history of a file checked in by right-clicking on ("Show History").
From there, in the "History" view, you can right-click on any version and select "Compare to" with any other version (not just the previous one).
As explained in this thread, you can access (open) the content of any older version you want, which gives you the opportunity of replacing the current version with said content, should you want to revert back for just one file.
Rolling back would be a slightly different issue:
If the change set that created the current version contains only that version, then you can replace the current version with the previous version by discarding that change set.
But if that change-set modifies multiple versions, you cannot roll back just that file. Work Item 59688 requests the ability to "split" a change set, so you can move this change into it's own separate change set (and then you could roll back the change to just that file).
Note that the history will be by default the one for that given file done in your repo workspace (checkins) or in your stream (deliver).
The same "show history" done at the Component level (when you right click on a Component, in the "Components" section, and select "Show Repository files", would give the full history (done on any Stream), but wouldn't display the history done on repo workspace (chekins).
Note also that only RTC4.0 has "Checkin history"
This is essentially the history of a file within a change set.
Each time you check-in a file into a change set, the content is stored in the repository. Normally you see only the final version of a file within the change set. But sometimes you want to go back and see what the intermediate versions of the file were. Check-in History is an expansion of the changes made to the file each time it was checked into a change set.