SCM Boot Camp
9 likes9,805 views
This document summarizes the key differences between centralized version control systems (CVS) and distributed version control systems (DVCS). It explains that DVCS allow for non-linear development with features like rebasing and branching that are not possible in CVS. Examples of DVCS like Git and Mercurial are given. The document also discusses how to migrate from CVS to a DVCS and advantages of using continuous integration with a DVCS.
1 of 98
Downloaded 35 times
Recommended
SCMBC闇LT資料
SCMBC闇LT資料bleis tift The document discusses using Git for version control in Visual Studio and integrating it with test-driven development. It provides commands for rebasing a development branch onto the master branch and then deleting the development branch. It also mentions using Git from the command line, Git GUI tools, integrating with issue trackers like Redmine and GitHub, and continuous integration tools.
Git training with Devaamo
Git training with DevaamoOtto Kekäläinen Git training with Tampere-based developer community Devaamo ry (devaamo.fi) at New Factory on Nov 28th 2012.
Web Programming - Git basics
Web Programming - Git basicsÖmer Taşkın Git is a version control system that provides versioning of source code history, logs of changes, and the ability for developers to work collaboratively. The document outlines how to initialize a local git repository by cloning an existing remote repository. It describes how to add and commit new files locally and then push those changes to the remote repository using git add, git commit, and git push commands. The git pull command is used to retrieve updates from the remote repository.
Git in Eclipse
Git in EclipseDariusz Łuksza This document discusses Git and the Eclipse Git integration tool EGit. It provides an overview of Git's history and how it works, compares it to other version control systems, demonstrates common Git commands, and describes what EGit can do. The presentation then demonstrates using EGit for basic tasks like committing and branching, as well as more advanced workflows involving remote repositories and code review.
第32回PHP勉強会 LT 極めてない! Git
第32回PHP勉強会 LT 極めてない! Gitkunit This document discusses version control systems and frameworks, including Git, PHP frameworks like Symfony, and other systems like CVS, RCS, Subversion, SVN, and BitKeeper. It mentions that Git was created by Linus Torvalds for Linux kernel development as an alternative to BitKeeper after issues arose, and that Git became very popular after being used for the Linux kernel and other open source software projects.
Skaffold - faster development on K8S
Skaffold - faster development on K8SHuynh Thai Bao Agenda
1. GitOps recall
2. GitOps challenges
3. Skaffold: healing the pains
4. Demo & Usage
5. Integration with current CICD
Contributing to open source using Git
Contributing to open source using GitYan Vugenfirer This document discusses contributing to open source projects using Git. It explains that contributing can help gain programming experience and build a resume while giving back to the community. The overview outlines that contributors commit code to their local Git repository and then send those commits to the project's maintainers and community through patches or pull requests. It provides checklists for testing, coding style and commit messages before sending code. Specifically, it details Linux's strict coding style and two main models - patches sent via email and pull requests on sites like GitHub, outlining their workflows and lifecycles for review and merging code changes.
Helios in Action: Git at Eclipse
Helios in Action: Git at EclipseChris Aniszczyk The document discusses Git and Eclipse tools for working with Git. It describes EGit, an Eclipse plugin that provides integration with Git repositories, and JGit, a Java library for Git. EGit and JGit are open source projects hosted by the Eclipse Foundation. The document outlines features and history of EGit releases and the goal of building a community around Git usage at Eclipse.
Git hooks for front end developers
Git hooks for front end developersBradley Gore Discover how to use the power of Git Hooks within your front-end development workflow - while using the same tools you already know and love.
Introduction to Git
Introduction to GitYan Vugenfirer Git is a distributed version control system that was created by Linus Torvalds in 2005 to manage changes to files over time. It works by tracking changes made to files in a git repository and allowing users to commit snapshots of changes. The key git commands are git init to create a new repository, git clone to copy an existing one, git add to stage changes, git commit to commit staged changes, and git log to view the commit history. GitHub is a popular web-based hosting service for git repositories.
Git hooks
Git hooksBinBin He This document discusses using Git hooks to automate tasks during the Git workflow. It provides examples of using pre-commit hooks to check for debugging code and validate commit messages include ticket numbers. prepare-commit-msg hooks can template commit messages with default text like ticket references. post-commit hooks may open a browser to log work time against a referenced ticket after a commit. Server-side hooks on push can trigger tasks like running tests. Overall the document explores leveraging Git hooks for tasks like validation, templating, integration and to enforce best practices when committing code changes.
Git hooks
Git hooksSkills Matter This document discusses using Git hooks for deployment to staging and production environments. It provides examples of a simple scenario using a post-update hook to automatically deploy code on push to a single production server. It also outlines a more advanced setup using Git hooks to deploy to staging and production environments with different processes, including emails on staging deploys and manual gem updates for production.
Nicolás Aravena - Cómo aprender Git y no morir en el intento
Nicolás Aravena - Cómo aprender Git y no morir en el intento9punto5 Entregar una introducción básica sobre git y sus beneficios, demás de entregar herramientas para su aprendizaje y los desafíos que presenta el trabajo remoto al momento de versionar el desarrollo con distintos miembros del equipo.
Git back on_your_feet
Git back on_your_feetChristian Couder - Git is a distributed version control system created by Linus Torvalds and maintained by Junio Hamano since 2005.
- The document provides tips for using Git commands like git status, git log, and git diff to understand the current state after an error.
- It recommends drawing diagrams to visualize branches and commits, and explains how to use git reflog and shell history to understand what happened.
- The key to getting "back on your feet" after a Git error is to avoid losing data by resetting, stashing, or creating a new branch before changing the project state.
GIT - DUG Antwerp
GIT - DUG AntwerpKrimson This document provides an overview and introduction to Git:
1. Git is a distributed version control system created by Linus Torvalds that allows for blazingly fast local version control and collaboration through distributed development.
2. Git can be used through both a command line interface (CLI) and graphical user interfaces (GUIs). The CLI provides many basic commands for initializing repositories, making commits, branching, tagging, and more.
3. Users can create their own Git repositories on their local machine or hosting services like GitHub to collaborate on projects and share code.
How to store large binary files in git repositories
How to store large binary files in git repositoriesMatt Aunger This document discusses 7 approaches for handling large binary files in Git repositories:
1. Git Annex stores file contents separately from the repository and uses symlinks to reference them. Allows sharing between teams but requires learning new commands.
2. Git Large File Storage (LFS) stores file blobs on a separate server using pointers. Supported by GitHub but requires a custom server.
3. Git-bigfiles aimed to backport large file handling directly into Git but the project is abandoned.
4. Git-fat and Git-media work similarly to LFS using filters and storing files on remote servers like S3. They are older and less actively developed.
5. Git-bigstore and Git
Git and github fundamentals
Git and github fundamentalsRajKharvar Git is an open source distributed version control system (VCS) developed by Linus Torvalds in 2005. Version control allows tracking changes to files over time through commits, enabling recall of specific versions. GitHub is a code hosting platform that allows collaboration on projects remotely using Git. Common Git commands include git init to create a repository, git add to stage files, git commit to save changes, and git push to sync a local repository with a remote one. Pull requests allow proposing and reviewing changes before merging into a main branch like master.
about Debian "squeeze" @201002 OSC Tokyospring
about Debian "squeeze" @201002 OSC TokyospringHideki Yamane The document discusses the upcoming Debian 6.0 release codenamed "Squeeze". It provides details on the development process, expected release timeline in 2010, and highlights some of the new components and packages that will be included such as Linux 2.6.32, GNOME 2.28, KDE 4.3, and Perl 5.10. It also discusses the process for moving packages from testing to stable and addressing release critical bugs.
Git for standalone use
Git for standalone useIkuru Kanuma This document provides an overview of Git and version control systems, including:
- A brief history of Git and how it was created by Linux's original author to be distributed and scale with large projects.
- Explanations of common Git terms and commands like checkout/branch, commit, push, pull, and how the Git repository, index, and workspace interact.
- Instructions for getting Git set up on different operating systems and making the first commit to a new Git project locally or connecting it to a remote repository like GitHub.
用 Go 語言實戰 Push Notification 服務
用 Go 語言實戰 Push Notification 服務Bo-Yi Wu Gorush 是一套用 Go 語言所撰寫的輕量級 Push Notification 服務，除了架設服務外，還可以讓 Android 或 iOS 開發者可以輕鬆使用 Command line 發送訊息給 App。本議程會介紹作者為什麼選用 Go 語言，以及其中的 Go 開發技巧與經驗。
專案網址: https://github.com/appleboy/gorush
How do Centralized and Distributed Version Control Systems Impact Software Ch...
How do Centralized and Distributed Version Control Systems Impact Software Ch...Caius Brindescu The document analyzes how centralized (SVN) and distributed (Git) version control systems impact software changes based on a survey of 820 developers and analysis of 132 repositories. The key findings are:
1) Commits are typically smaller in Git (34% smaller) than SVN due to the ability to commit privately without merging.
2) Developers split changes more often in Git (81% vs 68% for SVN) due to easier commit processes and tools for splitting changes.
3) Developers prefer Git over SVN for its features like private commits, while some prefer SVN out of habit or ease of use.
Git and GitHub
Git and GitHubAshwinRaj57 This document discusses Git and GitHub. It begins by introducing the author and their background. It then covers problems that version control systems solve like maintaining a history of file changes. It describes key concepts of Git like its distributed nature, how it stores data through snapshots instead of file differences, and the three main states files can be in. The document concludes by discussing GitHub and how it builds upon Git to enable collaboration through features like pull requests, issues, and actions.
Terrible Ideas in Git - Corey Quinn, FutureAdvisor - DevOpsDays Tel Aviv 2015
Terrible Ideas in Git - Corey Quinn, FutureAdvisor - DevOpsDays Tel Aviv 2015DevOpsDays Tel Aviv The document discusses both powerful and dangerous things that can be done with Git, such as committing large files or secrets. It recommends tools like git-annex and git-lfs to avoid committing large files directly, and warns not to commit secrets. The document also introduces myrepos and vcsh as tools to manage multiple Git repositories, with myrepos allowing batch updates and vcsh providing a sane directory structure. Overall, the document humorously warns of potential pitfalls with Git while also offering advice and tools to help users leverage Git more safely and effectively.
Github
GithubIFEDAYO ADEYEMI Git is an open-source version control system created by Linus Trovalds that helps users achieve version control and track changes on files. Version control systems like Git allow developers and non-developers to collaborate by downloading, modifying, and uploading new versions of projects. Github builds on Git by providing a platform for developers to store projects in repositories and connect with other developers. Key Github concepts include repositories for storing project files, forking to create new projects from existing ones, and pull requests and change logs for tracking changes made to projects.
Git advanced
Git advancedPeter Vandenabeele git advanced
GitX and other GUI’s
fundamentals
git init, git status, git add -i, git commit
git remote -v, git init --bare
git branch -a, git merge, git rebase -i
git cherry-pick, git log --author
Git and GitHub
Git and GitHubRick Umali A beginner's talk on Git and GitHub. Three main sections: the basics, branching/merging, and collaborating (with GitHub). A funny xkcd comic is used (#1597). Brief mentions of GitHub alternatives (GitLab).
Intro to git
Intro to gitjosh_cutler Git is a distributed version control system that allows for efficient branching and merging. It tracks changes to files and allows multiple users to edit files simultaneously. Users initialize a Git project by creating a hidden .git directory to store change information. They can then add and commit changes, check the status of changes, and view commit logs. Users can also create branches to work in parallel and merge branches together once work is complete. Git enables collaboration through remote repositories hosted on services like GitHub.
Git and GitHub | Concept about Git and GitHub Process | Git Process overview
Git and GitHub | Concept about Git and GitHub Process | Git Process overviewRueful Robin This presentation may help you to know about the version control, git, github and so more. You may get a brief about the whole process of git system.
輪るビングドラム.NET
輪るビングドラム.NETbleis tift The document discusses using Jenkins for continuous integration of .NET projects. It recommends installing plugins for Git, MSBuild, NUnit and other tools to integrate them with Jenkins. The Groovy and PowerShell plugins allow adding custom build steps. Overall Jenkins is presented as a good option for continuous integration of .NET projects by automating builds and running tests on each code change.
Jenkins the definitive guide lt(第四回jenkins勉強会)
Jenkins the definitive guide lt(第四回jenkins勉強会)Ryuji Tamagawa This document is about Jenkins, an open source automation server that enables developers to reliably build, test, and deploy their software. It discusses how Jenkins can be used to automate tasks like building Java projects, running tests with tools like JUnit, and deploying code to servers like Amazon EC2, Google App Engine, or Windows Azure. The document also mentions that Jenkins supports integration with version control systems and platforms like Hadoop and can be used to continuously build and test code changes from tools like Git.
More Related Content
What's hot (20)
Git hooks for front end developers
Git hooks for front end developersBradley Gore Discover how to use the power of Git Hooks within your front-end development workflow - while using the same tools you already know and love.
Introduction to Git
Introduction to GitYan Vugenfirer Git is a distributed version control system that was created by Linus Torvalds in 2005 to manage changes to files over time. It works by tracking changes made to files in a git repository and allowing users to commit snapshots of changes. The key git commands are git init to create a new repository, git clone to copy an existing one, git add to stage changes, git commit to commit staged changes, and git log to view the commit history. GitHub is a popular web-based hosting service for git repositories.
Git hooks
Git hooksBinBin He This document discusses using Git hooks to automate tasks during the Git workflow. It provides examples of using pre-commit hooks to check for debugging code and validate commit messages include ticket numbers. prepare-commit-msg hooks can template commit messages with default text like ticket references. post-commit hooks may open a browser to log work time against a referenced ticket after a commit. Server-side hooks on push can trigger tasks like running tests. Overall the document explores leveraging Git hooks for tasks like validation, templating, integration and to enforce best practices when committing code changes.
Git hooks
Git hooksSkills Matter This document discusses using Git hooks for deployment to staging and production environments. It provides examples of a simple scenario using a post-update hook to automatically deploy code on push to a single production server. It also outlines a more advanced setup using Git hooks to deploy to staging and production environments with different processes, including emails on staging deploys and manual gem updates for production.
Nicolás Aravena - Cómo aprender Git y no morir en el intento
Nicolás Aravena - Cómo aprender Git y no morir en el intento9punto5 Entregar una introducción básica sobre git y sus beneficios, demás de entregar herramientas para su aprendizaje y los desafíos que presenta el trabajo remoto al momento de versionar el desarrollo con distintos miembros del equipo.
Git back on_your_feet
Git back on_your_feetChristian Couder - Git is a distributed version control system created by Linus Torvalds and maintained by Junio Hamano since 2005.
- The document provides tips for using Git commands like git status, git log, and git diff to understand the current state after an error.
- It recommends drawing diagrams to visualize branches and commits, and explains how to use git reflog and shell history to understand what happened.
- The key to getting "back on your feet" after a Git error is to avoid losing data by resetting, stashing, or creating a new branch before changing the project state.
GIT - DUG Antwerp
GIT - DUG AntwerpKrimson This document provides an overview and introduction to Git:
1. Git is a distributed version control system created by Linus Torvalds that allows for blazingly fast local version control and collaboration through distributed development.
2. Git can be used through both a command line interface (CLI) and graphical user interfaces (GUIs). The CLI provides many basic commands for initializing repositories, making commits, branching, tagging, and more.
3. Users can create their own Git repositories on their local machine or hosting services like GitHub to collaborate on projects and share code.
How to store large binary files in git repositories
How to store large binary files in git repositoriesMatt Aunger This document discusses 7 approaches for handling large binary files in Git repositories:
1. Git Annex stores file contents separately from the repository and uses symlinks to reference them. Allows sharing between teams but requires learning new commands.
2. Git Large File Storage (LFS) stores file blobs on a separate server using pointers. Supported by GitHub but requires a custom server.
3. Git-bigfiles aimed to backport large file handling directly into Git but the project is abandoned.
4. Git-fat and Git-media work similarly to LFS using filters and storing files on remote servers like S3. They are older and less actively developed.
5. Git-bigstore and Git
Git and github fundamentals
Git and github fundamentalsRajKharvar Git is an open source distributed version control system (VCS) developed by Linus Torvalds in 2005. Version control allows tracking changes to files over time through commits, enabling recall of specific versions. GitHub is a code hosting platform that allows collaboration on projects remotely using Git. Common Git commands include git init to create a repository, git add to stage files, git commit to save changes, and git push to sync a local repository with a remote one. Pull requests allow proposing and reviewing changes before merging into a main branch like master.
about Debian "squeeze" @201002 OSC Tokyospring
about Debian "squeeze" @201002 OSC TokyospringHideki Yamane The document discusses the upcoming Debian 6.0 release codenamed "Squeeze". It provides details on the development process, expected release timeline in 2010, and highlights some of the new components and packages that will be included such as Linux 2.6.32, GNOME 2.28, KDE 4.3, and Perl 5.10. It also discusses the process for moving packages from testing to stable and addressing release critical bugs.
Git for standalone use
Git for standalone useIkuru Kanuma This document provides an overview of Git and version control systems, including:
- A brief history of Git and how it was created by Linux's original author to be distributed and scale with large projects.
- Explanations of common Git terms and commands like checkout/branch, commit, push, pull, and how the Git repository, index, and workspace interact.
- Instructions for getting Git set up on different operating systems and making the first commit to a new Git project locally or connecting it to a remote repository like GitHub.
用 Go 語言實戰 Push Notification 服務
用 Go 語言實戰 Push Notification 服務Bo-Yi Wu Gorush 是一套用 Go 語言所撰寫的輕量級 Push Notification 服務，除了架設服務外，還可以讓 Android 或 iOS 開發者可以輕鬆使用 Command line 發送訊息給 App。本議程會介紹作者為什麼選用 Go 語言，以及其中的 Go 開發技巧與經驗。
專案網址: https://github.com/appleboy/gorush
How do Centralized and Distributed Version Control Systems Impact Software Ch...
How do Centralized and Distributed Version Control Systems Impact Software Ch...Caius Brindescu The document analyzes how centralized (SVN) and distributed (Git) version control systems impact software changes based on a survey of 820 developers and analysis of 132 repositories. The key findings are:
1) Commits are typically smaller in Git (34% smaller) than SVN due to the ability to commit privately without merging.
2) Developers split changes more often in Git (81% vs 68% for SVN) due to easier commit processes and tools for splitting changes.
3) Developers prefer Git over SVN for its features like private commits, while some prefer SVN out of habit or ease of use.
Git and GitHub
Git and GitHubAshwinRaj57 This document discusses Git and GitHub. It begins by introducing the author and their background. It then covers problems that version control systems solve like maintaining a history of file changes. It describes key concepts of Git like its distributed nature, how it stores data through snapshots instead of file differences, and the three main states files can be in. The document concludes by discussing GitHub and how it builds upon Git to enable collaboration through features like pull requests, issues, and actions.
Terrible Ideas in Git - Corey Quinn, FutureAdvisor - DevOpsDays Tel Aviv 2015
Terrible Ideas in Git - Corey Quinn, FutureAdvisor - DevOpsDays Tel Aviv 2015DevOpsDays Tel Aviv The document discusses both powerful and dangerous things that can be done with Git, such as committing large files or secrets. It recommends tools like git-annex and git-lfs to avoid committing large files directly, and warns not to commit secrets. The document also introduces myrepos and vcsh as tools to manage multiple Git repositories, with myrepos allowing batch updates and vcsh providing a sane directory structure. Overall, the document humorously warns of potential pitfalls with Git while also offering advice and tools to help users leverage Git more safely and effectively.
Github
GithubIFEDAYO ADEYEMI Git is an open-source version control system created by Linus Trovalds that helps users achieve version control and track changes on files. Version control systems like Git allow developers and non-developers to collaborate by downloading, modifying, and uploading new versions of projects. Github builds on Git by providing a platform for developers to store projects in repositories and connect with other developers. Key Github concepts include repositories for storing project files, forking to create new projects from existing ones, and pull requests and change logs for tracking changes made to projects.
Git advanced
Git advancedPeter Vandenabeele git advanced
GitX and other GUI’s
fundamentals
git init, git status, git add -i, git commit
git remote -v, git init --bare
git branch -a, git merge, git rebase -i
git cherry-pick, git log --author
Git and GitHub
Git and GitHubRick Umali A beginner's talk on Git and GitHub. Three main sections: the basics, branching/merging, and collaborating (with GitHub). A funny xkcd comic is used (#1597). Brief mentions of GitHub alternatives (GitLab).
Intro to git
Intro to gitjosh_cutler Git is a distributed version control system that allows for efficient branching and merging. It tracks changes to files and allows multiple users to edit files simultaneously. Users initialize a Git project by creating a hidden .git directory to store change information. They can then add and commit changes, check the status of changes, and view commit logs. Users can also create branches to work in parallel and merge branches together once work is complete. Git enables collaboration through remote repositories hosted on services like GitHub.
Git and GitHub | Concept about Git and GitHub Process | Git Process overview
Git and GitHub | Concept about Git and GitHub Process | Git Process overviewRueful Robin This presentation may help you to know about the version control, git, github and so more. You may get a brief about the whole process of git system.
Viewers also liked (20)
輪るビングドラム.NET
輪るビングドラム.NETbleis tift The document discusses using Jenkins for continuous integration of .NET projects. It recommends installing plugins for Git, MSBuild, NUnit and other tools to integrate them with Jenkins. The Groovy and PowerShell plugins allow adding custom build steps. Overall Jenkins is presented as a good option for continuous integration of .NET projects by automating builds and running tests on each code change.
Jenkins the definitive guide lt(第四回jenkins勉強会)
Jenkins the definitive guide lt(第四回jenkins勉強会)Ryuji Tamagawa This document is about Jenkins, an open source automation server that enables developers to reliably build, test, and deploy their software. It discusses how Jenkins can be used to automate tasks like building Java projects, running tests with tools like JUnit, and deploying code to servers like Amazon EC2, Google App Engine, or Windows Azure. The document also mentions that Jenkins supports integration with version control systems and platforms like Hadoop and can be used to continuously build and test code changes from tools like Git.
Jenkins user conference 2011
Jenkins user conference 2011Kohsuke Kawaguchi The document summarizes Jenkins creator Kohsuke Kawaguchi's 2011 State of the Union address about the progress and future of the Jenkins project. Key points include Jenkins transitioning to a legal entity affiliated with SPI for governance, fundraising efforts, infrastructure donations, adoption statistics continuing to show conversion from Hudson to Jenkins, upcoming improvements to the core and plugins, and thanks to sponsors.
Jenkinsstudy#4kokawa
Jenkinsstudy#4kokawaTakashi Kokawa 第4回Jenkins勉強会
http://kokucheese.com/event/index/16114/
で発表した資料です。
Ruby Plugins for Jenkins
Ruby Plugins for Jenkinscowboyd After almost a year of slow but steady development, the time is soon approaching when you will be able to start writing Jenkins plugins armed with nothing but a simple JRuby environment.
To illustrate exactly what this means, we'll study the anatomy of a Ruby plugin, how it works at runtime, and walk through the creation, testing and deploying of an example using nothing put 100% pure Ruby.
Finally, beyond the mechanical, we'll discuss why this effort is important for the entire Jenkins community, not just the part of the community that uses Ruby.
Jenkins実践入門目次チラ見せしちゃいます
Jenkins実践入門目次チラ見せしちゃいますMasanori Satoh Jenkinsを愛する全ての人に贈る『Jenkins実践入門』 2011年11月11日発売予定! 目次チラ見せしちゃいます。
第四回Jenkins勉強会のLTで発表しました。
Discover The Unknown Flex 4.5 (MAX 2011)
Discover The Unknown Flex 4.5 (MAX 2011)Piotr Walczyszyn This document provides tips and tricks for ActionScript 3 (AS3), Flex, and Flash Builder. It begins with 15 AS3 secrets including short conditional statements, constructors, throwing objects, and more. It then shares 10 Flex secrets such as using ObjectProxy to avoid binding warnings and using states, Reparent, and private metadata tags. The document concludes with 5 Flash Builder secrets like keeping generated ActionScript, using content assist for metadata completion, and the Quick Assist feature.
No011-01-Suc3rum-20100225
No011-01-Suc3rum-20100225Sukusuku Scrum The document discusses the benefits of meditation for reducing stress and anxiety. It notes that meditation can help calm the mind and body by lowering heart rate and easing muscle tension. Regular meditation of 10-20 minutes per day is recommended to experience stress-relieving benefits.
20110118 scrum 10 mins
20110118 scrum 10 minsYasunobu Kawaguchi The document provides an overview of the Scrum framework for agile software development. Some key points include: Scrum is implemented through a series of short "sprints" that typically last 2 weeks; at the end of each sprint a potentially shippable product increment is created; backlogs are used to track work including a prioritized product backlog; roles include the product owner, development team, and scrum master.
Hudson以外の何か with 任意
Hudson以外の何か with 任意bleis tift The document discusses various topics related to continuous integration including:
1. Using Git and Jenkins for continuous integration with commits triggering builds.
2. Various plugins for Jenkins including the Groovy Postbuild Plugin for running Groovy scripts after builds and the Notification Plugin.
3. Methods for running Jenkins on Windows including using Cygwin.
4. The Sakura Script language and using it with the SSTP protocol for notification scripts.
Similar to SCM Boot Camp (20)
Git - Intro to the Basics of DVCS
Git - Intro to the Basics of DVCSMatthew McCullough A quick intro to the basics of the Git source code control system and Distributed Version Control Systems (DVCS)
Git - Intro to the Basics of DVCS
Git - Intro to the Basics of DVCSMatthew McCullough A quick intro to the basics of the Git source code control system and Distributed Version Control Systems (DVCS)
Making the switch to DVCS
Making the switch to DVCSSven Peters This document discusses Atlassian's switch from centralized version control (Subversion) to distributed version control (Git and Mercurial). It provides an overview of the benefits of distributed version control such as increased flexibility and collaboration. It also outlines Atlassian's process for migrating to a distributed system, including bringing over history from the previous centralized system, integrating tools, and using continuous integration. The key benefits that drove Atlassian's switch are cited as increased development speed, more flexible workflows, and being able to code without server limitations.
Version Control History and Git Basics
Version Control History and Git BasicsSreedath N S A 45 minutes presentation slides on Version Control History and Git Basics by
1. Sreedath N S, Devops Engineer, Zesty Beanz Technologies Pvt. Ltd. http://in.linkedin.com/in/sreedathnamangalam
2. Fahad Basheer, Cloud Computing Consultant, Zesty Beanz Technologies Pvt. Ltd. http://in.linkedin.com/in/fahadpv
http://www.zbeanztech.com/
Intro To Git
Intro To Gitkyleburton Source Code Management and Version Control Systems are tools for helping you track your file based assets (typically source code). Traditional SCM systems are centralised (CVS, Subversion, Visual Source Safe), Distributed version control systems systems provide new capabilities, work-flows, are becoming mature and are gaining mind share in the open source community.
Git is one of those Distributed Version Control Systems. It was invented by the creator of Linux (Linus Torvalds) for protecting the Linux kernel source code and coordinating the activity of hundreds of developers. This talk discusses what Distributed Version Control is, the history of Git, basic version control features and some very uncommon and amazing capabilities of git. Time permitting it will include live demonstration of the tools.
Git'in on Windows
Git'in on WindowsStacy Vicknair This speech aims to provide the basics of git, integrating with GitHub and TFS on the Windows platform.
Git Going With DVCS v1.5.2
Git Going With DVCS v1.5.2Matthew McCullough Git is a distributed version control system (DVCS) that provides three main benefits - distributed development, non-linear workflows, and high performance. It uses a fast, efficient file-based database to track changes to files and supports branching, merging, and many non-linear workflows. Git is commonly used for both open source and private projects, with hosting options like GitHub making collaboration and code sharing easy.
Distributed Version Control (DVCS) With Mercurial
Distributed Version Control (DVCS) With MercurialTed Naleid Distributed version control presentation with a focus on Mercurial and it's usage as well as a live-coding section
Distributed Version Control Systems
Distributed Version Control SystemsMihail Stoynov An intro lecture on DVCS given on BGOUG and then on BGJUG. Git and Mercurial (Hg) are shown in the demos
Git training
Git trainingadm_exoplatform This document provides an introduction to GIT. It describes the advantages of GIT over other version control systems like SVN. It explains the basic data model and architecture of GIT including local repositories, branches, and remote repositories. It also covers common GIT commands for configuring, tracking changes, viewing history, sharing changes with others through pushing and pulling. Finally, it provides some tips for using GIT aliases, auto-completion, and external diff/merge tools.
Git! Why? How?
Git! Why? How?Daniel Kummer The document discusses why developers should use Git over Subversion (SVN) for version control, explaining that Git was created by Linus Torvalds as a distributed system that is optimized for workflows like branching, merging, and handling large codebases. It provides an overview of Git's core features like snapshots instead of differences, distributed model instead of centralized server, and various tools that can be used with Git. The document concludes by recommending that the company Namics switch from using SVN to using Git for version control.
Git and git hub
Git and git hubSebastiaan Deckers Git is a version control system that is better than SVN for several reasons:
1. Git allows for cheap and easy local branching so developers can work independently without affecting others.
2. With Git, the entire codebase history is downloaded when cloning a repository, enabling highly responsive local operations and distribution of work.
3. Common Git workflows like the Git Flow process support integration manager and dictator/lieutenant models for code collaboration on GitHub repositories.
Git
GitGayan Kalanamith Mannapperuma Version control systems allow recording changes to files over time. There are local, centralized, and distributed version control systems. Git is a free and open-source distributed version control system created by Linus Torvalds. It provides features like speed, support for non-linear development, and ability to handle large projects efficiently.
Introduce to Git and Jenkins
Introduce to Git and JenkinsAn Nguyen This document provides an introduction to Git and Jenkins. It begins with an overview of Git, covering core concepts like repositories, the index, commits, and branches. It then discusses installing Git and basic usage including configuration, creating repositories, adding and committing files. The document also covers viewing changes and history. It introduces Jenkins, explaining what it is and why it is useful for continuous integration. It outlines Jenkins terminology, architecture, features, plugins and how it can be used to trigger builds, test code, and integrate with source control systems like Git. Finally, it previews a demo of integrating Jenkins with Git.
Git and Github
Git and GithubWen-Tien Chang The document discusses Git and GitHub. It begins with an overview of distributed version control systems (DVCS) like Git and how they differ from centralized version control systems. It then covers the basics of Git, including installing Git, initializing repositories, tracking changes, branching and merging. Finally, it discusses GitHub and how developers can use features like forking, pull requests and wikis to collaborate on projects hosted there. Common Git workflows like Git flow are also introduced.
Version Control Lassosoft 2009 Lasso Developers Conference
Version Control Lassosoft 2009 Lasso Developers ConferenceBrian Loomis This document discusses version control systems and compares centralized and decentralized versions. It provides information on common version control systems like Git, Subversion, CVS, and Mercurial. It highlights key differences between centralized and distributed systems and provides commands to perform common version control tasks in both Git and Subversion.
Git Going With DVCS v1.5.1
Git Going With DVCS v1.5.1Matthew McCullough This document provides an overview of distributed version control systems (DVCS) and introduces the basic usage of Git. It discusses the advantages of DVCS over centralized version control systems, including greater independence, integrity and flexibility to experiment and innovate. The document explains the basic Git commands for creating a repository, making commits, and sharing changes between remote repositories. It also covers some key Git concepts like hashes, the three-stage workflow, and stash for temporarily storing changes.
Brown bag sessions git workshop
Brown bag sessions git workshopBishant Shrestha The document provides an introduction to Git, a distributed version control system. It discusses what Git is, how it tracks changes to files, and its benefits over other version control systems like Subversion. Key features of Git include tracking changes via SHA-1 hashes, supporting distributed and offline development, easy branching and merging, and hosting options like GitHub and BitBucket. Basic Git commands and workflows are also covered.
Why Git Sucks and you'll use it anyways
Why Git Sucks and you'll use it anywaysCarlos Taborda The document discusses the pros and cons of using Git. It acknowledges that Git is complex and unintuitive, but argues people will still use it because distributed version control encourages contributions and experimentation through easy branching. It also notes many popular open source projects use Git. The document then provides a basic overview of how to get started with Git configuration, cloning repositories, committing changes, branching, merging, and interacting with remote repositories on services like GitHub.
Git Basics Philips
Git Basics PhilipsAriejan de Vroom Git is a distributed version control system created by Linus Torvalds that allows for non-linear development with features like very fast branching and merging. The document provides an overview of basic Git commands and concepts including initializing a repository, making commits, branching, merging, tagging, stashing, resolving conflicts, and using Git with Subversion. It also discusses the distributed nature of Git and how it works with local repositories that can be pushed to and pulled from remote repositories.
More from bleis tift (20)
No more Legacy documents
No more Legacy documentsbleis tift NL名古屋での発表資料です。発表ではExcel方眼紙で行いました。これはそれをPDFに変換したものです。
発表に使ったExcelファイルはこちら https://onedrive.live.com/redir?resid=C562DFDEB23518F0!2128&authkey=!ABEB2nl_ZrSQ45Q&ithint=file%2cxlsx
yield and return (poor English ver)
yield and return (poor English ver)bleis tift This document discusses the differences between using yield and return in computation expressions in F#. It presents several implementations of computation expressions to demonstrate how yield and return can be distinguished. The key differences are:
- yield continues the remaining computation expression, while return stops any remaining expressions from executing.
- Several approaches are presented: using exceptions, a state field on the builder, and passing state as an argument. The state argument approach provides a clear separation of yield and return without sharing state between uses of the builder.
- Continuations are also proposed as an implementation, where yield calls the continuation and return discards it. This approach makes the symmetry between yield and return very clear.
yieldとreturnの話
yieldとreturnの話bleis tift クラウド温泉4.0＠小樽 - The Return of F#の発表資料です。
F#のコンピュテーション式のyieldとreturnがどうあるべきかを説明しています。
async/await不要論
async/await不要論bleis tift 並列/並行基礎勉強会での発表資料です。
補足エントリもどうぞ。 http://bleis-tift.hatenablog.com/entry/asyncawaitdis
Recently uploaded (20)
MCP Dev Summit - Pragmatic Scaling of Enterprise GenAI with MCP
MCP Dev Summit - Pragmatic Scaling of Enterprise GenAI with MCPSambhav Kothari MCP Dev Summit Talk By Sambhav Kothari - Head of AI Productivity at Bloomberg.
RDM Training: Publish research data with the Research Data Repository
RDM Training: Publish research data with the Research Data RepositoryCSUC - Consorci de Serveis Universitaris de Catalunya Presentació del curs "Publicar dades de recerca amb el Repositori de Dades de Recerca (en anglès)
Breaking it Down: Microservices Architecture for PHP Developers
Breaking it Down: Microservices Architecture for PHP Developerspmeth1 Transitioning from monolithic PHP applications to a microservices architecture can be a game-changer, unlocking greater scalability, flexibility, and resilience. This session will explore not only the technical steps but also the transformative impact on team dynamics. By decentralizing services, teams can work more autonomously, fostering faster development cycles and greater ownership. Drawing on over 20 years of PHP experience, I’ll cover essential elements of microservices—from decomposition and data management to deployment strategies. We’ll examine real-world examples, common pitfalls, and effective solutions to equip PHP developers with the tools and strategies needed to confidently transition to microservices.
Key Takeaways:
1. Understanding the core technical and team dynamics benefits of microservices architecture in PHP.
2. Techniques for decomposing a monolithic application into manageable services, leading to more focused team ownership and accountability.
3. Best practices for inter-service communication, data consistency, and monitoring to enable smoother team collaboration.
4. Insights on avoiding common microservices pitfalls, such as over-engineering and excessive interdependencies, to keep teams aligned and efficient.
Managing Geospatial Open Data Serverlessly [AWS Community Day CH 2025]![Managing Geospatial Open Data Serverlessly [AWS Community Day CH 2025]](https://cdn.slidesharecdn.com/ss_thumbnails/managinggeospatialopendataserverlesslyawscommunitydaych2025-250521152228-1e59a40c-thumbnail.jpg?width=560&fit=bounds)
Managing Geospatial Open Data Serverlessly [AWS Community Day CH 2025]Chris Bingham At the AWS Community Day 2025 in Dietlikon I presented a journey through the technical successes, service issues, and open-source perils that have made up the paddelbuch.ch story. With the goal of a zero-ops, (nearly) zero-cost system, serverless was the apparent technology approach. However, this was not without its ups and downs!
Reducing Bugs With Static Code Analysis php tek 2025
Reducing Bugs With Static Code Analysis php tek 2025Scott Keck-Warren Have you ever deployed code only to have it causes errors and unexpected results? By using static code analysis we can reduce, if not completely remove this risk. In this session, we'll discuss the basics of static code analysis, some free and inexpensive tools we can use, and how we can run the tools successfully.
TrustArc Webinar: Cross-Border Data Transfers in 2025
TrustArc Webinar: Cross-Border Data Transfers in 2025TrustArc In 2025, cross-border data transfers are becoming harder to manage—not because there are no rules, the regulatory environment has become increasingly complex. Legal obligations vary by jurisdiction, and risk factors include national security, AI, and vendor exposure. Some of the examples of the recent developments that are reshaping how organizations must approach transfer governance:
- The U.S. DOJ’s new rule restricts the outbound transfer of sensitive personal data to foreign adversaries countries of concern, introducing national security-based exposure that privacy teams must now assess.
- The EDPB confirmed that GDPR applies to AI model training — meaning any model trained on EU personal data, regardless of location, must meet lawful processing and cross-border transfer standards.
- Recent enforcement — such as a €290 million GDPR fine against Uber for unlawful transfers and a €30.5 million fine against Clearview AI for scraping biometric data signals growing regulatory intolerance for cross-border data misuse, especially when transparency and lawful basis are lacking.
- Gartner forecasts that by 2027, over 40% of AI-related privacy violations will result from unintended cross-border data exposure via GenAI tools.
Together, these developments reflect a new era of privacy risk: not just legal exposure—but operational fragility. Privacy programs must/can now defend transfers at the system, vendor, and use-case level—with documentation, certification, and proactive governance.
The session blends policy/regulatory events and risk framing with practical enablement, using these developments to explain how TrustArc’s Data Mapping & Risk Manager, Assessment Manager and Assurance Services help organizations build defensible, scalable cross-border data transfer programs.
This webinar is eligible for 1 CPE credit.
John Carmack’s Slides From His Upper Bound 2025 Talk
John Carmack’s Slides From His Upper Bound 2025 TalkRazin Mustafiz Source: https://docs.google.com/presentation/d/1GmGe9ref1nxEX_ekDuJXhildpWGhLEYBMeXCclVECek/edit?usp=sharing
Optimize IBM i with Consulting Services Help
Optimize IBM i with Consulting Services HelpAlice Gray We offers a comprehensive overview of legacy system modernization, integration, and support services. It highlights key challenges businesses face with IBM i systems and presents tailored solutions such as modernization strategies, application development, and managed services. Ideal for IT leaders and enterprises relying on AS400, the deck includes real-world case studies, engagement models, and the benefits of expert consulting. Perfect for showcasing capabilities to clients or internal stakeholders.
Introducing High Availability: Business Continuity for Every NAS User
Introducing High Availability: Business Continuity for Every NAS UserQNAP Marketing Slidedeck for Introducing High Availability: Business Continuity for Every NAS User Webinar hosted by QNAP (May 20, 2025)
"AI in the browser: predicting user actions in real time with TensorflowJS", ...
"AI in the browser: predicting user actions in real time with TensorflowJS", ...Fwdays With AI becoming increasingly present in our everyday lives, the latest advancements in the field now make it easier than ever to integrate it into our software projects. In this session, we’ll explore how machine learning models can be embedded directly into front-end applications. We'll walk through practical examples, including running basic models such as linear regression and random forest classifiers, all within the browser environment.
Once we grasp the fundamentals of running ML models on the client side, we’ll dive into real-world use cases for web applications—ranging from real-time data classification and interpolation to object tracking in the browser. We'll also introduce a novel approach: dynamically optimizing web applications by predicting user behavior in real time using a machine learning model. This opens the door to smarter, more adaptive user experiences and can significantly improve both performance and engagement.
In addition to the technical insights, we’ll also touch on best practices, potential challenges, and the tools that make browser-based machine learning development more accessible. Whether you're a developer looking to experiment with ML or someone aiming to bring more intelligence into your web apps, this session will offer practical takeaways and inspiration for your next project.
Four Principles for Physically Interpretable World Models (poster)
Four Principles for Physically Interpretable World Models (poster)Ivan Ruchkin Presented by:
- Jordan Peper and Ivan Ruchkin at ICRA 2025 https://2025.ieee-icra.org/
- Yuang Geng and Ivan Ruchkin at NeuS 2025 https://neus-2025.github.io/
Paper: https://openreview.net/forum?id=bPAIelioYq
Abstract: As autonomous robots are increasingly deployed in open and uncertain settings, there is a growing need for trustworthy world models that can reliably predict future high-dimensional observations. The learned latent representations in world models lack direct mapping to meaningful physical quantities and dynamics, limiting their utility and interpretability in downstream planning, control, and safety verification. In this paper, we argue for a fundamental shift from physically informed to physically interpretable world models — and crystallize four principles that leverage symbolic knowledge to achieve these ends:
1. Structuring latent spaces according to the physical intent of variables
2. Learning aligned invariant and equivariant representations of the physical world
3. Adapting training to the varied granularity of supervision signals
4. Partitioning generative outputs to support scalability and verifiability.
We experimentally demonstrate the value of each principle on two benchmarks. This paper opens intriguing directions to achieve and capitalize on full physical interpretability in world models.
A simple Introduction to Algorithmic Fairness
A simple Introduction to Algorithmic FairnessPaolo Missier Algorithmic bias and its effect on Machine Learning models.
Simple fairness metrics and how to achieve them by fixing either the data, the model, or both
SQL Database Design For Developers at PhpTek 2025.pptx
SQL Database Design For Developers at PhpTek 2025.pptxScott Keck-Warren Databases are the magic box in a lot of our workflows and in this presentation I show you my rules for better database design
Wondershare Filmora 14.3.2 Crack + License Key Free for Windows PC
Wondershare Filmora 14.3.2 Crack + License Key Free for Windows PCMudasir COPY & PASTE LINK 👉👉👉
https://pcsoftsfull.org/dl
Wondershare Filmora for Windows PC is an all-in-one home video editor with powerful functionality and a fully stacked feature set. Filmora has a simple drag-and-droptop interface, allowing you to be artistic with the story you want to create.
Fully Open-Source Private Clouds: Freedom, Security, and Control
Fully Open-Source Private Clouds: Freedom, Security, and ControlShapeBlue In this presentation, Swen Brüseke introduced proIO's strategy for 100% open-source driven private clouds. proIO leverage the proven technologies of CloudStack and LINBIT, complemented by professional maintenance contracts, to provide you with a secure, flexible, and high-performance IT infrastructure. He highlighted the advantages of private clouds compared to public cloud offerings and explain why CloudStack is in many cases a superior solution to Proxmox.
--
The CloudStack European User Group 2025 took place on May 8th in Vienna, Austria. The event once again brought together open-source cloud professionals, contributors, developers, and users for a day of deep technical insights, knowledge sharing, and community connection.
Eating Our Own Dog Food: How to be taken seriously when it comes to adding va...
Eating Our Own Dog Food: How to be taken seriously when it comes to adding va...UXPA Boston As user experience professionals, we've had a better-than-front-row seat when it comes to understanding the humans who try to use our products, services, and platforms. We've been on or in the field, researching users, gaining deep empathy and insights, and finding how to pull business and user needs together, for the happiest Venn diagram since "you got your chocolate in my peanut butter." We've gotten really good at this. When given some room and runway, we've turned journeys that were fraught with friction into seamless experiences for customers, clients, employees, patients, and so many other kinds of users. There's just one problem. Like the accountant, attorney, marketer, and more, we've been struck —mightily — by the curse of knowledge. We have our own jargon, which has become our seemingly secret internal UX code. We can talk in concepts with each other toward great results but, when we talk to our peers, stakeholders, leadership, and others, we forget to tailor our business and technology to their human needs. So they get lost, confused, and frustrated. In these cases, we're providing a terrible user experience. Eating Our Own Dog Food will give you a more objective way to view, talk about, and show the tremendous value that UX brings to the table, in a way that our users in this circumstance can understand it, be energized by it, and be sure to invite us to "the table."
Is Your QA Team Still Working in Silos? Here's What to Do.
Is Your QA Team Still Working in Silos? Here's What to Do.marketing943205 Often, QA teams find themselves working in silos: the mobile team focused solely on app functionality, the web team on their portal, and API testers on their endpoints, with limited visibility into how these pieces truly connect. This separation can lead to missed integration bugs that only surface in production, causing frustrating customer experiences like order errors or payment failures. It can also mean duplicated efforts, communication gaps, and a slower overall release cycle for those innovative F&B features everyone is waiting for.
If this sounds familiar, you're in the right place! The carousel below, "Is Your QA Team Still Working in Silos?", visually explores these common pitfalls and their impact on F&B quality. More importantly, it introduces a collaborative, unified approach with Qyrus, showing how an all-in-one testing platform can help you break down these barriers, test end-to-end workflows seamlessly, and become a champion for comprehensive quality in your F&B projects. Dive in to see how you can help deliver a five-star digital experience, every time!
I’d like to resell your CloudStack services, but...
I’d like to resell your CloudStack services, but...ShapeBlue In this session, Brian Turnbow went over the process and challenges faced onboarding a whitelabel reseller into their CloudStack offering. What happens when a potential customer wants to use his own IP addresses and bandwidth, his ecommerce and his brand name?
--
The CloudStack European User Group 2025 took place on May 8th in Vienna, Austria. The event once again brought together open-source cloud professionals, contributors, developers, and users for a day of deep technical insights, knowledge sharing, and community connection.
RDM Training: Publish research data with the Research Data Repository
RDM Training: Publish research data with the Research Data RepositoryCSUC - Consorci de Serveis Universitaris de Catalunya
SCM Boot Camp
- 1. SCM Boot Camp bleis-tift July 30, 2011
- 2. id:bleis-tift / @bleis F# Git Git
- 3. Git-Hooks Git https://github.com/bleis-tift/Git-Hooks rewrite ( )
- 5. Reject
- 6. Geek Bar (bleis hook )
- 7. rewrite
- 8. SVN Git
- 13. .zip .zip
- 16. 1 SCM Boot Camp SCM Boot Camp
- 18. Git Mercurial
- 20. Git Git VCS or
- 21. (CVS) (Git) (SVN/HG/BZR)
- 23. (SVN ) (Git)
- 27. (VSS) ( )
- 28. VS
- 29. or (SVN) (Git/HG) (BZR)
- 31. DVCS commit DVCS
- 34. commit
- 35. commit
- 36. DVCS DVCS
- 37. better DVCS SVN DVCS Git
- 38. ( ) DVCS
- 39. DVCS DVCS
- 40. DVCS
- 41. hoge DVCS
- 43. rebase
- 44. rebase
- 45. rebase rebase DVCS
- 46. rebase rebase DVCS
- 47. rebase
- 49. BTS/ITS rebase BTS/ITS
- 50. SVN
- 51. SVN SVN
- 52. SVN svn
- 53. SVN DVCS clone
- 77. SVN DVCS (clone push pull)
- 78. SVN DVCS (clone push pull)
- 79. SVN DVCS (clone push pull)
- 80. SVN DVCS (clone push pull)
- 81. SVN DVCS (clone push pull)
- 82. SVN DVCS (clone push pull)
- 83. SVN DVCS (clone push pull)
- 84. SVN DVCS (clone push pull)
- 85. SVN DVCS (clone push pull)
- 86. SVN DVCS push Git http://d.hatena.ne.jp/pasela/20110216/git not pushed
- 88. SVN DVCS Mercurial Bazaar
- 89. SVN DVCS SVN SVN SVN DVCS
- 91. DVCS DVCS
- 95. Jenkins CI push 1 push 2 push 3 push . push CI . . ..
- 96. Jenkins
- 97. Jenkins 5 1 5