More information about the voting process is below. 3.30pm Friday - Everyone votes to select the best project.Everyone gets three minutes to present their project. 2pm Friday - Presentations start in a number of locations.12pm Friday - Organiser and a couple of helpers start to arrange voting sheets and presentation areas.10am Friday - Organiser reminds everyone to take screenshots or videos of their work in progress, in case it breaks at the last minute.The majority, more sensible people, go home to get some rest. Overnight Thursday - A few dedicated participants sometimes keep working on their projects overnight.There's a great buzz in the office when everyone gets together to discuss their projects and how far they've come in the first five or six hours. 6-7pm Thursday - Dinner is provided by the company for those who are working late.In the Sydney office now, the organiser usually just sends an email. When we were smaller, everyone used to get together for a quick kick-off announcement. Some time prior - Participants are expected to write up their "shipment orders" – a short document describing their project, the reason they're doing it, and how much they expect to achieve in a day.One week prior - Second "brown bag" meeting.Two weeks prior to ShipIt Day - First "brown bag" (lunchtime) meeting to brainstorm and discuss ideas.From there, the process in our head office in Sydney looks like something this: An organiser is appointed (more on that below) and picks a date after consulting with the engineering managers. Preparation normally starts three or four weeks before we want to hold a ShipIt Day. Log pending commits (diff between HEAD and currently deployed revision) to console.What is the timeline for a typical ShipIt Day?.The current symlink path : path.join(, 'current'). The complete release path : path.join(shipit.releasesPath, shipit.releaseDirname). shipit.releasesPathĪttached during deploy:init, rollback:init, and pending:log tasks. The current release dirname of the project, the format used is "YYYYMMDDHHmmss" (moment format). shipit.releaseDirnameĪttached during deploy:update and rollback:init task. You can manipulate the repository using git command, the API is describe in gift. Several variables are attached during the deploy and the rollback process: nfig.*Īll options described in the config sections are available in the nfig object. Parameter to pass to cp to copy the previous release. For example /d/tmp/workspace if your workspace is located in d:\tmp\workspace.īy default, it will run rsync from the workspace folder. When deploying from Windows, prepend the workspace path with the drive letter. Used to display revision diffs in pending task. gitConfigĬustom git configuration settings for the cloned repo. Number of releases to keep on the remote server. Whether or not to delete the old release when rolling back to a previous release. These paths are used in the rsync command. branchĪn array of paths that match ignored files. In edge cases like quick PoC projects without a repository or a living on the edge production patch applying this can be helpful. If empty Shipit will try to deploy without pulling the changes. A symlink current is linked to the current release. A directory releases is automatically created. deployToĭefine the remote path where the project will be deployed. dirToCopyĭefine directory within the workspace which should be deployed. Beware to not set this path to the root of your repository as shipit-deploy cleans the directory at the given path as a first step. Define a path to an empty directory where Shipit builds it's syncing source.
0 Comments
Leave a Reply. |