[JBoss JIRA] (JBIDE-25315) Include Fuse CI job update for job configuration update
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25315?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25315:
-------------------------------
Fix Version/s: 4.5.2.AM2
(was: 4.5.2.AM1)
> Include Fuse CI job update for job configuration update
> -------------------------------------------------------
>
> Key: JBIDE-25315
> URL: https://issues.jboss.org/browse/JBIDE-25315
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: fusetools
> Affects Versions: 4.5.1.Final
> Reporter: Aurélien Pupier
> Assignee: Nick Boldt
> Fix For: 4.5.2.AM2
>
> Attachments: image-2017-11-02-09-23-36-305.png
>
>
> the CI jobs on Fuse Ci are often not synchronized with modifications done on other jboss tools project such as TARGET_PLATFORM version.
> for instance today again:
> !image-2017-11-02-09-23-36-305.png|thumbnail!
> it would be useful to include the update of the FUSE CI jobs in the process to update the jobs
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBIDE-25228) target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25228?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25228:
------------------------------------
Given you're running a maven task, why do you need to find mvn on the PATH? surely you can just discover mvn from the running process?
Until this compiles in Jenkins, I can't accept it as a commit because I can't build & deploy it to nexus.
> target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-25228
> URL: https://issues.jboss.org/browse/JBIDE-25228
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.5.1.Final
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.5.x
>
>
> With these recent changes [0], [1], target platform resolution is no longer able to fetch more than one version of an IU.
> We need apache.commons.codec 1.6.0.v201305230611, per the .target file [2], but only org.apache.commons.codec_1.9.0.v20170208-1614.jar is found in the update site [3], so the job [4] cannot perform an installation and validation of the TP fails.
> Is there a setting I can pass in to make TargetToRepo more greedy about pulling multiple versions of IUs?
> Note too that I was having problems last night getting the fix-version mojo to properly find and update the versions of WTP in the new 3.9.1a site, even when explicitly setting 0.0.0 to force it to search and update. Seems the target platform resolver will only pull the latest version of an IU, rather than an older one (a few WTP features have gone backwards in their timestamp). But it could also not resolve a version change from 3.3.600 [5] to 3.3.601 [6], so I had to update the version manually.
> [0] https://github.com/jbosstools/jbosstools-maven-plugins/commit/2b724eceadb...
> [1] https://github.com/jbosstools/jbosstools-maven-plugins/commit/ac4e492fab4...
> [2] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo...
> [3] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7...
> [4] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
> [5] https://github.com/jbosstools/jbosstools-target-platforms/blob/14ec465a9b...
> [6] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months