[jbosstools-issues] [JBoss JIRA] (JBIDE-12773) Create a jenkins.target and use it on CI

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-12773:
----------------------------------------

{quote}
Why put in place a solution you'll just be changing again in a couple months? Can't we just wait for 0.16 and go to the final solution instead of a temporary one?
{quote}
We can see that as a first increment: relying in .target on CI rather than on sites. Next increment is using mirrors instead of dedicated target. This is not a trivial change, I think it's good to start having a look at it right now.
It will make our job way easier in 2 monthes ;)
It also makes CI behave more and more like a regular developer, and reduce the number of workflows to maintain.

{quote}
How does pointing the builds at the .target file get us better performance than the local nfs mounted copy of the target site?
{quote}
The jenkins.target file points to the local nfs mounted copy. So performance should be the same as pointing directly to this site.

                
> Create a jenkins.target and use it on CI
> ----------------------------------------
>
>                 Key: JBIDE-12773
>                 URL: https://issues.jboss.org/browse/JBIDE-12773
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: Build/Releng, target-platform
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>             Fix For: 4.0.0.Beta1
>
>
> Instead of relying on profiles to use the local mirror of TP, we could create and use a jenkins.target which would simply be a copy of unified.target, but using a different URL.
> Then jobs could use it, and we'd finally use target-platforms on CI!
> As soon as Tycho 0.16 is resolved, we can replace this hudson.target by Tycho repository mirroring.

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