[jbosstools-issues] [JBoss JIRA] (JBIDE-15388) Compute whether to publish or not based on output signature rather than commits

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-15388:
---------------------------------------------

reproducible qualifiers won't detect if job configuration changed would it ?

you changing TP version won't change the commit that is used for reproducible qualifiers?

With respect to the new comparison, we would need to remove and date/time stamping happening in the builds since that would trigger a diff on binary level.



                
> Compute whether to publish or not based on output signature rather than commits
> -------------------------------------------------------------------------------
>
>                 Key: JBIDE-15388
>                 URL: https://issues.jboss.org/browse/JBIDE-15388
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>             Fix For: LATER
>
>
> [Assuming we already have reproducible qualifiers...]
> Currently, the CI jobs publish the output of a build if a change was detected in the Git repo since last publication.
> However there are some case not correctly supported:
> * Job configuration changed and caused changes in build output. In that case, we would like build output to be re-published, but it won't happen
> * Job source changed but not build output (eg a change in a pom.xml or any non-included file), then we don't need to republish output whereas current mechanism would republish it.
> instead, it would make sense to compare what's already published and what is to publish in order to decide or not whether this has to be published. Looking at signatures of update site zip would probably be enough.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira