Version Control System to Storage BIG Design Files

I am designing the architect of a version control system to store big design files across an enterprise. Most of files are ~10MB. But some files (Multi-media) are as big as ~500MB. The employee number is around 3000. The service will be used quite often during the day time. I am wondering that Web Service is a capable technique to handle such problem.

Hi
Is that anybody would like to post his opinion? Or web service is not mature enough for such kind of service.
CuiLu

Similar Messages

Reg: Openscript files should store version control system (CVS)

Dear's.
I dont see any option in Openscript to directly send files to repository like Eclipse. Eclipse has an option to team sync with repository .Is their a way to store openscript files in to any kind of version control system .
Thnkq
Raju.

Hello
Pls find here http://dl.free.fr/gZ9qmGToA (for the next 30 days) a HowTo integrate OpenScript with Subversion.
Let us know if it fits your needs.
Cheers
JB

Putting ~ into a version control system

Hey folks!
I'm curious as to how one could put ones home directory into version control, to quote Codemac;
codemac wrote:I keep my ~ in mercurial, so all files are checked in and versioned. [...] I highly suggest you put your $HOME into version control. It's real fun to see what your home directory looked like 3 years ago
I once used Subversion under Mac OS X to download a random project just for kicks, but had no idea what it was all about really. I understand that a version control system assists (manually or automatically?) in labeling files/data/"units" with version numbers, and storing the data as well? I've also seen that a number of users here use Git, another version control system, to label and share their various configuration files. Where is the data stored? On a server belonging to someone else or on ones own computer?
I found a Wikipedia article on the topic, although Subversion isn't named there, so I may be wrong on that one.
Is there a CVS that is small in size and amount of features and easy to get the grasp of?
Thanks in advance.

