[JIRA] (JENKINS-50674) Switch from Perforce plugin (discontinued) to P4 plugin
Title: Message Title Daniel Beck commented on JENKINS-50674 Re: Switch from Perforce plugin (discontinued) to P4 plugin perforce is an optional dependency of jira plugin, so I would expect that it (perforce) can be removed without negative impact (but it's not possible through the UI due to a bug in the plugin manager). Looking over the code it's possible the optional dependency is not properly implemented (i.e. to fail loading if the plugin isn't available), but I haven't tested it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50460) Builds marked as failed - Dr Memory plugin (JEP-200)
Title: Message Title
Piotr Bogdanski updated an issue
Jenkins / JENKINS-50460
Builds marked as failed - Dr Memory plugin (JEP-200)
Change By:
Piotr Bogdanski
After recent update of Jenkins builds which uses Dr Memory plugin are marked as failed.Sequence of events: # Build run finishes successfully as before Jenkins update. Marked as SUCCESS, Dr Memory results produced and visible in Jenkins # Jenkins server restart # Build marked as FAILED, Dr Memory report no more visible error from jenkins.err log: {code:java} WARNING: net.praqma.drmemory.DrMemoryResult in file:/C:/Program%20Files%20(x86)/Jenkins/plugins/drmemory-plugin/WEB-INF/lib/drmemory-api-0.1.4.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/Apr 10, 2018 8:27:59 AM hudson.model.Run execute SEVERE: Failed to save build recordjava.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.model.FreeStyleBuildat hudson.XmlFile.write(XmlFile.java:200)at hudson.model.Run.save(Run.java:1923)at hudson.model.Run.execute(Run.java:1784)at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)at hudson.model.ResourceController.execute(ResourceController.java:97)at hudson.model.Executor.run(Executor.java:429)Caused by: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.model.FreeStyleBuildat hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256)at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224)at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138)at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209)at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150)at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43)at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82)at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37)at com.thoughtworks.xstream.XStream.marshal(XStream.java:1026)at com.thoughtworks.xstream.XStream.marshal(XStream.java:1015)at com.thoughtworks.xstream.XStream.toXML(XStream.java:988)at hudson.XmlFile.write(XmlFile.java:193)... 5 moreCaused by: java.lang.RuntimeException: Failed to serialize net.praqma.jenkins.plugin.drmemory.DrMemoryBuildAction#results for class net.praqma.jenkins.plugin.drmemory.DrMemoryBuildActionat hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256)at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224)at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflec
[JIRA] (JENKINS-50460) Builds marked as failed - Dr Memory plugin (JEP-200)
Title: Message Title Piotr Bogdanski commented on JENKINS-50460 Re: Builds marked as failed - Dr Memory plugin (JEP-200) Reto Minder in both cases(before and after jenkins restart) I can see build.xml file under location: "jobs/JOB_NAME/builds/BUILD_NUMBER." File does not seems to be affected by the restart itself. Note: also option to start jenkins with param as below gives the same failing build: jenkins.exe start -Dhudson.remoting.ClassFilter=net.praqma.drmemory.DrMemoryResult Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50460) Builds marked as failed - Dr Memory plugin (JEP-200)
Title: Message Title Piotr Bogdanski updated an issue Jenkins / JENKINS-50460 Builds marked as failed - Dr Memory plugin (JEP-200) Change By: Piotr Bogdanski Attachment: image-2018-04-10-08-39-10-762.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50460) Builds marked as failed - Dr Memory plugin (JEP-200)
Title: Message Title Piotr Bogdanski updated an issue Jenkins / JENKINS-50460 Builds marked as failed - Dr Memory plugin (JEP-200) Change By: Piotr Bogdanski Attachment: image-2018-04-10-08-39-26-762.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50460) Builds marked as failed - Dr Memory plugin (JEP-200)
Title: Message Title Piotr Bogdanski updated an issue Jenkins / JENKINS-50460 Builds marked as failed - Dr Memory plugin (JEP-200) Change By: Piotr Bogdanski Attachment: image-2018-04-10-08-39-10-706.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50478) Add support for data disks
Title: Message Title Chenyang Liu assigned an issue to Chenyang Liu Jenkins / JENKINS-50478 Add support for data disks Change By: Chenyang Liu Assignee: Dave Tucker Chenyang Liu Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50478) Add support for data disks
Title: Message Title Chenyang Liu commented on JENKINS-50478 Re: Add support for data disks It looks good to me. Please feel free to open a PR. For the risky part, let's keep in contact and do more test to make sure it works well. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50708) Post commit hook for CVS
Title: Message Title Priyanga G created an issue Jenkins / JENKINS-50708 Post commit hook for CVS Issue Type: Bug Assignee: Unassigned Components: cvs-plugin Created: 2018-04-10 05:52 Priority: Minor Reporter: Priyanga G For triggering Jenkins job,I want to use CVS commit.Is it possible.I tried but I am getting error Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50501) Jenkins won't load after updating maven plugin
Title: Message Title Tomas Norre Mikkelsen edited a comment on JENKINS-50501 Re: Jenkins won't load after updating maven plugin I can confirm this, but unfortunately a downgrade doesn't help me. We are also at jenkins 2.107.1 Maven Plugin: 3.1.2 (downgrading to 3.1) UPDATE:I read the description wrong.My Problem is that I cannot configure the maven Project (clicking configure) The overlay never disappears. The Jenkins it self is starting like it's supposed too. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50623) Build trigger using SVN is getting error in URL
Title: Message Title Priyanga G assigned an issue to Priyanga G Jenkins / JENKINS-50623 Build trigger using SVN is getting error in URL Change By: Priyanga G Assignee: Mathieu Cantin Priyanga G Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50674) Switch from Perforce plugin (discontinued) to P4 plugin
Title: Message Title Oleg Nenashev commented on JENKINS-50674 Re: Switch from Perforce plugin (discontinued) to P4 plugin Yes, there should be no functional impact for missing optional deps excepting logging. CC Daniel Beck just to confirm Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50460) Builds marked as failed - Dr Memory plugin (JEP-200)
Title: Message Title Reto Duss commented on JENKINS-50460 Re: Builds marked as failed - Dr Memory plugin (JEP-200) The build.xml in the jobs/JOB_NAME/builds/BUILD_NUMBER is not written. After a restart these jobs are no longer loaded. The newest containing a build.xml is the displayed in the browser. Going back from 1.4 to 1.3 did not help. Any dependency to an other plugin? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50654) cannot configure rebuildOpenMergeRequest using job-dsl
Title: Message Title Owen Mehegan commented on JENKINS-50654 Re: cannot configure rebuildOpenMergeRequest using job-dsl It's hard for us to support the combination of GitLab plugin and Job DSL. There are relatively few people using the plugin this way. I would suggest that you search our GitHub issues page (https://github.com/jenkinsci/gitlab-plugin/issues) and see if you find similar issues. If not, feel free to open a new one there, that is where we track all gitlab-plugin work. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50654) cannot configure rebuildOpenMergeRequest using job-dsl
Title: Message Title Owen Mehegan closed an issue as Done Jenkins / JENKINS-50654 cannot configure rebuildOpenMergeRequest using job-dsl Change By: Owen Mehegan Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-48345) Cloud statistics is still counting the hours even after terminated the Azure VM agents
Title: Message Title Azure DevOps resolved as Fixed Fixed in 0.7.0 Jenkins / JENKINS-48345 Cloud statistics is still counting the hours even after terminated the Azure VM agents Change By: Azure DevOps Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-47923) Plugin should not recreate storage accounts if "Use Existing" is selected
Title: Message Title Azure DevOps resolved as Fixed Fixed in 0.7.0 Jenkins / JENKINS-47923 Plugin should not recreate storage accounts if "Use Existing" is selected Change By: Azure DevOps Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-46421) Agents stuck in 'Provisioning' mode for several days
Title: Message Title Azure DevOps resolved as Fixed Fixed in 0.7.0 Jenkins / JENKINS-46421 Agents stuck in 'Provisioning' mode for several days Change By: Azure DevOps Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-42341) UNSTABLE status when filtering downloads from a matrix job completely filters a matrix configuration
Title: Message Title Azure DevOps resolved as Fixed Fixed in 0.3.9 Jenkins / JENKINS-42341 UNSTABLE status when filtering downloads from a matrix job completely filters a matrix configuration Change By: Azure DevOps Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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://group
[JIRA] (JENKINS-48076) Custom User Image, possibility to use azure image
Title: Message Title Azure DevOps resolved as Fixed Fixed in 0.7.0 Jenkins / JENKINS-48076 Custom User Image, possibility to use azure image Change By: Azure DevOps Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-46337) Template verification logs should include the verification failure reason
Title: Message Title Azure DevOps resolved as Fixed Fixed in 0.7.0 Jenkins / JENKINS-46337 Template verification logs should include the verification failure reason Change By: Azure DevOps Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-48901) Exception regularly thrown "/var/jenkins_home/deployment.out (No such file or directory)"
Title: Message Title Azure DevOps resolved as Fixed Fixed in 0.7.0 Jenkins / JENKINS-48901 Exception regularly thrown "/var/jenkins_home/deployment.out (No such file or directory)" Change By: Azure DevOps Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.co
[JIRA] (JENKINS-48253) Empty list of existing Storage Account Names
Title: Message Title Azure DevOps resolved as Fixed Fixed in 0.7.0 Jenkins / JENKINS-48253 Empty list of existing Storage Account Names Change By: Azure DevOps Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50589) Need to view Performance Plugin test results in BlueOcean UI
Title: Message Title Michael Neale commented on JENKINS-50589 Re: Need to view Performance Plugin test results in BlueOcean UI Ivan Meredith is there is some way plugins can publish links in the results screen, that could do nicely for this and a bunch of others. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50707) java.lang.StackOverflowError
Title: Message Title kang hao created an issue Jenkins / JENKINS-50707 java.lang.StackOverflowError Issue Type: Bug Assignee: Alex Earl Attachments: image-2018-04-10-11-20-10-154.png, wx20180410-111...@2x.png Components: publish-over-ftp-plugin Created: 2018-04-10 03:20 Environment: Jenkins V2.107.1 Publish-over-FTP v1.13 Priority: Minor Reporter: kang hao Something went wrong when I update Publish-over-FTP plugin from v1.12 to v1.13，I reviewed the source code and guessed that it was caused by the feature import in https://issues.jenkins-ci.org/browse/JENKINS-37259 Add Comment
[JIRA] (JENKINS-49150) Azure VM Agentes plugin does not prevent me using reserved domain names
Title: Message Title Azure DevOps resolved as Fixed Fixed in 0.7.0 Jenkins / JENKINS-49150 Azure VM Agentes plugin does not prevent me using reserved domain names Change By: Azure DevOps Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title Andrew Gray commented on JENKINS-28335 Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support) Is this going to be fixed anytime soon? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50706) Non Administrator cannot configure credentials in the Slack Notifier step.
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-50706 Non Administrator cannot configure credentials in the Slack Notifier step. Issue Type: Bug Assignee: Kurt Madel Attachments: slack-notifier-credentials.png Components: slack-plugin Created: 2018-04-10 02:42 Environment: slack:2.3 Priority: Major Reporter: Allan BURDAJEWICZ It is possible to specify credentials in the Slack Notifier post build step however only an administrator can configure it: In the screenshot above, as a non administrator I can actually create credentials from here but I cannot use them. Reference: https://github.com/jenkinsci/slack-plugin/blob/slack-2.3/src/main/java/jenkins/plugins/slack/SlackNotifier.java#L398 Add Comment
[JIRA] (JENKINS-50705) Can withCredentials() pull creds from an external keystore?
Title: Message Title Jon B created an issue Jenkins / JENKINS-50705 Can withCredentials() pull creds from an external keystore? Issue Type: New Feature Assignee: Stephen Connolly Components: credentials-plugin Created: 2018-04-10 02:38 Priority: Minor Reporter: Jon B We have a secret service which has a REST endpoint. If someone calls for the credential "FOO", the REST api might return a json document with "bar" in it which is the appropriate credential in this simple example. We really like what you have done with the withCredentials() context manager, but we'd like to know how to make this work with our existing keystore. Add Comment
[JIRA] (JENKINS-50704) Add support for folder credentials
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-50704 Add support for folder credentials Issue Type: New Feature Assignee: Kurt Madel Components: slack-plugin Created: 2018-04-10 02:36 Environment: slack:2.3 Priority: Major Reporter: Allan BURDAJEWICZ The Slack Notifier accepts Secret Text credentials. Only credentials defined at Jenkins root can be used. If credentials are created in a Folder, there are not visible to underlying items. It would be really useful if the Slack Notifier could accept folder credentials. Add Comment
[JIRA] (JENKINS-50589) Need to view Performance Plugin test results in BlueOcean UI
Title: Message Title Ivan Meredith commented on JENKINS-50589 Re: Need to view Performance Plugin test results in BlueOcean UI We could special case this for now. I'm working on a plan for extensibility currently but still not 100% sure how we will deal with things like this. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-45814) "Suppress automatic SCM triggering" prevents push notifications
Title: Message Title Sam Gleske edited a comment on JENKINS-45814 Re: "Suppress automatic SCM triggering" prevents push notifications I experience this with the GitHub branch source plugin within multibranch pipelines. I nearly created a new issue but then found this.So, what's the best course of action here? "Suppress automatic scm triggering" blocks GitHub pushing push triggers . Should I create a new plugin, add to an existing plugin (like the scm-filter-branch-pr plugin), or file a new bug report for this plugin? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-45814) "Suppress automatic SCM triggering" prevents push notifications
Title: Message Title Sam Gleske commented on JENKINS-45814 Re: "Suppress automatic SCM triggering" prevents push notifications I experience this with the GitHub branch source plugin within multibranch pipelines. I nearly created a new issue but then found this. So, what's the best course of action here? "Suppress automatic scm triggering" blocks GitHub pushing. Should I create a new plugin, add to an existing plugin (like the scm-filter-branch-pr plugin), or file a new bug report for this plugin? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50674) Switch from Perforce plugin (discontinued) to P4 plugin
Title: Message Title Michael Neale commented on JENKINS-50674 Re: Switch from Perforce plugin (discontinued) to P4 plugin Oleg Nenashev not quite - I think that has to be rolled back temporarily, so it will be part of it, however there is a plan to fix up the JIRA plugin. I am not sure of the connection with perforce? FYI if ther eis an issue the JIRA plugni can be disabled, the blueocean-JIRA plugin will complain but it wont' affect any non JIRA functionality, but just be an ugly (temporary) error. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50703) Jenkins slave jar retained context when Jenkins master was offline
Title: Message Title Philip Bloom updated an issue Jenkins / JENKINS-50703 Jenkins slave jar retained context when Jenkins master was offline Change By: Philip Bloom The issue was first encountered as a set of jobs that were behaving as if they were Allowing Concurrent Jobs even though they were not set to allow this. Even with a single run occurring, starting from an empty workspace (The workspace on the slave was completely wiped) it was creating jobname@2 to run the job. We cleared this situation up by forcing a restart of the slave.jar process running on the jenkins slave by using Disconnect, confirming that it had shut down, and then reconnected and then backtraced what had actually happened.Earlier in the week, the Jenkins master had been suddenly restarted while active jobs on some slaves were processing. These jobs were left in an undetermined state on the slaves (the master decided they had failed) and were the 1 job that the slaves were seeing. The jenkins master, having no knowledge of these ongoing jobs, would fire off a new job which the slave would treat as a concurrent job. This state persisted long after the job would have normally finished (Days later). Repro step:1) Have one jenkins master, 1 slave.2) Start long enough job on slave.3) Restart master, interrupting connectivity.4) Verify job has failed on master.5) Run job again. @2 should occur. Jenkins version 2.107.1 (had just been upgraded a little before this). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e
[JIRA] (JENKINS-50703) Jenkins slave jar retained context when Jenkins master was offline
Title: Message Title Philip Bloom created an issue Jenkins / JENKINS-50703 Jenkins slave jar retained context when Jenkins master was offline Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-04-10 00:27 Priority: Minor Reporter: Philip Bloom The issue was first encountered as a set of jobs that were behaving as if they were Allowing Concurrent Jobs even though they were not set to allow this. Even with a single run occurring, starting from an empty workspace (The workspace on the slave was completely wiped) it was creating jobname@2 to run the job. We cleared this situation up by forcing a restart of the slave.jar process running on the jenkins slave by using Disconnect, confirming that it had shut down, and then reconnected and then backtraced what had actually happened. Earlier in the week, the Jenkins master had been suddenly restarted while active jobs on some slaves were processing. These jobs were left in an undetermined state on the slaves (the master decided they had failed) and were the 1 job that the slaves were seeing. The jenkins master, having no knowledge of these ongoing jobs, would fire off a new job which the slave would treat as a concurrent job. This state persisted long after the job would have normally finished (Days later). Repro step: 1) Have one jenkins master, 1 slave. 2) Start long enough job on slave. 3) Restart master, interrupting connectivity. 4) Verify job has failed on master. 5) Run job again. @2 should occur.
[JIRA] (JENKINS-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title
Jae Gangemi commented on JENKINS-50525
Re: Error When Provisioning Slave: mountPath: Required value
i'm now getting this error after upgrading for a pod template that was working before and has no volumes/mount paths associated with it at all
Error in provisioning; agent=KubernetesSlave name: kubectl-8-debian-lv201, template=PodTemplate{inheritFrom='', name='kubectl-8-debian', namespace='', label='kubectl-8-debian', nodeSelector='', nodeUsageMode=NORMAL, workspaceVolume=org.csanchez.jenkins.plugins.kubernetes.volumes.workspace.EmptyDirWorkspaceVolume@2d52e6f4, containers=[ContainerTemplate{name='jnlp', image='registry.battery-park.conductor.com/jenkins-slave-8-kubectl-debian', alwaysPullImage=true, workingDir='', command='', args='${computer.jnlpmac} ${computer.name}', ttyEnabled=true, resourceRequestCpu='', resourceRequestMemory='', resourceLimitCpu='', resourceLimitMemory='', livenessProbe=org.csanchez.jenkins.plugins.kubernetes.ContainerLivenessProbe@774c827b}]}
io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: http://jenkins-kubernetes-master.infra.us-east-1.conductor.sh/api/v1/namespaces/beta/pods. Message: Pod "kubectl-8-debian-lv201" is invalid: spec.containers[0].volumeMounts[0].mountPath: Required value. Received status: Status(apiVersion=v1, code=422, details=StatusDetails(causes=[StatusCause(field=spec.containers[0].volumeMounts[0].mountPath, message=Required value, reason=FieldValueRequired, additionalProperties={})], group=null, kind=Pod, name=kubectl-8-debian-lv201, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=Pod "kubectl-8-debian-lv201" is invalid: spec.containers[0].volumeMounts[0].mountPath: Required value, metadata=ListMeta(resourceVersion=null, selfLink=null, additionalProperties={}), reason=Invalid, status=Failure, additionalProperties={}).
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:472)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:411)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:381)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:344)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleCreate(OperationSupport.java:227)
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleCreate(BaseOperation.java:756)
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.create(BaseOperation.java:334)
at org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher.launch(KubernetesLauncher.java:105)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:288)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
[JIRA] (JENKINS-50642) intermittent JenkinsRule test timeout failure
Title: Message Title Jacob Keller edited a comment on JENKINS-50642 Re: intermittent JenkinsRule test timeout failure As a comment, Jenkins did not start disabling the SSHD server by default until 2.83 it looks like (based on the disablement landing in SSHD 2.1, and that version not being pulled in until 2.83..So the jenkins-jdk-8 branch likely will fail for the same reason (low entropy when spawning the SSHD server). EDIT: I ran the tests, and checked the output,it appears that SSHD is not run when we build with 2.60.3 as the base. Note that you may be able to get the remote VFs for the Jenkins CI server to enable something like virtio-rng if you have sufficient RNG from the hosts, but haveged may be sufficient as well. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50642) intermittent JenkinsRule test timeout failure
Title: Message Title Jacob Keller edited a comment on JENKINS-50642 Re: intermittent JenkinsRule test timeout failure As a comment, Jenkins did not start disabling the SSHD server by default until 2.83 it looks like (based on the disablement landing in SSHD 2.1, and that version not being pulled in until 2.83..So the jenkins-jdk-8 branch likely will fail for the same reason (low entropy when spawning the SSHD server).Note that you may be able to get the remote VFs for the Jenkins CI server to enable something like virtio-rng if you have sufficient RNG from the hosts, but haveged may be sufficient as well. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50642) intermittent JenkinsRule test timeout failure
Title: Message Title Jacob Keller commented on JENKINS-50642 Re: intermittent JenkinsRule test timeout failure As a comment, Jenkins did not start disabling the SSHD server by default until 2.83 it looks like (based on the disablement landing in SSHD 2.1, and that version not being pulled in until 2.83.. So the jenkins-jdk-8 branch likely will fail for the same reason (low entropy when spawning the SSHD server). Note that you may be able to get the remote VFs for the Jenkins CI server to enable virtio-rng if you have sufficient RNG from the hosts, but haveged may be sufficient as well. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50642) intermittent JenkinsRule test timeout failure
Title: Message Title Jacob Keller commented on JENKINS-50642 Re: intermittent JenkinsRule test timeout failure I also just discovered that my linux system had been running without RNGD for a few months, which may explain the failures (no RNGD means that I don't have good entropy source on the system). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50642) intermittent JenkinsRule test timeout failure
Title: Message Title Jacob Keller commented on JENKINS-50642 Re: intermittent JenkinsRule test timeout failure Additionally, I added some logging to the SSHD plugin, and I was able to extract this information: === Starting changelogAndPolling(jenkins.plugins.git.GitStepTest) 0.009 [id=380] INFO o.jvnet.hudson.test.JenkinsRule#createWebServer: Running on http://localhost:44701/jenkins/ 0.059 [id=386] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization 0.060 [id=398] INFO jenkins.InitReactorRunner$1#onAttained: Listed all plugins 0.066 [id=391] INFO jenkins.InitReactorRunner$1#onAttained: Prepared all plugins 0.070 [id=389] INFO jenkins.InitReactorRunner$1#onAttained: Started all plugins 0.071 [id=389] INFO jenkins.InitReactorRunner$1#onAttained: Augmented all extensions 0.276 [id=409] WARNING h.ExtensionFinder$GuiceFinder$FaultTolerantScope$1#error: Failed to instantiate optional component org.jenkinsci.plugins.workflow.steps.scm.GitStep$DescriptorImpl; skipping 0.709 [id=399] INFO jenkins.InitReactorRunner$1#onAttained: Loaded all jobs 0.711 [id=391] INFO o.j.main.modules.sshd.SSHD#start: SSHD - start() 0.712 [id=391] INFO o.j.main.modules.sshd.SSHD#start: start() - stopped server 177.722 [id=391] INFO o.j.main.modules.sshd.SSHD#start: start() - set port 177.723 [id=391] INFO o.j.main.modules.sshd.SSHD#start: start() - set key pair 177.723 [id=391] INFO o.j.main.modules.sshd.SSHD#start: start() - set public key 177.734 [id=391] INFO o.j.main.modules.sshd.SSHD#start: Started SSHD at port 39243 177.735 [id=406] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization It appears that we go into SSHD start() and get stuck early in setup. Suddenly, a bunch of things made sense and I think the problem has to do with the platform not generating enough entropy so calls to get random numbers result installs waiting for entropy in /dev/random... That definitely explains the problem and why it's platform specific. I suspect my system I'm testing on does not have enough entropy so when running and re-running the SSHD server in rapid succession, it gets consumed, until the SSHD initialization stalls. Using something like haveged on the VFs would be a good solution I think. I'm looking into whether I can enable the hw rng on my system to avoid the stalls. > If you must support old lines and the Linux CI system has insufficient entropy, the only workaround I know of is installing the haveged package. Nice tip to think in terms of SSH key setup and entropy requirements. Add Comment
[JIRA] (JENKINS-50642) intermittent JenkinsRule test timeout failure
Title: Message Title Jacob Keller commented on JENKINS-50642 Re: intermittent JenkinsRule test timeout failure > I'm thrilled that you've found what appears to be a persistent source of long running tests in test environments. Thanks for the investigation! Mostly persisted due to the timeout failures. > Are your changes to jenkins-test-harness something you'd be willing to share with me so that I could evaluate them in my test environments? I'd love to remove the source of the periodic timeouts that I receive when running tests on varied environments. If you really wanna see what I did: https://github.com/jacob-keller/jenkins-test-harness/tree/jk-disable-sshd > Jacob Keller if you run your tests using code from that pull request, do you see the same problems? I'll give it a shot. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50589) Need to view Performance Plugin test results in BlueOcean UI
Title: Message Title Michael Neale commented on JENKINS-50589 Re: Need to view Performance Plugin test results in BlueOcean UI I think initially having links to existing is a great start - don't you Ivan Meredith? If there are data driven charting things that can be used to make a new UI for it (similar to trends) then that could be a follow on I think Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50687) When using docker.withRegistry withEnv repeats indefinitely.
Title: Message Title Aaron Haaf commented on JENKINS-50687 Re: When using docker.withRegistry withEnv repeats indefinitely. Whoops! Thanks for the correction Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50702) jenkins pipeline with groovy and use of “Withcredentials”
Title: Message Title
guillermo casco created an issue
Jenkins / JENKINS-50702
jenkins pipeline with groovy and use of “Withcredentials”
Issue Type:
Story
Assignee:
Stephen Connolly
Attachments:
Extractor.groovy
Components:
credentials-plugin
Created:
2018-04-09 21:17
Priority:
Minor
Reporter:
guillermo casco
I have a jenkins pipeline from SCM running in jenkins with a groovyscript. In one of the steps I have upload a file to artifactory with CURL - u user:pass , but don´t wan´t that user and pass be visible in output of pipeline in jenkins. I have read in several places the "Withcredential" function but I´m not quite sure how to this works or apply or implement. I tried this 2 options with no luck: stage ('Upload war to Artifactory') { withCredentials([usernamePassword(credentialsId: 'artifactory', usernameVariable: username', passwordVariable: 'password')]) sh "sudo curl -u $username:$password -T $warPath 'https://artifactory.xxx.com:443/artifactory/form/$warFile'" } In this case I´m getting: org.jenkinsci.plugins.credentialsbinding.impl.CredentialNotFoundException: artifactory at org.jenkinsci.plugins.credentialsbinding.MultiBinding.getCredentials(MultiBinding.java:153) at org.jenkinsci.plugins.credentialsbinding.impl.UsernamePasswordMultiBinding.bind(UsernamePasswordMultiBinding.java:76) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Execution.start(BindingStep.java:114) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) at groovy.lang.MetaCl
[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Matt Grochowalski commented on JENKINS-32167 Re: ISVNAuthentication provider did not provide credentials Liyaa submitted a pull request to fix this issue: https://github.com/jenkinsci/subversion-plugin/pull/212 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50572) Pipeline create flow fails when done against a blank repo on Bitbucket Server
Title: Message Title Vivek Pandey updated JENKINS-50572 Jenkins / JENKINS-50572 Pipeline create flow fails when done against a blank repo on Bitbucket Server Change By: Vivek Pandey Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50605) Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server
Title: Message Title
ritica r updated an issue
Jenkins / JENKINS-50605
Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server
Change By:
ritica r
{{Jenkins}} version 2.114 (upgraded from 2.107.1 to try to resolve issue) is running builds but they seem to disappear from the Dashboard after a restart. I have Jenkins setup on {{Linux}} and all the log is present under {{$\{JENKINS_HOME}/jobs/$\{ITEM_FULL_NAME}/builds}}I have tried Reload Configuration from Disk with following set in {{/etc/sysconfig/jenkins}}\{\{JENKINS_JAVA_OPTIONS="-Djava.awt.headless=true -Dhudson.Util.symlinkEscapeHatch=true" }}Below is build and workspace directory settings:\{\{Workspace Root Directory :$\{JENKINS_HOME}/workspace/$\{ITEM_FULL_NAME} Build Record Root Directory: $\{JENKINS_HOME}/jobs/$\{ITEM_FULL_NAME}/builds }}Below you can see the build number 117 and 118 for one of my jobs, but still, the lastFailedBuild, lastStableBuild , lastSuccessfulBuild are set to -1, which doesn't existdrwxr-xr-x 4 jenkins jenkins 4096 Apr 2 20:17 117 drwxr-xr-x 4 jenkins jenkins 4096 Apr 3 20:17 118 lrwxrwxrwx 1 jenkins jenkins 2 Apr 3 11:09 lastFailedBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 4 10:44 lastStableBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 4 03:21 lastSuccessfulBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 3 10:58 lastUnstableBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 3 10:58 lastUnsuccessfulBuild -> -1 I have also set the{{Discard Old Builds Slicer - Days to keep artifacts as 30 Discard Old Builds Slicer - Max # of builds to keep as 40}}I ran the jenkins-job-checker[ [https://github.com/docwhat/jenkins-job-checker] ] on one of the jobs and found the following : Problem: NOTLINK: The number link builds/1 is not a symlink! Problem: NOTLINK: The number link builds/2 is not a symlink! Problem: NOTLINK: The number link builds/3 is not a symlink! Proposal: Archive non-link builds/1 Proposal: Archive non-link builds/2 {{Proposal: Archive non-link builds/3}} Really appreaciate some help
Add Comment
[JIRA] (JENKINS-50605) Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server
Title: Message Title
ritica r updated an issue
Jenkins / JENKINS-50605
Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server
Change By:
ritica r
{{Jenkins}} version 2.114 (upgraded from 2.107.1 to try to resolve issue) is running builds but they seem to disappear from the Dashboard after a restart. I have Jenkins setup on {{Linux}} and all the log is present under {{$\{JENKINS_HOME}/jobs/$\{ITEM_FULL_NAME}/builds}}I have tried Reload Configuration from Disk with following set in {{/etc/sysconfig/jenkins}}\{\{JENKINS_JAVA_OPTIONS="-Djava.awt.headless=true -Dhudson.Util.symlinkEscapeHatch=true" }}Below is build and workspace directory settings:\{\{Workspace Root Directory :$\{JENKINS_HOME}/workspace/$\{ITEM_FULL_NAME} Build Record Root Directory: $\{JENKINS_HOME}/jobs/$\{ITEM_FULL_NAME}/builds }}Below you can see the build number 117 and 118 for one of my jobs, but still, the lastFailedBuild, lastStableBuild , lastSuccessfulBuild are set to -1, which doesn't existdrwxr-xr-x 4 jenkins jenkins 4096 Apr 2 20:17 117 drwxr-xr-x 4 jenkins jenkins 4096 Apr 3 20:17 118 lrwxrwxrwx 1 jenkins jenkins 2 Apr 3 11:09 lastFailedBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 4 10:44 lastStableBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 4 03:21 lastSuccessfulBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 3 10:58 lastUnstableBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 3 10:58 lastUnsuccessfulBuild -> -1 I have also set the{{Discard Old Builds Slicer - Days to keep artifacts as 30 Discard Old Builds Slicer - Max # of builds to keep as 40}}I ran the jenkins-job-checker[ [https://github.com/docwhat/jenkins-job-checker] ] on one of the jobs and found the following : {{ Problem: NOTLINK: The number link builds/1 is not a symlink! }} {{ Problem: NOTLINK: The number link builds/2 is not a symlink! }} {{ Problem: NOTLINK: The number link builds/3 is not a symlink! }} {{ Proposal: Archive non-link builds/1 }} {{ Proposal: Archive non-link builds/2 }} {{Proposal: Archive non-link builds/3}} Really appreaciate some help
Add Comment
[JIRA] (JENKINS-50605) Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server
Title: Message Title ritica r updated an issue Jenkins / JENKINS-50605 Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server Change By: ritica r Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50605) Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server
Title: Message Title
ritica r updated an issue
Jenkins / JENKINS-50605
Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server
Change By:
ritica r
{{Jenkins}} version 2.114 (upgraded from 2.107.1 to try to resolve issue) is running builds but they seem to disappear from the Dashboard after a restart. I have Jenkins setup on {{Linux}} and all the log is present under {{$\{JENKINS_HOME}/jobs/$\{ITEM_FULL_NAME}/builds}}I have tried Reload Configuration from Disk with following set in {{/etc/sysconfig/jenkins}}\{\{JENKINS_JAVA_OPTIONS="-Djava.awt.headless=true -Dhudson.Util.symlinkEscapeHatch=true" }}Below is build and workspace directory settings:\{\{Workspace Root Directory :$\{JENKINS_HOME}/workspace/$\{ITEM_FULL_NAME} Build Record Root Directory: $\{JENKINS_HOME}/jobs/$\{ITEM_FULL_NAME}/builds }}Below you can see the build number 117 and 118 for one of my jobs , but still, the lastFailedBuild, lastStableBuild , lastSuccessfulBuild are set to -1, which doesn't existdrwxr-xr-x 4 jenkins jenkins 4096 Apr 2 20:17 117 drwxr-xr-x 4 jenkins jenkins 4096 Apr 3 20:17 118 lrwxrwxrwx 1 jenkins jenkins 2 Apr 3 11:09 lastFailedBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 4 10:44 lastStableBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 4 03:21 lastSuccessfulBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 3 10:58 lastUnstableBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 3 10:58 lastUnsuccessfulBuild -> -1 I have also set the{{Discard Old Builds Slicer - Days to keep artifacts as 30 Discard Old Builds Slicer - Max # of builds to keep as 40}} I ran the jenkins-job-checker[ [https://github.com/docwhat/jenkins-job-checker] ] on one of the jobs and found the following : {{ Problem: NOTLINK: The number link builds/1 is not a symlink! }}{{Problem: NOTLINK: The number link builds/2 is not a symlink! }}{{Problem: NOTLINK: The number link builds/3 is not a symlink! }}{{Proposal: Archive non-link builds/1 }}{{Proposal: Archive non-link builds/2 }}{{Proposal: Archive non-link builds/3}} Really appreaciate some help
Add Comment
[JIRA] (JENKINS-50682) Error when selecting when / changeRequest or tag in the Directive Generator
Title: Message Title Andrew Bayer started work on JENKINS-50682 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50682) Error when selecting when / changeRequest or tag in the Directive Generator
Title: Message Title Andrew Bayer commented on JENKINS-50682 Re: Error when selecting when / changeRequest or tag in the Directive Generator Got it - PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/261 fixing that and making a few other changes to when condition directive generation. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50682) Error when selecting when / changeRequest or tag in the Directive Generator
Title: Message Title Andrew Bayer updated JENKINS-50682 Jenkins / JENKINS-50682 Error when selecting when / changeRequest or tag in the Directive Generator Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50701) Jenkin Dynatrace SAAS Integration issue
Title: Message Title Arun Singh Christopher updated an issue Jenkins / JENKINS-50701 Jenkin Dynatrace SAAS Integration issue Change By: Arun Singh Christopher We are trying to Integrate Jenkins with Dynatrace SAAS. However the Jenkins plugin provides only two options http and https where I am not able to specify the proxy to be used to connect to the Dynatrace SAAS.When connecting from Dynatrace Client to DynatraceSAAS we use the following1. Type - Via Proxy2. Host - x...@domain.com3. Port: 12344. User: abcdef5. password: password6. Proxy host: a...@domain.com7. Proxy host: 34568 Authentication: Annonymous.However Jenkins plugin for Dynatrace only has that the below fields. Please find the attachment which shows the Jenkins plugin fields for Dynatrace. Kindly help how i can connect to dynatrace from Jenkins. We are not able to specify dynatrace proxy details. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Gr
[JIRA] (JENKINS-50701) Jenkin Dynatrace SAAS Integration issue
Title: Message Title Arun Singh Christopher created an issue Jenkins / JENKINS-50701 Jenkin Dynatrace SAAS Integration issue Issue Type: Bug Assignee: Victor Martinez Attachments: Jenkins_DynatraceFields.png Components: jenkinslint-plugin Created: 2018-04-09 20:36 Priority: Major Reporter: Arun Singh Christopher We are trying to Integrate Jenkins with Dynatrace SAAS. However the Jenkins plugin provides only two options http and https where I am not able to specify the proxy to be used to connect to the Dynatrace SAAS. When connecting from Dynatrace Client to DynatraceSAAS we use the following 1. Type - Via Proxy 2. Host - x...@domain.com 3. Port: 1234 4. User: abcdef 5. password: password 6. Proxy host: a...@domain.com 7. Proxy host: 3456 8 Authentication: Annonymous. However Jenkins plugin for Dynatrace only that the below fields. Please find the attachment which shows the Jenkins plugin fields for Dynatrace. Kindly help how i can connect to dynatrace from Jenkins. Add Comment
[JIRA] (JENKINS-50642) intermittent JenkinsRule test timeout failure
Title: Message Title Mark Waite edited a comment on JENKINS-50642 Re: intermittent JenkinsRule test timeout failure @ [~ jglick ] I think I've seen the same behavior from the [require-jdk-8 pull request|https://github.com/jenkinsci/git-plugin/pull/565].[~jekeller] if you run your tests using code from that pull request, do you see the same problems? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50642) intermittent JenkinsRule test timeout failure
Title: Message Title Mark Waite commented on JENKINS-50642 Re: intermittent JenkinsRule test timeout failure @jglick I think I've seen the same behavior from the require-jdk-8 pull request. Jacob Keller if you run your tests using code from that pull request, do you see the same problems? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50642) intermittent JenkinsRule test timeout failure
Title: Message Title Jesse Glick commented on JENKINS-50642 Re: intermittent JenkinsRule test timeout failure Do not bother. Mark Waite already has a branch (IIRC) for this plugin which uses a more contemporary Jenkins baseline. There is no point in wasting development effort supporting PRs built against obsolete lines. If you must support old lines and the Linux CI system has insufficient entropy, the only workaround I know of is installing the haveged package. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50642) intermittent JenkinsRule test timeout failure
Title: Message Title Mark Waite commented on JENKINS-50642 Re: intermittent JenkinsRule test timeout failure I'm thrilled that you've found what appears to be a persistent source of long running tests in test environments. Thanks for the investigation! Are your changes to jenkins-test-harness something you'd be willing to share with me so that I could evaluate them in my test environments? I'd love to remove the source of the periodic timeouts that I receive when running tests on varied environments. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50698) Integration tests
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-50698
Integration tests
Change By:
Jesse Glick
Can https://repo set {{incrementals . jenkins-ci url}} if we can start a temporary Docker container to host Nexus . org/incrementals/ be replaced with another URL for testing?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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] (JENKINS-32895) "The referenced task was not found" prevents docker slaves from being deleted
Title: Message Title Philipp Garbe resolved as Fixed Has already been released Jenkins / JENKINS-32895 "The referenced task was not found" prevents docker slaves from being deleted Change By: Philipp Garbe Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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/op
[JIRA] (JENKINS-33928) Communication to AWS API should support HTTP proxies
Title: Message Title Philipp Garbe resolved as Fixed Has already been fixed. Jenkins / JENKINS-33928 Communication to AWS API should support HTTP proxies Change By: Philipp Garbe Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50671) Jenkins won't start after upgrading workflow-cps plugin to 2.47
Title: Message Title Nathan Vahrenberg commented on JENKINS-50671 Re: Jenkins won't start after upgrading workflow-cps plugin to 2.47 Thanks for the investigation. Sorry to point blame the wrong direction, but it's definitely curious that downgrading the workflow-cps plugin "fixes" it. I'll keep an eye on the other Jira for a fix. Thanks again! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-36468) Tasks fail to run on ECS after upgrade to 1.4
Title: Message Title Philipp Garbe commented on JENKINS-36468 Re: Tasks fail to run on ECS after upgrade to 1.4 Is this still an issue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-39220) ECS Cluster drop-down does not show more than 100 ecs clusters
Title: Message Title Philipp Garbe resolved as Fixed Has been fixed in v1.12 Jenkins / JENKINS-39220 ECS Cluster drop-down does not show more than 100 ecs clusters Change By: Philipp Garbe Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-46581) DNS Search Domains not honored in Amazon ECS Plugin
Title: Message Title Philipp Garbe closed an issue as Fixed Jenkins / JENKINS-46581 DNS Search Domains not honored in Amazon ECS Plugin Change By: Philipp Garbe Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-46581) DNS Search Domains not honored in Amazon ECS Plugin
Title: Message Title Philipp Garbe resolved as Fixed Fixed with https://github.com/jenkinsci/amazon-ecs-plugin/pull/42 Jenkins / JENKINS-46581 DNS Search Domains not honored in Amazon ECS Plugin Change By: Philipp Garbe Status: Open Resolved Assignee: Jan Roehrich Philipp Garbe Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this messa
[JIRA] (JENKINS-50689) Document opt-in process
Title: Message Title Jesse Glick started work on JENKINS-50689 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50642) intermittent JenkinsRule test timeout failure
Title: Message Title Mark Waite assigned an issue to Jacob Keller Jenkins / JENKINS-50642 intermittent JenkinsRule test timeout failure Change By: Mark Waite Assignee: Mark Waite Jacob Keller Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-46842) Add support for specifying volumes
Title: Message Title Philipp Garbe closed an issue as Not A Defect Jenkins / JENKINS-46842 Add support for specifying volumes Change By: Philipp Garbe Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50663) Deadlock on jenkins startup
Title: Message Title Sam Van Oort commented on JENKINS-50663 Re: Deadlock on jenkins startup I have upgraded this to Blocker because it prevents Jenkins from functioning at all. Note that I'm not impacted, but am something of collateral damage since plugins I maintain caught the initial blame until we investigated. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50671) Jenkins won't start after upgrading workflow-cps plugin to 2.47
Title: Message Title Sam Van Oort resolved as Duplicate I'm closing this one as a duplicate since it appears to be caused by an already-identified bug in the sonar plugin – will be happy to re-open if there proves to be more going on than that (just reply back and re-open it). Jenkins / JENKINS-50671 Jenkins won't start after upgrading workflow-cps plugin to 2.47 Change By: Sam Van Oort Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" gr
[JIRA] (JENKINS-50671) Jenkins won't start after upgrading workflow-cps plugin to 2.47
Title: Message Title Sam Van Oort commented on JENKINS-50671 Re: Jenkins won't start after upgrading workflow-cps plugin to 2.47 Nathan Vahrenberg Ah, thank you, that helps a lot – It looks like the root cause of your problem is actually https://issues.jenkins-ci.org/browse/JENKINS-50663 which is caused by the Sonar Plugin triggering a deadlock. You should be able to resolve the issue by downgrading sonar to 2.6.1 and can freely upgrade workflow-cps again at the same time. The workflow-cps upgrade appears to be a red herring – probably since this is a deadlock it just so happens that the timing of the startup process was a bit different between restarts so you got a deadlock in one case but not the other. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50663) Deadlock on jenkins startup
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-50663 Deadlock on jenkins startup Change By: Sam Van Oort Priority: Major Blocker Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50682) Error when selecting when / changeRequest or tag in the Directive Generator
Title: Message Title Andrew Bayer commented on JENKINS-50682 Re: Error when selecting when / changeRequest or tag in the Directive Generator tag barfs too, but you have to open the "Advanced" options to get it to do so. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50682) Error when selecting when / changeRequest or tag in the Directive Generator
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-50682 Error when selecting when / changeRequest or tag in the Directive Generator Change By: Andrew Bayer Summary: Error when selecting when / changeRequest or tag in the Directive Generator Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50671) Jenkins won't start after upgrading workflow-cps plugin to 2.47
Title: Message Title Nathan Vahrenberg edited a comment on JENKINS-50671 Re: Jenkins won't start after upgrading workflow-cps plugin to 2.47 Thread dump: [^ stacktrace threaddump .txt] I took a glance at it and it mentions a deadlock, is that what you're looking for? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50671) Jenkins won't start after upgrading workflow-cps plugin to 2.47
Title: Message Title Nathan Vahrenberg updated an issue Jenkins / JENKINS-50671 Jenkins won't start after upgrading workflow-cps plugin to 2.47 Change By: Nathan Vahrenberg Attachment: stacktrace.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50671) Jenkins won't start after upgrading workflow-cps plugin to 2.47
Title: Message Title Nathan Vahrenberg updated an issue Jenkins / JENKINS-50671 Jenkins won't start after upgrading workflow-cps plugin to 2.47 Change By: Nathan Vahrenberg Attachment: threaddump.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50671) Jenkins won't start after upgrading workflow-cps plugin to 2.47
Title: Message Title Nathan Vahrenberg commented on JENKINS-50671 Re: Jenkins won't start after upgrading workflow-cps plugin to 2.47 Stacktrace: stacktrace.txt I took a glance at it and it mentions a deadlock, is that what you're looking for? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50671) Jenkins won't start after upgrading workflow-cps plugin to 2.47
Title: Message Title Nathan Vahrenberg edited a comment on JENKINS-50671 Re: Jenkins won't start after upgrading workflow-cps plugin to 2.47 Stacktrace Thread dump : [^stacktrace.txt] I took a glance at it and it mentions a deadlock, is that what you're looking for? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50671) Jenkins won't start after upgrading workflow-cps plugin to 2.47
Title: Message Title Nathan Vahrenberg updated an issue Jenkins / JENKINS-50671 Jenkins won't start after upgrading workflow-cps plugin to 2.47 Change By: Nathan Vahrenberg Attachment: stacktrace.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50700) Fix maven-hpi-plugin to use hudson.util.VersionNumber
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-50700 Fix maven-hpi-plugin to use hudson.util.VersionNumber Issue Type: Story Assignee: Jesse Glick Components: maven-hpi-plugin Created: 2018-04-09 19:47 Priority: Minor Reporter: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Je
[JIRA] (JENKINS-50578) Add support to specify checks on ArachniScanner
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50578 Re: Add support to specify checks on ArachniScanner Code changed in jenkins User: irissmann Path: pom.xml src/main/java/org/jenkinsci/plugins/arachni/ArachniScanner.java src/main/resources/org/jenkinsci/plugins/arachni/ArachniScanner/config.jelly src/main/resources/org/jenkinsci/plugins/arachni/ArachniScanner/help-checks.html src/test/java/org/jenkinsci/plugins/arachni/ArachniScannerTest.java http://jenkins-ci.org/commit/arachni-scanner-plugin/043e5c227a0c77cdd02637ce996cbed0927065ae Log: JENKINS-50578 support checks Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50671) Jenkins won't start after upgrading workflow-cps plugin to 2.47
Title: Message Title Nathan Vahrenberg commented on JENKINS-50671 Re: Jenkins won't start after upgrading workflow-cps plugin to 2.47 Thanks for the quick response Sam Van Oort. I'll grab the thread dump and upload here as soon as I can - I have to try not to disrupt users of this instance too much if possible. Yes, the workflow-job plugin was also updated this morning. It appears that disk total usage (R/W combined) spiked to about 24% around the upgrade (I can try to get more specific metrics if necessary). Right now it's around 2-5% and it looks like that's about the same as what it was before upgrading. I've left the workflow-job plugin upgraded, the only plugin I have reverted to an older version at this moment is workflow-cps. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50677) Groovy will fail to execute shell via dir()
Title: Message Title Christian Dechery commented on JENKINS-50677 Re: Groovy will fail to execute shell via dir() I didn't put the error messages because I believe they are not really related to the problem. It would be a diversion. Yes, Pipeline Groovy v 2.4.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50699) Tool to switch between snapshot and incremental versions of a dep
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-50699 Tool to switch between snapshot and incremental versions of a dep Issue Type: Story Assignee: Jesse Glick Components: plugin-pom Created: 2018-04-09 19:18 Priority: Minor Reporter: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Grou
[JIRA] (JENKINS-50698) Integration tests
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-50698 Integration tests Issue Type: Story Assignee: Jesse Glick Components: plugin-pom Created: 2018-04-09 19:17 Priority: Minor Reporter: Jesse Glick Can https://repo.jenkins-ci.org/incrementals/ be replaced with another URL for testing? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50677) Groovy will fail to execute shell via dir()
Title: Message Title Oleg Nenashev commented on JENKINS-50677 Re: Groovy will fail to execute shell via dir() It is hard to say anything without error messages and plugin versions. I assume you use Pipeline, but I am not 100% sure Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50677) Groovy will fail to execute shell via dir()
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50677 Groovy will fail to execute shell via dir() Change By: Oleg Nenashev Component/s: _unsorted Component/s: groovy-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50677) Groovy will fail to execute shell via dir()
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-50677 Groovy will fail to execute shell via dir() Change By: Oleg Nenashev Assignee: vjuranek Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50674) Switch from Perforce plugin (discontinued) to P4 plugin
Title: Message Title Oleg Nenashev commented on JENKINS-50674 Re: Switch from Perforce plugin (discontinued) to P4 plugin JIRA plugin has been recently excluded from BlueOcean FYI (see conversation log in JENKINS-48357) CC Michael Neale Vivek Panday Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-30744) multibranch issues if branch contains /
Title: Message Title Varun Reddy commented on JENKINS-30744 Re: multibranch issues if branch contains / Thijs Borst is this issue resolved for you? I am facing the same exact same issue. The / in the branch name(Releases/test-db) for branches is not working. Any help or workaround that you are aware of ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50656) Google Compute Engine Plugin uncontrolled creation of instances
Title: Message Title dmitrii dudin commented on JENKINS-50656 Re: Google Compute Engine Plugin uncontrolled creation of instances Hello Evan. Thank you for fast reply. I don't think it's related to https://issues.jenkins-ci.org/browse/JENKINS-50566 I can try to reproduce this problem on jenkins master version 2.89.4 tomorrow Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50687) When using docker.withRegistry withEnv repeats indefinitely.
Title: Message Title Oleg Nenashev commented on JENKINS-50687 Re: When using docker.withRegistry withEnv repeats indefinitely. It is Docker Pipeline plugin. fixed the JIRA component Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50687) When using docker.withRegistry withEnv repeats indefinitely.
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-50687 When using docker.withRegistry withEnv repeats indefinitely. Change By: Oleg Nenashev Assignee: Nicolas De Loof Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50696) Evaluate impact on NetBeans workflows
Title: Message Title Jesse Glick started work on JENKINS-50696 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50687) When using docker.withRegistry withEnv repeats indefinitely.
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50687 When using docker.withRegistry withEnv repeats indefinitely. Change By: Oleg Nenashev Component/s: docker-workflow-plugin Component/s: docker Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
