Of metacello, git, scripting and things

Of Metacello, Git, Scripting and Things

ESUG 2012Dale Henrichs

VMware

Thursday, September 20, 2012

“It is not sufficient to manage Smallatlk source files in git ...

for Smalltalk we need to manage package structure”

Dale Henrichsbefore January 2012


“We've built a little package [FileTree] that allows us to save all our source in git.

...In short, we save and load all the monticello packages on our project as smalltalk source files. We use git to merge and not

monticello....

We are 5-6 developers on the project, committing numerous times a day. We currently have about 1100 classes and 23500

methods managed in this way.”

Otto BehrensJanuary 2012

http://forum.world.st/Smalltalk-for-small-projects-only-tt4336237.html#a4339381


http://forum.world.st/Smalltalk-for-small-projects-only-tt4336237.html#

http://forum.world.st/Smalltalk-for-small-projects-only-tt4336237.html#

FileTree directory structure


What is Git?

• Disk-based, Distributed Version Control System for source code

• `Clone` repository to local disk for off-line work

• Each `clone` is a complete copy of repository

• Merge changes to/from any other `clone`


“Git really changed the way developers think of merging and branching.

...merging/branching has always been considered a bit scary

...with Git, these actions are extremely cheap and simple, and they

are considered one of the core parts of your daily workflow”

A successful Git branching model “Git-Flow” January 2010

Vincent Driessenhttp://nvie.com/posts/a-successful-git-branching-model/

Why Git?


http://nvie.com/posts/a-successful-git-branching-model/


A successful Git branching model“Git-Flow” January 2010

Vincent Driessenhttp://nvie.com/posts/a-successful-git-branching-model/

Git-Flow




Why Git?

Git makes it possible to leverage GitHub’s most excellent tools.


“[Git-Flow is] more complicated than I think most developers and development teams actually require”

GitHub FlowAugust 2011

Scott Chaconhttp://scottchacon.com/2011/08/31/github-flow.html


http://scottchacon.com/2011/08/31/github-flow.html


GitHub Flow

• Use named branches off master for all development

• use PULL request to review and merge work into master branch

• deploy as soon as you merge into the master branch

GitHub FlowAugust 2011

Scott Chaconhttp://scottchacon.com/2011/08/31/github-flow.html




GitHub: Pull Request

https://github.com/github/github-services/pull/377




GitHub: Pull Request



https://github.com/github/github-services/pull/373#issuecomment-7586837


GitHub: Commit Comments





GitHub: Pull Request Comments


GitHub: Commit Comments




TravisCI automatically runs build against Pull Rquests

https://github.com/dalehenrich/builderCI/pull/14




GitHub: continuous integration w/Travis CI

http://travis-ci.org/#!/dalehenrich/builderCI/builds/2205547




Sample TravisCI log

http://travis-ci.org/#!/dalehenrich/builderCI/jobs/2205548




travisCI.st for Sample project

https://github.com/dalehenrich/sample/blob/master/tests/baselineTravisCI.st




Why Git for Smalltalk?

Git can bring sophisticated branch-based workflow to Smalltalk without having to build it from scratch!


Git/GitHub Ecosystem• Cypress

• Cross-dialect package structure

• FileTree

• Monticello integration w/Git

• MetacelloPreview

• filetree:// and github:// repo types

• BaselineOf and ConfigurationOf

• Scripting APIThursday, September 20, 2012

Cypress

“The goal of the Cypress project is to have a version controlled environment for cross-dialect projects.

We do not aim to replace existing dialect solutions.”

https://github.com/CampSmalltalk/Cypress


https://github.com/CampSmalltalk/Cypress/blob/master/README.md


https://github.com/CampSmalltalk/Cypress/blob/master/img/CypressStructure-STIC2012.png

Cypress spec




Cypress implementations

• Amber (amber-cypress)

• Cuis (cuis-cypress)

• GemStone (FileTree)

• Pharo (FileTree)

• Squeak (FileTree)

• VW (STIG)

https://github.com/CampSmalltalk/Cypress#cypress-implementations




FileTree

FileTree is a fully functional Monticello repository type where packages are stored in Cypress format instead

of .mcz fomat.

FileTree is SCM neutral and can be used with git, mercurial, svn, etc.

https://github.com/dalehenrich/filetree




filetree://

filetree:// <path>

filetree:///opt/git/filetree/packages


github://github:// <user> / <project> [ : <SHA> ] [ / <path> ]

github://dalehenrich/filetree:master/packages github://dalehenrich/filetree:1.0/packages github://dalehenrich/filetree:a772ac2ecc/packages


https://github.com/dalehenrich/builderCI/commit/a772ac2ecc4c700fdfb4fc63d24b2ade929199da

https://github.com/dalehenrich/builderCI/commit/a772ac2ecc4c700fdfb4fc63d24b2ade929199da

BaselineOf

single #baseline: method in the BaselinOf class


ConfigurationOf

Metacello version numbers become tags for git commits


Scripting APIInvented API to replace the “standard” load expression:

with this expression:


Current Status

• Metacello class for scripts will be included in base images for Pharo2.0 and Squeak4.4.

• MetacelloPreview 1.0-beta.32.2

• looking for a few git savvy users to use the preview release

• FsGit

• in-image support for Git


Resources/Questions

mailing list: http://groups.google.com/group/metacellopreview installation & docs: https://github.com/dalehenrich/metacello-work/blob/master/README.md

Metacello Dr. will be IN today and ThursdayAll questions will be answered!


http://groups.google.com/group/metacello

http://groups.google.com/group/metacello

https://github.com/dalehenrich/metacello-work/blob/master/README.md

https://github.com/dalehenrich/metacello-work/blob/master/README.md

Of metacello, git, scripting and things

Technology

github flowaugust

masterpackages github

git commitsthursday

github flow use

model gitflow

git savvy users

daily workowa successful

cypress project