I'm having my ~ under version control now for a while (I am using git - the decision to do so was mainly motivated by my desire to learn git). However, I don't track every file in my ~. Just the configuration files (.bashrc, .bash_logout, .zshrc, .awesomerc, vim ... etc. etc.) and some docs (though I keep them in a different private repository). I'd recommend that if you plan to put your ~ under a VCS that you should think about what you plan to track and what not first. It certainly means some additional work, because you have to remember to commit changes back into your repository every time you change a tracked file. Of course you can perform a commit on every logout, but if you want to revert/restore a single file, it's better to track changes in files individually. As I see it, the main idea of keeping your ~ in a VCS system is to have a backup from where you can restore a single file to every point in time you want, or to revert uncommited changes which broke sth. in an instant. So, IMHO it doesn't make that much sense to have the repository on your laptop only, but also to have a remote repository (in case your HD dies). For me, it's also a nice way to keep my home directory in sync over multiple machines.
As for the decision on which particular VCS to use. I first tried to do that a year ago using svn, and it didn't work out that well - for some reason I don't like svn - but that doesn't mean that svn is bad - it could be right for you . Darcs is an easy to learn VCS but it lacks some features like branches and the like (which you may not need in this szenario anyway). I don't know much about Bazaar or Mercurial, because I've never used them, however from what I've read, these two are very popular choices nowadays (maybe someone with some experience with those can shed some more light ). Also, you have to chose the VCS according to what you like to track, because they differ in performance and the extra storage they need to keep track of the changes (I read a good article which compared all named VCSs regarding repository/metadata size in differrent szenarios, small files only, big files only etc. etc. - but unfortunately I can't find it atm).

What version control system you use?

We are 20 developer and we use bitkeeper as a version control system.
But we have 4 envirronnement.
dev/test/pre-prod/prod.
Sometimes, 2-3 projects are affecting the same packages.
And different packages version is all over the place since we have 4 envirronnements.
What version control system you use for packages?
Would be cool to have a version control system intergrated to our tools, like toad, pl/sql dev or sql developer, is there one for those tools?
Is the tool you using it doing all you want it to do?
Have any link for me to check out?

Hi,
I recommend SourceAnywhere Standalone to you. It is an SQL-based source control application that provides all of the key features of VSS, plus much more. It is well integrated with Microsoft Visual Studio 6/2003/2005/2008, Dreamweaver and Eclipse. Here is the home page of SourceAnywhere Standalone:
http://www.dynamsoft.com/Products/SAWstandalone_Overview.aspx
The Hosted edition, SourceAnywhere Hosted that is delivered as a SaaS application is also available.
http://www.dynamsoft.com/Products/SAWhosted_Overview.aspx
You can take a look.
Thanks,
Catherine Sea
www.dynamsoft.com
the leading developer of version control and issue tracking software
Message was edited by:
Catherine Sea

Jdev support with PVCS Version control system

Hi,
Is there any JDev plugin available for PVCS source control system.
We have to use PVCS version control system for our SOA composites. If there is no plugin available, what is the approach commonly used for these scenarios.
Thanks for your response.

Which JDev version do you use?
AFAIK there is no extension for PVCS available for 11g (check http://www.oracle.com/ocom/groups/public/@otn/documents/webcontent/131167.xml).
Anyway if you have an external tool which lets you work with PVCS you can use it outside of jdev without a problem. Depending on the interface you might be able to do some kind of integration into jdev using the 'External Tools...' interface.
Timo

Issue using microsoft tfs as version control system with jdeveloper 11g

Hi ,
I am using TeamFoundationServer as source control system and trying to use Jdeveloper with TeamVCS Extension.
Software Details :
Jdeveloper Version : Studio Edition Version 11.1.1.6.0 Build JDEVADF_11.1.1.6.0CLOUD_GENERIC_121118.1600.6229
Versioning Support for Team System - oracle.jdeveloper.vsts 11.1.1.6.38.62.29
Steps followed :
1. Install the Microsoft Visual Studio Team Explorer 2010 ( http://www.microsoft.com/en-in/download/details.aspx?id=329 ).
2. Install upgrade for Version Support for Team System using CheckForUpdates in Jdeveloper Help Menu.
3. Now create a workspace in TeamExplorer and get the latest version of code.
4. Click connectToTeamSystem in Versioning->Team System.
5. Click Set workspace .
6. Now open the Application .
Issue : Checkin Checkout and other options are still grey out.
Error : No error message in log.
Additional Note : I tried doing the same steps on 11.1.1.7.0, and even there it doesn't work.
Please help !!!!
Thanks,
Rajdeep

JDev 11g support TFS 2008 - http://www.oracle.com/technetwork/developer-tools/jdev/index-091111.html#Source_Control_Systems

Version Control System?

Is there an option for integrated version control?
Specifically, is there a recommended plug-in available that
integrates with Visual Source Safe (2005)? I'm using the dedicated
Eclipse IDE for Flex 2 (ie... I'm not running Eclipse with the Flex
2 plugin)
I'm using Visual Studio 2005 and web services to integrate
with Flex 2. I'm having a wonderful experience so far....kudos to
your product team (I seriously think Microsoft delayed their
expressions' tools after trying this out.) I hope you consider
creating a Visual Studio plugin for Flex.
Thanks,
Daniel

There are options for source control plugins for Eclipse
(Flex Builder 2), but you'd have to go to the eclipse site to see
what those options are.
Here's the link to our bug and enhancement request form:
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&product=20&6213=35
Please give as much detail as you can regarding your desire
for a Visual Studio edition of Flex. Can't hurt to ask.

What's version control system do people arround here favour?

I started with CVS. A bit crude and flaky so we decided to upgrade to subversion, which seemed more solid (transaction management etc.). Trouble is I'm getting problems with that too, I suspect it doesn't cope all that well with file sharing, most of my checked out directories are on a shared drive.
It has can get very stubborn, for example I imported a netbeans project and accidentally failed to exclude the dist directory with the distribution jars in it. Once you've done that it seems impossible to remove the directory from subversion control.

PeteFord wrote:
Where I am we use CVS; it's ok but Subversion is better. ClearCase? puh-leeze. I was stuck with that at a previous job - what a damn nightmare; all it took was one developer to check something out and go home forgetting to check it back in, and everything stopped until we could find an admin to unlock the thing.I used CC years ago, and I loved it. However, it is not free, and it has a fairly large administrative overhead. It's target audience is definitely larger groups working on large projects with lots of branching. Its powerful query language and tools were godsends for me. As for the locking, I thought it allowed you to steal a lock. If not, that becomes a management issue, and shouldn't really be a major problem.
For smaller projects, I definitely like Subversion. The one thing I don't like is its branching and labeling model. I've found it hard to do things that were trivial in CC--and maybe even in CVS--are major pains in SVN, though I admit that I haven't taken the time to learn that part of it thoroughly.
VSS and PVCS are Satan.

Version Control with JDeveloper

Does any one know what version control packages can be used with JDeveloper? If you do, would you please let me know where I can get info on them.
Thank you

Alex,
There are two parts to this answer.
You can hook up any version control system
to JDeveloper using various JDeveloper
extension mechanisms including adding items
to the tools menu or complete wizards.
On OTN, you can find an CustomAddins which provides a way to integrate to any version control system by editing some batch files to point to their "put" and "get" type tools. This is meant as a simple starting point.
Starting with JDeveloper 3.2, you will be able to take advantage of the intergrated source control feature that integrates Oracle Repository's source control features into JDeveloper.
I hope this helps,
-John

Version Control with JDeveloper application using ClearCase

My team is evaluating J Developer to see if
it matchs our requirement. We want
to know how we will be able to use Clearcase
as version control tool with our Java or JSP application developed using JDeveloper.
We understand that J Developer will help us
to create a zip file for deployment. Do we need to check in/out that zip file, zip/unzip the zip file, look for the file
that we want to change, and then make change to it?
If so how Clear Case knows which files in that zip file has been changed and what changes have been made?
Currently, we use Clearcase to check in/out
every single file, one at a time. We don't know how it will work with a zip file.
Sincerely,
Khanh

Alex,
There are two parts to this answer.
You can hook up any version control system
to JDeveloper using various JDeveloper
extension mechanisms including adding items
to the tools menu or complete wizards.
On OTN, you can find an CustomAddins which provides a way to integrate to any version control system by editing some batch files to point to their "put" and "get" type tools. This is meant as a simple starting point.
Starting with JDeveloper 3.2, you will be able to take advantage of the intergrated source control feature that integrates Oracle Repository's source control features into JDeveloper.
I hope this helps,
-John

Keynote destroys version control files inside of .key directory

Hi - I've been using Keynote for a couple of years now and in general I really prefer it. However, I've noticed a change in the more recent versions of the iWork apps, particularly Keynote. It seems that when I save my presentation, Keynote is erasing data files (".svn" directories) which my version control system (Subversion) leaves inside of the Keynote directories, which renders me unable to check the changes to my Keynote file back into the repository (Subversion). A similar problem occurs when I save my ".pages" documents.
Storing my files in Subversion is an important part of how I manage my business' documents, and I cannot see how erasing the ".svn" directories as part of the "save" routine adds useful function to Keynote or any of the iWork apps. This problem is not unique to subversion, as CVS does the same thing. I would suggest removing the code which erases/cleans the directories under the ".key" top-level directory.
Thanks for your consideration!

The "your bug/my bug" dialogue doesn't seem to be very helpful in this discussion (and the open/proprietary arguments even less so). It's a bug at the interaction of how two packages are using the file system, an "our bug" so to speak.
I think the underlying issue has to do with the design discipline of orthogonality which is part of the Unix DNA. Different components are designed to both not step on each other and (where possible) to connect together well. One of the tricks for that orthogonality is the use of dot.files to store application information in the file hierarchy.
OS X Packages, which are a great idea, break orthogonality when they delete information from other tools with prejudice and compound the problem by having no way to override that policy (for example, allowing the declaration of some dotted file or directory names as valid external metadata).
Whose bug is it that subversion doesn't respect one particular vendor's way of using the file system? Given that dot.files are a broad and historically deep Unix convention, I'd be inclined to suggest that the application doing the deleting is in error. subversion could fix the problem with vendor-specific patches, but this doesn't seem the right kind of open approach.
The argument could be made that the iWork applications are Mac applications, not Unix applications, so they shouldn't have to worry about these Unix conventions. But one of the nicest things about the Mac is that it is both Apple and Unix and it would be nice if it stayed that way as Apple added more cool pieces to the OS X universe.
I think I've seen all the workaround and I'm using one for the time being, but I am also seriously but regrettably considering dropping iWork in my company to switch to something more Unix-resonant.

Regarding version control

Hi,
Could u please help me out in giving some ideas of version control in sap?
First let me give some example as follows:
First if i develop something in the developement server then later when i transfer to the QA server and later to production server then is there any change in version.
Please give me a details of this issue????
Thanks,
Batista....

hi priya,
Version Control
Version control is a mechanism that helps maintaining the revision history of a development resource and tracking the changes done to it. It defines a set of constraints on how a development resource can be changed. A development resource that complies with the constraints defined by the version control is called a versioned resource. When a versioned resource is modified or deleted, a new version is created for the resource. A unique sequence number is associated with each version of the resource created in a particular workspace. This sequence number identifies the order in which the versions were created in that workspace. The DTR graphically represents the relationship between the different versions of a versioned resource in the form of a version graph.
For the representation of version graphs, this document follows the conventions shown in this figure.
The figure shows the meaning of the symbols in the version graph.
The following changes are tracked by the version control mechanism of the DTR:
·        Addition of the resource to the repository
·        Modification of the resource in the repository
·        Deletion of the resource from the repository
In all the above cases, a new version of the resource is created.
Production Delivery
Packaging
To deliver your product, you have first to package it. There are different packages you can use for shipping your product to your customers:
●      Software Component Archives (SCAs) this is the standard way to deliver software for the SAP NetWeaver platform.
●      Software Deployment Archives (SDAs) for top-level applications you can deliver only the executable part of the software. You can directly deploy the SDA file.
●      Public Part Archives (PPAs) in Development Component Interface Archives (DCIAs) for reusable components (Java EE server libraries, Web Dynpro components, Visual Composer components and so on). You can deliver only the metadata of the components. DCIA can be included in SCA file too.
How to do that?
Using the command line tool provided with the SAP NetWeaver Composition Environment you can:
●      package a collection of components into an SCA including only the deployable archives. This is required if you do not want others to reuse the delivered components.
●      package a collection of components into an SCA including the deployable archives and the corresponding interface archives. This allows customers to develop against these components. Those customers can directly import the SCA into their own SAP NetWeaver Development Infrastructure (NWDI) or into an SAP NetWeaver Developer Studio local installation.
●      package the public parts of a component together with the required metadata into a DCIA (and further into an SCA).
●      include source code into an SCA.
●      unpack a deliverable archive and drop the result into an existing version control system for example, or directly import them into an existing Design Time Repository (DTR).
Delivery of Source Code for Further Customization
In addition, you can deliver source code to your customers to allow further customizing or add-on development. The deliverable archive may contain sources for:
●      individual development components (DCs).
●      a collection of development components, for example a whole software component (SC).
Example
A customer can add a new source compartment to an existing configuration, and then locate that compartment in the file system where it is accessible by the version control system in charge. Then he or she extracts the sources with the command line tool to the compartments root directory and refreshes the configuration in the SAP NetWeaver Developer Studio. The compartment tree is populated with components from the archive. Afterwards, the customer may put those components under version control. Deliverables that contain only individual components may be treated accordingly.
This mechanism may also be used for other purposes, for example for setting up a simple backup and restore mechanism for components in Developer Studio, or sharing DC sources without having a central version control system: a developer may pack a compartment and store the resulting SCA on a central share or backup system. Another developer may take that SCA and import it.
Limitations
Note the following limitations connected with this kind of source code delivery:
●      There is no support for handling conflicts when different actors in a delivery chain develop independently in the same source code. You cannot prevent the customer from modifying delivered sources. When you ship a new version of the sources, there is no special support for updating and no support for merging the update with modifications done by the customer. You and the customer have to agree on a process how those conflicts are handled. For example, the customer can decide not to import the update you deliver directly into the active development line, but to unpack the delivered sources to some unconnected sandbox system and perform the required merges manually.
●      When you deliver source code to customers, it is important that you also deliver the required libraries and generators that are needed to build these sources. For example, it may be necessary to ship some archive compartments that contain used components.
●      There is no support for delivering deletions in a new version. If a source file was deleted, the customer has to manually ensure that the file is also deleted in the Developer Studio or source code management system.
●      If a customer prefers to work with the SAP NetWeaver Development Infrastructure (NWDI), this customer cannot directly import the source delivery package into the NWDI landscape. Between NWDI landscapes at different places, sources usually are exchanged through a more sophisticated export format that contains not only the pure source code, but also the versioning meta information of the exporting DTRs. This ensures that the importing repository can detect conflicts that arise due to modifications. If this versioning information is not available, the only way to import source deliveries is to unpack them to a file system and manually put them under version control with the Design Time Repository perspective of the Developer Studio. In case of an update, the customer would have to check out all affected files, merge them with the new versions from the source delivery, and finally check them in as a new version.
More information: Composition Environment Command Line Tool
see this url
http://www8.sap.com/businessmaps/0134713B1D6046C59DE21DD54E908318.htm
thanks
karthik
reward me if usefull

OWB Change Management/Version Control Best Practice

Hi
I am about to start developing a data warehouse using OWB 10g R2, and I've been doing quite a lot of research into the various deployment/change management/version control techniques that can be used, but am still unsure which is the best to use.
We will have 2-3 developers working on the project, and will be deploying from Development, to Test, to Production (each will have a separate repository). We want to be able to easily identify changes made between 1 release and the next to have a greater degree of control and awareness of what goes into each release. We also wish to use a source control system to track changes (we'll probably use SVN, but I don't think that the actual SCS tool makes a big difference to our decision at this point).
The options available (that I'm aware of), are:
1. Full MDL export/import.
2. Snapshot MDL export/import.
3. Manual coding of everything using OMB Plus.
I am loath to use the full MDL export/import functionality since it will be difficult, if not impossible, to identify easily the changes made between 1 release and the next.
The snapshot MDL export/import functionality is a little better at comparing releases, but it's still difficult to see exactly what has changed between 1 version and the next - particularly when a change to a transformation has been made. It also doesn't cope that well with tracking individually made changes to different components of the model.
The manual coding using OMB Plus seems like the best option at the moment, though I keep thinking "What's the point of using a GUI tool, if I'm just going to code everything in scripts anyway?".
I know that you can create OMB Plus code generation scripts to create your 'creation' scripts, but the code generation of the Alteration scripts seems that it would be more complicated than just writing the Alteration scripts manually.
Any thoughts anyone out there has would be much appreciated.
Thanks
Liffey

Well, you can also do per-object MDL exports and then manage those in your version control system. With a proper directory structure it would be fairly simple to code an OMB+ Script that scans a release directory tree and imports the objects one by one. I have done this before, although if you are using OWB as the primary metadata location for database objects then you have to come up with some way to manage object dependency order issues.
The nice thing about this sort of system is that a patch can be easily shipped with only those objects that need to be updated.
And if you force developers to put object-level MDL into your version control system then your system should also have pretty reporting on what objects were changed for a release and why.
At my current job we do full exports of the project MDL and have a deployment script that drops the pre-existing deployed version of the project before importing and deploying the new version, which also works quite well - although as you note the tracking of what has changed in a release then needs to be carefully managed elsewhere. But we don't deploy any of our physical database objects through OWB. Those are deployed from Designer, and our patch script applies all physical changes first before we replace the mappings from the OWB project. We don't even bother synching the project metadata for tables / views / etc. at deployment. If the OWB project's metadata for database objects is not in sync with Designer, then we wind up with deployment errors. But on the whole it works pretty well.

Control Systems Engineer

Control Systems Engineer
Seattle Safety – Kent, WA 98032
Seattle Safety is looking for a qualified individual to fill an opening for Control Systems Engineer. Seattle Safety designs, manufactures, and installs advanced crash test sled systems that are used in automotive and aeronautical industries. The duties of the Control Systems Engineer include:
• Experience designing, testing, and optimizing industrial automation and control systems utilizing modern and classic control methodologies such as PID. Experience with neural networks.
• Strong background in mathematics, physics, and signal analysis.
• Electrical / Electronic design experience including automation.
• Design, troubleshoot, and test software written in LabVIEW 8.6 & 2012 and C.
• Help customers diagnosing electrical, software, and mechanical problems with their systems. This will sometimes involve working odd hours for customers on the other side of the planet.
• Support installations of crash test equipment at on-site locations worldwide.
• Provide round the clock technical support for team members locally and abroad in subject matters concerning performance, installation, and maintenance of software and data acquisition hardware.
• Prepare and maintain software flowcharts, layouts, and diagrams as needed to demonstrate solutions to outside staff.
• Work with current team members to restructure existing crash test software.
• Supports all aspects of software application design, development, testing, deployment, and support.
• Perform software testing at a unit and integration level to ensure expected behavior.
• Comment code clearly and consistently throughout the development process.
• Maintain professional relationships with suppliers and vendors in order to keep up with industry developments.
• Candidates must be located in the US, the northwest would be ideal.
Furthermore, the ideal candidate would possess the following skills:
• Advanced or expert knowledge of LabVIEW.
• Advanced or expert knowledge of C.
• Expert knowledge of industrial controls.
• Familiarity with a minimum one low-level programming language (C#, VB, Ladder, etc)
• Familiarity with data acquisition concepts and hardware.
• Discipline and organization with respect to software maintenance and version management. Experience with source configuration management tools a plus (CVS, ClearCase, Perforce, etc.)
• Experience with sophisticated feedback control systems.
• BSEE, BS Physics, and BSME are preferred but not required depending on experience.
• Ability to work both alone and with colleagues to solve problems and to weigh the merits of differing approaches.
Pay is commensurate with skills and qualifications of the applicant.

Dear Sir/Mam,
I’m particularly interested in the position of Control System Engineer, which relates strongly to my more than six years of experience in designing various applications for testing and automation. I am Certified LabVIEW Associate Developer & prepared for CLD also. Currently I am leading a team for the project for Machine Automation and remote diagnostics, and I believe I meet all the essential criteria of the position. My work at my current organization has been rewarding and productive. However, I wish to expand my career further, into the application designing and development role. The position also has a definite correlation with my practical knowledge and experience. You’ll see from my CV that I have been deeply involved in designing and development of various applications based on Programming techniques, hardware and network designing. I feel that I am well qualified to make an effective and useful contribution to design good application which will be market acceptable.
I’m enthusiastic about the chance to participate in a meaningful role with an industry leader in the field.
Thank you for your consideration of my application. Please contact me should you require any further information,
Yours sincerely,
Mohit Monga
Mohit Monga
Attachments:
Mohit Monga_CV.doc ‏159 KB

New to JDeveloper/ADF, need to create a UI Mockup for a Version Control app

Hi,
I have experience with Java/J2EE, however I'm new to both JDeveloper and ADF and was hoping someone could point me in the right direction with what I'm trying to accomplish/start. We are working on a new application for a client and to kick start things I need to come up with a User Interface Mockup of a Version Control system we're going to create. It should be nothing fancy, and not very functional (for the time being) but should use some dummy data (preferably from a text file - just for demo purposes), be a one-page layout, and use Oracle ADF components (folder tree, datagrid, data view, xml view to be specific). Of course, it is requested that this all be done using JDeveloper/Oracle ADF. I was able to install both of these (it seems ADF is bundled with JDev), however that's about as far as I got. What steps do I need to take in order to come up with something simple like this? When I loaded up JDeveloper there are alot of options when creating a new project and I'm not sure what to choose. ANY help would be appreciated.

Thanks! This is exactly what I was looking for.
However, I'm having some trouble figuring out how to set up my Data Controls for the dummy data. I'd basically like to set up the entire page as follows:
A column on the left that displays a tree as follows:
Folder 1
     ...File 1
     ...File 2
     ...File 3
Folder 2
     ...File 1
     ...File 2
Folder 3
     ...File 1
     ...File 3
     ...File 4
     ...File 5
..etc
The right side of the screen will have 3 "columns" or borders that will take up the entire screen, from top to bottom:
List of Versions (large column)
Version Data (smallest column)
Version Text (large column)
List of Versions:
When the user selects a "File" from the tree, a datagrid will appear that displays all versions of the selected file with columns like "File Name", "Version", "Date", and a checkbox to select a row.
Version Data:
When the user selects a row using the checkbox, some relevant version info will display here. This info will come from the database when the final version of the app is written using various fields from the "Files" tables
Version Text:
When the user selects a row using the checkbox, some relevant version CODE (possible to display code neatly?) will display here. This info will come from the database when the final version of the app is written using a field from the Files table that has not been seen yet
How would I go about setting something like this up? Using the sample you provided earlier, the example just has main categories on the left. I'm confused how to set up a fell fledged tree and then to incorporate the functionality I described above.
ANY help would be appreciated.

Version Control System to Storage BIG Design Files

Similar Messages

Maybe you are looking for