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
0
Merge Requests
0
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
Jérome Perrin
gitlab-ce
Commits
c15dc455
Commit
c15dc455
authored
Aug 19, 2016
by
Grzegorz Bizon
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Move and improvement comment in pipeline fixtures
parent
7450fe78
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
5 deletions
+4
-5
db/fixtures/development/14_pipelines.rb
db/fixtures/development/14_pipelines.rb
+4
-5
No files found.
db/fixtures/development/14_pipelines.rb
View file @
c15dc455
...
@@ -74,6 +74,10 @@ class Gitlab::Seeder::Pipelines
...
@@ -74,6 +74,10 @@ class Gitlab::Seeder::Pipelines
.
merge
(
commands:
'$ build command'
)
.
merge
(
commands:
'$ build command'
)
Ci
::
Build
.
create!
(
attributes
).
tap
do
|
build
|
Ci
::
Build
.
create!
(
attributes
).
tap
do
|
build
|
# We need to set build trace and artifacts after saving a build
# (id required), that is why we need `#tap` method instead of passing
# block directly to `Ci::Build#create!`.
setup_artifacts
(
build
)
setup_artifacts
(
build
)
setup_build_log
(
build
)
setup_build_log
(
build
)
build
.
save
build
.
save
...
@@ -93,11 +97,6 @@ class Gitlab::Seeder::Pipelines
...
@@ -93,11 +97,6 @@ class Gitlab::Seeder::Pipelines
end
end
def
setup_build_log
(
build
)
def
setup_build_log
(
build
)
##
# We need to set build trace after saving a build (id required)
# That is why we need `#tap` method instead of passing block
# directly to `Ci::Build#create!`.
#
if
%w(running success failed)
.
include?
(
build
.
status
)
if
%w(running success failed)
.
include?
(
build
.
status
)
build
.
trace
=
FFaker
::
Lorem
.
paragraphs
(
6
).
join
(
"
\n\n
"
)
build
.
trace
=
FFaker
::
Lorem
.
paragraphs
(
6
).
join
(
"
\n\n
"
)
end
end
...
...
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