[JBoss JIRA] (JBIDE-23322) create mojo that takes as input a list of URLs and a name, and generates a composite site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23322?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23322:
-------------------------------
Fix Version/s: 4.4.4.AM2
(was: 4.4.4.AM1)
> create mojo that takes as input a list of URLs and a name, and generates a composite site
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-23322
> URL: https://issues.jboss.org/browse/JBIDE-23322
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.4.AM2
>
>
> In https://issues.jboss.org/browse/WINDUP-1189 it was requested that tycho builds be able to produce a simple composite site, using as input 1 or more URLs.
> So, to generalize this for use by other projects, we need a mojo that can be configured with a set of URLs, and a site name, in order to produce three files:
> {code}
> target/composite/compositeContent.xml
> target/composite/compositeArtifacts.xml
> target/composite/p2.index (like https://devstudio.jboss.com/10.0/stable/updates/p2.index )
> {code}
> Secondary use case would be to generate a composite site from subfolders in an existing folder, eg., to replace https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u...
> So we could use this to create composite sites in folders like:
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/core/ (invalid composite points to ../, which has no composite either)
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/central/ (no composite)
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/earlyaccess/ (no composite)
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/integrati... (no composite)
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ (up to date)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/core/ (invalid composite points to ../, which has no composite either)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/cent... (no composite)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/earl... (no composite)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/inte... (no composite)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/core... (composite out of date)
> But also to point to remote (/stable/) URLs from pointer sites, like:
> * http://download.jboss.org/jbosstools/neon/stable/updates/compositeArtifac... (up to date, name = JBoss Tools - Core + Central Update Site)
> * http://download.jboss.org/jbosstools/neon/stable/updates/central/ (composite missing)
> * http://download.jboss.org/jbosstools/neon/stable/updates/earlyaccess/ (composite missing)
> * http://download.jboss.org/jbosstools/neon/stable/updates/coretests/compos... (up to date, name = JBoss Tools 4.4.2.Final Stable Release Tests Site)
> * http://download.jboss.org/jbosstools/neon/stable/updates/integration-tests (404'd)
> * http://download.jboss.org/jbosstools/neon/development/updates/compositeAr... (up to date, name = JBoss Tools - Core + Central Update Site)
> * http://download.jboss.org/jbosstools/neon/development/updates/central/ (composite missing)
> * http://download.jboss.org/jbosstools/neon/development/updates/earlyaccess/ (composite missing)
> * http://download.jboss.org/jbosstools/neon/development/updates/coretests/c... (out of date, points to 4.4.0.Alpha1)
> * http://download.jboss.org/jbosstools/neon/development/updates/integration... (404'd)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23503) Target platform PR check fails to use p2diff correctly, so build fails
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23503?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23503:
-------------------------------
Fix Version/s: 4.4.4.AM2
(was: 4.4.4.AM1)
> Target platform PR check fails to use p2diff correctly, so build fails
> ----------------------------------------------------------------------
>
> Key: JBIDE-23503
> URL: https://issues.jboss.org/browse/JBIDE-23503
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, target-platform
> Affects Versions: 4.4.2.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.4.AM2
>
> Attachments: dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com.log.txt
>
>
> Recently, it was noticed that the TP PR checks are failing. And have been for a long time.
> So, I'm opening this to track the work needed to make them work again.
> There are two different TP PR jobs:
> * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... (which seems to have never worked)
> * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... (which has been blue in the past)
> Recent failure:
> {code}
> [INFO] Command line:
> [/qa/tools/opt/x86_64/jdk1.8.0_101/jre/bin/java, -jar, /mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/.repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.3.100.v20150511-1540/org.eclipse.equinox.launcher-1.3.100.v20150511-1540.jar, -install, /mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/eclipserun-work, -configuration, /mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/eclipserun-work/configuration, -application, org.eclipse.equinox.p2.example.p2diff.application, -outputFile=/mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/jbosstools-multiple-ignoreVersions.p2diff, -mode=ignoreVersions, file:/mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/jbosstools-multiple.target.repo, http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...]
> An error has occurred. See the log file
> /mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/eclipserun-work/configuration/1479683354475.log.{code}
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23017) use sshfs to speed up publishing process
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23017?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23017:
-------------------------------
Fix Version/s: 4.4.4.AM2
(was: 4.4.4.AM1)
> use sshfs to speed up publishing process
> -----------------------------------------
>
> Key: JBIDE-23017
> URL: https://issues.jboss.org/browse/JBIDE-23017
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.4.1.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.4.AM2
>
>
> Currently, publishing from /snapshots to /staging and from /staging to /development requires that we fetch several GBs of data from filemgmt.jboss.org to a temp folder, then push those bits to a new folder on filemgmt.jboss.org.
> If we could simply copy bits over sshfs, the process might be a lot faster than these times:
> {code}
> JBT coretests 1.1G: 59m20
> JBT core 1.2G: 64m23
> devstudio (copy from filemgmt to filemgmt) 2.4G: 2h13
> devstudio (copy from local to www.qa) 3.1G: 6mins(?)
> {code}
> To make this work, however, we need more slaves to have sshfs installed. Currently, it appears that only dev01 [1] is so equipped. And that slave, currently, has a build queue more than 170 jobs long, making it impractical to even TEST publishing over sshfs.
> [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev01-rhel5-x86/
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23678) remediation required installing jbosstools 4.4.3.AM1 on Neon.2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23678?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23678:
-------------------------------
Fix Version/s: 4.4.4.AM2
(was: 4.4.4.AM1)
> remediation required installing jbosstools 4.4.3.AM1 on Neon.2
> --------------------------------------------------------------
>
> Key: JBIDE-23678
> URL: https://issues.jboss.org/browse/JBIDE-23678
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.4.AM2
>
> Attachments: remediation-required-jbt443am1.png, remediation-required-jbt443am1_skip_items.png, remediation-required-jbt443am1_upgrades.png
>
>
> Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have newer versions of JSON/JSDT plugins in our target platform than are in Neon.2.
> Install manifest contains:
> * org.eclipse.wst.jsdt.feature 2.0.0 (4 versions),
> * 1.6.201 (2 versions), and
> * 2.0.200 (1 version) - *total 7 references*!
> Also, org.eclipse.wst.web_ui.feature.feature.group depends on org.eclipse.wst.jsdt.feature.feature.group, which pulls in another ref/requirement.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23780) Import Application: uncheck "Use default clone destination" wont recheck if I removed the folder that it''s complaining about
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23780?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23780:
------------------------------------------
merged into jbosstools-4.4.x, cherry-picked to master.
> Import Application: uncheck "Use default clone destination" wont recheck if I removed the folder that it''s complaining about
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23780
> URL: https://issues.jboss.org/browse/JBIDE-23780
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Labels: import_wizard, openshift_v3
> Fix For: 4.4.4.AM2
>
> Attachments: clone-destination-already-exists.png, error-even-though-clone-destination-doesnt-exist.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have a folder "jboss-eap-quickstarts" in your default Eclipse git clone destination (if you didnt change your preferences, it will point to ~/git/. If you dont have it yet git clone it from https://github.com/jboss-developer/jboss-eap-quickstarts.git)
> # EXEC: create a new application using the "eap64-basic-s2i" template
> # ASSERT: the OpenShift resources for your application are created, the import wizard pops up with the following error that complains about the directory already existing:
> !clone-destination-already-exists.png!
> # EXEC: manually remove the directory (ex. in cmd-line)
> # EXEC: uncheck "Use default clone destination:"
> Result:
> The error wont go away, the wizard is still complaining even though the folder isnt in the way any more.
> !error-even-though-clone-destination-doesnt-exist.png!
> Hitting "Browse" and pointing to the same folder, that doesnt containt the folder anymore, wont help. The error persists. There'
> s no way to work around this, you have to cancel the import and start over again.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years