[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org
cjo9900 created JENKINS-12418:
---------------------------------

             Summary: flexible publish - Parametrized trigger does not work
                 Key: JENKINS-12418
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12418
             Project: Jenkins
          Issue Type: Bug
          Components: flexible-publish, parameterized-trigger
         Environment: Jenkins 1.446 on RHEL 6
Plugin:run-condition, 0.7,
Plugin:flexible-publish, 0.7
Plugin:token-macro, 1.5.1,
Plugin:conditional-buildstep,
Plugin:any-buildstep, 0.1,
Plugin:parameterized-trigger, 2.12
            Reporter: cjo9900
            Assignee: bap
            Priority: Critical


Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.

Log shows that it should have been called.

Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
Strings match run condition: string 1=[], string 2=[]
Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
[ArtifactDeployer] - Starting deployment from the post-action ...
[ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/nokia/fa_nmp/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
[ArtifactDeployer] - Stopping deployment from the post-action...

Next job is not called and they do not show up as Downstream Projects on the project page


possible solutions:

1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.

2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.







--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157807#comment-157807 ]

bap commented on JENKINS-12418:
-------------------------------

Hi,
Can you re check the logic (change the result of the Run condition that is inside the not) and try again?

The line "Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]"
is actually stating that the Run condition called "Not" is preventing the step called "Trigger param..." from being run.

So from that output, I would *not* have expected the parameterized trigger step to have executed.
               

> flexible publish - Parametrized trigger does not work
> -----------------------------------------------------
>
>                 Key: JENKINS-12418
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12418
>             Project: Jenkins
>          Issue Type: Bug
>          Components: flexible-publish, parameterized-trigger
>         Environment: Jenkins 1.446 on RHEL 6
> Plugin:run-condition, 0.7,
> Plugin:flexible-publish, 0.7
> Plugin:token-macro, 1.5.1,
> Plugin:conditional-buildstep,
> Plugin:any-buildstep, 0.1,
> Plugin:parameterized-trigger, 2.12
>            Reporter: cjo9900
>            Assignee: bap
>            Priority: Critical
>
> Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.
> Log shows that it should have been called.
> Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
> Strings match run condition: string 1=[], string 2=[]
> Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
> [ArtifactDeployer] - Starting deployment from the post-action ...
> [ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/nokia/fa_nmp/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
> [ArtifactDeployer] - Stopping deployment from the post-action...
> Next job is not called and they do not show up as Downstream Projects on the project page
> possible solutions:
> 1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.
> 2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157809#comment-157809 ]

cjo9900 commented on JENKINS-12418:
-----------------------------------


I tested the always and not string == string cases

Always case:

Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]


not string == string case:

Strings match run condition: string 1=[], string 2=[]
Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]

both gave the same results,

The reason is that the trigger parameterized build performs no action in the Perform code.
This is because it creates Dependancy's that it attaches to the DependancyGraph in
buildDependencyGraph() which is part of the DependecyDeclarer interface

        @Override
        public void buildDependencyGraph(AbstractProject owner, DependencyGraph graph) {
                // Can only add dependencies in Hudson 1.341 or higher
                if (!canDeclare(owner)) return;

                for (BuildTriggerConfig config : configs)
                        for (AbstractProject project : config.getProjectList(null))
                                ParameterizedDependency.add(owner, project, config, graph);
        }



               

> flexible publish - Parametrized trigger does not work
> -----------------------------------------------------
>
>                 Key: JENKINS-12418
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12418
>             Project: Jenkins
>          Issue Type: Bug
>          Components: flexible-publish, parameterized-trigger
>         Environment: Jenkins 1.446 on RHEL 6
> Plugin:run-condition, 0.7,
> Plugin:flexible-publish, 0.7
> Plugin:token-macro, 1.5.1,
> Plugin:conditional-buildstep,
> Plugin:any-buildstep, 0.1,
> Plugin:parameterized-trigger, 2.12
>            Reporter: cjo9900
>            Assignee: bap
>            Priority: Critical
>
> Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.
> Log shows that it should have been called.
> Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
> Strings match run condition: string 1=[], string 2=[]
> Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
> [ArtifactDeployer] - Starting deployment from the post-action ...
> [ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/nokia/fa_nmp/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
> [ArtifactDeployer] - Stopping deployment from the post-action...
> Next job is not called and they do not show up as Downstream Projects on the project page
> possible solutions:
> 1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.
> 2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157809#comment-157809 ]

cjo9900 edited comment on JENKINS-12418 at 1/16/12 2:04 PM:
------------------------------------------------------------

I tested the always and not string == string cases

Always case:

Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]


not string == string case:

Strings match run condition: string 1=[], string 2=[]
Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]

