[JBoss JIRA] (JBIDE-19730) Build Improvement
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19730?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19730:
-------------------------------
Description:
Epic to track issues related to improving how we release software.
This may include tools & workflows to improve how we build, what we build, how we release, process automation, Jenkins, etc.
was:
Epic to track issues related to auditing and quality control.
This may include tools & workflows to ensure we're not building the wrong stuff, including too much (or incompatible versions) in target platforms, forgetting to upversion components, etc.
> Build Improvement
> -----------------
>
> Key: JBIDE-19730
> URL: https://issues.jboss.org/browse/JBIDE-19730
> Project: Tools (JBoss Tools)
> Issue Type: Epic
> Components: build
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
>
> Epic to track issues related to improving how we release software.
> This may include tools & workflows to improve how we build, what we build, how we release, process automation, Jenkins, etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19730) Build Improvements
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19730:
----------------------------------
Summary: Build Improvements
Key: JBIDE-19730
URL: https://issues.jboss.org/browse/JBIDE-19730
Project: Tools (JBoss Tools)
Issue Type: Epic
Components: build
Affects Versions: 4.3.0.Alpha2
Reporter: Nick Boldt
Epic to track issues related to auditing and quality control.
This may include tools & workflows to ensure we're not building the wrong stuff, including too much (or incompatible versions) in target platforms, forgetting to upversion components, etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19730) Build Improvement
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19730?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19730:
-------------------------------
Summary: Build Improvement (was: Build Improvements)
> Build Improvement
> -----------------
>
> Key: JBIDE-19730
> URL: https://issues.jboss.org/browse/JBIDE-19730
> Project: Tools (JBoss Tools)
> Issue Type: Epic
> Components: build
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
>
> Epic to track issues related to auditing and quality control.
> This may include tools & workflows to ensure we're not building the wrong stuff, including too much (or incompatible versions) in target platforms, forgetting to upversion components, etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19726) Error messages related to failures configuring Cordova version 4 engine are written to .log, and displayed in dialog for only a fraction of a second
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19726?page=com.atlassian.jira.plugi... ]
Len DiMaggio updated JBIDE-19726:
---------------------------------
Summary: Error messages related to failures configuring Cordova version 4 engine are written to .log, and displayed in dialog for only a fraction of a second (was: Error messages related to failures configuring Cordova version 4 engine are written to .log, not displayed to user)
> Error messages related to failures configuring Cordova version 4 engine are written to .log, and displayed in dialog for only a fraction of a second
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19726
> URL: https://issues.jboss.org/browse/JBIDE-19726
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.3.0.Alpha2
> Reporter: Len DiMaggio
> Assignee: Gorkem Ercan
>
> Attempts to configure Cordova version 4.0 fail - another case of changes in directory tree - the errors are written to the .log, and are not communicated to the user via the UI
> !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882
> !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/cordova-4.0.0.jar
> !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882
> !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/assets/www/cordova.js
> !ENTRY org.eclipse.thym.ios.core 4 0 2015-04-28 11:28:43.882
> !MESSAGE Can not detect version. VERSION file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/CordovaLib/VERSION is missing
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19729) Version Auditing
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19729:
----------------------------------
Summary: Version Auditing
Key: JBIDE-19729
URL: https://issues.jboss.org/browse/JBIDE-19729
Project: Tools (JBoss Tools)
Issue Type: Epic
Components: build
Affects Versions: 4.3.0.Alpha2
Reporter: Nick Boldt
Epic to track issues related to auditing and quality control.
This may include tools & workflows to ensure we're not building the wrong stuff, including too much (or incompatible versions) in target platforms, forgetting to upversion components, etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-17103) No warning/error is shown when detected runtime fails to be added
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17103?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17103:
---------------------------------------------
since this is used by seam, drools, esb, and I assume others this should be raised to IS guys on jbosstools-dev at least.
> No warning/error is shown when detected runtime fails to be added
> -----------------------------------------------------------------
>
> Key: JBIDE-17103
> URL: https://issues.jboss.org/browse/JBIDE-17103
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.x
>
>
> When there is a new version of a runtime, e.g. WildFly 8.1, that is not yet supported by the tooling, runtime detection usually detects it alright, but when you then click OK, the runtime+server are not added. And there is no error anywhere at all - we should fix that.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19714) seam.core test failure
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19714?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19714:
-----------------------------------
Sprint: Sprint #2 April 2015 (was: Sprint #3 May 2015)
> seam.core test failure
> ----------------------
>
> Key: JBIDE-19714
> URL: https://issues.jboss.org/browse/JBIDE-19714
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: seam2
> Affects Versions: 4.3.0.Alpha2
> Reporter: Alexey Kazakov
> Assignee: Daniel Azarov
> Fix For: 4.3.0.Beta1
>
>
> Failed tests:
> SeamComponentRefactoringTest.testSeamComponentRename:90->renameComponent:142 There is unexpected number of changes expected:<7> but was:<3>
> SeamContextVariableRefactoringTest.testSeamContextVariable_Component_Rename:76->AbstractRefactorTest.checkRename:33 expected:<2> but was:<1>
> SeamEARTest.testEarProject:80 War project must see component 'org.jboss.seam.core.interpolator' declared in ejb project
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19467) repository-utils :: FetchSourcesFromManifests should create its own source zip, not rely on publish.sh
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19467?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19467:
------------------------------------
I've merged PR #38. Things to fix in the next iteration:
* remove commented block about md5 generation
* use enum instead of two ints for CACHE_ZIPS, etc.
* decide what to put in target/repository/ instead of target/fullSite/all/
* investigate using truezip?
* make output filename more generic / parameterized, not just jbosstools-src.zip
Things suggested today by Max:
* include buildinfo.json files in the zip
* compare SHA from buildinfo.json files w/ the value found in MANIFEST.MF files; if they don't match, break the build
* get more properties into buildinfo.json for ALL builds (including those in _master branch, which currently show nulls)
** TARGET_PLATFORM_*
** BUILD_ID, BUILD_NUMBER, BUILD_ALIAS
** JOB_NAME
** jbosstools_site_stream ?
> repository-utils :: FetchSourcesFromManifests should create its own source zip, not rely on publish.sh
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19467
> URL: https://issues.jboss.org/browse/JBIDE-19467
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
>
> In repository-utils, FetchSourcesFromManifests should create its own source zip, not rely on publish.sh. Because we no longer use publish.sh and don't want to have rsync.sh produce artifacts, only rsync them.
> Here's what publish.sh does:
> {code}
> # collect component zips from upstream aggregated build jobs
> if [[ ${JOB_NAME/.aggregate} != ${JOB_NAME} ]] && [[ -d ${WORKSPACE}/sources/aggregate/site/zips ]]; then
> mkdir -p ${STAGINGDIR}/components
> for z in $(find ${WORKSPACE}/sources/aggregate/site/zips -name "*updatesite-*.zip"); do
> # generate MD5 sum for zip (file contains only the hash, not the hash + filename)
> for m in $(md5sum ${z}); do if [[ $m != ${z} ]]; then echo $m > ${z}.MD5; fi; done
> mv $z ${z}.MD5 ${STAGINGDIR}/components
> done
> # TODO :: JBIDE-9870 When we have a -Update-Sources- zip, this can be removed
> mkdir -p ${STAGINGDIR}/all/sources
> # OLD: unpack component source zips like jbosstools-pi4soa-3.1_trunk-Sources-SNAPSHOT.zip or jbosstools-3.2_trunk.component--ws-Sources-SNAPSHOT.zip
> # NEW: JBIDE-16632: unpack component source zips like jbosstools-base_Alpha2-v20140221-1555-B437_184e18cc3ac7c339ce406974b6a4917f73909cc4_sources.zip
> for z in $(find ${WORKSPACE}/sources/aggregate/site/zips -name "*Sources*.zip" -o -name "*_sources.zip" -o -name "*-src.zip"); do
> zn=${z%*-Sources*.zip}; zn=${zn%*_sources.zip}; zn=${zn%*-src.zip}; zn=${zn#*--}; zn=${zn##*/}; zn=${zn#jbosstools-};
> # zn=${zn%_trunk}; zn=${zn%_stable_branch};
> mkdir -p ${STAGINGDIR}/all/sources/${zn}/
> # remove one level of folder nesting - don't want an extra jbosstools-base-184e18cc3ac7c339ce406974b6a4917f73909cc4 folder under jbosstools-base_Alpha2-v20140221-1555-B437_184e18cc3ac7c339ce406974b6a4917f73909cc4
> unzip -qq -o -d ${tmpdir}/${zn}/ $z
> mkdir -p ${STAGINGDIR}/all/sources/${zn}/
> mv ${tmpdir}/${zn}/jbosstools-*/* ${STAGINGDIR}/all/sources/${zn}/
> rm -fr ${tmpdir}/${zn}/
> done
> # add component sources into sources zip
> pushd ${STAGINGDIR}/all/sources
> zip ${STAGINGDIR}/all/${SRCSNAME} -q -r * -x hudson_workspace\* -x documentation\* -x download.jboss.org\* -x requirements\* \
> -x workingset\* -x labs\* -x build\* -x \*test\* -x \*target\* -x \*.class -x \*classes\* -x \*bin\* -x \*.zip \
> -x \*docs\* -x \*reference\* -x \*releng\* -x \*.git\* -x \*/lib/\*.jar -x \*getRemoteFile\*
> popd
> rm -fr ${STAGINGDIR}/all/sources
> z=${STAGINGDIR}/all/${SRCSNAME}; for m in $(md5sum ${z}); do if [[ $m != ${z} ]]; then echo $m > ${z}.MD5; fi; done
> # JBIDE-7444 get aggregate metadata xml properties file
> if [[ -f ${WORKSPACE}/sources/aggregate/site/zips/build.properties.all.xml ]]; then
> rsync -aq ${WORKSPACE}/sources/aggregate/site/zips/build.properties.all.xml ${STAGINGDIR}/logs/
> fi
> fi
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19532) "Edit Server Runtime Environment" Dialog configuration validation is broken
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19532?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-19532:
--------------------------------
Attachment: JBIDE-19532.png
Screenshot showing error ;)
> "Edit Server Runtime Environment" Dialog configuration validation is broken
> ---------------------------------------------------------------------------
>
> Key: JBIDE-19532
> URL: https://issues.jboss.org/browse/JBIDE-19532
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.CR1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.3.0.Beta1
>
> Attachments: data-folder-config.png, Edit Server Runtime Environment _102.png, JBIDE-19532.png
>
>
> If I use "Browse" button for "Configuration base directory" and "Configuration file" validation has no complains, but result is broken Server that cannot start.
> {code}java.lang.IllegalStateException: basedir /home/eskimo/Java/wildfly-8.0.0.Final/configuration does not exist.
> at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:879)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.AntFileFilter.getIncludedFiles(AntFileFilter.java:40)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:133)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:80)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:128)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:110)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:227)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:213)
> at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:68)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:117)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:119)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months