hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-20162) [nightly] depending on pipeline execution we sometimes refer to the wrong workspace
Date Fri, 09 Mar 2018 23:44:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-20162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393820#comment-16393820

Hudson commented on HBASE-20162:

SUCCESS: Integrated in Jenkins build HBase-1.2-IT #1084 (See [https://builds.apache.org/job/HBase-1.2-IT/1084/])
HBASE-20162 [nightly] depending on pipeline execution we sometimes refer (busbey: rev d317aa4a10df19a106f837d98a4bfcf7938ba255)
* (edit) dev-support/hbase_nightly_yetus.sh
* (edit) dev-support/Jenkinsfile

> [nightly] depending on pipeline execution we sometimes refer to the wrong workspace
> -----------------------------------------------------------------------------------
>                 Key: HBASE-20162
>                 URL: https://issues.apache.org/jira/browse/HBASE-20162
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 2.0.0, 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.3.3, 1.4.3
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Critical
>             Fix For: 2.0.0, 3.0.0, 2.1.0, 1.5.0, 1.3.3, 1.2.8, 1.4.3
>         Attachments: HBASE-20162.0.patch
> we set BASEDIR at the top of our pipeline to point at the component checkout within WORKSPACE.
> but!
> a) at that point WORKSPACE is the workspace for the launching task
> b) sometimes our parallel executions get a task with a different local WORKSPACE to allow
for coexisting on the same build host
> c) when this happens our parallel stages are referring to some other absolute path on
the host
> d) in most cases we're referring to dev-support files like e.g. the nightly build script
or machine info script that are the same across branches so things are fine if we aren't running
at the same time as a job that's overwritting them
> e) we also refer to the Dockerfile this way, so weird bugs I'm sure.
> f) we build the source tarball from here, so that's probably broken subtly
> g) sometimes that other directory _doesn't exist at all_ and we fail with confusing messages
about stuff not found

This message was sent by Atlassian JIRA

View raw message