OPM 10.2 Subversion Source Control - Version History Error

I installed OPM 10.2.0.110 after installing subversion and everything worked running through the first time, but now when trying to see the version history I am getting the error message:
info failed (Subcommand 'info' doesn't accept option '-v[--verbose]"Type 'svn help info' for usage.)
Any ideas as to what is causing this problem?

Hi Andrew,
I'm hitting the same problem with my local subversion install and OPM10.2
I'm rocking version 1.6.15 of the SVN for Win32 available here http://sourceforge.net/projects/win32svn/
trace from console:
C:\Documents and Settings\phjones>svnserve --version
svnserve, version 1.6.15 (r1038135)
compiled Dec 17 2010, 09:05:59
Copyright (C) 2000-2009 CollabNet.
Subversion is open source software, see http://subversion.apache.org/
This product includes software developed by CollabNet (http://www.Collab.Net/).
The following repository back-end (FS) modules are available:
* fs_base : Module for working with a Berkeley DB repository.
* fs_fs : Module for working with a plain file (FSFS) repository.
Cyrus SASL authentication is available.
also I tried checking 'svn help info' and got this (no verbose option):
C:\Documents and Settings\phjones>svn help info
info: Display information about a local or remote item.
usage: info [TARGET[@REV]...]
Print information about each TARGET (default: '.').
TARGET may be either a working-copy path or URL. If specified, REV
determines in which revision the target is first looked up.
Valid options:
-r [--revision] ARG : ARG (some commands also take ARG1:ARG2 range)
A revision argument can be one of:
NUMBER revision number
'{' DATE '}' revision at start of the date
'HEAD' latest in repository
'BASE' base rev of item's working copy
'COMMITTED' last commit at or before BASE
'PREV' revision just before COMMITTED
-R [--recursive] : descend recursively, same as --depth=infinity
--depth ARG              : limit operation by depth ARG ('empty', 'files',
'immediates', or 'infinity')
--targets ARG            : pass contents of file ARG as additional args
--incremental            : give output suitable for concatenation
--xml                    : output in XML
--changelist ARG         : operate only on members of changelist ARG
[aliases: --cl]
Global options:
--username ARG           : specify a username ARG
--password ARG           : specify a password ARG
--no-auth-cache          : do not cache authentication tokens
--non-interactive        : do no interactive prompting
--trust-server-cert      : accept unknown SSL server certificates without
prompting (but only with '--non-interactive')
--config-dir ARG         : read user configuration files from directory ARG
--config-option ARG      : set user configuration option in the format:
FILE:SECTION:OPTION=[VALUE]
For example:
servers:global:http-library=serf
Thanks,
P.

Similar Messages

  • Error when trying to add a project to Subversion source control

    When trying to add a project to source control from within the OPM 10 studio (File - Source Control - Add Project to Source Control), the following error occurs:
    "There was a problem accessing the source control system, probably due to network or contention issues. A retry is recommended."
    This has been tried with Subversion versions 1.6.2, 1.6.5 and 1.6.6, with local repositories and repositories on a Apache webserver.
    Once the project has been added to a repository, by using TortoiseSVN for example, working with source control is no problem.
    Does anyone have a clue what the problem (and a solution) might be?
    Thanks,
    Theo.

    Hi,
    Davin mentioned:
    This appears to be an issue with the source control integration. We are looking into it.I am using OPM 10.0.1.14
    The OPM help on collaborating mentions:
    Open a rulebase project from source control
    To open an existing Oracle Policy Modeling project from a source control repository:
    In Oracle Policy Modeling, select File | Source Control | Open Existing Project from Source Control. When I open the File menu I do not see the "Source Control" at all.
    Is this caused by an installation error or part of the "issue with the source control integration" ?
    Please let me know if I'm the only one experiencing this problem ....
    Thankx,
    Paul

  • APEX Version/Source control

    Hi,
    I would like to know how other people are managing this. We have developed our own way which works 99% of the time however there are some flaws.
    We require that more than one user be working on an application at a time and that these different pages can be released to production at different times.
    We have some pretty large applications, some business critical.
    1) We export the full application into our CVS application
    2) We export each page individually and assign module numbers as we do with apps forms etc
    3) Initially the full application is released to prod
    4) Any subsequent page changes are done to the page export and that page only is released. The revision is increased on that page module.
    5) If any changes to shared components are made then the full application is released.
    All updates are stored in packages which we manage as per our normal apps packages without any problems. Our problems are with apex applications.
    Let's say user A has exported page 1 of an application and is working on a large change.
    User B is also working on a very small change which involves adding a new item to a list.
    User B wishes to release his change but cannot do so at page level because of the shared component - he must release either full app or do a separate export for that component.
    He cannot release the full app because user A is still using it.
    The only thing he can do is do an export of the components and then import that. This is then not version controlled. It is not acceptable for us to have to export and manage every single component individually (I know you can do them as one whole but then if two users are modifying shared components then the issue arises again!)
    There is always a mis-match between the application full export and the pages. If we ever had to recover an app, our strategy is to install the full app and then the individual pages. This isn't ideal however so long as we keep things up to date then we have to accept it.
    Does anyone have any better procedures than this?? With APEX becoming more and more popular then I believe it needs to become a little more formal in this area. Or perhaps I am just missing something?
    I've read the thread Source/version control with APEX? but it doesn't really relate to the issue above.

    Hello Chris,
    I'm not sure how you organized your project, but a typical APEX project for me has different components:
    - PL/SQL where all business logic is in
    - External JavaScript files to do some client side things
    - External CSS files to handle the look and feel
    - APEX application(s)
    So for all of the above you want source control. We use Subversion. For the first three (plsql, javascript, css) I guess it's trivial how do this as they are just files.
    For APEX you can export your application every night (and even split it into different components if you want). So that gives you one or more files as well which can be loaded in Subversion.
    If you want to do team development in APEX; we use following features:
    - Locking of Page
    - Build Options
    - Entering Comments
    If it's a very big project you might want to split your APEX application in multiple ones which can work together (same Authentication scheme, same Theme etc. by Publish and Subscribe option).
    APEX itself is also build in APEX, and they use different applications as well, but you don't see it in APEX itself, you just see it by the changing APP number in the url.
    I'm not sure how familiar you are with all of the above, but this is roughly the way we do it.
    Hope that helps and give you a clearer view.
    Regards,
    Dimitri
    http://dgielis.blogspot.com/
    http://www.apex-evangelists.com/

  • Versioning/Source Control

    What tool are people using to version/source control changes made to the OBIA and what components are being source controlled?
    We are setting up an OBI EE+ installation and have bought a number of the OBI Applicationes eg Financial Analytics etc.
    I am wondering whether people are using a single tool to source control all the components from ETL, DAC, Presentation Layer etc or whether people are using separate source control tools eg Informatica versioning for ETL, another tool for DAC, Presentation etc.

    This is a useful link: http://www.rittmanmead.com/2009/01/22/simple-version-control-for-obiee-using-subversion-visualsvn-server-and-tortoisesvn/
    You should be thinking about WHY you are version controlling. If it's to have a consistent copy of your BI environment at a given point in time (and I'd suggest that's a good idea) then splitting version control throughout the tools is not such a good idea and you should be looking to something like SVN to centralise version control.
    The trouble you have is that several files are binary so cannot be merged by the version control tool. There's no silver bullet for this problem, or if there is I'd love to hear about it!

  • Is there any plans to have subversion (SVN) source control support in LabVIEW 8?

    I was wondering if there were any plans or any workarounds to tie into a subversion (SVN) revision system control system with the integrated LabVIEW 8 source control.
    We are currently using rev. 1.2.3 SVN.
    Please advise.

    Search the forums here or on Lava User Group.
    Basically LabVIEW for Windows makes use of the Microsoft SCC API for
    all version control activities and any source code control system with
    such an interface can be used. The SCC API is treated by Microsoft as a
    trade secret and you can't really get the specs without signing an NDA.
    So there is not likely to be an Open Source SubVersion interface to be
    out there soon but there is a company selling an SCC provider for
    SubVersion PushOK SubVersion Proxy.
    Rolf Kalbermatter
    Message Edited by rolfk on 12-21-2005 11:14 AM
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Getting Error on viewing subversion version history on file

    I'm using SQL Dev Version 2.1.1.64.39 with version control to an existing subversion-server in the LAN.
    Doing an SVN Update or Commit in SQL Developer works fine!
    Working in file system with Windows Explorer and TortoiseSVN works fine, too.
    But when I want to view the history of an file in SQL Developer I got the error:
    Unable to retrieve version history for D:\Test\bla.sql
    with the exception Stack:
    org.tigris.subversion.svnclientadapter.SVNClientException: org.tigris.subversion.javahl.ClientException: svn: authentication cancelled
         at org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.getLogMessages(AbstractJhlClientAdapter.java:2205)
         at org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.getLogMessages(AbstractJhlClientAdapter.java:2225)
         at org.tigris.subversion.svnclientadapter.AbstractClientAdapter.getLogMessages(AbstractClientAdapter.java:194)
         at org.tigris.subversion.svnclientadapter.AbstractClientAdapter.getLogMessages(AbstractClientAdapter.java:139)
         at oracle.jdevimpl.vcs.svn.history.SVNHistoryEntryProducer.produceEntries(SVNHistoryEntryProducer.java:79)
         at oracle.jdevimpl.vcs.svn.history.SVNHistoryEntryProducer.produceEntries(SVNHistoryEntryProducer.java:52)
         at oracle.jdevimpl.vcs.generic.GenericHistoryProvider.getEntries(GenericHistoryProvider.java:142)
         at oracle.jdeveloper.history.HistoryManager.buildModel(HistoryManager.java:348)
         at oracle.jdevimpl.history.HistoryViewer$7.doInBackground(HistoryViewer.java:499)
         at oracle.jdevimpl.history.HistoryViewer$7.doInBackground(HistoryViewer.java:495)
         at javax.swing.SwingWorker$1.call(SwingWorker.java:278)
         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
         at javax.swing.SwingWorker.run(SwingWorker.java:317)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
         at java.lang.Thread.run(Thread.java:619)
    Caused by: org.tigris.subversion.javahl.ClientException: svn: authentication cancelled
         at org.tigris.subversion.javahl.JavaHLObjectFactory.throwException(JavaHLObjectFactory.java:777)
         at org.tmatesoft.svn.core.javahl.SVNClientImpl.throwException(SVNClientImpl.java:1850)
         at org.tmatesoft.svn.core.javahl.SVNClientImpl.logMessages(SVNClientImpl.java:470)
         at org.tmatesoft.svn.core.javahl.SVNClientImpl.logMessages(SVNClientImpl.java:430)
         at org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.getLogMessages(AbstractJhlClientAdapter.java:2195)
         ... 16 more
    Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: authentication cancelled
         at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:60)
         at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
         at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.findStartingProperties(DAVUtil.java:126)
         at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getBaselineProperties(DAVUtil.java:216)
         at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getBaselineInfo(DAVUtil.java:174)
         at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:182)
         at org.tmatesoft.svn.core.wc.SVNBasicClient.getRevisionNumber(SVNBasicClient.java:482)
         at org.tmatesoft.svn.core.wc.SVNBasicClient.getLocations(SVNBasicClient.java:851)
         at org.tmatesoft.svn.core.wc.SVNBasicClient.createRepository(SVNBasicClient.java:534)
         at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:716)
         at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:532)
         at org.tmatesoft.svn.core.javahl.SVNClientImpl.logMessages(SVNClientImpl.java:462)
         ... 18 more

    version 2.1.0.63 (main build 63.73) also has the same problem
    Wayne
    -- it appears to be some type of authentication error. When we turn off authentication we can view the history with no problems. Possibly same problem as
    Re: EA3: Versioning : Subversion - Commit ?
    Edited by: wcoleku on Mar 26, 2010 5:00 PM
    Our version of subversion is 1.4.2
    USE AT OWN RISK
    tried the following fix and it appears that it worked (haven't fully tested yet)
    downloaded and installed jdeveloper Studio 11.1.1.2.0
    make a copy of files before trying
    copied C:\oracle\Middleware\jdeveloper\jdev\extensions\oracle.jdeveloper.subversion\*.jar files to C:\sqldeveloper64-2.1.1.64.39\sqldeveloper\jdev\extensions\oracle.jdeveloper.subversion
    copied C:\oracle\Middleware\jdeveloper\jdev\extensions\oracle.jdeveloper.subversion.jar to C:\sqldeveloper64-2.1.1.64.39\sqldeveloper\jdev\extensions\
    Edited by: wcoleku on Mar 26, 2010 5:35 PM

  • Version Source Control

    Hi,
    We're planning to develop applications with APEX in a team environment. I'm wondering what is the "best practice" for Version or Source Control? Note, we're going to use version 3.0
    I do know about the java export tool which is very handy when you are a single developer. However, it does present a problem when working in a team. If they're multiple people working on an application, development will need to be stopped when an application moves from dev -> test -> prod so that testing and fixes can be performed for that specific version.
    Though not ideal, I did try to export a page from one application into another and got an error stating: "This page was exported from a different application or from an application in different workspace. Page cannot be installed in this application"
    Any ideas would be greatly appreciated. Please note that I'm not looking for help with tools such as cvs and svn.
    Thank you,
    Martin

    I just tested 2 cases here's my results:
    - Export from DevWS App 100, P3
    - Change references from 100 to 102
    - Import to DevWS App 102
    - I get the following error message:
    ORA-20001: GET_BLOCK Error. ORA-20001: Execution of the statement was unsuccessful. ORA-00001: unique constraint (FLOWS_030000.WWV_FLOW_PAGE_PLUGS_PK) violated <pre>declare s varchar2(32767) := null; l_clob clob; l_length number := 1; begin s := null; wwv_flow_api.create_page_plug ( p_id=&gt; 1054801262233595 + wwv_flow_api.g_id_offset, p_flow_id=&gt; wwv_flow.g_flow_id, p_page_id=&gt; 3, p_plug_name=&gt; 'Form 1', p_region_name=&gt;'', p_plug_template=&gt;
    TEST 2
    - Export from DevWS App 100, P3
    - Change references from 100 to 104
    - Import to TestWS App 104
    - I get the following error message: This page was exported from a different application or from an application in different workspace. Page cannot be installed in this application.
    Martin

  • Source Control 3.1 : History and change reports

    Robo Source Control 3.1 : History and change reports are allways empty. I only see titles on the file report.htm (using IE9 or Google Chrome).

    What I was saying in your other post was not necessarily that it will work differently on a 64 bit machine, simply that there were known issues with a 64 bit machine that are referenced in
    http://blogs.adobe.com/techcomm/2011/12/robohelp-9-0-2-is-now-available.html
    It may be the fix referred to there is simply to make it work the same way as on a 32 bit machine and clearly that is giving you grief. Only way way to find out.
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • Robohelp 8 integration via the Microsoft Source Control API (Perforce/Subversion)

    Robohelp 8 claims to support the Micorsoft Source Control API, which allows third party source control systems to be used with it. Unfortunately, it seems to work great with Subversion (third party plug-in required) and Perforce until we rename a file. Then it fails. For Perforce, it fails with no error. The file just doesn't get renamed. For Subversion, we get an ugly error from the plug-in, but after consulting with the plug-in's developers (PushOK) and given the same problem in Perforce, I think this is an RH8 bug.
    Has anyone else seen this, or does anyone else have experience with this?
    Thanks in advance!
    Jason

    was routing problem

  • How to move a project in source control

    I messed up & need your advice. I put my first RH project, "core", at the root level of my VSS project:
    $
    rh_projects
       core
    Unfortunately, my "core" RH project is now a child project in a merged help system.  I also put the "parent" project at the root level, so now it looks like this in VSS:
    $
      rh_projects
         core
         parent
    ... but my VSS folder structure really should reflect my real folder structure, so that other writers can use the same structure when they open the project.
    So I want to change my VSS folder structure to this:
    $
      rh_projects
        parent
        projects
           core
    So here's my question (finally!):  what's the best way to move the core project in VSS?
    * In RH, remove the core project from source control, then put it back under source control at the new folder level, OR
    * In VSS, add the new "projects" folder structure and move the "core" folder underneath it, then open it in RH as a "new" project?
    thanks,
    Jenny

    Either way should work.
    Method 1 will ensure the source control path in the RH files points to the correct VSS location
    Method 2 will keep your change history if this is important to you. However, it is trickier to do.  Zip up a copy of your project just in case.
    Method 2 details
    If you use this method, you need to manually change the VSS path listed in the .xpj file.
    Look for something similar to the following. It may be different depending on your versions of RH and VSS. The below is from RH6 and VSS2005. '[' represents and angle bracket.
    [matchedpair]
               [name]vc::cookie[/name]
               [value]"$/Dev/Source/Documentation/MyProject", ZTZQBAAA[/value]
    [/matchedpair]
    You will need to change the [value] line: change the path beginning with $ to your project location.
    I don't think you need to change the 8 character code after the comma, but I was never quite sure what it meant. If want to be safe or things don't work, create a temporary new project and add it to VSS at the same level as your project. Copy the bit in green from the temp project and paste it into your real one. Delete the temp project.
    Also make sure you delete the .cpd file before opening the project as this sometimes remembers the old location.
    HTH,
    Amebr
    Message was edited by: Amebr
    Couldn't get colours to work so changed to words. Hopefully it's clear enough.

  • Looking For Guidance: Best Practices for Source Control of Database Assets

    Database Version: 11.2.0.3
    OS: RHEL 6.2
    Source Control: subversion
    This is a general question aimed at database professionals, however, it is not specific to any oracle version, etc.  Its a leadership question for other Oracle shops regarding source control.
    The current trunk, in my client's source control, is the implementation of a previous employee who used ER Studio.  After walking the batch scripts and subordinate files , it was determined that there would be no formal or elegant way to recreate the current version of the database from our source control - the engineers who have contributed to these assets are no longer employed or available for consulting.  The batch scripts are stale, if you will.
    To clean this up and to leverage best practices, I need some guidance on whether or not to baseline the current repository and how to move forward with additions of assets; tables, procs, pkgs, etc.  I'm really interested in how larger oracle shops organize their repository - what directories do you use, how are they labeled...are they labeled with respect to version?
    Assumptions:
    1. repository (database assets only) needs to be baselined (?)
    2. I have approval to change this database directory under the trunk to support best practices and get the client steered straight in terms of recovery and
    Knowns:
    1. the current application version in the database is 5.11.0 (that's my client's application version)
    2. this is for one schema/user of a database (other schemas under the database belong to different trunks)
    This is the layout that we currently have and for the privacy of the
    client I've made this rather generic.  I'd love to have a fresh
    start...how do I go about doing that...initially, I like using
    SqlDeveloper's ability to create sql scripts from a connected target. 
    product_name
      |_trunk
         |_database
           |_config
           |_data
           |_database
           |_integration
           |_patch
           |   |_5.2A.2
           |   |_5.2A.4
           |   |_5.3.0
           |   |_5.3.1
           |
           |_scripts
           |   |_config
           |   |_logs
           |
           |_server
    Thank you in advance.

    HiWe are using Data ONTAP 8.2.3p3 on our FAS8020 in 7-mode and we have 2 aggregates, a SATA and SAS aggregate. I want to decommission the SATA aggregate as I want to move that tray to another site. If I have a flexvol containing 3 qtrees CIFS shares can I use data motion (vol copy) to move the flex vol on the same controller but to a different aggregate without major downtime? I know this article is old and it says here that CIFS are not supported however I am reading mix message that on the version of data ONTAP we are now on does support CIFS and data motion however there will be a small downtime with the CIFS share terminating. Is this correct? Thanks

  • RoboHelp Server 8 - compatible with "source control system" ?

    Greetings,
    Using RoboHelp Server 8, is it possible to add in a "source control system," such as Subversion or Bazaar, to track updates and versions? Is there another "source control system" alternative?
    Also, is there a hosted RoboHelp Server 8 option, where Adobe provides, sets up and maintains the server hosting the RH?

    Hi again
    Well, sort of. Note that basic WebHelp and FlashHelp are capable of being merged. This allows a search to occur across the merged set. As I said earlier, merging can be automatically enabled or disabled in the RoboHelp Server. So theoretically, you could turn off merging at the server. Then you could publish ten projects. Perhaps you want two of those projects to be isolated islands where search only occurs in them individually. But for the other eight, you want a search to be performed across the eight projects. You could create a standard merge in this case and publish to the RoboHelp Server and have a search work across the eight merged files. You could also open each of the eight individually and search only that file set.
    At least that's my understanding of how it works. Perhaps fellow Adobe Community Professional and fellow Adobe Certified Instructor John Daigle will pop in and offer some clarification if I've muddied the waters.
    Cheers... Rick
    Helpful and Handy Links
    RoboHelp Wish Form/Bug Reporting Form
    Begin learning RoboHelp HTML 7 or 8 within the day - $24.95!
    Adobe Certified RoboHelp HTML Training
    SorcerStone Blog
    RoboHelp eBooks

  • Integrated Source Control doesn't honor given username after restart of LabVIEW

    I don't really like the integrated Source Control of LabVIEW 8.20 due to some missing features and failures which happen. But for a presentation I had to get some practical information. As SCC API provider I selected Microsoft Visual Source Safe for an example project. While playing around I noticed following bug in the implementation for LabVIEW.
    All given information to access the SCC provider is saved inside 'labview.ini' (which is IMO not the correct place, especially when you are working with different projects). As user I selected 'admin' and not the logged on system user. Access to the repository is granted within the current session and I can do all operations. But if you restart LabVIEW it cannot access the repository because it uses the system user and not the given username to log into the repository.
    If you wan't to work with the integrated Source Control each user who should get access to the repository should have an own user account with the same username as his Windows account.
    This is one of a number of bugs since a couple of versions which don't let me use the integrated Source Control.
    Henrik

    Due to following items I don't want to work with the integrated source control:
    1. All SCC options are stored inside the file 'labview.ini'. That makes you unimpossible to work with different projects without reconfiguring the SCC again and again. Each project should hold it's own SCC options which overrides the LabVIEW global SCC options. If you are working without projects the global SCC options should be used.
    2. If you don't have access to the repository (e.g. network disconnected) you get an error message each time you open a vi (last tested with 8.0 a long time ago). LabVIEW should silently fail and give me at maximum one alert that the connection to the repository cannot be established. Opening the SCC options you can see that everyting is resetted while the correct configuration is still located inside the 'labview.ini'. You have to delete them manually inside the configuration file.
    Both parts are already reported to NI in february last year.
    3. Comparing two different versions of one file is not working unless you compare the current local version with the latest version inside the repository. Using subversion I can do that by integrating metadiff and lvdiff. It is more than helpful.
    4. You have to use an external scc client to create a branch or tag.
    5. That's a personal thing but I like the way of using update/commit instead of checkout/checkin.
    Dunno if I remember all the things I missed while testing the integrated source control some time ago.
    Henrik

  • Versions History in TestStand3​.0

    Hi,
    Ist es möglich in TestStand 3.0 nach jeder Speicherung eine Versions History zu erzwingen, sprich das Eingeben der vollzogenen Änderungen, und das die Versionsnummer anschließend in der Titelleiste angezeigt wird.
    In LabView7.0 ist die möglich, kann ich dies in TestStand auch realisieren, wenn ja wie geht man dann vor ?
    mfG.Andy

    In the "Configure" Men u go to "Station options" and select the "Preferences"-Tab. Check the "Auto Increment Sequence File Version". Everytime a Sequence file is saved, it will automatically get a new Version Number. Unfortunately the user does not see a window where he can/must enter a description of the changes he made, as in labView. You would have to use a Source-Code Control Tool like VSS, Perforce to get a similar behaviour.

  • Bringing SSAS Source Control Up to date

    Hi all
    I've recently taken over managing an MI team who have a set of SSAS 2008 cubes deployed with a production and development server.  We also have a TFS 2008 project which has the source for the cubes.  However, the team have some bad work practices
    such as updating code directly in production without updating source control or testing properly in development first.
    I want to first bring TFS source control up to date with the latest code from live and wondered on best way to do this?  I will then lock down who can alter code in production to enforce a better release process.  Any help greatly appreciated!

    Thank you David, the issue is we already have solutions in TFS but these are out of date as changes have been made to the AS databases outside of TFS directly on the server.   I ideally want to check out the existing cube solutions and somehow update
    them with the latest versions by pulling them in from the AS server databases, then lock down the release process.
    Otherwise I guess I'll have to delete the solutions and start again using your method but I'd rather not lose what source control history we have.

Maybe you are looking for