[
https://issues.apache.org/jira/browse/SPARK-33713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246808#comment-17246808
]
Shane Knapp commented on SPARK-33713:
-------------------------------------
hmm. so while i heartily endorse this, there will be a side-effect of renaming
the jobs (particularly as we use Jenkins Job Builder – JJB – to deploy and
manage the build configs):
once i redeploy the updated JJB configs w/the shortened build names, it will
create new builds and not change the names of existing ones. unless i'm unable
to read docs anymore (which is entirely possible) there's no 'rename' ability.
and since, according to jenkins, these are new builds, all previous build
history will be lost... unless i manually copy things over on the jenkins
primary filesystem (which i'd like to avoid if possible). given that we're
only storing 2 weeks of builds, if we time it properly (aka at 3.1 release) the
impact of losing these logs will be pretty insignificant.
my suggestion:
i want to do this, but i propose moving everything over when 3.1 is officially
released. we'll lose the previous 2 weeks of build history across all
branches, but since we're "starting fresh"-ish i think the impact will be
minimized.
thoughts? comments? should we pull anyone else in for their opions? [~sowen]
[~hyukjin.kwon] [~holden]
> Remove `hive-2.3` post fix at master/branch-3.1 Jenkins job names
> -----------------------------------------------------------------
>
> Key: SPARK-33713
> URL: https://issues.apache.org/jira/browse/SPARK-33713
> Project: Spark
> Issue Type: Task
> Components: Project Infra
> Affects Versions: 3.2.0
> Reporter: Dongjoon Hyun
> Assignee: Shane Knapp
> Priority: Major
>
> We removed `hive-1.2` profile since branch-3.1. So, we can simplify the
> Jenkins job title.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
