Version control systems allow developers to track changes to files over time by recording file revisions, versions, and change history. They provide key benefits like backup and restore capabilities, the ability to revert files, and facilitating collaboration through features such as branching and merging. Common version control systems include Git, SVN, Mercurial, and CVS. Git is a distributed system while SVN uses a centralized model. This document discusses Git version control basics like cloning a repository, checking in and out files, viewing diffs of changes, branching, merging branches, and tagging releases.
I have a compiled a How-To guide for using Subversion. As a developer using subversion was a day in and day out task for me which made me to present it here.
Use my slide as a reference for using SVN features.
I have a compiled a How-To guide for using Subversion. As a developer using subversion was a day in and day out task for me which made me to present it here.
Use my slide as a reference for using SVN features.
Version control systems are a category of software tools that help a software team manage changes.
Git is a very well supported open source project.
Git is a mature, actively maintained open source project
originally developed in 2005 by Linus Torvalds.
What is svn?
how svn works ?
diagram of SVN ?
Merging with SVN ?
Conflict With SVN ?
Checkout and Checkin ,update ,branch , tags ?
what is version control "?
SVN file directory ?
Directories locked in Tags ?
An introduction to Atlassian Bitbucket PipelinesDave Clark
Slides from the session at the October 2016 Sydney Docker meet up. Group event page: https://www.meetup.com/Sydney-Docker-User-Group/events/234458971/
The purpose of the session was to introduce attendees to building, testing and deploying using Docker containers via Bitbucket Pipelines.
A brief overview of the features of Subversion using TortoiseSVN on Windows. This covers a number of common commands encountered when using Subversion.
We don’t need to burden modern PHP code with countless “require” or “include” statements. In this talk, we’ll learn how the PHP autoloader works, how to write our own autoloader, and how to work with composer’s autoloading map. We’ll see exactly how to design our namespaces for PSR-4 compatibility so everything “just works.” We’ll learn the PEAR and PECL conventions as well. We’ll finish by learning how to create our own packages for distribution and reuse.
Introduction to Distributed Version Control System with Mercurial / TortoiseHgEng Chin Gan
This is a presentation that I made for Experian Tech Talk in August 2012. It covers basic introduction to DVCS using Mercurial / TortoiseHg as example.
It is a presentation to help software developers get started with a testing platform Cypress. I have created it personally and given the most basics of explanation regarding the new concepts.
Version control systems are a category of software tools that help a software team manage changes.
Git is a very well supported open source project.
Git is a mature, actively maintained open source project
originally developed in 2005 by Linus Torvalds.
What is svn?
how svn works ?
diagram of SVN ?
Merging with SVN ?
Conflict With SVN ?
Checkout and Checkin ,update ,branch , tags ?
what is version control "?
SVN file directory ?
Directories locked in Tags ?
An introduction to Atlassian Bitbucket PipelinesDave Clark
Slides from the session at the October 2016 Sydney Docker meet up. Group event page: https://www.meetup.com/Sydney-Docker-User-Group/events/234458971/
The purpose of the session was to introduce attendees to building, testing and deploying using Docker containers via Bitbucket Pipelines.
A brief overview of the features of Subversion using TortoiseSVN on Windows. This covers a number of common commands encountered when using Subversion.
We don’t need to burden modern PHP code with countless “require” or “include” statements. In this talk, we’ll learn how the PHP autoloader works, how to write our own autoloader, and how to work with composer’s autoloading map. We’ll see exactly how to design our namespaces for PSR-4 compatibility so everything “just works.” We’ll learn the PEAR and PECL conventions as well. We’ll finish by learning how to create our own packages for distribution and reuse.
Introduction to Distributed Version Control System with Mercurial / TortoiseHgEng Chin Gan
This is a presentation that I made for Experian Tech Talk in August 2012. It covers basic introduction to DVCS using Mercurial / TortoiseHg as example.
It is a presentation to help software developers get started with a testing platform Cypress. I have created it personally and given the most basics of explanation regarding the new concepts.
Brief training targeted to middle school aged students who are participating in First Lego League robotics and planning to use a version control tool such as EV3Hub
Concept and need of version control and the uses in production implementation.
Presented on DotNetters Tech Summit - 2015 RUET
Presenter: Ronald Roni Saha
Event Url: https://www.facebook.com/events/512834685530439/
[2015/2016] Collaborative software development with GitIvano Malavolta
This presentation is about a lecture I gave within the "Software systems and services" immigration course at the Gran Sasso Science Institute, L'Aquila (Italy): http://cs.gssi.infn.it/.
http://www.ivanomalavolta.com
Over the last several years one of the biggest changes in how developers collaborate with each other has come through, of all things, their source control system. The adoption of Git has changed many of the patterns of software development.
Demystify version control
Cover some of the whys, whats, and hows
Cover some of the version control tools
Help understand some of the things we can track with version control
Demonstrate some version control basics
Describe the benefits to any type of business / developer
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
2. Key Topics
•
•
•
•
What is version control?
Why is it important?
Should I be using it?
What Version Control app should I use?
3. Version control started as
scratching an itch…
• It’s why we use “Save As”. You want the
new file without obliterating the old one.
It’s a common problem, and solutions are
usually like this:
– Chances are you've already rolled your own without knowing
it...
– Make a single backup copy (Document.old.txt).
– If we’re clever, we add a version number or date:
Document_V1.txt, DocumentMarch2007.txt
– We may even use a shared folder so other people can see
and edit files without sending them over email. Hopefully
they re-label the file after they save it.
4. Version Control to the rescue
File
Management
Team
Management
• Backup and Restore
• The Ultimate Undo
• Blame-Storming Credit!
• Sandboxing
• Synchronization
5. Terminology
Make with the lingo jack…
•
•
•
Repository (repo) – Database storing the files
Working Copy – Your local directory of files
Trunk / Master * – The primary location for code in the repo.
Basics
•
•
•
•
•
Add – Begin tracking with VC
Revision – What version a file is on
Head – The latest version in the repo
Checkout – Download a file from the repo
Check in - Upload to the repo
–
•
•
•
*Some systems call this main
The file gets a new version number, people can check it out
Change-log / History – List of changes to the file since it was
created in VC
Update / Sync – Synchronize your files with Head
Revert – Throw away your changes, and reload from HEAD
7. Version Control
What are my options?
VCS Name
Type
Git (the topic today)
Distributed
SVN
Centralized
Bazaar
Distributed
Mercurial
Distributed
Team Foundation
Server
Centralized
CVS (Legacy)
Rating
Centralized
Source: http://en.wikipedia.org/wiki/Comparison_of_revisoin_control_software
11. Basic Diffs
The repository has a history of changes as a file evolves. Diffs are the changes you
made while editing: imagine “peeling” them off and applying them to a file
TRUNK
Milk
R1
+Eggs
Milk
Eggs
R2
+Juic
e
Milk
Eggs
Juice
Juice
+
Soup
R3
Milk
Eggs
Soup
R4
To go from R1 to R2, we add eggs. Imagine peeling off that red sticker and placing it on R1
to get to R2.
And from R2 to R3 we add Juice, from R3 to R4 we delete Juice and add Soup
Most VCS store diffs rather than full copies of the file. This saves disk space: 4 revs of a
file doesn’t mean we have 4 copies; we have 1 copy with 4 small diffs.
12. Diffs help us notice changes. (“How did you fix that bug?”) and even
apply them from one branch to another. -- more on that in a second.
git rev-list --all
1bc4b508a68c4dc85873beb0836823a0799d695a
286d7c1b00a4bf408a046ccfda1e6064d6fc5960
4a5e80a2e83671de7985852a94a6c43549c4c4ab
...
Git diff 1a3a050aaf29b9411552c5a66c85698414b0611d
Note: (git uses computed hash’s for revisions)
Bonus Question: in the previous diagram, whats the diff from R1 to R4
+ Eggs
+ Soup
Notice how “Juice” wasn’t even involved – The direct jump from
R1 to R4 doesn’t need that change, since Juice was overridden
by Soup
14. We branch for our new, experimental ideas.
git branch noms
git checkout noms
Now that we have a branch, and we are working IN that branch,
we can change our code and work out the kinks. Testing in
isolation, knowing our changes wont hurt anyone, and our
branch history is under version control
It’s a tough concept for newbie's, so pretend you copied your
code into a different directory.
15. Merging
This step is the most daunting of all and hangs up most first-time use
Milk
Egg
s
Sou R5
Milk
p
Eggs
Soup
New Feature
R6
Rice
TRUNK
Milk
Egg
s
Sou
p
R4
Milk
Eggs
Soup
Brea
d
+Ric
e
R7
Milk
Eggs
Soup
Brea
d
R8
Rice
Re-Integration of a branch usually winds up in conflicts – this is why it
seen as difficult. You will be making good use of the diff command
16. git
git
branch experimental
branch
experimental
* master
git checkout experimental
(edit file)
git commit -a
git checkout master
(edit same file in master)
git commit –a
git merge experimental
We now have a conflict.
PANIC! What do I do? Relax,
grab a beer and start resolving
conflicts with git-diff
17. A charted example of conflicts
-Eggs
+Cheese
R3* Bob
Milk
Egg
s
Sou
p
Valid
Milk
Cheese Checkin
Juice
TRUNK
R3
-Eggs
+Hot Dog
Milk
Cheese
Juice
R4
Conflicting Checkin
(Cannot remove eggs)
R3* Judy
Milk
Hot Dog
Juice
18. Tagging
•
Version Control Systems support a method of easy identification
on –stable branches that we branch out of our source-tree called
“tags”
•
They are snapshots, of feature-complete code. Typically
releases.
•
To learn more about this however, you’ll have to visit the git
manpage or mr google