Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
b8fba958
Commit
b8fba958
authored
May 19, 2017
by
Rémy Coutable
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix some conflicts
Signed-off-by:
Rémy Coutable
<
remy@rymai.me
>
parent
00df1306
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
0 additions
and
51 deletions
+0
-51
.gitlab-ci.yml
.gitlab-ci.yml
+0
-7
doc/ci/pipeline_schedules.md
doc/ci/pipeline_schedules.md
+0
-44
No files found.
.gitlab-ci.yml
View file @
b8fba958
...
...
@@ -422,14 +422,7 @@ gitlab:assets:compile:
paths
:
-
webpack-report/
<<<<<<< HEAD
rake karma
:
=======
karma
:
cache
:
paths
:
-
vendor/ruby
>
>>>>>>
origin/master
stage
:
test
<<
:
*use-pg
<<
:
*dedicated-runner
...
...
doc/ci/pipeline_schedules.md
deleted
100644 → 0
View file @
00df1306
# Pipeline Schedules
> **Note**:
-
This feature was introduced in 9.1 as
[
Trigger Schedule
][
ce-105533
]
-
In 9.2, the feature was
[
renamed to Pipeline Schedule
][
ce-10853
]
Pipeline schedules can be used to run pipelines only once, or for example every
month on the 22nd for a certain branch.
## Using Pipeline Schedules
In order to schedule pipelines, navigate to your their pages
**Pipelines ➔ Schedules**
and click the
**New Schedule**
button.
![
New Schedule Form
](
img/pipeline_schedules_new_form.png
)
After entering the form, hit
**Save Schedule**
for the changes to have effect.
You can check a next execution date of the scheduled trigger, which is automatically calculated by a server.
## Taking ownership
![
Schedules list
](
img/pipeline_schedules_list.png
)
Pipelines are executed as a user, which owns a schedule. This influences what
projects and other resources the pipeline has access to. If a user does not own
a pipeline, you can take ownership by clicking the
**Take ownership**
button.
The next time a pipeline is scheduled, your credentials will be used.
> **Notes**:
-
Those pipelines won't be executed precicely. Because schedules are handled by
Sidekiq, which runs according to its interval. For exmaple, if you set a schedule to
create a pipeline every minute (
`* * * * *`
) and the Sidekiq worker performs 00:00
and 12:00 o'clock every day (
`0 */12 * * *`
), only 2 pipelines will be created per day.
To change the Sidekiq worker's frequency, you have to edit the
`trigger_schedule_worker_cron`
value in your
`gitlab.rb`
and restart GitLab. The Sidekiq worker's configuration
on GiLab.com is able to be looked up at
[
here
](
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/config/gitlab.yml.example#L185
)
.
-
Cron notation is parsed by
[
Rufus-Scheduler
](
https://github.com/jmettraux/rufus-scheduler
)
.
-
When the owner of the schedule does not have the ability to create pipelines
anymore, due to e.g. being blocked or removed from the project, the schedule is
deactivated. Another user can take ownership and activate it, so the schedule is
run again.
[
ce-10533
]:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10533
[
ce-10853
]:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10853
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment