Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
frama-c
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container Registry
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
pub
frama-c
Commits
bee3756c
Commit
bee3756c
authored
5 years ago
by
François Bobot
Committed by
David Bühler
5 years ago
Browse files
Options
Downloads
Patches
Plain Diff
[release] Updates release doc: creates branch stable/release by using frama-ci.
parent
bfefa440
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/release/branch.tex
+13
-2
13 additions, 2 deletions
doc/release/branch.tex
with
13 additions
and
2 deletions
doc/release/branch.tex
+
13
−
2
View file @
bee3756c
...
@@ -22,8 +22,19 @@ $\rightarrow$ Repository $\rightarrow$ Protected Branches.
...
@@ -22,8 +22,19 @@ $\rightarrow$ Repository $\rightarrow$ Protected Branches.
\section
{
Creating the branch
}
\section
{
Creating the branch
}
Create the branch
\texttt
{
stable/release
}
where
\texttt
{
release
}
is the
Create the branch
\texttt
{
stable/release
}
where
\texttt
{
release
}
is the
element name.
element name using
\texttt
{
frama-ci-create-branch
}
tool:
\begin{enumerate}
\item
Install
\texttt
{
frama-ci
}
tools:
\begin{shell}
opam pin add frama-ci-tools git@git.frama-c.com:frama-c/Frama-CI.git
\end{shell}
\item
Create an API token for gitlab, in your gitlab profile settings
\item
Run the command
\begin{shell}
frama-ci-create-branch --token=
\$
TOKEN
\
--new-branch=stable/release --default-branch
\end{shell}
\end{enumerate}
What can be committed in this branch must follow the release schedule,
What can be committed in this branch must follow the release schedule,
and go through Merge-requests. Everything else should go in
\texttt
{
master
}
,
and go through Merge-requests. Everything else should go in
\texttt
{
master
}
,
which can then be reset to standard-level protection (Developers + Masters
which can then be reset to standard-level protection (Developers + Masters
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment