[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins

1,561 views
Skip to first unread message

dinaa.mca@gmail.com (JIRA)

unread,
Jul 31, 2018, 2:10:03 AM7/31/18
to jenkinsc...@googlegroups.com
Dineshkumar N created an issue
 
Jenkins / Bug JENKINS-52810
Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Issue Type: Bug Bug
Assignee: KaiHsiang Chang
Components: parameterized-remote-trigger-plugin
Created: 2018-07-31 06:09
Environment: Parameterized Remote Trigger Plugin version - 3.0.3
My Jenkins version - 2.121.2
Remote Jenkins version - 2.73.3
Priority: Blocker Blocker
Reporter: Dineshkumar N

While triggering remote jenkins job from my local jenkins it was working with the version 2.2.2. But since few weeks it was not triggering, so we have updated the Parameterized Remote Trigger Plugin version from 2.2.2 to 3.0.3. But still the remote jenkins job and was showing the below issue:

Run condition [Execute Windows Batch commands] enabling perform for step [BuilderChain]
ERROR: Build step failed with exception
java.lang.NullPointerException
at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.evaluateEffectiveRemoteHost(RemoteBuildConfiguration.java:385)
at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:533)
at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:514)
at org.jenkinsci.plugins.conditionalbuildstep.BuilderChain.perform(BuilderChain.java:71)
at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110)
at org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154)
at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105)
at org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuilder.perform(ConditionalBuilder.java:134)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
at hudson.model.Build$BuildExecution.build(Build.java:206)
at hudson.model.Build$BuildExecution.doRun(Build.java:163)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
at hudson.model.Run.execute(Run.java:1798)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Build step 'Conditional steps (multiple)' marked build as failure

In the remote jenkins i have given a folder path, in that particular folder it has around 5 jobs and I wanted to trigger all of them. But it triggers 1st job alone and fails with the above issue.

 
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

cash924n@gmail.com (JIRA)

unread,
Jul 31, 2018, 2:15:01 AM7/31/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang commented on Bug JENKINS-52810
 
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins

Would you check your job and global configuration setting first against the release note? 

It's a huge change from v2.2.2 to v3.x. 

Or, would you share the configuration image for me? 

 

 

dinaa.mca@gmail.com (JIRA)

unread,
Jul 31, 2018, 2:33:02 AM7/31/18
to jenkinsc...@googlegroups.com

The configurations are proper. PFA.

dinaa.mca@gmail.com (JIRA)

unread,
Jul 31, 2018, 2:33:02 AM7/31/18
to jenkinsc...@googlegroups.com
Dineshkumar N updated an issue
 
Change By: Dineshkumar N
Attachment: Configuration.png

cash924n@gmail.com (JIRA)

unread,
Jul 31, 2018, 2:54:02 AM7/31/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang commented on Bug JENKINS-52810
 
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins

thanks, would you also provide the global remote host configuration? 

dinaa.mca@gmail.com (JIRA)

unread,
Jul 31, 2018, 4:50:01 AM7/31/18
to jenkinsc...@googlegroups.com
Dinesh commented on Bug JENKINS-52810

Yes, we use it Jenkins A. There we will be providing a "Display name" and "Remote Jenkins URL", then the same will be reflecting under "Select a remote host" inside the Server Info for the job.

cash924n@gmail.com (JIRA)

unread,
Aug 1, 2018, 8:45:02 AM8/1/18
to jenkinsc...@googlegroups.com

Dinesh, you should check your remote server configuration.

If the URL can be correctly parsed, it's no way that url.getHost() throw NPE. 