both gave the same results,

The reason is that the trigger parameterized build performs no action in the Perform code.
This is because it creates Dependancy's that it attaches to the DependancyGraph in
buildDependencyGraph() which is part of the DependecyDeclarer interface
{noformat}
        @Override
        public void buildDependencyGraph(AbstractProject owner, DependencyGraph graph) {
                // Can only add dependencies in Hudson 1.341 or higher
                if (!canDeclare(owner)) return;

                for (BuildTriggerConfig config : configs)
                        for (AbstractProject project : config.getProjectList(null))
                                ParameterizedDependency.add(owner, project, config, graph);
        }
{noformat}


               
      was (Author: cjo9900):
   
I tested the always and not string == string cases

Always case:

Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]


not string == string case:

Strings match run condition: string 1=[], string 2=[]
Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]

both gave the same results,

The reason is that the trigger parameterized build performs no action in the Perform code.
This is because it creates Dependancy's that it attaches to the DependancyGraph in
buildDependencyGraph() which is part of the DependecyDeclarer interface

        @Override
        public void buildDependencyGraph(AbstractProject owner, DependencyGraph graph) {
                // Can only add dependencies in Hudson 1.341 or higher
                if (!canDeclare(owner)) return;

                for (BuildTriggerConfig config : configs)
                        for (AbstractProject project : config.getProjectList(null))
                                ParameterizedDependency.add(owner, project, config, graph);
        }



                 

> flexible publish - Parametrized trigger does not work
> -----------------------------------------------------
>
>                 Key: JENKINS-12418
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12418
>             Project: Jenkins
>          Issue Type: Bug
>          Components: flexible-publish, parameterized-trigger
>         Environment: Jenkins 1.446 on RHEL 6
> Plugin:run-condition, 0.7,
> Plugin:flexible-publish, 0.7
> Plugin:token-macro, 1.5.1,
> Plugin:conditional-buildstep,
> Plugin:any-buildstep, 0.1,
> Plugin:parameterized-trigger, 2.12
>            Reporter: cjo9900
>            Assignee: bap
>            Priority: Critical
>
> Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.
> Log shows that it should have been called.
> Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
> Strings match run condition: string 1=[], string 2=[]
> Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
> [ArtifactDeployer] - Starting deployment from the post-action ...
> [ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/nokia/fa_nmp/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
> [ArtifactDeployer] - Stopping deployment from the post-action...
> Next job is not called and they do not show up as Downstream Projects on the project page
> possible solutions:
> 1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.
> 2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157809#comment-157809 ]

cjo9900 edited comment on JENKINS-12418 at 1/16/12 2:05 PM:
------------------------------------------------------------

I tested the always and not string == string cases

Always case:

Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]


not string == string case:

Strings match run condition: string 1=[], string 2=[]
Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]

both gave the same results,

The reason is that the trigger parameterized build performs no action in the Perform code.
This is because it creates Dependancy's that it attaches to the DependancyGraph in
buildDependencyGraph() which is part of the DependecyDeclarer interface
{code}
        @Override
        public void buildDependencyGraph(AbstractProject owner, DependencyGraph graph) {
                // Can only add dependencies in Hudson 1.341 or higher
                if (!canDeclare(owner)) return;

                for (BuildTriggerConfig config : configs)
                        for (AbstractProject project : config.getProjectList(null))
                                ParameterizedDependency.add(owner, project, config, graph);
        }
{code}


               
      was (Author: cjo9900):
    I tested the always and not string == string cases

Always case:

Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]


not string == string case:

Strings match run condition: string 1=[], string 2=[]
Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]

both gave the same results,

