tkl/tex-framework
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

release howto for pike blue

Browse Source
This commit is contained in:
Thomas Klaehn 2016-12-08 13:16:15 +01:00
parent b8e8949aa9
commit e387bc1bab
1 changed files with 27 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

48
content.tex
View File

@ -1,39 +1,45 @@
\section*{Agricola Release HowTo} \section*{Pike Blue Release HowTo}
\subsection*{Create release branch} \subsection*{Internal release}
A push event to a \textit{release/...} named branch will create release A push event to a \textit{release/...} named branch will create release
candidates. These release candidates are deployed to agricola's project svn. candidates. These release candidates are deployed to the pike blue project svn
(\texttt{http://dabsvn01.internal.novero.com/svn/\ \\ repository (\texttt{http://dabsvn01.internal.novero.com/svn/\ \\
0\_31X\_P0070\_agricola/trunk/development/software/\ \\ 0\_31X\_P0610\_pike\_blue/trunk/development/software/\ \\
releases/release\_candidate/})\\ releases/release\_candidate/}).\\
The branch can be created eiter by gitlab ui or locally.
\subsubsection*{Local}
Checkout the new release branch: Checkout the new release branch:
\lstsetbash
\begin{lstlisting} \begin{lstlisting}
git checkout -b release/<release_name> git checkout -b release/<release_name>
\end{lstlisting} \end{lstlisting}
Prepare build variables in the \textit{variables} section of the build job Prepare build variables in the \textit{variables} section of the build job
file\\(\texttt{.gitlab-ci.yml} in agricola's root directory). file\\(\texttt{.gitlab-ci.yml} in pike blue's root directory).
\begin{lstlisting} \begin{lstlisting}
variables: variables:
PRODUCT_NAME: "AG" PRODUCT_NAME: "PI"
PRODUCT_VARIANT: "NA" PRODUCT_VARIANT: "CX"
# PRODUCT_VARIANT: "EU" PROJECT_VERSION: "20"
# PRODUCT_VARIANT: "CN"
PROJECT_VERSION: "10"
SW_MAJOR: "1" SW_MAJOR: "1"
SW_MINOR: "2" SW_MINOR: "0"
\end{lstlisting} \end{lstlisting}
Push the new branch to the gitlab-server: Push the new branch to the gitlab-server:
\begin{lstlisting} \begin{lstlisting}
git push --set-upstream origin release/<release_name> git push -u origin release/<release_name>
\end{lstlisting} \end{lstlisting}
\subsection*{Create release tag} \subsection*{External release}
A \textit{release/174\_AG...} named tag in the agricola repository at the A \textit{release/\_PI\_CX\_20...} named tag in the pike blue repository at the
gitlab server will create a release and deploys it to the agricola project gitlab server will create a release and deploys it to the pike blue project
svn repository. To create the tag: svn repository (\texttt{http://dabsvn01.internal.novero.com/svn/\ \\
0\_31X\_P0610\_pike\_blue/trunk/development/software/\ \\
releases/release/}).\\
The tag can be created eiter by gitlab ui or locally.
\subsubsection{Gitlab UI}
To create the tag:
\begin{itemize} \begin{itemize}
\item go to agricola's gitlab tags section \\ \item go to the pike blue gitlab tags section \\
(\texttt{https://novgit05.novero.com/agricola/agricola/tags}) (\texttt{https://novgit05.novero.com/Pike/Blue/tags})
\item Hit the \textit{+ New tag} button \item Hit the \textit{+ New tag} button
\item Choose a valid tag name \textit{(release/174\_AG...)} \item Choose a valid tag name \textit{(release/PI\_CX\_20...)}
\item Choose the above created release branch as source for the new tag. \item Choose the above created release branch as source for the new tag.
\item Hit the \textit{Create tag} button \item Hit the \textit{Create tag} button
\end{itemize} \end{itemize}