blob: 01278e789f31005325dec34baa9eb1314731267f (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
|
#!/usr/bin/env groovy
//Jenkinsfile (Declarative Pipeline)
// Where they differ however is in syntax and flexibility. Declarative limits what is available to the user with a more strict and pre-defined structure, making it an ideal choice for simpler continuous delivery pipelines. Scripted provides very few limits, insofar that the only limits on structure and syntax tend to be defined by Groovy itself, rather than any Pipeline-specific systems, making it an ideal choice for power-users and those with more complex requirements
//e5-build-gentoo-cross1
//e5-build-gentoo-x86-1
//e5-build-gentoo-x86_64-1
pipeline {
agent any
stages {
stage('Build x86_64 GCC') {
agent {
label 'e5-build-gentoo-x86_64-1'
}
steps {
sh '.ci/ci-linux-build.sh'
}
}
}
}
pipeline {
agent any
stages {
stage('Build x86 GCC') {
agent {
label 'e5-build-gentoo-x86-1'
}
steps {
sh '.ci/ci-linux-build.sh'
}
}
}
}
/* stages {
stage('Build misc') {
agent any
steps {
parallel(
one: {
sh '.ci/ci-linux-build-misc.sh'
},
two: {
sh '.ci/ci-linux-build-wayland.sh'
}
)
}
}
}
}
stage('Build x86 Clang') {
agent {
label 'e5-build-gentoo-x86-1'
}
environment {
CC = 'clang'
}
steps {
sh '.ci/ci-linux-build.sh'
}
}
stage('Build x86_64 Clang') {
agent {
label 'e5-build-gentoo-x86_64-1'
}
environment {
CC = 'clang'
}
steps {
sh '.ci/ci-linux-build.sh'
}
} */
|
