Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-45788

WARNING: Actions from org.jenkinsci.plugins.workflow.job.properties.PipelineTriggersJobProperty$Factory@1234 for org.jenkinsci.plugins.workflow.job.WorkflowJob@123[job-name] included null not assignable to interface hudson.model.Action

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • workflow-job-plugin
    • None
    • Jenkins ver. 2.60.2

      Jenkins log displays this error every few seconds and so far I was unable to get any meaning out of it.

      WARNING: Actions from org.jenkinsci.plugins.workflow.job.properties.PipelineTriggersJobProperty$Factory@1b6f4974 for org.jenkinsci.plugins.workflow.job.WorkflowJob@26a5b3af[DFG-storage-sahara-10-unit-rhos] included null not assignable to interface hudson.model.Action
      Jul 25, 2017 6:31:29 PM hudson.model.Actionable createFor

      It seems that I had to raise a bug in order to find out what could cause it.

          [JENKINS-45788] WARNING: Actions from org.jenkinsci.plugins.workflow.job.properties.PipelineTriggersJobProperty$Factory@1234 for org.jenkinsci.plugins.workflow.job.WorkflowJob@123[job-name] included null not assignable to interface hudson.model.Action

          Andrew Bayer added a comment -

          Any chance you could give the triggers config you're using? I think I see the problem, but without a reproduction case, I can't write a test.

          Andrew Bayer added a comment - Any chance you could give the triggers config you're using? I think I see the problem, but without a reproduction case, I can't write a test.

          Queria Sa-Tas added a comment -

          Hi abayer, I've attached example/simplified config.xml of job mentioned by Sorin hope it shows the part You requested (gerrit trigger there are no other triggers for that job, aside when run manually or such), as it's still happening (jenkins 2.60.3 now).

          Queria Sa-Tas added a comment - Hi abayer , I've attached example/simplified config.xml of job mentioned by Sorin hope it shows the part You requested (gerrit trigger there are no other triggers for that job, aside when run manually or such), as it's still happening (jenkins 2.60.3 now).

          Sorin Sbarnea added a comment - - edited

          After some extra digging I found that the error disappears if you open job config and save it without making any change to it, meaning the Jenkins is fixing the XML file.

          Doing a diff of before and after this, I came up with few changes being added by Jenkins:

          1. <dynamicGerritProjects class="empty-list"/> is added, missing before.
          2. <triggerInformationAction/> is added, missing before, this being probably the cause of the error message.
          3. few others which I am going to ignore for the moment.

          Sorin Sbarnea added a comment - - edited After some extra digging I found that the error disappears if you open job config and save it without making any change to it, meaning the Jenkins is fixing the XML file. Doing a diff of before and after this, I came up with few changes being added by Jenkins: <dynamicGerritProjects class="empty-list"/> is added, missing before. <triggerInformationAction/> is added, missing before, this being probably the cause of the error message. few others which I am going to ignore for the moment.

          Sorin Sbarnea added a comment -

          I have final confirmation that what causes this bug is the missing `<triggerInformationAction/>` section from config.xml file. This is clearly a gerrit-trigger plugin bug but I also made CR for improving JJB in order to mention this parameter when generating config.xml file.

          See https://review.openstack.org/#/c/540851/ – I already tested it and found it as working. Still, this bug should not be closed as missing section should have same effect as one that is empty.

          Sorin Sbarnea added a comment - I have final confirmation that what causes this bug is the missing `<triggerInformationAction/>` section from config.xml file. This is clearly a gerrit-trigger plugin bug but I also made CR for improving JJB in order to mention this parameter when generating config.xml file. See https://review.openstack.org/#/c/540851/ – I already tested it and found it as working. Still, this bug should not be closed as missing section should have same effect as one that is empty.

          Sorin Sbarnea added a comment -

          abayer, can you give some insights regarding the purpose of triggerInformationAction? Where is this supposed to be used. Reviewers questioned the purpose of this parameter and I need to know how to respond to it (see last comment on the review above).

          So I either need to document it or to change the code to remove it and always create it as empty. 

          Sorin Sbarnea added a comment - abayer , can you give some insights regarding the purpose of triggerInformationAction? Where is this supposed to be used. Reviewers questioned the purpose of this parameter and I need to know how to respond to it (see last comment on the review above). So I either need to document it or to change the code to remove it and always create it as empty. 

            Unassigned Unassigned
            ssbarnea Sorin Sbarnea
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: