You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by zh...@apache.org on 2020/10/19 09:36:11 UTC
[hbase] branch HBASE-25194 updated (a9669b5 -> d7463e9)
This is an automated email from the ASF dual-hosted git repository.
zhangduo pushed a change to branch HBASE-25194
in repository https://gitbox.apache.org/repos/asf/hbase.git.
discard a9669b5 fix scripts
discard 0daaccd fix archiveArtifacts
discard 5528145 fix script
new d7463e9 remove env as not sure how it works
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (a9669b5)
\
N -- N -- N refs/heads/HBASE-25194 (d7463e9)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
dev-support/flaky-tests/flaky-reporting.Jenkinsfile | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
[hbase] 01/01: remove env as not sure how it works
Posted by zh...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
zhangduo pushed a commit to branch HBASE-25194
in repository https://gitbox.apache.org/repos/asf/hbase.git
commit d7463e936cee515022c66bf09350aaebfe19ef4d
Author: Duo Zhang <zh...@apache.org>
AuthorDate: Mon Oct 19 17:34:48 2020 +0800
remove env as not sure how it works
---
dev-support/flaky-tests/flaky-reporting.Jenkinsfile | 11 ++++-------
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/dev-support/flaky-tests/flaky-reporting.Jenkinsfile b/dev-support/flaky-tests/flaky-reporting.Jenkinsfile
index cbd41b5..99214e9 100644
--- a/dev-support/flaky-tests/flaky-reporting.Jenkinsfile
+++ b/dev-support/flaky-tests/flaky-reporting.Jenkinsfile
@@ -31,9 +31,6 @@ pipeline {
parameters {
booleanParam(name: 'DEBUG', defaultValue: false, description: 'Produce a lot more meta-information.')
}
- environment {
- OUTPUT_DIR_RELATIVE_REPORT = "output-report"
- }
stages {
stage ('build flaky report') {
steps {
@@ -46,8 +43,8 @@ pipeline {
flaky_args=("${flaky_args[@]}" --urls "${JENKINS_URL}/job/HBase/job/HBase%20Nightly/job/master" --is-yetus True --max-builds 10)
flaky_args=("${flaky_args[@]}" --urls "${JENKINS_URL}/job/HBase/job/HBase-Flaky-Tests/job/master" --is-yetus False --max-builds 30)
docker build -t hbase-dev-support dev-support
- docker run --ulimit nproc=12500 -v "${WORKSPACE}":/hbase --workdir=/hbase hbase-dev-support \
- python dev-support/flaky-tests/report-flakies.py --mvn -v -o ${OUTPUT_DIR_RELATIVE_REPORT} "${flaky_args[@]}"
+ docker run --ulimit nproc=12500 -v "${WORKSPACE}":/hbase -u `id -u`:`id -g` --workdir=/hbase hbase-dev-support \
+ python dev-support/flaky-tests/report-flakies.py --mvn -v -o output "${flaky_args[@]}"
'''
}
}
@@ -55,13 +52,13 @@ pipeline {
post {
always {
// Has to be relative to WORKSPACE.
- archiveArtifacts artifacts: "${OUTPUT_DIR_RELATIVE_REPORT}/includes,${OUTPUT_DIR_RELATIVE_REPORT}/excludes,${OUTPUT_DIR_RELATIVE_REPORT}/dashboard.html"
+ archiveArtifacts artifacts: "output/*"
publishHTML target: [
allowMissing: true,
keepAll: true,
alwaysLinkToLastBuild: true,
// Has to be relative to WORKSPACE
- reportDir: ${OUTPUT_DIR_RELATIVE_REPORT},
+ reportDir: "output",
reportFiles: 'dashboard.html',
reportName: 'Flaky Test Report'
]