[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title Ariel M commented on JENKINS-15570 Re: Coverage report includes classes that have been excluded from Jacoco analysis We are also facing the same issue. it's weird coz' it's working for one MS, but not for the other. is there any update for it? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.146326.1350570861000.6131.1572535860677%40Atlassian.JIRA.
[JIRA] (JENKINS-59239) Pipeline job's builds are missing in bulk after failure
Title: Message Title Ariel M closed an issue as Cannot Reproduce Jenkins / JENKINS-59239 Pipeline job's builds are missing in bulk after failure Change By: Ariel M Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201696.1567669735000.4467.1569358200110%40Atlassian.JIRA.
[JIRA] (JENKINS-58179) Jenkins builds disappearing from Unix machine due to open shift sync plugin issue
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-58179 Jenkins builds disappearing from Unix machine due to open shift sync plugin issue Change By: Ariel M Comment: I don't think it's related to openshift... I've opened new case for it: https://issues.jenkins-ci.org/browse/JENKINS-59239BTW, I've found one case where they said "the whole _problem disappears after I uninstalled the JobConfigHistoryPlugin":_https://issues.jenkins-ci.org/browse/JENKINS-50595_ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200230.1561449713000.4465.1569358080166%40Atlassian.JIRA.
[JIRA] (JENKINS-58281) Pipeline job's builds are missing randomly in bulk
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-58281 Pipeline job's builds are missing randomly in bulk Change By: Ariel M Comment: anyone is checking? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200345.1561974734000.4447.1569357960631%40Atlassian.JIRA.
[JIRA] (JENKINS-50595) build history disappeared after upgrade to 2.107.1
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-50595 build history disappeared after upgrade to 2.107.1 Change By: Ariel M Comment: [~swf] do you think the uninstall of _JobConfigHistoryPlugin_ can help me solve this issue:https://issues.jenkins-ci.org/browse/JENKINS-59239 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189669.1522939372000.4449.1569357960682%40Atlassian.JIRA.
[JIRA] (JENKINS-59517) How can I add groovy code to String parameter fields in pipeline?
Title: Message Title Ariel M created an issue Jenkins / JENKINS-59517 How can I add groovy code to String parameter fields in pipeline? Issue Type: Bug Assignee: vjuranek Components: groovy-plugin, pipeline Created: 2019-09-24 20:32 Priority: Minor Reporter: Ariel M I have a pipeline job with some String parameters. I want to hide/disable them in case I'm choosing some active choice parameter, and I understood I can do it using groovy code. But I don't see such an option when choosing String parameter. Add Comment
[JIRA] (JENKINS-58281) Pipeline job's builds are missing randomly in bulk
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-58281 Pipeline job's builds are missing randomly in bulk Change By: Ariel M Priority: Critical Blocker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200345.1561974734000.1377.1568223660273%40Atlassian.JIRA.
[JIRA] (JENKINS-59239) Pipeline job's builds are missing in bulk after failure
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-59239 Pipeline job's builds are missing in bulk after failure Change By: Ariel M Priority: Critical Blocker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201696.1567669735000.750.1568129820092%40Atlassian.JIRA.
[JIRA] (JENKINS-50595) build history disappeared after upgrade to 2.107.1
Title: Message Title Ariel M commented on JENKINS-50595 Re: build history disappeared after upgrade to 2.107.1 Yves Schumann do you think the uninstall of JobConfigHistoryPlugin can help me solve this issue: https://issues.jenkins-ci.org/browse/JENKINS-59239 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189669.1522939372000.8689.1567943880379%40Atlassian.JIRA.
[JIRA] (JENKINS-59239) Pipeline job's builds are missing in bulk after failure
Title: Message Title Ariel M commented on JENKINS-59239 Re: Pipeline job's builds are missing in bulk after failure Can someone check it? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201696.1567669735000.8670.1567937940075%40Atlassian.JIRA.
[JIRA] (JENKINS-58179) Jenkins builds disappearing from Unix machine due to open shift sync plugin issue
Title: Message Title Ariel M edited a comment on JENKINS-58179 Re: Jenkins builds disappearing from Unix machine due to open shift sync plugin issue I don't think it's related to openshift... I've opened new case for it:https://issues.jenkins-ci.org/browse/JENKINS-59239BTW, I've found one case where they said "the whole _problem disappears after I uninstalled the JobConfigHistoryPlugin":_ _https https ://issues.jenkins-ci.org/browse/JENKINS-50595_ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200230.1561449713000.7072.1567682940159%40Atlassian.JIRA.
[JIRA] (JENKINS-58179) Jenkins builds disappearing from Unix machine due to open shift sync plugin issue
Title: Message Title Ariel M commented on JENKINS-58179 Re: Jenkins builds disappearing from Unix machine due to open shift sync plugin issue I don't think it's related to openshift... I've opened new case for it: https://issues.jenkins-ci.org/browse/JENKINS-59239 BTW, I've found one case where they said "the whole problem disappears after I uninstalled the JobConfigHistoryPlugin": _https://issues.jenkins-ci.org/browse/JENKINS-50595_ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200230.1561449713000.7062.1567681500301%40Atlassian.JIRA.
[JIRA] (JENKINS-58179) Jenkins builds disappearing from Unix machine due to open shift sync plugin issue
Title: Message Title Ariel M edited a comment on JENKINS-58179 Re: Jenkins builds disappearing from Unix machine due to open shift sync plugin issue Gabe/Vibhav, could it be related to open sync version? we are currently working with 1.0.37. any change Chance updating to 1.0.41 will solve the issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200230.1561449713000.6958.1567675560348%40Atlassian.JIRA.
[JIRA] (JENKINS-58179) Jenkins builds disappearing from Unix machine due to open shift sync plugin issue
Title: Message Title Ariel M commented on JENKINS-58179 Re: Jenkins builds disappearing from Unix machine due to open shift sync plugin issue Gabe/Vibhav, could it be related to open sync version? we are currently working with 1.0.37. any change updating to 1.0.41 will solve the issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200230.1561449713000.6916.1567671540158%40Atlassian.JIRA.
[JIRA] (JENKINS-59239) Pipeline job's builds are missing in bulk after failure
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-59239 Pipeline job's builds are missing in bulk after failure Change By: Ariel M We notice that for some reason every time that we have a successful build, and after its failure, all the builds between them deleted from the build history. Do you know why it is happening? Can we change it?For example, in this attached image you can see that all the builds between 611 to 694 were deleted (we have some successes between them, but we can't see it… ) !example.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201696.1567669735000.6914.1567671120258%40Atlassian.JIRA.
[JIRA] (JENKINS-58281) Pipeline job's builds are missing randomly in bulk
Title: Message Title Ariel M commented on JENKINS-58281 Re: Pipeline job's builds are missing randomly in bulk anyone is checking? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200345.1561974734000.6913.1567670160122%40Atlassian.JIRA.
[JIRA] (JENKINS-59239) Pipeline job's builds are missing in bulk after failure
Title: Message Title Ariel M created an issue Jenkins / JENKINS-59239 Pipeline job's builds are missing in bulk after failure Issue Type: Bug Assignee: Unassigned Attachments: example.png Components: pipeline Created: 2019-09-05 07:48 Priority: Critical Reporter: Ariel M We notice that for some reason every time that we have a successful build, and after its failure, all the builds between them deleted from the build history. Do you know why it is happening? Can we change it? For example, in this attached image you can see that all the builds between 611 to 694 were deleted (we have some successes between them, but we can't see it… Add Comment
[JIRA] (JENKINS-58179) Jenkins builds disappearing from Unix machine due to open shift sync plugin issue
Title: Message Title
Ariel M updated an issue
Jenkins / JENKINS-58179
Jenkins builds disappearing from Unix machine due to open shift sync plugin issue
Change By:
Ariel M
In some Jenkins, the some builds are automatically getting deleted because of the from job page and unix machine. we suspect it's some issue with open shift sync plugin. from the jenkins log: {{INFO: onDeleted job/ocp-oc-cd-for-fit/job/ocp-oc-cd-for-fit-oc-cd-ocp/4272/ Jun 27, 2019 7:28:07 AM io.fabric8.jenkins.openshiftsync.JenkinsUtils deleteRun INFO: Deleting run: ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4272 Jun 27, 2019 7:28:07 AM io.fabric8.jenkins.openshiftsync.JenkinsUtils deleteRun WARNING: Unable to delete run ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4272:ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4272: /pciuser/tools/jenkins/jenkins-production/jobs/ocp-oc-cd-for-fit/jobs/ocp-oc-cd-for-fit-oc-cd-ocp/builds/4272 looks to have already been deleted; siblings: [4259, 4138, 3351, 4271, 3753, 4277, lastUnstableBuild, 4139, 4276, legacyIds, 4280, 3385, 49, 4260, 3722, lastStableBuild, 4275, lastFailedBuild, 4279, 3220, 3413, 4270, {color:#de350b}**4254, lastUnsuccessfulBuild, 3404, 4220, lastSuccessfulBuild, 4215, 4278] Jun 27, 2019 7:28:07 AM io.fabric8.jenkins.openshiftsync.JenkinsUtils deleteRunINFO: Deleting run: ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4271INFO: Deleting run: ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4270Jun 27, 2019 7:28:51 AM io.fabric8.jenkins.openshiftsync.JenkinsUtils deleteRun**{color}WARNING: Unable to delete run ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4270:ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4270: /pciuser/tools/jenkins/jenkins-production/jobs/ocp-oc-cd-for-fit/jobs/ocp-oc-cd-for-fit-oc-cd-ocp/builds/4270 looks to have already been deleted; siblings: [4259, 4138, 3351, 3753, 4277, lastUnstableBuild, 4139, 4276, legacyIds, 4280, 3385, 49, 4260, 3722, lastStableBuild, 4275, lastFailedBuild, 4279, 3220, 3413, 4254, lastUnsuccessfulBuild, 3404, 4220, lastSuccessfulBuild, 4215, 4278] Jun 27, 2019 7:28:51 AM io.fabric8.jenkins.openshiftsync.BuildWatcher reconcileRunsAndBuilds}}
Add Comment
[JIRA] (JENKINS-58179) Jenkins builds disappearing from Unix machine due to open shift sync plugin issue
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-58179 Jenkins builds disappearing from Unix machine due to open shift sync plugin issue Change By: Ariel M Component/s: openshift-sync-plugin Component/s: core Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200230.1561449713000.15219.1563447060116%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58179) Jenkins builds disappearing from Unix machine due to open shift sync plugin issue
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-58179 Jenkins builds disappearing from Unix machine due to open shift sync plugin issue Change By: Ariel M Priority: Critical Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200230.1561449713000.15218.1563447000272%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58179) Jenkins builds disappearing from Unix machine due to open shift sync plugin issue
Title: Message Title
Ariel M updated an issue
Jenkins / JENKINS-58179
Jenkins builds disappearing from Unix machine due to open shift sync plugin issue
Change By:
Ariel M
In some Jenkins, the builds are automatically deleted because of the open shift sync plugin. from the log: {{INFO: onDeleted job/ocp-oc-cd-for-fit/job/ocp-oc-cd-for-fit-oc-cd-ocp/4272/Jun 27, 2019 7:28:07 AM io.fabric8.jenkins.openshiftsync.JenkinsUtils deleteRunINFO: Deleting run: ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4272Jun 27, 2019 7:28:07 AM io.fabric8.jenkins.openshiftsync.JenkinsUtils deleteRunWARNING: Unable to delete run ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4272:ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4272: /pciuser/tools/jenkins/jenkins-production/jobs/ocp-oc-cd-for-fit/jobs/ocp-oc-cd-for-fit-oc-cd-ocp/builds/4272 looks to have already been deleted; siblings: [4259, 4138, 3351, 4271, 3753, 4277, lastUnstableBuild, 4139, 4276, legacyIds, 4280, 3385, 49, 4260, 3722, lastStableBuild, 4275, lastFailedBuild, 4279, 3220, 3413, 4270, {color:#de350b}**4254, lastUnsuccessfulBuild, 3404, 4220, lastSuccessfulBuild, 4215, 4278] Jun 27, 2019 7:28:07 AM io.fabric8.jenkins.openshiftsync.JenkinsUtils deleteRunINFO deleteRunINFO : Deleting run: ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp # 4271INFO 4271INFO : Deleting run: ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp # 4270Jun 4270Jun 27, 2019 7:28:51 AM io.fabric8.jenkins.openshiftsync.JenkinsUtils deleteRun**{color}WARNING: Unable to delete run ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4270:ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4270: /pciuser/tools/jenkins/jenkins-production/jobs/ocp-oc-cd-for-fit/jobs/ocp-oc-cd-for-fit-oc-cd-ocp/builds/4270 looks to have already been deleted; siblings: [4259, 4138, 3351, 3753, 4277, lastUnstableBuild, 4139, 4276, legacyIds, 4280, 3385, 49, 4260, 3722, lastStableBuild, 4275, lastFailedBuild, 4279, 3220, 3413, 4254, lastUnsuccessfulBuild, 3404, 4220, lastSuccessfulBuild, 4215, 4278]Jun 27, 2019 7:28:51 AM io.fabric8.jenkins.openshiftsync.BuildWatcher reconcileRunsAndBuilds}}
Add Comment
[JIRA] (JENKINS-58179) Jenkins builds disappearing from Unix machine due to open shift sync plugin issue
Title: Message Title
Ariel M updated an issue
Jenkins / JENKINS-58179
Jenkins builds disappearing from Unix machine due to open shift sync plugin issue
Change By:
Ariel M
I have an issue in specific In some Jenkins (version , the builds are automatically deleted because of the open shift sync plugin. from the log: 2 {{INFO: onDeleted job/ocp-oc-cd-for-fit/job/ocp-oc-cd-for-fit-oc-cd-ocp/4272/Jun 27, 2019 7:28:07 AM io . 138 fabric8 . 1) jenkins.openshiftsync.JenkinsUtils deleteRunINFO: Deleting run: ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4272Jun 27 , where some version disappeared in Jenkins history 2019 7:28:07 AM io . I've checked in the disk fabric8.jenkins.openshiftsync.JenkinsUtils deleteRunWARNING: Unable to delete run ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4272:ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4272: /pciuser/tools/jenkins/jenkins-production/jobs/ocp-oc-cd-for-fit/jobs/ocp-oc-cd-for-fit-oc-cd-ocp/builds/4272 looks to have already been deleted; siblings: [4259 , and it's missing there as well 4138, 3351, 4271, 3753, 4277, lastUnstableBuild, 4139, 4276, legacyIds, 4280, 3385, 49, 4260, 3722, lastStableBuild, 4275, lastFailedBuild, 4279, 3220, 3413, 4270, {color:#de350b}**4254, lastUnsuccessfulBuild, 3404, 4220, lastSuccessfulBuild, 4215, 4278]Jun 27, 2019 7:28:07 AM io . how can I investigate what happened? fabric8.jenkins.openshiftsync.JenkinsUtils deleteRun INFO: Deleting run: ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4271 The difference between this case INFO: Deleting run: ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4270Jun 27, 2019 7:28:51 AM io.fabric8.jenkins.openshiftsync.JenkinsUtils deleteRun**{color}WARNING: Unable to the others is here I can't understand why build were delete run ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4270:ocp-oc-cd-for-fit/ocp-oc-cd-for-fit-oc-cd-ocp #4270: /pciuser/tools/jenkins/jenkins-production/jobs/ocp-oc-cd-for-fit/jobs/ocp-oc-cd-for-fit-oc-cd-ocp/builds/4270 looks to have already been deleted from the Unix machine ; siblings: [4259, 4138, 3351, 3753, 4277, lastUnstableBuild, 4139, 4276, legacyIds, 4280, 3385, 49, 4260, 3722, lastStableBuild, 4275, lastFailedBuild, 4279, 3220, 3413, 4254, lastUnsuccessfulBuild, 3404, 4220, lastSuccessfulBuild, 4215, 4278]Jun 27, 2019 7:28:51 AM io . does it have anything with Jenkins configuration? fabric8.jenkins.openshiftsync.BuildWatcher reconcileRunsAndBuilds}}
[JIRA] (JENKINS-58179) Jenkins builds disappearing from Unix machine due to open shift sync plugin issue
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-58179 Jenkins builds disappearing from Unix machine due to open shift sync plugin issue Change By: Ariel M Summary: Some Jenkins builds disappeared in jenkins history (also not exists in disk) disappearing from Unix machine due to open shift sync plugin issue Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200230.1561449713000.15215.1563446880059%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58179) Some builds disappeared in jenkins history (also not exists in disk)
Title: Message Title Ariel M reopened an issue Jenkins / JENKINS-58179 Some builds disappeared in jenkins history (also not exists in disk) Change By: Ariel M Resolution: Not A Defect Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200230.1561449713000.15214.1563446820136%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58382) Build is stuck due to blocked thread
Title: Message Title Ariel M commented on JENKINS-58382 Re: Build is stuck due to blocked thread Gabe, why do you think it will fix the build with parameters issue? what is the connection between two things? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200506.1562597218000.14400.1563376140112%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58496) Jenkins prefix doesn't work (HTTP ERROR 404)
Title: Message Title Ariel M updated JENKINS-58496 Jenkins / JENKINS-58496 Jenkins prefix doesn't work (HTTP ERROR 404) Change By: Ariel M Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200635.1563193574000.11988.1563280260210%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58508) nginx redirect is not working
Title: Message Title Ariel M updated JENKINS-58508 Jenkins / JENKINS-58508 nginx redirect is not working Change By: Ariel M Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200652.1563269602000.11986.1563280200448%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58508) nginx redirect is not working
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-58508 nginx redirect is not working Change By: Ariel M Attachment: jenkins.conf Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200652.1563269602000.11884.1563273780098%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58508) nginx redirect is not working
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-58508 nginx redirect is not working Change By: Ariel M Attachment: jenkins.conf Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200652.1563269602000.11885.1563273780151%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58508) nginx redirect is not working
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-58508 nginx redirect is not working Change By: Ariel M Attachment: jenkins.conf Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200652.1563269602000.11881.1563273601030%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58508) nginx redirect is not working
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-58508 nginx redirect is not working Change By: Ariel M Attachment: jenkins.conf Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200652.1563269602000.11880.1563273540177%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58508) nginx redirect is not working
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-58508 nginx redirect is not working Change By: Ariel M Attachment: jenkins.conf Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200652.1563269602000.11835.1563269700097%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58508) nginx redirect is not working
Title: Message Title Ariel M created an issue Jenkins / JENKINS-58508 nginx redirect is not working Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-07-16 09:33 Priority: Major Reporter: Ariel M Hi I created a new container of nginx in my env: PORTS: 0.0.0.0:9005->80/tcp NAMES: mynginx1 After it, I have created a file named jenkins.conf based on this link: creativity/SpaceDirectory/Sites/Pci DevOps Operatinal/Shared Documents/Portal/PciToolPortal.html I attached the file to the case. Then I copied the file into this location in the container: /etc/nginx/conf.d/ and restart the nginx container, but it doesn't work. any idea what I did wrong? Add Comment
[JIRA] (JENKINS-58496) Jenkins prefix doesn't work (HTTP ERROR 404)
Title: Message Title Ariel M resolved as Fixed I had to use the below param: env JENKINS_OPTS="-prefix=/jenkins Jenkins / JENKINS-58496 Jenkins prefix doesn't work (HTTP ERROR 404) Change By: Ariel M Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200635.1563193574000.11817.1563268740381%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58382) Build is stuck due to blocked thread
Title: Message Title Ariel M commented on JENKINS-58382 Re: Build is stuck due to blocked thread Will it solve also the below issue I'm facing: Hitting build with parameters not triggering the build, only rebuild option works for me Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200506.1562597218000.11759.1563265020138%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58496) Jenkins prefix doesn't work (HTTP ERROR 404)
Title: Message Title
Ariel M updated an issue
Jenkins / JENKINS-58496
Jenkins prefix doesn't work (HTTP ERROR 404)
Change By:
Ariel M
Summary:
Jenkins prefix doesn't work (HTTP ERROR 404)
I have a job which runs the following command; sudo docker run d p ${Jenkins_PORT}:8080 -p ${Jenkins_TCP_PORT}:5 --name ${Conatiner_name} -e TZ=Asia/Jerusalem -v /pciuser/tools/jenkins/${Conatiner_name}/jenkins-production:/var/jenkins_home --env JAVA_OPTS="-Xmx2048m" {color:#de350b}--*env JENKINS_ARGS="-prefix=/jenkins*"{color} ${ImageID}However, Jenkins is not starting with the Prefix :HTTP ERROR 404Problem accessing /jenkins . Reason: Not Found any idea where I can see more info on why it's not working?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200635.1563193574000.10929.1563194880215%40Atlassian.JIRA.
For more
[JIRA] (JENKINS-58496) Jenkins prefix doesn't work
Title: Message Title
Ariel M updated an issue
Jenkins / JENKINS-58496
Jenkins prefix doesn't work
Change By:
Ariel M
I have a job which runs the following command; sudo docker run d - p ${Jenkins_PORT}:8080 -p ${Jenkins_TCP_PORT}:5 --name ${Conatiner_name} -e TZ=Asia/Jerusalem -v /pciuser/tools/jenkins/${Conatiner_name}/jenkins-production:/var/jenkins_home --env JAVA_OPTS="-Xmx2048m" ** {color:#de350b} --*env JENKINS_ARGS="-prefix=/jenkins*" {color} ${ImageID}However, Jenkins is not starting with the Prefix. any idea where I can see more info on why it's not working?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200635.1563193574000.10927.1563193740135%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58496) Jenkins prefix doesn't work
Title: Message Title
Ariel M updated an issue
Jenkins / JENKINS-58496
Jenkins prefix doesn't work
Change By:
Ariel M
I have a job which runs the following command; sudo docker run d -p ${Jenkins_PORT}:8080 -p ${Jenkins_TCP_PORT}:5 --name ${Conatiner_name} -e TZ=Asia/Jerusalem -v /pciuser/tools/jenkins/${Conatiner_name}/jenkins-production:/var/jenkins_home --env JAVA_OPTS="-Xmx2048m" ** -- *env JENKINS_ARGS="-prefix=/jenkins*" ${ImageID}However, Jenkins is not starting with the Prefix. any idea where I can see more info on why it's not working?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200635.1563193574000.10925.1563193680319%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58496) Jenkins prefix doesn't work
Title: Message Title
Ariel M updated an issue
Jenkins / JENKINS-58496
Jenkins prefix doesn't work
Change By:
Ariel M
I have a job which runs the following command;sudo docker run - d -p ${Jenkins_PORT}:8080 -p ${Jenkins_TCP_PORT}:5 --name ${Conatiner_name} -e TZ=Asia/Jerusalem -v /pciuser/tools/jenkins/${Conatiner_name}/jenkins-production:/var/jenkins_home --env JAVA_OPTS="-Xmx2048m" * -- ** env JENKINS_ARGS="- - prefix=/jenkins*" ${ImageID}However, Jenkins is not starting with the Prefix. any idea where I can see more info on why it's not working?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200635.1563193574000.10923.1563193680286%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58496) Jenkins prefix doesn't work
Title: Message Title
Ariel M updated an issue
Jenkins / JENKINS-58496
Jenkins prefix doesn't work
Change By:
Ariel M
I have a job which runs the following command;sudo docker run -d -p ${Jenkins_PORT}:8080 -p ${Jenkins_TCP_PORT}:5 --name ${Conatiner_name} -e TZ=Asia/Jerusalem -v /pciuser/tools/jenkins/${Conatiner_name}/jenkins-production:/var/jenkins_home --env JAVA_OPTS="-Xmx2048m" {color:#DE350B} * --env JENKINS_ARGS="--prefix=/jenkins {color} * " ${ImageID}However, Jenkins is not starting with the Prefix. any idea where I can see more info on why it's not working?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200635.1563193574000.10921.1563193620432%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58496) Jenkins prefix doesn't work
Title: Message Title
Ariel M created an issue
Jenkins / JENKINS-58496
Jenkins prefix doesn't work
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
docker
Created:
2019-07-15 12:26
Priority:
Minor
Reporter:
Ariel M
I have a job which runs the following command; sudo docker run -d -p ${Jenkins_PORT}:8080 -p ${Jenkins_TCP_PORT}:5 --name ${Conatiner_name} -e TZ=Asia/Jerusalem -v /pciuser/tools/jenkins/${Conatiner_name}/jenkins-production:/var/jenkins_home --env JAVA_OPTS="-Xmx2048m" -env JENKINS_ARGS="-prefix=/jenkins" ${ImageID} However, Jenkins is not starting with the Prefix. any idea where I can see more info on why it's not working?
Add Comment
[JIRA] (JENKINS-58432) Sonar Quality Gate fails due to wrong call to Json (double backslashes in the URL)
Title: Message Title Ariel M closed an issue as Cannot Reproduce Jenkins / JENKINS-58432 Sonar Quality Gate fails due to wrong call to Json (double backslashes in the URL) Change By: Ariel M Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200561.1562782481000.10034.1563091380403%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58179) Some builds disappeared in jenkins history (also not exists in disk)
Title: Message Title Ariel M closed an issue as Not A Defect Jenkins / JENKINS-58179 Some builds disappeared in jenkins history (also not exists in disk) Change By: Ariel M Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200230.1561449713000.10032.1563091380347%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58432) Sonar Quality Gate fails due to wrong call to Json (double backslashes in the URL)
Title: Message Title Ariel M created an issue Jenkins / JENKINS-58432 Sonar Quality Gate fails due to wrong call to Json (double backslashes in the URL) Issue Type: Bug Assignee: Rafael Ramos Components: sonar-quality-gates-plugin Created: 2019-07-10 18:14 Priority: Critical Reporter: Ariel M I have Jenkins where all jobs fail in Sonar Quality Gate for the same reason: [Bitbucket] Build result notified hudson.remoting.ProxyException: net.sf.json.JSONException: Invalid JSON String and few lines after it, the next info: Caused: hudson.remoting.ProxyException: java.lang.IllegalStateException: Unable to parse response from http://illin5566.corp.amdocs.com:19090//api/ce/task? id=AWvbAMmYTj8ZIUmGCNc1: I can't understand why I'm getting two backslashes instead of one after the port. I couldn't figure out where it's coming. Below is query is working fine. http://illin5566.corp.amdocs.com:19090/api/ce/task?id=AWvafAKkTj8ZIUmGCNaW Add Comment
[JIRA] (JENKINS-58382) Build is stuck due to blocked thread
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-58382 Build is stuck due to blocked thread Change By: Ariel M Attachment: Thread Dump.docx Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200506.1562597218000.4976.1562609400176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58382) Build is stuck due to blocked thread
Title: Message Title Ariel M commented on JENKINS-58382 Re: Build is stuck due to blocked thread attached Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200506.1562597218000.4978.1562609400205%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58382) Build is stuck due to blocked thread
Title: Message Title Ariel M created an issue Jenkins / JENKINS-58382 Build is stuck due to blocked thread Issue Type: Bug Assignee: Gabe Montero Components: openshift-sync-plugin Created: 2019-07-08 14:46 Priority: Major Reporter: Ariel M There is a build which is stuck on intial stage. I saw in monitoring screen the below message: Threads on 50aa853439c2@172.17.0.4: Number = 110, Maximum = 526, Total started = 464,563 Warning, the following threads are deadlocked : Handling POST /job/oc-cd-drop22/job/oc-cd-drop22-oc-cd-ocp/214/kill from 10.75.36.119 : qtp544724190-466789, jenkins.util.Timer 9, OkHttp https://ilocpde07-master.corp.amdocs.com:8443/..., OkHttp https://ilocpde07-master.corp.amdocs.com:8443/... I tried to kill that thread but it's not getting deleted. Then I went to the threadDump log and saw: jenkins.util.Timer 9 "jenkins.util.Timer 9" Id=71 Group=main BLOCKED on java.lang.String@39c5d884 owned by "OkHttp https://ilocpde07-master.corp.amdocs.com:8443/..." Id=139290 at io.fabric8.jenkins.openshiftsync.JenkinsUtils.triggerJob(JenkinsUtils.java:422) - blocked on java.lang.String@39c5d884 at io.fabric8.jenkins.openshiftsync.BuildWatcher.addEventToJenkinsJobRun(BuildWatcher.java:345) at io.fabric8.jenkins.openshiftsync.JenkinsUtils.handleBuildList(JenkinsUtils.java:815) at io.fabric8.jenkins.openshiftsync.JenkinsUtils.maybeScheduleNext(JenkinsUtils.java:717) at io.fabric8.jenkins.openshiftsync.BuildSyncRunListener.onDeleted(BuildSyncRunListener.java:184) at hudson.model.listeners.RunListener.fireDeleted(RunListener.java:269) at hudson.model.Run.delete(Run.java:1573) at io.fabric8.jenkins.openshiftsync.JenkinsUtils.deleteRun(JenkinsUtils.java:567) - locked java.lang.Class@b802391 at io.fabric8.jenkins.openshiftsync.BuildWatcher.reconcileRunsAndBuilds(BuildWatcher.java:494) at io.fabric8.jenkins.openshiftsync.BuildWatcher.access$100(BuildWatcher.java:65) at io.fabric8.jenkins.openshiftsync.BuildWatcher$1.doRun(BuildWatcher.java:148) at
[JIRA] (JENKINS-58286) JaCoCo plugin fails while adding the parameter buildOverBuild
Title: Message Title Ariel M commented on JENKINS-58286 Re: JaCoCo plugin fails while adding the parameter buildOverBuild Tnx Do you know if this functionality supported in version 2.20 or only on the latest version (3.0.4)? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200350.1561992468000.13321.1562004720128%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58286) JaCoCo plugin fails while adding the parameter buildOverBuild
Title: Message Title
Ariel M created an issue
Jenkins / JENKINS-58286
JaCoCo plugin fails while adding the parameter buildOverBuild
Issue Type:
Bug
Assignee:
Victor Martinez
Components:
jenkinslint-plugin
Created:
2019-07-01 14:47
Priority:
Critical
Reporter:
Ariel M
I'm trying to add 2 optional parameters to JaCoCo per the below documentation: https://jenkins.io/doc/pipeline/steps/jacoco/ The parameters are: publishers { jacocoCodeCoverage { buildOverBuild(jacocoChangeBuildStatus) classPattern(jacocoClassPattern) exclusionPattern(jacocoExclusionPattern) execPattern('*/*.exec') maximumBranchCoverage('0') maximumClassCoverage('0') maximumComplexityCoverage('0') maximumInstructionCoverage('0') maximumLineCoverage('0') maximumMethodCoverage('0') minimumBranchCoverage('0') minimumClassCoverage('0') minimumComplexityCoverage('0') minimumInstructionCoverage('0') minimumLineCoverage('0') minimumMethodCoverage('0') deltaLineCoverage('10') sourcePattern(jacocoSourcePattern) } } The error I'm getting from the log: ERROR: (GenericSnapshotBuildTst.groovy, line 506) No signature of method: javaposse.jobdsl.dsl.helpers.publisher.JacocoContext.buildOverBuild() is applicable for argument types: (java.lang.Boolean) values: [true] 506 is exactly the line of buildOverBuild. The plugin version is: 2.20
[JIRA] (JENKINS-58179) Some builds disappeared in jenkins history (also not exists in disk)
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-58179 Some builds disappeared in jenkins history (also not exists in disk) Change By: Ariel M I have an issue in specific Jenkins (version 2.138.1), where some version disappeared in Jenkins history. I've checked in the disk, and it's missing there as well. how can I investigate what happened? The difference between this case to the others is here I can't understand why build were deleted from the Unix machine. does it have anything with Jenkins configuration? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200230.1561449713000.7854.1561450800159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58179) Some builds disappeared in jenkins history (also not exists in disk)
Title: Message Title Ariel M created an issue Jenkins / JENKINS-58179 Some builds disappeared in jenkins history (also not exists in disk) Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-06-25 08:01 Priority: Critical Reporter: Ariel M I have an issue in specific Jenkins (version 2.138.1), where some version disappeared in Jenkins history. I've checked in the disk, and it's missing there as well. how can I investigate what happened? Add Comment This message was sent by
