[jbosstools-issues] [JBoss JIRA] (JBIDE-23206) build flag for always use current timestamp to assist QE in testing PRs
[
https://issues.jboss.org/browse/JBIDE-23206?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-23206 at 9/20/16 9:08 PM:
-------------------------------------------------------------
PR: https://github.com/jbosstools/jbosstools-build/pull/232
To test this out:
1. clone the jbosstools-build project and build the parent pom with this PR applied:
https://github.com/jbosstools/jbosstools-build/pull/232
2. clone jbosstools-openshift, and build from master. observe the timestamps of
openshift.client plugin and openshift.feature in
jbosstools-openshift/site/target/repository/
3. apply this PR https://github.com/jbosstools/jbosstools-openshift/pull/1312 and build
again. observe the timestamps of openshift.client plugin and openshift.feature.
4. NOW... using the new R profile in parent pom (
https://github.com/jbosstools/jbosstools-build/pull/232 ) rebuild openshift:
{code}mvn clean install -PR{code}
5. observe that ALL the features and plugins in
jbosstools-openshift/site/target/repository/ have the timestamp of when you started the
latest build, in UTC (GMT+0).
was (Author: nickboldt):
PR:
To test this out:
1. clone the jbosstools-build project and build the parent pom with this PR applied:
https://github.com/jbosstools/jbosstools-build/pull/232
2. clone jbosstools-openshift, and build from master. observe the timestamps of
openshift.client plugin and openshift.feature in
jbosstools-openshift/site/target/repository/
3. apply this PR https://github.com/jbosstools/jbosstools-openshift/pull/1312 and build
again. observe the timestamps of openshift.client plugin and openshift.feature.
4. NOW... using the new R profile in parent pom (
https://github.com/jbosstools/jbosstools-build/pull/232 ) rebuild openshift:
{code}mvn clean install -PR{code}
5. observe that ALL the features and plugins in
jbosstools-openshift/site/target/repository/ have the timestamp of when you started the
latest build, in UTC (GMT+0).
build flag for always use current timestamp to assist QE in testing
PRs
-----------------------------------------------------------------------
Key: JBIDE-23206
URL: https://issues.jboss.org/browse/JBIDE-23206
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build
Affects Versions: 4.4.2.AM1
Reporter: Rob Stryker
Assignee: Nick Boldt
In the case where a PR is not rebased against master constantly, QE is blocked from
testing it under two situations:
1) The PR job has produced a site. QE installs most recent jbt, then tries to install the
PR site. This fails because the PR site is older than the nightly build.
2) The QE rep checks out the PR and tries to build locally. The timestamps match the
change date (ie the date the PR was last changed), which is still older than the nightly
build.
In both situations, QE cannot install a locally-built or PR-built site on top of a more
recent nightly build of JBT. We cannot expect QE to rebase and (if required) merge /
change code.
The best bet here is to simply add a flag QE can use when building locally to always use
current timestamp, to ensure locally built unit is always 'newest'.
We then document that flag in devdoc for QE and make it part of their standard workflow.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)