-
Notifications
You must be signed in to change notification settings - Fork 15
/
Copy pathcreateTaskJIRAs.py.examples_44x.txt
129 lines (89 loc) · 5.12 KB
/
createTaskJIRAs.py.examples_44x.txt
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
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
cd ~/tru/jbosstools-build-ci/util
python createTaskJIRAs.py --jbide 4.4.1.Alpha1 --jbds 10.1.0.Alpha1 \
--task "Prepare for 4.4.1.Alpha1" --taskfull "Please perform the following tasks:
1. Check out your existing *{color:orange}master{color}* branch:
{code}
git checkout master
{code}
2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.1.Alpha1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0)
{code}
mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT
{code}
4. Close (do not resolve) this JIRA when done.
" \
-s https://issues.jboss.org \
-u nickboldt \
-p \
PASSWORD
############################################################################################################
cd ~/tru/jbosstools-build-ci/util
python createTaskJIRAs.py --jbide 4.4.0.Final --jbds 10.0.0.GA \
--task "Prepare for Final/GA" --taskfull "Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA
[Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE%22%20and%20fixVersion%20in%20%284.4.0.Final%2C4.4.0.Final%29%29%20or%20%28project%20%3D%20%22JBDS%22%20and%20fixversion%20in%20%2810.0.0.GA%2C10.0.0.GA%29%29%29%20and%20resolution%20%3D%20Unresolved]
1. Check out your existing *{color:blue}jbosstools-4.4.x{color}* branch:
{code}
git checkout jbosstools-4.4.x
{code}
2. Update your *{color:blue}jbosstools-4.4.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.4.0.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.0.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0)
{code}
mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0)
{code}
mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT
{code}
4. Close (do not resolve) this JIRA when done.
5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE%22%20and%20fixVersion%20in%20%284.4.0.Final%2C4.4.0.Final%29%29%20or%20%28project%20%3D%20%22JBDS%22%20and%20fixversion%20in%20%2810.0.0.GA%2C10.0.0.GA%29%29%29%20AND%20resolution%20is%20null%20AND%20%28labels%20%3D%20new_and_noteworthy%20OR%20summary%20~%20%22New%20and%20Noteworthy%20for%20%22%29] to do, please complete them next.
" \
-s https://issues.jboss.org \
-u nickboldt \
-p \
PASSWORD
############################################################################################################
As of jbosstools 4.4.1.Final / 4.4.2.AM1, you can use these jobs to perform the above steps, including sending emails to project leads to speed up the branching and root pom repairs:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbosstools-releng/job/jbosstools-releng-parent-pom-update-and-branch-task-jiras/
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbosstools-releng/job/jbosstools-releng-parent-pom-update-task-jiras/
############################################################################################################
Create task jiras for ui plugins as deps of core ones:
# create console log summary files
# run in a given jbosstools-* git checkout folder
p=$(pwd); p=${p##*/}; mvn clean install -DskipTests | \
tee ~/Screenshots/${p}-log.txt && cat ~/Screenshots/${p}-log.txt | \
egrep -B1 "\[CoreUIDependency\]| > " | grep -v "failed" | \
tee ~/Screenshots/${p}-log-coreui.txt
# rename console log files to match JIRA component names (as required, eg., for vpe => visual-page-editor-core, javaee => cdi, base => common)
# create JIRAs
for c in central common cdi visual-page-editor-core \
hibernate webservices server; do \
file="$(cat ~/Screenshots/coreui/jbosstools-${c}-log-coreui.txt)"; \
python createTaskJIRAs.py -s https://issues.stage.jboss.org -u USER -p PWD \
-i 4.4.2.AM3 -d 10.2.0.AM3 \
-t "UI dependencies from Core plugins" \
-f "The following core plugins depend on UI plugins directly or indirectly. {code}${file}{code}" \
-c ${c} -A; \
done