Jenkins and Synergy 7.1 ::Assistance Needed::

[michaeltr]

*Hello,

I have recently joined a team that is using Synergy 7.1.0.1 and wants to use
Jenkins as a build manager. I've installed Jenkins and the Synergy Plug-in
on our RedHat Enterprise Linux 5.0 server. All software installations were
successful, but when I create a project in Jenkins and click build I get the
following messages:*

Building in workspace /var/lib/jenkins/jobs/secondTestJob-2/workspace
$ /usr/local/ccm71/bin/ccm start -d /data/ccmdb/testdb -nogui -m -q -h
ncml01-cmdmsp01
[workspace] $ /usr/local/ccm71/bin/ccm start -d /data/ccmdb/testdb -nogui -m
-q -h ncml01-cmdmsp01
ncml01-cmdmsp01:54702:172.17.69.60

$ /usr/local/ccm71/bin/ccm attr -s status -p secondTestJob-2
[workspace] $ /usr/local/ccm71/bin/ccm attr -s status -p secondTestJob-2
ccm command failed
Specified project cannot be identified: 'secondTestJob-2'

Command: The environment was :
CCM_ADDR=ncml01-cmdmsp01:54702:172.17.69.60
CCM_UILOG=/usr/local/ccm71/log/ccm_ui.log
CCM_ENGLOG=/usr/local/ccm71/log/ccm_eng.log
CCM_HOME=/usr/local/ccm71
PATH=$CCM_HOME/bin:$PATH
$ /usr/local/ccm71/bin/ccm stop
[workspace] $ /usr/local/ccm71/bin/ccm stop
IBM Rational Synergy engine exiting.

Finished: FAILURE

*After spending several days researching and testing other methods of fixing
this problem, I cannot find a workable solution. The Synergy engine is
starting and stopping correctly, but the problem seems to be in the work
area. My builds are showing as FAILURE but there is information being
written to the /var/lib/jenkins/jobs/secondTestJob-2/builds folder.
build.xml and log.*

*This is what build.xml contains:*
<hudson.maven.MavenModuleSetBuild>
<actions>
<hudson.model.CauseAction>
<causes>
<hudson.model.Cause_-UserIdCause/>
</causes>
</hudson.model.CauseAction>
</actions>
<number>8</number>
<result>FAILURE</result>
<duration>6520</duration>
<charset>UTF-8</charset>
<keepLog>false</keepLog>
<builtOn></builtOn>
<workspace>/var/lib/jenkins/jobs/secondTestJob-2/workspace</workspace>
<hudsonVersion>1.465</hudsonVersion>
<scm class="hudson.scm.NullChangeLogParser"/>
<culprits class="com.google.common.collect.EmptyImmutableSortedSet"/>
</hudson.maven.MavenModuleSetBuild>

*I'm not really sure where to go from here. I've done some reading and have
seen that Synergy Plug-in development has slowed or mostly stopped, but any
assistance that can be offered would be greatly appreciated.*

-Michael

--
View this message in context: http://jenkins.361315.n4.nabble.com/Jenkins-and-Synergy-7-1-Assistance-Needed-tp4631316.html
Sent from the Jenkins dev mailing list archive at Nabble.com.

[Emanuele Zattin]

Oh... another poor Synergy user. I feel your pain!

Did you try running the same commands from the command line with the user you're running Jenkins from?

From the logs you provide it looks like Synergy is not able to find a project with the name you provided.

BR,

Emanuele Zattin
---------------------------------------------------
-I don't have to know an answer. I don't feel frightened by not knowing things; by being lost in a mysterious universe without any purpose — which is the way it really is, as far as I can tell, possibly. It doesn't frighten me.- Richard Feynman

[cjo]

Further to Emanuele's response,

You should check the name of the project you entered as the -2 at the end seems to 

indicate a version and doing a few tests, shows that you also need :project:[instance] in this 

case if your database is DCM enabled.

In our case we have DCM enabled (ability to transfer tasks and projects between 

different synergy databases), and this then causes you to have to specify all parts  

of the 4-part names in most command line calls.

In my case doing (assuming default delimiters)

ccm attr -s status -p <projectname>-<version>   >> fails

ccm attr -s status -p <projectname>-<version>:project   >> fails

ccm attr -s status -p <projectname>-<version>:project:<instance>   >> success

And synergy is not that bad once you get to know it, it just takes some time 

and willingness to learn.

[michaeltr]

Correct, it does not work from the command line.

If I create a project in Jenkins, are these projects supposed to show up if
I were to log into the Synergy Client? If so, they're not. Or, am I suppose
to create a project in Synergy then make a duplicate build project in
Jenkins?

Michael



--
View this message in context: http://jenkins.361315.n4.nabble.com/Jenkins-and-Synergy-7-1-Assistance-Needed-tp4631316p4631327.html

[michaeltr]

*Hey CJO,

