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

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-15388:
----------------------------------------

[~maxandersen]: See the first line of the description: "[Assuming we already have reproducible qualifiers...]"

But anyway I'm working on something smarter on Tycho side, that would remove the need for us to avoid publishing: http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00979.html . If this works, it means that we are free and safe to republish any build, if there was no change, it will republish the exact same artifacts. This should make us create much less artifacts (only new artifacts when there are actual changes in bytecode or plugin resources), and we could get rid of all efforts in deciding whether something needs to be republished or not. This would not even require reproducible version qualifiers and doesn't rely on SCM.
                
> 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