The reason is that the trigger parameterized build performs no action in the Perform code.
This is because it creates Dependancy's that it attaches to the DependancyGraph in
buildDependencyGraph() which is part of the DependecyDeclarer interface
{noformat}
        @Override
        public void buildDependencyGraph(AbstractProject owner, DependencyGraph graph) {
                // Can only add dependencies in Hudson 1.341 or higher
                if (!canDeclare(owner)) return;

                for (BuildTriggerConfig config : configs)
                        for (AbstractProject project : config.getProjectList(null))
                                ParameterizedDependency.add(owner, project, config, graph);
        }
{noformat}


                 

> flexible publish - Parametrized trigger does not work
> -----------------------------------------------------
>
>                 Key: JENKINS-12418
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12418
>             Project: Jenkins
>          Issue Type: Bug
>          Components: flexible-publish, parameterized-trigger
>         Environment: Jenkins 1.446 on RHEL 6
> Plugin:run-condition, 0.7,
> Plugin:flexible-publish, 0.7
> Plugin:token-macro, 1.5.1,
> Plugin:conditional-buildstep,
> Plugin:any-buildstep, 0.1,
> Plugin:parameterized-trigger, 2.12
>            Reporter: cjo9900
>            Assignee: bap
>            Priority: Critical
>
> Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.
> Log shows that it should have been called.
> Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
> Strings match run condition: string 1=[], string 2=[]
> Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
> [ArtifactDeployer] - Starting deployment from the post-action ...
> [ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/nokia/fa_nmp/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
> [ArtifactDeployer] - Stopping deployment from the post-action...
> Next job is not called and they do not show up as Downstream Projects on the project page
> possible solutions:
> 1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.
> 2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157812#comment-157812 ]

bap commented on JENKINS-12418:
-------------------------------

Sorry, I just saw the the 2nd entry - my bad.

I'll try to have a look at this this evening and see if there is anything that can be done from the Flexible publish side (other than just adding the parameterized trigger to the list of excluded steps)

               

> flexible publish - Parametrized trigger does not work
> -----------------------------------------------------
>
>                 Key: JENKINS-12418
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12418
>             Project: Jenkins
>          Issue Type: Bug
>          Components: flexible-publish, parameterized-trigger
>         Environment: Jenkins 1.446 on RHEL 6
> Plugin:run-condition, 0.7,
> Plugin:flexible-publish, 0.7
> Plugin:token-macro, 1.5.1,
> Plugin:conditional-buildstep,
> Plugin:any-buildstep, 0.1,
> Plugin:parameterized-trigger, 2.12
>            Reporter: cjo9900
>            Assignee: bap
>            Priority: Critical
>
> Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.
> Log shows that it should have been called.
> Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
> Strings match run condition: string 1=[], string 2=[]
> Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
> [ArtifactDeployer] - Starting deployment from the post-action ...
> [ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/nokia/fa_nmp/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
> [ArtifactDeployer] - Stopping deployment from the post-action...
> Next job is not called and they do not show up as Downstream Projects on the project page
> possible solutions:
> 1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.
> 2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

SCM/JIRA link daemon resolved JENKINS-12418.
--------------------------------------------

    Resolution: Fixed
   

> flexible publish - Parametrized trigger does not work
> -----------------------------------------------------
>
>                 Key: JENKINS-12418
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12418
>             Project: Jenkins
>          Issue Type: Bug
>          Components: flexible-publish, parameterized-trigger
>         Environment: Jenkins 1.446 on RHEL 6
> Plugin:run-condition, 0.7,
> Plugin:flexible-publish, 0.7
> Plugin:token-macro, 1.5.1,
> Plugin:conditional-buildstep,
> Plugin:any-buildstep, 0.1,
> Plugin:parameterized-trigger, 2.12
>            Reporter: cjo9900
>            Assignee: bap
>            Priority: Critical
>
> Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.
> Log shows that it should have been called.
> Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
> Strings match run condition: string 1=[], string 2=[]
> Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
> [ArtifactDeployer] - Starting deployment from the post-action ...
> [ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/nokia/fa_nmp/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
> [ArtifactDeployer] - Stopping deployment from the post-action...
> Next job is not called and they do not show up as Downstream Projects on the project page
> possible solutions:
> 1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.
> 2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157865#comment-157865 ]

SCM/JIRA link daemon commented on JENKINS-12418:
------------------------------------------------

Code changed in jenkins
User: bap2000
Path:
 src/main/java/org/jenkins_ci/plugins/flexible_publish/ConditionalPublisher.java
 src/main/java/org/jenkins_ci/plugins/flexible_publish/FlexiblePublisher.java
http://jenkins-ci.org/commit/flexible-publish-plugin/ca9d155ed5930eecacea781b63d99afcaf18da26
Log:
  Allow contained steps to participate in building the dependency graph

[FIXED JENKINS-12418]





               

> flexible publish - Parametrized trigger does not work
> -----------------------------------------------------
>
>                 Key: JENKINS-12418
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12418
>             Project: Jenkins
>          Issue Type: Bug
>          Components: flexible-publish, parameterized-trigger
>         Environment: Jenkins 1.446 on RHEL 6
> Plugin:run-condition, 0.7,
> Plugin:flexible-publish, 0.7
> Plugin:token-macro, 1.5.1,
> Plugin:conditional-buildstep,
> Plugin:any-buildstep, 0.1,
> Plugin:parameterized-trigger, 2.12
>            Reporter: cjo9900
>            Assignee: bap
>            Priority: Critical
>
> Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.
> Log shows that it should have been called.
> Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
> Strings match run condition: string 1=[], string 2=[]
> Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
> [ArtifactDeployer] - Starting deployment from the post-action ...
> [ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/nokia/fa_nmp/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
> [ArtifactDeployer] - Stopping deployment from the post-action...
> Next job is not called and they do not show up as Downstream Projects on the project page
> possible solutions:
> 1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.
> 2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157866#comment-157866 ]

bap commented on JENKINS-12418:
-------------------------------

Can you build HEAD of master and try out the changes?
               

> flexible publish - Parametrized trigger does not work
> -----------------------------------------------------
>
>                 Key: JENKINS-12418
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12418
>             Project: Jenkins
>          Issue Type: Bug
>          Components: flexible-publish, parameterized-trigger
>         Environment: Jenkins 1.446 on RHEL 6
> Plugin:run-condition, 0.7,
> Plugin:flexible-publish, 0.7
> Plugin:token-macro, 1.5.1,
> Plugin:conditional-buildstep,
> Plugin:any-buildstep, 0.1,
> Plugin:parameterized-trigger, 2.12
>            Reporter: cjo9900
>            Assignee: bap
>            Priority: Critical
>
> Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.
> Log shows that it should have been called.
> Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
> Strings match run condition: string 1=[], string 2=[]
> Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
> [ArtifactDeployer] - Starting deployment from the post-action ...
> [ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/nokia/fa_nmp/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
> [ArtifactDeployer] - Stopping deployment from the post-action...
> Next job is not called and they do not show up as Downstream Projects on the project page
> possible solutions:
> 1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.
> 2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157868#comment-157868 ]

bap commented on JENKINS-12418:
-------------------------------

Don't bother!
Unfortunately, when using the change above, the conditions are ignored and the downstream builds will always be triggered.

I will add the parameterized trigger to the list of excluded publishers.
               

> flexible publish - Parametrized trigger does not work
> -----------------------------------------------------
>
>                 Key: JENKINS-12418
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12418
>             Project: Jenkins
>          Issue Type: Bug
>          Components: flexible-publish, parameterized-trigger
>         Environment: Jenkins 1.446 on RHEL 6
> Plugin:run-condition, 0.7,
> Plugin:flexible-publish, 0.7
> Plugin:token-macro, 1.5.1,
> Plugin:conditional-buildstep,
> Plugin:any-buildstep, 0.1,
> Plugin:parameterized-trigger, 2.12
>            Reporter: cjo9900
>            Assignee: bap
>            Priority: Critical
>
> Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.
> Log shows that it should have been called.
> Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
> Strings match run condition: string 1=[], string 2=[]
> Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
> [ArtifactDeployer] - Starting deployment from the post-action ...
> [ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/nokia/fa_nmp/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
> [ArtifactDeployer] - Stopping deployment from the post-action...
> Next job is not called and they do not show up as Downstream Projects on the project page
> possible solutions:
> 1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.
> 2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

cjo9900 updated JENKINS-12418:
------------------------------

    Description:
Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.

Log shows that it should have been called.

Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
Strings match run condition: string 1=[], string 2=[]
Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
[ArtifactDeployer] - Starting deployment from the post-action ...
[ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/company/site/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
[ArtifactDeployer] - Stopping deployment from the post-action...

Next job is not called and they do not show up as Downstream Projects on the project page


possible solutions:

1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.

2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.







  was:
Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.

Log shows that it should have been called.

Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
Strings match run condition: string 1=[], string 2=[]
Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
[ArtifactDeployer] - Starting deployment from the post-action ...
[ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/nokia/fa_nmp/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
[ArtifactDeployer] - Stopping deployment from the post-action...

Next job is not called and they do not show up as Downstream Projects on the project page


possible solutions:

1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.

2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.







   

> flexible publish - Parametrized trigger does not work
> -----------------------------------------------------
>
>                 Key: JENKINS-12418
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12418
>             Project: Jenkins
>          Issue Type: Bug
>          Components: flexible-publish, parameterized-trigger
>         Environment: Jenkins 1.446 on RHEL 6
> Plugin:run-condition, 0.7,
> Plugin:flexible-publish, 0.7
> Plugin:token-macro, 1.5.1,
> Plugin:conditional-buildstep,
> Plugin:any-buildstep, 0.1,
> Plugin:parameterized-trigger, 2.12
>            Reporter: cjo9900
>            Assignee: bap
>            Priority: Critical
>
> Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.
> Log shows that it should have been called.
> Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
> Strings match run condition: string 1=[], string 2=[]
> Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
> [ArtifactDeployer] - Starting deployment from the post-action ...
> [ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/company/site/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
> [ArtifactDeployer] - Stopping deployment from the post-action...
> Next job is not called and they do not show up as Downstream Projects on the project page
> possible solutions:
> 1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.
> 2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157869#comment-157869 ]

cjo9900 commented on JENKINS-12418:
-----------------------------------

Ok, I expected this,
I will work on the parameterized trigger to add run condition support replacing existing job result only.
               

> flexible publish - Parametrized trigger does not work
> -----------------------------------------------------
>
>                 Key: JENKINS-12418
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12418
>             Project: Jenkins
>          Issue Type: Bug
>          Components: flexible-publish, parameterized-trigger
>         Environment: Jenkins 1.446 on RHEL 6
> Plugin:run-condition, 0.7,
> Plugin:flexible-publish, 0.7
> Plugin:token-macro, 1.5.1,
> Plugin:conditional-buildstep,
> Plugin:any-buildstep, 0.1,
> Plugin:parameterized-trigger, 2.12
>            Reporter: cjo9900
>            Assignee: bap
>            Priority: Critical
>
> Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.
> Log shows that it should have been called.
> Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
> Strings match run condition: string 1=[], string 2=[]
> Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
> [ArtifactDeployer] - Starting deployment from the post-action ...
> [ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/company/site/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
> [ArtifactDeployer] - Stopping deployment from the post-action...
> Next job is not called and they do not show up as Downstream Projects on the project page
> possible solutions:
> 1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.
> 2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

bap updated JENKINS-12418:
--------------------------

    Status: Open  (was: Reopened)
   

> flexible publish - Parametrized trigger does not work
> -----------------------------------------------------
>
>                 Key: JENKINS-12418
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12418
>             Project: Jenkins
>          Issue Type: Bug
>          Components: flexible-publish, parameterized-trigger
>         Environment: Jenkins 1.446 on RHEL 6
> Plugin:run-condition, 0.7,
> Plugin:flexible-publish, 0.7
> Plugin:token-macro, 1.5.1,
> Plugin:conditional-buildstep,
> Plugin:any-buildstep, 0.1,
> Plugin:parameterized-trigger, 2.12
>            Reporter: cjo9900
>            Assignee: bap
>            Priority: Critical
>
> Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.
> Log shows that it should have been called.
> Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
> Strings match run condition: string 1=[], string 2=[]
> Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
> [ArtifactDeployer] - Starting deployment from the post-action ...
> [ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/company/site/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
> [ArtifactDeployer] - Stopping deployment from the post-action...
> Next job is not called and they do not show up as Downstream Projects on the project page
> possible solutions:
> 1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.
> 2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

bap reopened JENKINS-12418:
---------------------------

   

> flexible publish - Parametrized trigger does not work
> -----------------------------------------------------
>
>                 Key: JENKINS-12418
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12418
>             Project: Jenkins
>          Issue Type: Bug
>          Components: flexible-publish, parameterized-trigger
>         Environment: Jenkins 1.446 on RHEL 6
> Plugin:run-condition, 0.7,
> Plugin:flexible-publish, 0.7
> Plugin:token-macro, 1.5.1,
> Plugin:conditional-buildstep,
> Plugin:any-buildstep, 0.1,
> Plugin:parameterized-trigger, 2.12
>            Reporter: cjo9900
>            Assignee: bap
>            Priority: Critical
>
> Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.
> Log shows that it should have been called.
> Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
> Strings match run condition: string 1=[], string 2=[]
> Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
> [ArtifactDeployer] - Starting deployment from the post-action ...
> [ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/company/site/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
> [ArtifactDeployer] - Stopping deployment from the post-action...
> Next job is not called and they do not show up as Downstream Projects on the project page
> possible solutions:
> 1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.
> 2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

bap resolved JENKINS-12418.
---------------------------

    Resolution: Fixed
   

> flexible publish - Parametrized trigger does not work
> -----------------------------------------------------
>
>                 Key: JENKINS-12418
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12418
>             Project: Jenkins
>          Issue Type: Bug
>          Components: flexible-publish, parameterized-trigger
>         Environment: Jenkins 1.446 on RHEL 6
> Plugin:run-condition, 0.7,
> Plugin:flexible-publish, 0.7
> Plugin:token-macro, 1.5.1,
> Plugin:conditional-buildstep,
> Plugin:any-buildstep, 0.1,
> Plugin:parameterized-trigger, 2.12
>            Reporter: cjo9900
>            Assignee: bap
>            Priority: Critical
>
> Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.
> Log shows that it should have been called.
> Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
> Strings match run condition: string 1=[], string 2=[]
> Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
> [ArtifactDeployer] - Starting deployment from the post-action ...
> [ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/company/site/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
> [ArtifactDeployer] - Stopping deployment from the post-action...
> Next job is not called and they do not show up as Downstream Projects on the project page
> possible solutions:
> 1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.
> 2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

bap closed JENKINS-12418.
-------------------------

   

> flexible publish - Parametrized trigger does not work
> -----------------------------------------------------
>
>                 Key: JENKINS-12418
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12418
>             Project: Jenkins
>          Issue Type: Bug
>          Components: flexible-publish, parameterized-trigger
>         Environment: Jenkins 1.446 on RHEL 6
> Plugin:run-condition, 0.7,
> Plugin:flexible-publish, 0.7
> Plugin:token-macro, 1.5.1,
> Plugin:conditional-buildstep,
> Plugin:any-buildstep, 0.1,
> Plugin:parameterized-trigger, 2.12
>            Reporter: cjo9900
>            Assignee: bap
>            Priority: Critical
>
> Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.
> Log shows that it should have been called.
> Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
> Strings match run condition: string 1=[], string 2=[]
> Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
> [ArtifactDeployer] - Starting deployment from the post-action ...
> [ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/company/site/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
> [ArtifactDeployer] - Stopping deployment from the post-action...
> Next job is not called and they do not show up as Downstream Projects on the project page
> possible solutions:
> 1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.
> 2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
T. Houdayer commented on Bug JENKINS-12418

cjo9900, do you fix this issue ? If yes, when do you plan to re-add the parameterized trigger into the Flexible plugin list of available publishers ?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
cjo9900 commented on Bug JENKINS-12418

The fix was to add the functionality to the parameterized trigger, as there is no way that the flexible publish can affect the Dependancies that are created.

See Pull request for it.
https://github.com/jenkinsci/parameterized-trigger-plugin/pull/17

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
emszpak commented on Bug JENKINS-12418

@cjo9900, from the comments I thought that fixing issue is waiting for merge of pull request 17 in parameterized-trigger-plugin, but when I asked there the reply was that it rather seems to be already fixed here. How does it really look like?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira