Differences

This shows you the differences between two versions of the page.

--- tech:devops:start [2015/11/23 16:09]
rk4n3
+++ tech:devops:start [2018/11/11 21:14] (current)
rk4n3
@@ Line 1: / Line 1: @@
-====== Software Development and Deployment Topics ======
+<typo fs:xx-large; fw:bold>DevOps</typo>
+====== Trivia of Technique ======
-===== Revision Control: git =====
+==== JWT ====
+=== Create a JWT Key ===
+''openssl rand -base64 32''
+====== Practices & Deployment Topics ======
 Mature revision control workflow uses some branching conventions combined with some access policies to ensure that work being done in parallel by a number of developers can proceed with a minimum of collision-caused trouble, and with maximum safety.
+===== Continuous Integration =====
+==== Jenkins ====
+[[tech:devops:jenkins:start|Jenkins topics]]
+==== Maven ====
+[[tech:devops:maven:start|Maven topics]]
+==== Archiva ====
+[[tech:devops:archiva:start|Archiva topics]]
+==== JMeter ====
+[[tech:devops:jmeter:start|JMeter topics]]
+==== Gatling ====
+[[tech:devops:gatling:start|Gatling topics]]
+===== Revision Control: git (self-hosted) =====
+==== Git Usage ====
+[[tech:devops:git|Basic usage, cheatsheet, tips, and tricks for git]]
 ==== Repositories ====
 In this proposal, there are three tiers of repository:
@@ Line 61: / Line 79: @@
 {{ :tech:devops:git-practices-01.png?nolink&640 |}}
+===== Revision Control: github =====
+The [[http://www.github.org|github]] hosting platform operates similarly to the above //self-hosted// scheme, with some differences that makes sense to github's free software community sensibilities.
+==== Details: under construction ====
+==== New branches created in upstream repo ====
+You may want a new branch, created in upstream repo, populated into your fork of that repo and your local clone(s) of your fork of that repo, so that you can work on the new branch, or at least see it.  With GitHub, this isn't as trivial as natively-stored repos.
+First, you'll need to make sure your local clone of your repo fork knows about its upstream:
+<code>git remote add upstream https://github.com/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git</code>
+Then, you'll need to make sure the new upstream branch is pulled into your local clone:
+  * Ensure your working tree is clean (commit/stash/revert any changes), then, do: \\ ''git fetch upstream''
+  * Create and switch to a local version of the new upstream branch //(which is named newbranch in this example)//: \\ ''git checkout -b newbranch upstream/newbranch''
+  * When you're ready, push the new branch to origin: \\ ''git push -u origin newbranch'' \\ // The -u switch sets up tracking to the specified remote (in this example, origin) //
+==== Trivia ====
+ \\
+ \\
+// Links: [[tech:start|Tech Info]] ... [[tech:linux:start|Linux Info]] // \\

Albert Lea Data Wiki

User Tools

Site Tools

Differences

Page Tools