If I make a project in Jenkins called "testProject" and try to build it,
this is what I'm getting from Jenkins. It fails at the same point, but the
error message is different. I'm not using multiple Synergy installations and
Jenkins is installed on the same box as Synergy, Change and RDS.*


Started by user anonymous
Building in workspace /var/lib/jenkins/jobs/testProject/workspace

$ /usr/local/ccm71/bin/ccm start -d /data/ccmdb/testdb -nogui -m -q -h

ncml01-cmdmsp01 -u /usr/local/ccm71

[workspace] $ /usr/local/ccm71/bin/ccm start -d /data/ccmdb/testdb -nogui -m

-q -h ncml01-cmdmsp01 -u /usr/local/ccm71
ncml01-cmdmsp01:40803:172.17.69.60

$ /usr/local/ccm71/bin/ccm attr -s status -p testProject
[workspace] $ /usr/local/ccm71/bin/ccm attr -s status -p testProject
ccm command failed
Project reference requires name and version optionally followed by instance:
'testProject'

Command: The environment was :
CCM_ADDR=ncml01-cmdmsp01:40803:172.17.69.60

CCM_UILOG=/usr/local/ccm71/log/ccm_ui.log
CCM_ENGLOG=/usr/local/ccm71/log/ccm_eng.log
CCM_HOME=/usr/local/ccm71
PATH=$CCM_HOME/bin:$PATH
$ /usr/local/ccm71/bin/ccm stop
[workspace] $ /usr/local/ccm71/bin/ccm stop
IBM Rational Synergy engine exiting.

Finished: FAILURE

*I'm not sending any of these commands manually. All I'm doing is clicking
Build Now, Jenkins is building the commands from the information I put in
the configuration.

So If I use your example ccm attr command, where are the values you're
referencing actually assigned?

ccm: assigned in configure jenkins
attr: java code
-s : java code
-p : java code
<project name> : Project Configuration
- : ??
<Version>: ??
:project: ?? Not sure how this is formatted is it the project name again?
<instance>: What this one means either.

You're probably correct on this, but I just don't have the synergy
background.*

Thanks,

Michael

--
View this message in context: http://jenkins.361315.n4.nabble.com/Jenkins-and-Synergy-7-1-Assistance-Needed-tp4631316p4631329.html

[cjo]

From your comments, it seems that you have been dropped in at the deep end with this work, regarding Synergy and Jenkins.

The synergy plugin requires that a project is already created in synergy and this is accessible by the jenkins user. 

This is so that it can check synergy for changes.

(can't remember if this has to be a released or intergrate or prep state one)

So here are the basics that you need to do, to get this to work.

synergy objects are referenced by 4 part names 

<name> : name of project, file, dir etc
- delimiter between name and version 

<Version> Version of the object 

:

:project: ?? Not sure how this is formatted is it the project name again? 
<instance>: What this one means either. 

Open Synergy as jenkins user and create or find an existing project. (i.e. find a prep or released project)

The project name will be the 

<project name> : Project Configuration 
- : ?? 
<Version>: ?? 
:project: ?? Not sure how this is formatted is it the project name again? 
<instance>: What this one means either. 

Set this project as 

"Project name"

[cjo]

Sorry about the previous incomplete post,

This is what it should have been:

From your comments, it seems that you have been dropped in at the deep end with this work, regarding Synergy and Jenkins.

The synergy plugin requires that a project is already created in synergy and this is accessible by the jenkins user. 

This is so that it can check synergy for changes.

So here are the basics that you need to do, to get this to work.

synergy objects are referenced by 4 part names 

<name> : name of project, file, dir etc

- delimiter between name and version 

<Version> Version of the object 

: delimiter between version and type

<type> - type of object, (project, csrc, header, dir, etc)

: delimiter between type and instance

<instance> - identifier for the originating database only when using DCM.

As you do not have DCM enabled in most cases name and version will only be needed for projects (as shown in gui)

Open Synergy as jenkins user and find an existing project, (i.e. find a prep or released project)

 or create a new working project.(name=testProject in your case, on creation version will default to 1)

 

 

Set this project as 

"Project name" This will be all of the project name until the first ":" displayed in synergy

("testProject-1" if you created a new project)

Then running the job should allow jenkins to copy or set the workspace to its workspace

and you should see the files visible in the workspace.

I'm afraid I cannot help you much after this point regarding the synergy plugin 

as Emanuele (and others) branched it early in its life and full customised it to work with our 

companies process, which required a large amount of changes and are not really 

compatable with other uses of synergy.

Chris

[michaeltr]

Thank you very much for providing on this issue. This information allowed me
to create a successful build on my project. Key points being usage of the
naming convention, and creation of the project (by the same Jenkins user
account) in Synergy.

-Michael

--
View this message in context: http://jenkins.361315.n4.nabble.com/Jenkins-and-Synergy-7-1-Assistance-Needed-tp4631316p4631438.html