| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| mqsicreatebar and jenkins |
« View previous topic :: View next topic » |
| Author |
Message
|
| ruimadaleno |
 Posted: Tue Aug 04, 2015 8:46 am Post subject: mqsicreatebar and jenkins |
 |
|
Master
Joined: 08 May 2014
Posts: 274
|
Hi all,
i'm doing some investigation/tests on automating the build/deploy process in broker environments
i am testing jenkins, i'm able to retrieve source code from repository (SVN) and start mqsicreatebar command, however the mqsicreatebar takes sooooo long
Can you provide some pointers/hints ? mqsicreatebar is running for more than 15 minutes 
Console output from jenkins job:
| Quote: |
Started by user anonymous
[EnvInject] - Loading node environment variables.
[EnvInject] - Preparing an environment for the build.
[EnvInject] - Keeping Jenkins system variables.
[EnvInject] - Keeping Jenkins build variables.
[EnvInject] - Injecting as environment variables the properties content
APPLICATION_NAME=SGMBEntities
EXECUTION_GROUP_NAME=eg_teste
BROKER_NAME=brkdvesb01
PROPERTIES_NAME=$APPLICATION_NAME||"Ambiente aplicacional"
[EnvInject] - Variables injected successfully.
[EnvInject] - Injecting contributions.
Building in workspace D:\Jenkins\jobs\Prj_Build_serviceteste\workspace
[EnvInject] - Unset unresolved 'USERNAME' variable.
Cleaning local Directory SGMBEntities
Checking out svn://bb-sped/csa/Area WF e BPM/SGMB/SGMBEntities/trunk at revision '2015-08-04T17:15:53.183 +0100'
AU CsaTiposGenericos.xsd
A log
A log\sgmbentities
AU log\sgmbentities\SGMBEntities.wsdl.report.txt
A log\com
A log\com\i2s
A log\com\i2s\egis
A log\com\i2s\egis\web
A log\com\i2s\egis\web\proxy
AU log\com\i2s\egis\web\proxy\ProxyCTLPessoa.wsdl.report.txt
A pt
A pt\contact admin
A pt\contact admin\sgmbentities
A pt\contact admin\sgmbentities\Constants.esql
A pt\contact admin\sgmbentities\SearchEntities_GISResponseMapping.map
A pt\contact admin\sgmbentities\Entities.esql
A pt\contact admin\sgmbentities\SearchEntities.esql
A pt\contact admin\sgmbentities\SearchEntities_GISRequestMapping.map
AU .project
A IBMdefined
AU IBMdefined\soap.xsd
A IBMdefined\org
A IBMdefined\org\xmlsoap
A IBMdefined\org\xmlsoap\schemas
A IBMdefined\org\xmlsoap\schemas\soap
A IBMdefined\org\xmlsoap\schemas\soap\envelope
AU IBMdefined\org\xmlsoap\schemas\soap\envelope\soapenv11.xsd
A IBMdefined\org\w3
A IBMdefined\org\w3\www
A IBMdefined\org\w3\www\xml
A IBMdefined\org\w3\www\xml\_1998
A IBMdefined\org\w3\www\xml\_1998\namespace
AU IBMdefined\org\w3\www\xml\_1998\namespace\xml.xsd
AU AcorServicesXmlStructure.xsd
AU CsaTypes.xsd
AU SGMBEntities.xsd
AU ProxyCTLPessoa_InlineSchema1.xsd
AU ProxyCTLPessoa.xsd
AU RetornaEntidadeOut.xsd
AU PesquisaEntidadesOut.xsd
AU SGMBEntities.wsdl
AU RetornaEntidade.xsd
AU SearchEntities.xsd
AU ProxyCTLPessoa.wsdl
AU PesquisaEntidades.xsd
A gen
A gen\Entities.msgflow
A gen\SearchEntitiesRequestResponse.subflow
AU BPMEntidadeType.xsd
A service.descriptor
At revision 8721
Cleaning local Directory SGMBLibrary
Checking out svn://bb-sped/csa/Area WF e BPM/SGMB/SGMBLibrary/trunk at revision '2015-08-04T17:15:53.183 +0100'
A pt
A pt\contact admin
A pt\contact admin\sgmb
A pt\contact admin\sgmb\library
A pt\contact admin\sgmb\library\Constants.esql
A pt\contact admin\sgmb\library\DateUtils.esql
A pt\contact admin\sgmb\library\ErrorHandling.esql
A pt\contact admin\sgmb\library\MappingGenericTypesUtils.esql
A pt\contact admin\sgmb\library\Utils.esql
A pt\contact admin\sgmb\library\XMLUtils.esql
A pt\contact admin\sgmb\library\globalcache
A pt\contact admin\sgmb\library\globalcache\CacheUtil.esql
A pt\contact admin\sgmb\library\globalcache\MasterdataCaching.esql
A pt\contact admin\sgmb\library\MasterDataMappingUtils.esql
A pt\contact admin\sgmb\library\invokegis
A pt\contact admin\sgmb\library\invokegis\ErrorHandling.esql
AU .project
A InputFailureHandler.subflow
AU TiposGenericos.xsd
A InvokeGIS.subflow
U .
At revision 8721
Cleaning local Directory SGMBLibraryJava
Checking out svn://bb-sped/csa/Area WF e BPM/SGMB/SGMBLibraryJava/trunk at revision '2015-08-04T17:15:53.183 +0100'
AU .classpath
AU .project
A Utilities
AU Utilities\CacheUtil.java
AU Utilities\CacheUtil.class
At revision 8721
no change for svn://bb-sped/csa/Area WF e BPM/SGMB/SGMBEntities/trunk since the previous build
no change for svn://bb-sped/csa/Area WF e BPM/SGMB/SGMBLibrary/trunk since the previous build
no change for svn://bb-sped/csa/Area WF e BPM/SGMB/SGMBLibraryJava/trunk since the previous build
Run condition [Always] enabling prebuild for step [Execute Windows batch command]
[workspace] $ cmd /c call C:\Windows\TEMP\hudson3664082953399804824.bat
D:\Jenkins\jobs\Prj_Build_serviceteste\workspace>call "C:\Program Files (x86)\IBM\WMBT800\mqsicreatebar.exe" -data D:\Jenkins\jobs\Prj_Build_serviceteste\workspace -b SGMBEntities_TESTE.BAR -a SGMBEntities -trace
[2015/08/04/17:16:08] [INFO] CommandProcessor: process { mqsicreatebar arguments: }
[2015/08/04/17:16:08] [INFO] CommandProcessor: process { [-b, SGMBEntities_TESTE.BAR, -a, SGMBEntities, -trace, -wmbtData] }
[2015/08/04/17:16:10] [INFO] CommandProcessor: process { Disable auto-build before opening the projects }
[2015/08/04/17:16:11] [INFO] CommandProcessor: openWorkspace { }
[2015/08/04/17:16:11] [INFO] CommandProcessor: openWorkspace { List of applications to be processed: SGMBEntities }
[2015/08/04/17:16:11] [INFO] CommandProcessor: addReferencedProjectForAppOrLib { List of reference projects for project D:\Jenkins\jobs\Prj_Build_serviceteste\workspace\SGMBEntities\.project to be processed: SGMBLibrary }
[2015/08/04/17:16:11] [INFO] CommandProcessor: addReferencedProjectForAppOrLib { List of reference projects for project D:\Jenkins\jobs\Prj_Build_serviceteste\workspace\SGMBLibrary\.project to be processed: SGMBLibraryJava }
[2015/08/04/17:16:11] [INFO] OpenWorkspaceRunnable: run { Creating project: SGMBLibrary }
[2015/08/04/17:16:11] [INFO] OpenWorkspaceRunnable: run { Opening project: SGMBLibrary }
[2015/08/04/17:16:11] [INFO] OpenWorkspaceRunnable: run { Creating project: SGMBLibraryJava }
[2015/08/04/17:16:11] [INFO] OpenWorkspaceRunnable: run { Opening project: SGMBLibraryJava }
[2015/08/04/17:16:14] [INFO] OpenWorkspaceRunnable: run { Creating project: SGMBEntities }
[2015/08/04/17:16:14] [INFO] OpenWorkspaceRunnable: run { Opening project: SGMBEntities }
[2015/08/04/17:16:18] [INFO] CommandProcessor: process { Enable auto-build after the projects are opened }
[2015/08/04/17:16:18] [INFO] CommandProcessor: waitForBuildsToComplete { Waiting for build to complete }
|
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Aug 04, 2015 8:54 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
mqsicreatebar runs the toolkit. in the background. always.
That means each time you run it, it starts up Eclipse, loads the workspace, performs all the normal eclipsy startup things, and *then* starts building your bar file.
The only ways to reduce this time are a) create a smaller workspace focused on the exact build that needs to be done, OR b) switch to using mqsipackagebar. |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Wed Aug 05, 2015 5:30 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
| mqjeff wrote: |
mqsicreatebar runs the toolkit. in the background. always.
That means each time you run it, it starts up Eclipse, loads the workspace, performs all the normal eclipsy startup things, and *then* starts building your bar file.
The only ways to reduce this time are a) create a smaller workspace focused on the exact build that needs to be done, OR b) switch to using mqsipackagebar. |
Hi mqjeff, thank you for you answer.
The workspace is one of the smallest in our environment, it's just a message flow and two dependencies, if mqsicreatebar takes this amount of time to create the bar file this is a huge constraint in our efforts to automate deployment (it is not acceptable to wait more than 15 minutes for a simple build like the one i'm trying).
However i assume there can be errors/misusage on the mqsicreatebar or other artifact (like the workspace creation) that result in this high time to bar creation.
Can you give some help ? some point i should investigate ? what are the thinks to look at when the mqsicreatebar takes so long ? 
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Aug 05, 2015 5:35 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Start by checking how long the Toolkit takes to start up interactively and load the workspace on the jenkins machine.
If that takes 15 minutes, then dig into the workspace .log file, and look into tracing Toolkit functions per instructions in KC or tech notes. And then open a PMR.
If that doesn't take 15 minutes, then examine the environment that jenkins runs under and provides to the mqsicreatebar command.
Also, your jenkins output didn't show the entries after the mqsicreatebar command finished. So it's hard to tell from here if the command threw errors or not.
You could also compare the time difference between -trace and no -trace. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Aug 05, 2015 5:45 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| ruimadaleno wrote: |
| mqjeff wrote: |
mqsicreatebar runs the toolkit. in the background. always.
That means each time you run it, it starts up Eclipse, loads the workspace, performs all the normal eclipsy startup things, and *then* starts building your bar file.
The only ways to reduce this time are a) create a smaller workspace focused on the exact build that needs to be done, OR b) switch to using mqsipackagebar. |
Hi mqjeff, thank you for you answer.
The workspace is one of the smallest in our environment, it's just a message flow and two dependencies, if mqsicreatebar takes this amount of time to create the bar file this is a huge constraint in our efforts to automate deployment (it is not acceptable to wait more than 15 minutes for a simple build like the one i'm trying).
However i assume there can be errors/misusage on the mqsicreatebar or other artifact (like the workspace creation) that result in this high time to bar creation.
Can you give some help ? some point i should investigate ? what are the thinks to look at when the mqsicreatebar takes so long ? |
When creating multiple bar files from a single workspace, mind you, it should not be your development workspace..., I have found that deleting the .metadata file in the workspace will restrict the workspace build to the current set needed for the current barfile and thus speed up (sometimes significantly) the mqsicreatebar process. (ant).
The invocation of mqsicreatebar starts with a rebuild of the workspace. If your workspace is significantly larger than needed for the current invocation of mqsicreatebar, it can add quite some delay to the build.
Another aspect you need to check is the memory setup for the toolkit. It is said to significantly impact toolkit startup time.
You may want to review the eclipse.ini file and set a -Xmx1024M value...
and maybe a higher -Xms (-Xms512M) value... Back up that file first... and make sure you have the physical memory to match. Avoid processing of multiple builds in parallel.... (again watch that memory).
Hope it helps some... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Wed Aug 05, 2015 8:49 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
some more info (not much)
log file from workspace/.metadata
| Quote: |
!SESSION 2015-08-04 17:16:03.265 -----------------------------------------------
eclipse.buildId=unknown
java.fullversion=JRE 1.6.0 IBM J9 2.4 Windows 7 x86-32 jvmwi3260sr16fp4-20150406_242976 (JIT enabled, AOT enabled)
J9VM - 20150406_242976
JIT - r9_20150402_88984
GC - GA24_Java6_SR16_20150406_1410_B242976
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=pt_PT
Framework arguments: -noupdate -application com.ibm.etools.mft.bar.cmdline.mqsicreatebar -b SGMBEntities_TESTE.BAR -a SGMBEntities -trace -wmbtData
Command-line arguments: -noupdate -os win32 -ws win32 -arch x86 -application com.ibm.etools.mft.bar.cmdline.mqsicreatebar -data D:\Jenkins\jobs\Prj_Build_serviceteste\workspace -b SGMBEntities_TESTE.BAR -a SGMBEntities -trace -wmbtData
!ENTRY org.eclipse.emf.ecore 2 0 2015-08-04 17:16:08.683
!MESSAGE Both 'com.ibm.ccl.mapping.codegen.xslt' and 'com.ibm.hcls.sdg' register an extension parser for 'map'
|
no clues ... 
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Aug 05, 2015 12:46 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
This is not the log file you want.
What you really want to look at is the trace file from mqsicreatebar...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Thu Aug 06, 2015 1:36 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
ok, some more info.
Workspace is
D:\Jenkins\jobs\Prj_Build_serviceteste\workspace
bellow workspace i have 3 projects
D:\Jenkins\jobs\Prj_Build_serviceteste\workspace\SGMBEntities
D:\Jenkins\jobs\Prj_Build_serviceteste\workspace\SGMBLibrary
D:\Jenkins\jobs\Prj_Build_serviceteste\workspace\SGMBLibraryJava
Main project is "SGMBEntities" wich references SGMBLibrary and SGMBLibraryJava
added -cleanBuild flag in mqsicreatebar command
| Quote: |
D:\Jenkins\jobs\Prj_Build_serviceteste\workspace>call "C:\Program Files (x86)\IBM\WMBT800\mqsicreatebar.exe" -data D:\Jenkins\jobs\Prj_Build_serviceteste\workspace -b SGMBEntities_TESTE.BAR -p SGMBEntities -o SGMBEntities -trace -cleanBuild
[2015/08/06/10:33:44] [INFO] CommandProcessor: process { mqsicreatebar arguments: }
[2015/08/06/10:33:44] [INFO] CommandProcessor: process { [-b, SGMBEntities_TESTE.BAR, -p, SGMBEntities, -o, SGMBEntities, -trace, -cleanBuild, -wmbtData] }
[2015/08/06/10:33:45] [INFO] CommandProcessor: process { Disable auto-build before opening the projects }
[2015/08/06/10:33:45] [INFO] CommandProcessor: openWorkspace { }
[2015/08/06/10:33:45] [INFO] CommandProcessor: openWorkspace { List of projects to be processed: SGMBEntities }
[2015/08/06/10:33:45] [INFO] CommandProcessor: addReferencedProjectForAppOrLib { List of reference projects for project D:\Jenkins\jobs\Prj_Build_serviceteste\workspace\SGMBEntities\.project to be processed: SGMBLibrary }
[2015/08/06/10:33:45] [INFO] CommandProcessor: addReferencedProjectForAppOrLib { List of reference projects for project D:\Jenkins\jobs\Prj_Build_serviceteste\workspace\SGMBLibrary\.project to be processed: SGMBLibraryJava }
[2015/08/06/10:33:45] [INFO] OpenWorkspaceRunnable: run { Creating project: SGMBLibrary }
[2015/08/06/10:33:45] [INFO] OpenWorkspaceRunnable: run { Opening project: SGMBLibrary }
[2015/08/06/10:33:45] [INFO] OpenWorkspaceRunnable: run { Creating project: SGMBLibraryJava }
[2015/08/06/10:33:45] [INFO] OpenWorkspaceRunnable: run { Opening project: SGMBLibraryJava }
[2015/08/06/10:33:45] [INFO] OpenWorkspaceRunnable: run { Creating project: SGMBEntities }
[2015/08/06/10:33:45] [INFO] OpenWorkspaceRunnable: run { Opening project: SGMBEntities }
[2015/08/06/10:33:46] [INFO] CommandProcessor: process { Enable auto-build after the projects are opened }
[2015/08/06/10:33:46] [INFO] CommandProcessor: waitForBuildsToComplete { Waiting for build to complete }
|
same behaviour, waiting for build to complete ... 
fjb_saper can you teach me on how to gather a trace file from mqsicreatebar ?
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Aug 06, 2015 4:54 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Does the behavior change if you don't use a CALL statement but merely launch the mqsicreatebar command ?
| Code: |
| D:\Jenkins\jobs\Prj_Build_serviceteste\workspace>"C:\Program Files (x86)\IBM\WMBT800\mqsicreatebar.exe" -data D:\Jenkins\jobs\Prj_Build_serviceteste\workspace -b SGMBEntities_TESTE.BAR -p SGMBEntities -o SGMBEntities -trace -cleanBuild |
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Aug 06, 2015 4:58 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
The way you set it up I'd expect the log would go to std out.
The help says
| Quote: |
'-trace' to display trace information for the command
'-v traceFilePath' to specify output log file name or path where the tracing data will be written to.
It is applicable only if the -trace option is set. If only file name or relative path is
specified then the file will be written to the default working directory. |
I would strongly recommend that you use the -v option in conjunction with -trace and then let it run its 15 mins. The trace file will then be able to tell you where the time was spent. I expect that you may have some major time spent in preparing the workspace. This would be the case if the toolkit is running low on memory (-Xmx set too low?) or the system memory is too low and you have paging going on...
How does it compare to running mqsicreatebar manually on the system?
What are your memory parameters for running Jenkins?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Thu Aug 06, 2015 5:36 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
ok makes sense,
eclipse.ini
| Quote: |
-vm
C:\Program Files (x86)\IBM\WMBT800\jdk\jre\bin\javaw.exe
-startup
plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
-install
C:\Program Files (x86)\IBM\WMBT800
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.2.R36x_v20101222
-vmargs
-Xquickstart
-Xms40m
-Xmx1024m
-Xmnx64m
-Xgcpolicy:gencon
-Xscmx96m
-Xshareclasses:name=IBMSDP_%u
-Xnolinenumbers
-XX:MaxPermSize=256M
-Xmaxf0.1
-Xminf0.05
-Xverify:none
|
jenkins.xml
| Quote: |
<!--
The MIT License
Copyright (c) 2004-2009, Sun Microsystems, Inc., Kohsuke Kawaguchi
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
-->
<!--
Windows service definition for Jenkins
To uninstall, run "jenkins.exe stop" to stop the service, then "jenkins.exe uninstall" to uninstall the service.
Both commands don't produce any output if the execution is successful.
-->
<service>
<id>jenkins</id>
<name>Jenkins</name>
<description>This service runs Jenkins continuous integration system.</description>
<env name="JENKINS_HOME" value="%BASE%"/>
<!--
if you'd like to run Jenkins with a specific version of Java, specify a full path to java.exe.
The following value assumes that you have java in your PATH.
-->
<executable>%BASE%\jre\bin\java</executable>
<arguments>-Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "%BASE%\jenkins.war" --httpPort=8080</arguments>
<!--
interactive flag causes the empty black Java window to be displayed.
I'm still debugging this.
<interactive />
-->
<logmode>rotate</logmode>
<onfailure action="restart" />
</service>
|
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Aug 06, 2015 5:44 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The jenkins memory shouldn't have any effect on the Toolkit memory.
They both run as separate processes, with their own memory stack.
The memory on the machine certainly has an effect. |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Thu Aug 06, 2015 5:53 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
I've setup jenkins job to execute:
| Quote: |
D:\Jenkins\jobs\Prj_Build_serviceteste\workspace>call "C:\Program Files (x86)\IBM\WMBT800\mqsicreatebar.exe" -data D:\Jenkins\jobs\Prj_Build_serviceteste\workspace -b SGMBEntities_TESTE.BAR -p SGMBEntities -o SGMBEntities -trace -cleanBuild -v c:\temp\build_log.txt"
|
After running for 24 minutes the trace file (C:\temp\build_log.txt):
| Quote: |
[2015/08/06/14:26:44] [INFO] CommandProcessor: process { mqsicreatebar arguments: }
[2015/08/06/14:26:44] [INFO] CommandProcessor: process { [-b, SGMBEntities_TESTE.BAR, -p, SGMBEntities, -o, SGMBEntities, -trace, -cleanBuild, -v, c:\temp\build_log.txt, -wmbtData] }
[2015/08/06/14:26:44] [INFO] CommandProcessor: process { Disable auto-build before opening the projects }
[2015/08/06/14:26:44] [INFO] CommandProcessor: openWorkspace { }
[2015/08/06/14:26:44] [INFO] CommandProcessor: openWorkspace { List of projects to be processed: SGMBEntities }
[2015/08/06/14:26:44] [INFO] CommandProcessor: addReferencedProjectForAppOrLib { List of reference projects for project D:\Jenkins\jobs\Prj_Build_serviceteste\workspace\SGMBEntities\.project to be processed: SGMBLibrary }
[2015/08/06/14:26:44] [INFO] CommandProcessor: addReferencedProjectForAppOrLib { List of reference projects for project D:\Jenkins\jobs\Prj_Build_serviceteste\workspace\SGMBLibrary\.project to be processed: SGMBLibraryJava }
[2015/08/06/14:26:44] [INFO] OpenWorkspaceRunnable: run { Creating project: SGMBLibrary }
[2015/08/06/14:26:44] [INFO] OpenWorkspaceRunnable: run { Opening project: SGMBLibrary }
[2015/08/06/14:26:44] [INFO] OpenWorkspaceRunnable: run { Creating project: SGMBLibraryJava }
[2015/08/06/14:26:44] [INFO] OpenWorkspaceRunnable: run { Opening project: SGMBLibraryJava }
[2015/08/06/14:26:44] [INFO] OpenWorkspaceRunnable: run { Creating project: SGMBEntities }
[2015/08/06/14:26:44] [INFO] OpenWorkspaceRunnable: run { Opening project: SGMBEntities }
[2015/08/06/14:26:46] [INFO] CommandProcessor: process { Enable auto-build after the projects are opened }
[2015/08/06/14:26:47] [INFO] CommandProcessor: waitForBuildsToComplete { Waiting for build to complete }
|
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Aug 06, 2015 5:58 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| ruimadaleno wrote: |
[2015/08/06/14:26:47] [INFO] CommandProcessor: waitForBuildsToComplete { Waiting for build to complete }
|
That's really the last line in the trace file?
Again, what happens if you run the Toolkit manually, instead of from Jenkins, with the same workspace and the same command?
Last edited by mqjeff on Thu Aug 06, 2015 6:11 am; edited 1 time in total |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Thu Aug 06, 2015 6:10 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
running from command line:
| Quote: |
C:\Windows\System32>
C:\Windows\System32>d:
D:\>cd D:\Jenkins\jobs\Prj_Build_serviceteste\workspace
D:\Jenkins\jobs\Prj_Build_serviceteste\workspace>call "C:\Program Files (x86)\IB
M\WMBT800\mqsicreatebar.exe" -data D:\Jenkins\jobs\Prj_Build_serviceteste\worksp
ace -b SGMBEntities_TESTE.BAR -p SGMBEntities -o SGMBEntities -trace -cleanBuild
-v c:\temp\build_log.txt"
!SESSION 2015-08-06 15:06:14.880 -----------------------------------------------
eclipse.buildId=unknown
java.fullversion=JRE 1.6.0 IBM J9 2.4 Windows 7 x86-32 jvmwi3260sr16fp4-20150406
_242976 (JIT enabled, AOT enabled)
J9VM - 20150406_242976
JIT - r9_20150402_88984
GC - GA24_Java6_SR16_20150406_1410_B242976
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=pt_PT
Framework arguments: -noupdate -application com.ibm.etools.mft.bar.cmdline.mqsi
createbar -b SGMBEntities_TESTE.BAR -p SGMBEntities -o SGMBEntities -trace -clea
nBuild -v c:\temp\build_log.txt -wmbtData
Command-line arguments: -noupdate -os win32 -ws win32 -arch x86 -application co
m.ibm.etools.mft.bar.cmdline.mqsicreatebar -data D:\Jenkins\jobs\Prj_Build_servi
ceteste\workspace -b SGMBEntities_TESTE.BAR -p SGMBEntities -o SGMBEntities -tra
ce -cleanBuild -v c:\temp\build_log.txt -wmbtData
!ENTRY org.eclipse.emf.ecore 2 0 2015-08-06 15:06:15.754
!MESSAGE Both 'com.ibm.ccl.mapping.codegen.xslt' and 'com.ibm.hcls.sdg' register
an extension parser for 'map'
Command log file is set to: c:\temp\build_log.txt
|
c:\temp\build_log.txt
| Quote: |
[2015/08/06/15:09:10] [INFO] CommandProcessor: process { mqsicreatebar arguments: }
[2015/08/06/15:09:10] [INFO] CommandProcessor: process { [-b, SGMBEntities_TESTE.BAR, -p, SGMBEntities, -o, SGMBEntities, -trace, -cleanBuild, -v, c:\temp\build_log.txt , -wmbtData] }
[2015/08/06/15:09:11] [INFO] CommandProcessor: process { Disable auto-build before opening the projects }
[2015/08/06/15:09:11] [INFO] CommandProcessor: openWorkspace { }
[2015/08/06/15:09:11] [INFO] CommandProcessor: openWorkspace { List of projects to be processed: SGMBEntities }
[2015/08/06/15:09:11] [INFO] CommandProcessor: addReferencedProjectForAppOrLib { List of reference projects for project D:\Jenkins\jobs\Prj_Build_serviceteste\workspace\SGMBEntities\.project to be processed: SGMBLibrary }
[2015/08/06/15:09:11] [INFO] CommandProcessor: addReferencedProjectForAppOrLib { List of reference projects for project D:\Jenkins\jobs\Prj_Build_serviceteste\workspace\SGMBLibrary\.project to be processed: SGMBLibraryJava }
[2015/08/06/15:09:11] [INFO] OpenWorkspaceRunnable: run { Creating project: SGMBLibrary }
[2015/08/06/15:09:11] [INFO] OpenWorkspaceRunnable: run { Opening project: SGMBLibrary }
[2015/08/06/15:09:11] [INFO] OpenWorkspaceRunnable: run { Creating project: SGMBLibraryJava }
[2015/08/06/15:09:11] [INFO] OpenWorkspaceRunnable: run { Opening project: SGMBLibraryJava }
[2015/08/06/15:09:11] [INFO] OpenWorkspaceRunnable: run { Creating project: SGMBEntities }
[2015/08/06/15:09:11] [INFO] OpenWorkspaceRunnable: run { Opening project: SGMBEntities }
[2015/08/06/15:09:12] [INFO] CommandProcessor: process { Enable auto-build after the projects are opened }
[2015/08/06/15:09:12] [INFO] CommandProcessor: waitForBuildsToComplete { Waiting for build to complete }
|
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
|
|
|
  |
Goto page 1, 2 Next |
Page 1 of 2 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