String addr = server.getAddress(); 
if (addr != null) { 
  URL url = new URL(addr); 
  Semaphore s = hostLocks.get(url.getHost());  <---- line 385

By the way, in the 3.x.x releases, almost every release has some configuration changes.

Although most of them are adding fields to the original configuration, you should still check your setting. 

cash924n@gmail.com (JIRA)

unread,
Aug 1, 2018, 8:46:02 AM8/1/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang started work on Bug JENKINS-52810
 
Change By: KaiHsiang Chang
Status: Open In Progress

dinaa.mca@gmail.com (JIRA)

unread,
Aug 2, 2018, 1:51:02 AM8/2/18
to jenkinsc...@googlegroups.com
Dinesh commented on Bug JENKINS-52810

I have validated the configurations and all are proper. When i executed the build i am facing the below issue without a configuration change :

fail to accquire lock because of timeout, skip locking...
CSRF protection is disabled on the remote server.
fail to accquire lock because of timeout, skip locking...
Connection to remote server failed [404], waiting for to retry - 10 seconds until next attempt. URL: https://<Jenkins_URL>/view/All/queue/item/81305/api/json/,
parameters: Retry attempt #1 out of 5
Connection to remote server failed [404], waiting for to retry - 10 seconds until next attempt. URL: https://<Jenkins_URL>/view/All/queue/item/81305/api/json/
parameters: Retry attempt #2 out of 5
Connection to remote server failed [404], waiting for to retry - 10 seconds until next attempt. URL: https://<Jenkins_URL>/view/All/queue/item/81305/api/json/,
parameters:
Retry attempt #3 out of 5
Connection to remote server failed [404], waiting for to retry - 10 seconds until next attempt. URL: https://<Jenkins_URL>/view/All/queue/item/81305/api/json/,
parameters:
Retry attempt #4 out of 5
Connection to remote server failed [404], waiting for to retry - 10 seconds until next attempt. URL: https://<Jenkins_URL>/view/All/queue/item/81305/api/json/,
parameters:
Retry attempt #5 out of 5
ERROR: Remote build failed with 'ExceedRetryLimitException' for the following reason: 'Max number of connection retries have been exeeded.'.
ERROR: ExceedRetryLimitException: Max number of connection retries have been exeeded.

BTW, in the error "view/All/queue/item/81305/api/json/" is automatically getting added. If that is added in URL the same path will not be present. Kindly can you provide your inputs.

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 2:06:03 AM8/2/18
to jenkinsc...@googlegroups.com

fail to accquire lock because of timeout, skip locking... <— this line wasn't related to your problem

Connection to remote server failed [404], waiting for to retry - 10 seconds until next attempt. URL: https://<Jenkins_URL>/view/All/queue/item/81305/api/json/, <--- this line told the problem,

Please check your remote server URL in either global configuration & job configuration, and check your job name or URL  as well, 

the segment "view/All" is definitely added by some mistakes and definitely not auto-generated by this plugin. 

 

I could almost 99% recognize this issue as a man-made error ...

Be more specifically, your job URL should be in http://*some_jenkins_host*/job/*some_job_name*/ instead of directly copy the URL with view in it.

Without the specific job URL, there's no way to 100% tell an accurate job name.

So, please,

use the url format i gave,

or just give a job name along with the remote server config whose URL should be http://*some_jenkins_host* .

 

Hope this will help you out.

 

 

 

dinaa.mca@gmail.com (JIRA)

unread,
Aug 2, 2018, 2:42:01 AM8/2/18
to jenkinsc...@googlegroups.com
Dinesh commented on Bug JENKINS-52810

I agree with your point, but in the URL at last it is appending queue/item/<Some Random Number>/api/json and now that is the place where the issue is with, and we are not pretty sure from where this is getting appended.

Even after providing the URL with the same format provided by you, still the same issue exists with the URL and it shows:

Connection to remote server failed [404], waiting for to retry - 10 seconds until next attempt. URL: https://<Jenkins_URL>/<FolderPath&FolderName>/queue/item/81594/api/json/, parameters:

Retry attempt #5 out of 5
ERROR: Remote build failed with 'ExceedRetryLimitException' for the following reason: 'Max number of connection retries have been exeeded.'.
ERROR: ExceedRetryLimitException: Max number of connection retries have been exeeded.

Finished: FAILURE

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 2:53:02 AM8/2/18
to jenkinsc...@googlegroups.com

Maybe you can provide the remote server config with replacement of your server name like http://my_jenkins:8080/ and so as the job config instead of blur the image.

Because all I can tell is that something wrong with your settings from the provided information.

 

dinaa.mca@gmail.com (JIRA)

unread,
Aug 2, 2018, 3:01:01 AM8/2/18
to jenkinsc...@googlegroups.com
Dinesh updated an issue
 
Change By: Dinesh
Attachment: TimeOutRemoteTrigger.png

dinaa.mca@gmail.com (JIRA)

unread,
Aug 2, 2018, 3:05:02 AM8/2/18
to jenkinsc...@googlegroups.com
Dinesh commented on Bug JENKINS-52810
 
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins

Please find my remote server configuration attached:

(As I have already mentioned, I wanted to trigger some 5 jobs inside folder, i wanted to provide my folder name in the URL)

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 3:06:01 AM8/2/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang updated an issue
 
Change By: KaiHsiang Chang
Attachment: image-2018-08-02-15-05-19-964.png

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 3:08:02 AM8/2/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang updated an issue
Change By: KaiHsiang Chang
Attachment: image-2018-08-02-15-07-31-063.png

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 3:09:02 AM8/2/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang updated an issue
Change By: KaiHsiang Chang
Attachment: image-2018-08-02-15-08-56-621.png

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 3:10:02 AM8/2/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang commented on Bug JENKINS-52810
 
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins

Yeah, much more easier...

The remote server config is not designed for specific job or folder, so you can use the full folder url in it...

It should be http://myjenkins:8080/ only.

 

Then, in your job config, if you want to trigger a folder-ed job , 

set the job name like the Jenkins reminds you,

 

 

then, it goes as what you expected.

 

 

 

 

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 3:10:02 AM8/2/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang edited a comment on Bug JENKINS-52810
Yeah, much more easier...

The remote server config is not designed for specific job or folder, so you can 't use the full folder url in it...


It should be [http://myjenkins:8080/] only.

 

Then, in your job config, if you want to trigger a folder-ed job , 

!image-2018-08-02-15-05-19-964.png!


set the job name like the Jenkins reminds you,

 

!image-2018-08-02-15-07-31-063.png!


 

then, it goes as what you expected.

 

!image-2018-08-02-15-08-56-621.png!

 

 

 

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 3:11:02 AM8/2/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang stopped work on Bug JENKINS-52810
 
Change By: KaiHsiang Chang
Status: In Progress Open

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 3:11:02 AM8/2/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang started work on Bug JENKINS-52810
 
Change By: KaiHsiang Chang
Status: Open In Progress

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 3:47:02 AM8/2/18
to jenkinsc...@googlegroups.com

If everything is okay after you fixed the setting, please let me know.

I'm going to close this ticket.

dinaa.mca@gmail.com (JIRA)

unread,
Aug 2, 2018, 5:21:01 AM8/2/18
to jenkinsc...@googlegroups.com
Dinesh commented on Bug JENKINS-52810

In the folder, out of number of jobs it is triggering only the 1st job and failing with the same issue.

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 5:25:01 AM8/2/18
to jenkinsc...@googlegroups.com

The plugin didn't support your batch scenario, and you should compose job steps by yourself.  (with other plugins or pipelines, etc.)

Failing with the same issue? could you paste the message? 

 

 

 

dinaa.mca@gmail.com (JIRA)

unread,
Aug 2, 2018, 5:35:01 AM8/2/18
to jenkinsc...@googlegroups.com
Dinesh updated an issue
 
Change By: Dinesh
Attachment: RemoteTriggerFailure.png

dinaa.mca@gmail.com (JIRA)

unread,
Aug 2, 2018, 5:36:02 AM8/2/18
to jenkinsc...@googlegroups.com
Dinesh commented on Bug JENKINS-52810
 
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins

I have updated the configurations according to what you have suggested, and we face the issue as attached.

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 5:46:02 AM8/2/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang updated an issue
 
Change By: KaiHsiang Chang
Attachment: image-2018-08-02-17-45-54-123.png

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 5:47:02 AM8/2/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang updated an issue
Change By: KaiHsiang Chang
Attachment: image-2018-08-02-17-46-28-212.png

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 5:51:01 AM8/2/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang updated an issue
Change By: KaiHsiang Chang
Attachment: image-2018-08-02-17-49-59-985.png

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 5:53:03 AM8/2/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang edited a comment on Bug JENKINS-52810
 
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Is the blur part the "*root of your remote jenkins master*" !?

The blur part should be identical to the URL of your remote server config. 

The length of the blur URLs in retry log  are is far more different from the trigger starting log.

!image-2018-08-02-17-46-28-212.png!

!image-2018-08-02-17-45-54-123.png!

 

These two parts should be identical.

How could that be ? Still, I think you should check your setting in both side.

Maybe check the "Jenkins URL" setting of remote Jenkins server is the same with you configure in the "URL of remote server jenkins" of local Jenkins server.

!image-2018-08-02-17-49-59-985.png!

 

 

 

 

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 5:53:04 AM8/2/18
to jenkinsc...@googlegroups.com

Is the blur part the "root of your remote jenkins master" !?

The blur part should be identical to the URL of your remote server config. 

The length of the blur URLs in retry log  are far more different from the trigger starting log.

 

These two parts should be identical.

How could that be ? Still, I think you should check your setting in both side.

Maybe check the "Jenkins URL" setting of remote Jenkins server is the same with you configure in the "URL of remote server jenkins" of local Jenkins server.

 

 

 

 

dinaa.mca@gmail.com (JIRA)

unread,
Aug 2, 2018, 6:02:01 AM8/2/18
to jenkinsc...@googlegroups.com
Dinesh commented on Bug JENKINS-52810

Both the URL's are identical only, since i have blurred it was looking like a different URL.

dinaa.mca@gmail.com (JIRA)

unread,
Aug 2, 2018, 6:05:01 AM8/2/18
to jenkinsc...@googlegroups.com
Dinesh edited a comment on Bug JENKINS-52810
Both the URL's are identical only, since i have blurred it was looking like a different URL.


In the remote server failing part in log (json appending URL), the URL is coming till which i have mentioned in the jenkins A configuration only. The remaining URL which i am giving in my job is not reflecting in the URL (Folder name and job name is not appending with the URL).

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 6:07:02 AM8/2/18
to jenkinsc...@googlegroups.com

Dinesh, even now, I think it's still a configuration issue.

I suggest that you can check you setting along with the source code. 

Except for the batch triggering part, the nested folder triggering is well-supported and I can't reproduce your case. 

dinaa.mca@gmail.com (JIRA)

unread,
Aug 2, 2018, 6:55:02 AM8/2/18
to jenkinsc...@googlegroups.com
Dinesh commented on Bug JENKINS-52810

Can you please share your both jenkins configurations for reference, so that i will still validate accordingly.

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 7:10:02 AM8/2/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang updated an issue
Change By: KaiHsiang Chang
Attachment: image-2018-08-02-19-09-26-082.png

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 7:14:01 AM8/2/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang commented on Bug JENKINS-52810
 
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins

The remote job 

The remote job config, (I can't upload files in my company, so you need to copy/paste as file by yourself.)
<?xml version='1.0' encoding='UTF-8'?>
<project>
<actions/>
<description></description>
<keepDependencies>false</keepDependencies>
<properties>
<jenkins.model.BuildDiscarderProperty>
<strategyclass="hudson.tasks.LogRotator">
<daysToKeep>-1</daysToKeep>
<numToKeep>500</numToKeep>
<artifactDaysToKeep>-1</artifactDaysToKeep>
<artifactNumToKeep>-1</artifactNumToKeep>
</strategy>
</jenkins.model.BuildDiscarderProperty>
<com.dabsquared.gitlabjenkins.connection.GitLabConnectionPropertyplugin="gitlab...@1.5.8">
<gitLabConnection></gitLabConnection>
</com.dabsquared.gitlabjenkins.connection.GitLabConnectionProperty>
<com.sonyericsson.rebuild.RebuildSettingsplugin="reb...@1.28">
<autoRebuild>false</autoRebuild>
<rebuildDisabled>false</rebuildDisabled>
</com.sonyericsson.rebuild.RebuildSettings>
<hudson.model.ParametersDefinitionProperty>
<parameterDefinitions>
<hudson.model.StringParameterDefinition>
<name>Test</name>
<description></description>
<defaultValue>1</defaultValue>
</hudson.model.StringParameterDefinition>
<hudson.model.StringParameterDefinition>
<name>Test2</name>
<description></description>
<defaultValue>2</defaultValue>
</hudson.model.StringParameterDefinition>
<hudson.model.BooleanParameterDefinition>
<name>Test3</name>
<description></description>
<defaultValue>false</defaultValue>
</hudson.model.BooleanParameterDefinition>
</parameterDefinitions>
</hudson.model.ParametersDefinitionProperty>
<hudson.plugins.throttleconcurrents.ThrottleJobPropertyplugin="throttle-c...@2.0.1">
<maxConcurrentPerNode>0</maxConcurrentPerNode>
<maxConcurrentTotal>0</maxConcurrentTotal>
<categoriesclass="java.util.concurrent.CopyOnWriteArrayList"/>
<throttleEnabled>false</throttleEnabled>
<throttleOption>project</throttleOption>
<limitOneJobWithMatchingParams>false</limitOneJobWithMatchingParams>
<paramsToUseForLimit></paramsToUseForLimit>
</hudson.plugins.throttleconcurrents.ThrottleJobProperty>
</properties>
<scmclass="hudson.scm.NullSCM"/>
<assignedNode>linux_agent</assignedNode>
<canRoam>false</canRoam>
<disabled>false</disabled>
<blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding>
<blockBuildWhenUpstreamBuilding>false</blockBuildWhenUpstreamBuilding>
<authToken>QQ</authToken>
<triggers/>
<concurrentBuild>true</concurrentBuild>
<builders>
<hudson.tasks.Shell>
<command>echo ${Test}
echo ${Test2}
echo ${Test3}
sleep 10
</command>
</hudson.tasks.Shell>
</builders>
<publishers/>
<buildWrappers/>
</project>
 

The local jenkins, plugini config (which should be under your jenkins home, a file named org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.xml)
<?xml version='1.1' encoding='UTF-8'?>
<org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration_-DescriptorImpl plugin="Parameterized-...@3.0.4">
<remoteSites>
<org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteJenkinsServer>
<displayName>abc.inc</displayName>
<hasBuildTokenRootSupport>false</hasBuildTokenRootSupport>
<auth2class="org.jenkinsci.plugins.ParameterizedRemoteTrigger.auth2.TokenAuth">
<userName>cc</userName>
<apiToken>1d748423a99a1d5374400066d179e16b</apiToken>
</auth2>
<address>http://ajenkins:8080</address>
<useProxy>false</useProxy>
</org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteJenkinsServer>
<org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteJenkinsServer>
<displayName>BBB</displayName>
<hasBuildTokenRootSupport>false</hasBuildTokenRootSupport>
<auth2class="org.jenkinsci.plugins.ParameterizedRemoteTrigger.auth2.TokenAuth">
<userName>cc</userName>
<apiToken>adec962e573e698ab34607263f67b03f</apiToken>
</auth2>
<address>http://BBB.inc/</address>
<useProxy>false</useProxy>
</org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteJenkinsServer>
</remoteSites>
</org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration_-DescriptorImpl>
 

The local job config
<?xml version='1.1' encoding='UTF-8'?>
<project>
<actions/>
<description></description>
<keepDependencies>false</keepDependencies>
<properties>
<org.bstick12.jenkinsci.plugins.leastload.LeastLoadDisabledPropertyplugin="leas...@2.0.1">
<leastLoadDisabled>false</leastLoadDisabled>
</org.bstick12.jenkinsci.plugins.leastload.LeastLoadDisabledProperty>
<com.chikli.hudson.plugin.naginator.NaginatorOptOutPropertyplugin="nagi...@1.17.2">
<optOut>false</optOut>
</com.chikli.hudson.plugin.naginator.NaginatorOptOutProperty>
<com.sonyericsson.rebuild.RebuildSettingsplugin="reb...@1.28">
<autoRebuild>false</autoRebuild>
<rebuildDisabled>false</rebuildDisabled>
</com.sonyericsson.rebuild.RebuildSettings>
</properties>
<scmclass="hudson.scm.NullSCM"/>
<assignedNode>slave_ap83</assignedNode>
<canRoam>false</canRoam>
<disabled>false</disabled>
<blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding>
<blockBuildWhenUpstreamBuilding>false</blockBuildWhenUpstreamBuilding>
<triggers/>
<concurrentBuild>false</concurrentBuild>
<builders>
<org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfigurationplugin="Parameterized-...@3.0.4">
<remoteJenkinsName>BBB</remoteJenkinsName>
<auth2class="org.jenkinsci.plugins.ParameterizedRemoteTrigger.auth2.NullAuth"/>
<shouldNotFailBuild>false</shouldNotFailBuild>
<preventRemoteBuildQueue>true</preventRemoteBuildQueue>
<pollInterval>5</pollInterval>
<blockBuildUntilComplete>true</blockBuildUntilComplete>
<job>TestFolder/Test2/RemoteReceiver</job>
<token>QQ</token>
<parameters>Test=1
Test2=2</parameters>
<enhancedLogging>true</enhancedLogging>
<loadParamsFromFile>false</loadParamsFromFile>
<parameterFile></parameterFile>
<maxConn>1</maxConn>
<useCrumbCache>true</useCrumbCache>
<useJobInfoCache>true</useJobInfoCache>
<abortTriggeredJob>true</abortTriggeredJob>
<hostLocks/>
<hostPermits/>
</org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration>
</builders>
<publishers/>
<buildWrappers/>
</project>

trey.bohon@ni.com (JIRA)

unread,
Aug 2, 2018, 10:07:02 AM8/2/18
to jenkinsc...@googlegroups.com
Trey Bohon updated an issue
 
Change By: Trey Bohon
Attachment: image-2018-08-02-09-06-29-421.png

trey.bohon@ni.com (JIRA)

unread,
Aug 2, 2018, 10:09:02 AM8/2/18
to jenkinsc...@googlegroups.com
Trey Bohon commented on Bug JENKINS-52810
 
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins

I get a very similar error with Jenkins 2.107.1, Parameterized Remote Trigger 3.0.3, and Job DSL 1.68 (we update infrequently due to frequent breakage).

However, if I manually go into the job in Jenkins UI and click save/apply before running, I don't encounter the issue.  This makes me think that Job DSL is generating a job configuration that won't be interpreted correctly at execution time, but if mutated with save/apply it updates it properly.

Here's my error:

ERROR: Build step failed with exception
java.lang.NullPointerException
at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.evaluateEffectiveRemoteHost(RemoteBuildConfiguration.java:385)
at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:533)
at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:514)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
at hudson.model.Build$BuildExecution.build(Build.java:206)
at hudson.model.Build$BuildExecution.doRun(Build.java:163)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
at hudson.model.Run.execute(Run.java:1727)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Build step 'Trigger a remote parameterized job' marked build as failure

 

Here is the mutation of the parameterized remote trigger portion of the config.xml:

 

If I manually copy in the job DSL code afterwards, reload configuration from disk, and run without save/apply it repeats the error.

I downloaded the master Job DSL plugin source and it still has the old auth, so I imagine it also will fail.

So from my 3rd party perspective, I'm not sure where the blame goes - Jenkins core for not interpreting the old job source, Job DSL for not updating the generated syntax, or this parameterized remote trigger plugin.  Regardless, if it's not resolved in a few days we're rolling back this plugin.

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 11:04:01 AM8/2/18
to jenkinsc...@googlegroups.com

Trey Bohon thx for your information.

 

First, I have to say that it's a huge code change from 2.2.2 to 3.0.0 which maybe not that fully considered the compatibility but brought many features and bug fixes. It's user's decision to upgrade or not, although the plugin has compatibility remind already. 

 

Second, in this case, I doubt the correctness of original usage ( Dinesh). I've never tried to put the folder URL in the remote server and surprisingly it even works in the old version. All these paradoxical usages are just because the original implementation didn't get the build number in an accurate approach, or more specifically, in a right way. Furthermore, there're many bugs resulted from the wrong build number like 404 not found, wrong status, etc.

So, once the approach is corrected, many of the  paradoxical usages  need to be changed and that's why you guys can't get over through this, and why the compatibility remind was shown in the upgrade page. 

 

IMHO, you guys should setup a testing environment before direct upgrading, and try to fix your processes.

I don't think the plugin needs to be compatible with the old and wrong approach . 

 

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 11:12:02 AM8/2/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang stopped work on Bug JENKINS-52810
 
Change By: KaiHsiang Chang
Status: In Progress Open

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 11:14:02 AM8/2/18
to jenkinsc...@googlegroups.com

And welcome to file a PR even it's just configuration experiences or some documentation. 

Need you guys' help to make the documentation more complete. 

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 9:58:03 PM8/2/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang resolved as Not A Defect
 

Some configurations were misled before v2.x.x, the URL of remote server configuration should be the root URL of remote jenkins or the build number can't be fetched correctly. 

If you have trouble when upgrading, try to fix the configuration in your test environment or you can choose to stay in the old version if no new features are required.
Change By: KaiHsiang Chang
Status: Open Resolved
Resolution: Not A Defect

cash924n@gmail.com (JIRA)

unread,
Aug 2, 2018, 9:59:02 PM8/2/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang edited a comment on Bug JENKINS-52810
 
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Some configurations were misled before v2.x.x, the URL of remote server configuration should be the root URL of remote jenkins , or the build number can't be fetched correctly. 


If you have trouble when upgrading, try to fix the configuration in your test environment or you can choose to stay in the old version if no new features are required.

dinaa.mca@gmail.com (JIRA)

unread,
Aug 6, 2018, 1:38:02 AM8/6/18
to jenkinsc...@googlegroups.com
Dinesh commented on Bug JENKINS-52810

KaiHsiang Chang, Still I have validated the configurations comparing with yours, and now the build is not failing. Now I am facing issue as below, and the build is not ending and still it tried to run the 1st build job in the folder again and again, and it is not trying to execute the 2nd and next build jobs in the folder:

 

################################################################################################################
Parameterized Remote Trigger Configuration:

  • job: <path_name>/<folder_name>/<FirstJobName>
  • remoteJenkinsName: Jenkins Server
  • parameters: [Version1=test22, Version2=test21]
  • blockBuildUntilComplete: false
  • connectionRetryLimit: 5
    ################################################################################################################
    fail to accquire lock because of timeout, skip locking...
    Triggering parameterized remote job 'http://<Jenkins:8080>/job/<FirstJobName>'
    Using globally defined 'Credentials Authentication' as user 'username' (Credentials ID 'my credentials id')
    Triggering remote job now.
    fail to accquire lock because of timeout, skip locking...
    CSRF protection is disabled on the remote server.
    fail to accquire lock because of timeout, skip locking...
    The remote job is blocked. Build #58 is already in progress (ETA:34 min).
    Remote job queue number: 101142
    Waiting for remote build to be executed...
    Waiting for 10 seconds until next poll.
    fail to accquire lock because of timeout, skip locking...
    The remote job is blocked. Build #58 is already in progress (ETA:33 min).
    Waiting for 10 seconds until next poll.
    fail to accquire lock because of timeout, skip locking...
    The remote job is blocked. Build #58 is already in progress (ETA:33 min).
    Waiting for 10 seconds until next poll.
    fail to accquire lock because of timeout, skip locking...
    The remote job is blocked. Build #58 is already in progress (ETA:33 min).
    Waiting for 10 seconds until next poll.
    fail to accquire lock because of timeout, skip locking...
    The remote job is blocked. Build #58 is already in progress (ETA:32 min).
    Waiting for 10 seconds until next poll.
    fail to accquire lock because of timeout, skip locking...
    The remote job is blocked. Build #58 is already in progress (ETA:32 min).
    Waiting for 10 seconds until next poll.
    fail to accquire lock because of timeout, skip locking...
    The remote job is blocked. Build #58 is already in progress (ETA:32 min).
    Waiting for 10 seconds until next poll.
    fail to accquire lock because of timeout, skip locking...
    The remote job is blocked. Build #58 is already in progress (ETA:31 min).
    Waiting for 10 seconds until next poll.
    fail to accquire lock because of timeout, skip locking...

dinaa.mca@gmail.com (JIRA)

unread,
Aug 6, 2018, 1:42:02 AM8/6/18
to jenkinsc...@googlegroups.com
Dinesh edited a comment on Bug JENKINS-52810
[~cashlalala], Still I have validated the configurations comparing with yours, and now the build is not failing. Now I am facing issue as below, and the build is not ending and still it tried to run the 1st build job in the folder again and again, and it is not trying to execute the 2nd and next build jobs in the folder:

 Can you please try to trigger more than 1 job in a particular folder and update whether it is triggering all of them.
 

################################################################################################################
Parameterized Remote Trigger Configuration:
- job: <path_name>/<folder_name>/<FirstJobName>

- remoteJenkinsName: Jenkins Server
- parameters: [Version1=test22, Version2=test21]
- blockBuildUntilComplete: false
- connectionRetryLimit: 5

dinaa.mca@gmail.com (JIRA)

unread,
Aug 6, 2018, 2:28:02 AM8/6/18
to jenkinsc...@googlegroups.com
Dinesh commented on Bug JENKINS-52810

The issue got resolved when the parameter "Block until the remote triggered projects finish their builds" is set to false (Uncheck the check box). The build is green now. Thank you for the support provided KaiHsiang Chang.

cash924n@gmail.com (JIRA)

unread,
Aug 6, 2018, 2:42:02 AM8/6/18
to jenkinsc...@googlegroups.com

Although I'm not a supporter, still glad to hear you solved it. 

Give a like on github if you don't mind, and you can also try to file some PRs about the configuration experience if you have free time.

robert.hencke@gmail.com (JIRA)

unread,
Sep 13, 2018, 1:28:02 PM9/13/18
to jenkinsc...@googlegroups.com
Robert Hencke reopened an issue
 

This is a bug not around the URL being null, but around the hostLocks and hostPermits fields being null when deserializing older configurations.

I have submitted a pull request to fix here:

https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/47
Change By: Robert Hencke
Resolution: Not A Defect
Status: Resolved Reopened
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

cash924n@gmail.com (JIRA)

unread,
Sep 18, 2018, 12:15:03 PM9/18/18
to jenkinsc...@googlegroups.com
KaiHsiang Chang resolved as Fixed
 

PR 47 resolved 

totoroliu1215@hotmail.com (JIRA)

unread,
Sep 25, 2018, 1:08:02 PM9/25/18
to jenkinsc...@googlegroups.com
Rick Liu commented on Bug JENKINS-52810
 
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins

Jenkins core. v.2.121.3
Parameterized Remote Trigger Plugin v.3.0.6

I still see this error from the job console:

{{[Pipeline]

{ [Pipeline] triggerRemoteJob ################################################################################################################ Parameterized Remote Trigger Configuration: - job: https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test - auth: 'Credentials Authentication' as user 'devops' (Credentials ID 'a14c5dae-94e0-4b12-991b-6f7d8620120e') - parameters: [BUILD=5098, LABEL=ECO_130206, ENV=SMOKE_PRODUCTION] - blockBuildUntilComplete: false - connectionRetryLimit: 5 ################################################################################################################ fail to accquire lock because of timeout, skip locking... Triggering parameterized remote job 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test' Using job-level defined 'Credentials Authentication' as user 'devops' (Credentials ID 'a14c5dae-94e0-4b12-991b-6f7d8620120e') Triggering remote job now. fail to accquire lock because of timeout, skip locking... CSRF protection is disabled on the remote server. fail to accquire lock because of timeout, skip locking... Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #1 out of 5 Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #2 out of 5 Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #3 out of 5 Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #4 out of 5 Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #5 out of 5 ERROR: Remote build failed with 'ExceedRetryLimitException' for the following reason: 'Max number of connection retries have been exeeded.'. [Pipeline] }

}}

totoroliu1215@hotmail.com (JIRA)

unread,
Sep 25, 2018, 1:11:02 PM9/25/18
to jenkinsc...@googlegroups.com
Rick Liu edited a comment on Bug JENKINS-52810
Jenkins core. v.2.121.3
Parameterized Remote Trigger Plugin v.3.0.6

I still see this error from the job console:

{ { quote} [Pipeline] {
[Pipeline] } {quote } }

totoroliu1215@hotmail.com (JIRA)

unread,
Sep 25, 2018, 1:12:02 PM9/25/18
to jenkinsc...@googlegroups.com

totoroliu1215@hotmail.com (JIRA)

unread,
Sep 25, 2018, 1:13:02 PM9/25/18
to jenkinsc...@googlegroups.com
Rick Liu edited a comment on Bug JENKINS-52810
Jenkins core. v.2.121.3
Parameterized Remote Trigger Plugin v.3.0.6

I still see this error from the job console:

[Pipeline] {
[Pipeline] triggerRemoteJob

[Pipeline] }

totoroliu1215@hotmail.com (JIRA)

unread,
Sep 25, 2018, 1:17:02 PM9/25/18
to jenkinsc...@googlegroups.com
Change By: Rick Liu
Status: In Review Progress

totoroliu1215@hotmail.com (JIRA)

unread,
Sep 25, 2018, 1:17:02 PM9/25/18
to jenkinsc...@googlegroups.com
Change By: Rick Liu
Status: Resolved In Review

totoroliu1215@hotmail.com (JIRA)

unread,
Sep 25, 2018, 1:19:02 PM9/25/18
to jenkinsc...@googlegroups.com
Rick Liu commented on Bug JENKINS-52810
 
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins

I'm sorry.
I was trying to re-open the issue,
but clicked the wrong butto to resolve the issue.

Could anyone help me to revert my action?

totoroliu1215@hotmail.com (JIRA)

unread,
Sep 25, 2018, 1:23:02 PM9/25/18
to jenkinsc...@googlegroups.com
Rick Liu edited a comment on Bug JENKINS-52810
Jenkins core. v.2.121.3
Parameterized Remote Trigger Plugin v.3.0.6

I still see this error from the job console:







Pipeline code:
triggerRemoteJob auth: CredentialsAuth(credentials: 'xxxxxxxxxxxxx'),
        blockBuildUntilComplete: false,
        job: 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test',
        parameters: """BUILD=${build}\nLABEL=ECO_${ECO_ID}\nENV=SMOKE_PRODUCTION""", pollInterval: 300

totoroliu1215@hotmail.com (JIRA)

unread,
Sep 25, 2018, 1:28:01 PM9/25/18
to jenkinsc...@googlegroups.com
Rick Liu edited a comment on Bug JENKINS-52810
Job Jenkins server:
Jenkins core. v.2.121.3

Parameterized Remote Trigger Plugin v.3.0.6

Remote Jenkins server:
Jenkins core. v.2.121.3


totoroliu1215@hotmail.com (JIRA)

unread,
Sep 25, 2018, 1:30:04 PM9/25/18
to jenkinsc...@googlegroups.com
Rick Liu edited a comment on Bug JENKINS-52810
Job Jenkins server:
Jenkins core. v.2.121.3
Parameterized Remote Trigger Plugin v.3.0.6

Remote Jenkins server:
Jenkins core. v.2.121.3


I still see this error from the job console:

[Pipeline] triggerRemoteJob
################################################################################################################
  Parameterized Remote Trigger Configuration:
    - job:                     https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test
    - auth:                    'Credentials Authentication' as user 'devops' (Credentials ID 'a14c5dae-94e0-4b12-991b-6f7d8620120e')
    - parameters:              [BUILD=5098, LABEL=ECO_130206, ENV=SMOKE_PRODUCTION]
    - blockBuildUntilComplete: false
    - connectionRetryLimit:    5
################################################################################################################
fail to accquire lock because of timeout, skip locking...
Triggering parameterized remote job 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test'
  Using job-level defined 'Credentials Authentication' as user 'devops' (Credentials ID ' a14c5dae-94e0-4b12-991b-6f7d8620120e xxxxxxxxxxxxx ')

Triggering remote job now.
fail to accquire lock because of timeout, skip locking...
CSRF protection is disabled on the remote server.
fail to accquire lock because of timeout, skip locking...
Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters:
Retry attempt #1 out of 5
Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters:
Retry attempt #2 out of 5
Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters:
Retry attempt #3 out of 5
Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters:
Retry attempt #4 out of 5
Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters:
Retry attempt #5 out of 5
ERROR: Remote build failed with 'ExceedRetryLimitException' for the following reason: 'Max number of connection retries have been exeeded.'.





Pipeline code:
triggerRemoteJob auth: CredentialsAuth(credentials: 'xxxxxxxxxxxxx'),
        blockBuildUntilComplete: false,
        job: 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test',
        parameters: """BUILD=${build}\nLABEL=ECO_${ECO_ID}\nENV=SMOKE_PRODUCTION""", pollInterval: 300


totoroliu1215@hotmail.com (JIRA)

unread,
Sep 25, 2018, 1:31:02 PM9/25/18
to jenkinsc...@googlegroups.com
Rick Liu edited a comment on Bug JENKINS-52810
Job Jenkins server:
Jenkins core. v.2.121.3
Parameterized Remote Trigger Plugin v.3.0.6

Remote Jenkins server:
Jenkins core. v.2.121.3


I still see this error from the job console:

[Pipeline] triggerRemoteJob
################################################################################################################
  Parameterized Remote Trigger Configuration:
    - job:                     https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test
    - auth:                    'Credentials Authentication' as user ' devops xxxxxx ' (Credentials ID ' a14c5dae-94e0-4b12-991b-6f7d8620120e xxxxxxxxxxxxx ')

    - parameters:              [BUILD=5098, LABEL=ECO_130206, ENV=SMOKE_PRODUCTION]
    - blockBuildUntilComplete: false
    - connectionRetryLimit:    5
################################################################################################################
fail to accquire lock because of timeout, skip locking...
Triggering parameterized remote job 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test'
  Using job-level defined 'Credentials Authentication' as user ' devops xxxxxx ' (Credentials ID 'xxxxxxxxxxxxx')

Triggering remote job now.
fail to accquire lock because of timeout, skip locking...
CSRF protection is disabled on the remote server.
fail to accquire lock because of timeout, skip locking...
Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters:
Retry attempt #1 out of 5
Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters:
Retry attempt #2 out of 5
Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters:
Retry attempt #3 out of 5
Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters:
Retry attempt #4 out of 5
Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters:
Retry attempt #5 out of 5
ERROR: Remote build failed with 'ExceedRetryLimitException' for the following reason: 'Max number of connection retries have been exeeded.'.





Pipeline code:
triggerRemoteJob auth: CredentialsAuth(credentials: 'xxxxxxxxxxxxx'),
        blockBuildUntilComplete: false,
        job: 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test',
        parameters: """BUILD=${build}\nLABEL=ECO_${ECO_ID}\nENV=SMOKE_PRODUCTION""", pollInterval: 300


philip.johnson@aveva.com (JIRA)

unread,
Dec 3, 2018, 12:05:02 PM12/3/18
to jenkinsc...@googlegroups.com

Rick Liu - I've run into this issue recently and it seems to occur when I up the polling time from 30 seconds to 300. If I use 30, it works again.
Reply all
Reply to author
Forward
0 new messages