[jbosstools-issues] [JBoss JIRA] (JBIDE-23206) build flag for always use current timestamp to assist QE in testing PRs

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-23206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13296709#comment-13296709 ] 

Rob Stryker commented on JBIDE-23206:
-------------------------------------

I like -PR.   -Prawblem is a horrible name. It's mean to accuse QE of causing all our problems, and reminding them of this each time they test a PR. ;)   

> 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)