[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Trey Bohon commented on 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. Add Comment
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Trey Bohon updated an issue Jenkins / JENKINS-52810 Parameterized Remote Trigger Plugin is not triggering job in remote jenkins Change By: Trey Bohon Attachment: image-2018-08-02-09-06-29-421.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-28958) Parameters from file not passed to downstream job
Title: Message Title Trey Bohon commented on JENKINS-28958 Re: Parameters from file not passed to downstream job Thanks for the workaround, this impacted us too. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mail-watcher-plugin] (JENKINS-30012) Mail on "Still Offline N hours" for nodes to LDAP resolved address
Title: Message Title Trey Bohon created an issue Jenkins / JENKINS-30012 Mail on "Still Offline N hours" for nodes to LDAP resolved address Issue Type: New Feature Assignee: Oliver Gondža Components: mail-watcher-plugin Created: 18/Aug/15 4:30 PM Priority: Major Reporter: Trey Bohon At our organization we have a large label of desktop build machines for build CI. When builds fail, we automatically send emails to perforce editors since the last successful build and to designated maintainers. Developers have the option to "checkout" a PC via Jenkins default UI to take nodes offline, and with LDAP user lookup we can identify user names. This works great because it saves build failure reproduction time, but it's not scaling well to human error - many people forget to put the node back online. The ideal solution that I'm thinking of is to automatically email the developer that checked out the PC every N hours. So basically this plugin but notify on still checkout status every N hours and using LDAP to lookup the email address. Add Comment
[JIRA] [build-blocker-plugin] (JENKINS-28513) Build-Blocker-Plugin blocks on builds queued leading to deadlock
Title: Message Title Trey Bohon commented on JENKINS-28513 Re: Build-Blocker-Plugin blocks on builds queued leading to deadlock Anyone try 1.618? There are a few queue deadlock related fixes in that build, wondering if this is a duplicate issue with one of those. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-blocker-plugin] (JENKINS-28513) Build-Blocker-Plugin blocks on builds queued leading to deadlock
Title: Message Title Trey Bohon edited a comment on JENKINS-28513 Re: Build-Blocker-Plugin blocks on builds queued leading to deadlock This was pretty brutal for us. v1.609.1 is completely broken without a working queue system for build blocker - we use it extensively along with job weight to control safe parallelism on single nodes. After mutating all of our build history to v1.609.1, going back to v1.596.3 removed all build history visibility. v1.608 fixes the queue system and most of build history, but we have some weird items...seems like any builds on v1.609.1 are identified as happening in year 1969, and tons of jobs claim never to have run or failed even though they have hundreds of times.I don't feel like v1.609.1 was delivered with the spirit of LTS. After remoting in a few hours over the weekend to update our Jenkins master (took 3 hours to mutate build history) I got in office to this bug. Why were such large changes rushed into an LTS release? Edit: If Kevin is correct and it is a pre-existing bug that happens to be exposed by core changes, then I could see how this streak of bad luck happened. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-blocker-plugin] (JENKINS-28513) Build-Blocker-Plugin blocks on builds queued leading to deadlock
Title: Message Title Trey Bohon commented on JENKINS-28513 Re: Build-Blocker-Plugin blocks on builds queued leading to deadlock This was pretty brutal for us. v1.609.1 is completely broken without a working queue system for build blocker - we use it extensively along with job weight to control safe parallelism on single nodes. After mutating all of our build history to v1.609.1, going back to v1.596.3 removed all build history visibility. v1.608 fixes the queue system and most of build history, but we have some weird items...seems like any builds on v1.609.1 are identified as happening in year 1969, and tons of jobs claim never to have run or failed even though they have hundreds of times. I don't feel like v1.609.1 was delivered with the spirit of LTS. After remoting in a few hours over the weekend to update our Jenkins master (took 3 hours to mutate build history) I got in office to this bug. Why were such large changes rushed into an LTS release? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
