[JIRA] (JENKINS-47283) Allow for different HTTP & SSH endpoint URIs
Title: Message Title Richard Bywater commented on JENKINS-47283 Re: Allow for different HTTP & SSH endpoint URIs rsandell - Wondering if you are still the maintainer for this plugin as per the plugin info? If so wondering if you can take a look at https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/115 which appears to be related to this issue. Would be to good to get this released soon as it would make life much easier for this use case 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-39952) "Registry credentials" is not working with a private docker registry
Title: Message Title Rehab Hassanein commented on JENKINS-39952 Re: "Registry credentials" is not working with a private docker registry I went on for hours in circles just to fix this at the end by adding an execute shell step to do the following: mv ~/.dockercfg ~/.dockercfg.old This fixed my issue. Thanks Ryan Currah for pointing out the exact issue with this file. 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-49455) Scroll up during input step causes Proceed not to respond in Blue Ocean
Title: Message Title Nicolae Pascu started work on JENKINS-49455 Change By: Nicolae Pascu 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-50560) add some docs to the readme on what kinds of Secrets are supported
Title: Message Title James Strachan created an issue Jenkins / JENKINS-50560 add some docs to the readme on what kinds of Secrets are supported Issue Type: Task Assignee: James Nord Components: kubernetes-credentials-provider-plugin Created: 2018-04-04 04:51 Priority: Minor Reporter: James Strachan would be nice to hack the README.md to describe the Secrets supported. I've hacked a wiki page https://wiki.jenkins.io/display/JENKINS/Kubernetes+Credentials+Provider+Plugin Add Comment This
[JIRA] (JENKINS-45251) User Input text doesn't be formatted in Blue Ocean
Title: Message Title Nicolae Pascu updated JENKINS-45251 Jenkins / JENKINS-45251 User Input text doesn't be formatted in Blue Ocean Change By: Nicolae Pascu 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-50559) Authorization Folder property for Multibranch jobs
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-50559 Authorization Folder property for Multibranch jobs Issue Type: New Feature Assignee: Unassigned Components: authorize-project-plugin, workflow-multibranch-plugin Created: 2018-04-04 03:36 Labels: permissions authorization Priority: Major Reporter: Allan BURDAJEWICZ Request I would like to set up Authorization (Authorize Project plugin) for a Multibranch item. Setting up authorization at multibranch level is required to prevent branch projects to be able to build ANY project in the system. Workaround A workaround is to set the Authorize project property from the Jenkinsfile but there is no special support for multibranch projects. Add Comment
[JIRA] (JENKINS-50557) GCR Credentials Plugin does not work
Title: Message Title Joseph Hughes created an issue Jenkins / JENKINS-50557 GCR Credentials Plugin does not work Issue Type: Bug Assignee: Wei Z Components: google-container-registry-auth-plugin Created: 2018-04-04 03:34 Environment: Jenkins ver. 2.109 Labels: docker Priority: Blocker Reporter: Joseph Hughes All builds trying to use this plugin result in the following... ERROR: Could not find credentials matching gcr:SOMEPROJECT hudson.AbortException: Could not find credentials matching gcr:plasma-column-128721 at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.newKeyMaterialFactory(DockerRegistryEndpoint.java:217) at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.newKeyMaterialFactory(DockerRegistryEndpoint.java:204) at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.newKeyMaterialFactory(DockerRegistryEndpoint.java:196) at com.cloudbees.dockerpublish.DockerBuilder$Perform.executeCmd(DockerBuilder.java:455) at com.cloudbees.dockerpublish.DockerBuilder$Perform.executeCmd(DockerBuilder.java:431) at com.cloudbees.dockerpublish.DockerBuilder$Perform.buildAndTag(DockerBuilder.java:373) at com.cloudbees.dockerpublish.DockerBuilder$Perform.exec(DockerBuilder.java:311) at com.cloudbees.dockerpublish.DockerBuilder$Perform.access$100(DockerBuilder.java:291) at
[JIRA] (JENKINS-50558) Valgrind plugin results error
Title: Message Title Marshall Galbraith created an issue Jenkins / JENKINS-50558 Valgrind plugin results error Issue Type: Bug Assignee: Johannes Ohlemacher Components: valgrind-plugin Created: 2018-04-04 03:34 Environment: jenkins 2.107.1 valgrind-plugin 0.28 Priority: Blocker Reporter: Marshall Galbraith Valgrind report pages have stopped working as of today. I recently installed the latest pipeline plugin upgrads, but I don't know if that is related. The valgrind xml files appear to be processes without warnings or errors in the console log. I get the following "Ooops" page when trying to view results: org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/plugins/valgrind/WEB-INF/lib/valgrind.jar!/org/jenkinsci/plugins/valgrind/ValgrindResult/index.jelly:13:57: No page found 'sidepanel.jelly' for class org.jenkinsci.plugins.valgrind.ValgrindResult at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:124) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at
[JIRA] (JENKINS-43016) BlueOcean editor: does not allow empty string for label on agent or node
Title: Message Title Nicolae Pascu commented on JENKINS-43016 Re: BlueOcean editor: does not allow empty string for label on agent or node I understand your reasoning but in the front-end a required field means it should not be empty e.g. "". I suggest we either leave things as they are now or if we want an empty string to be a valid value in BO then I suggest we change the isRequired to false. Vivek Pandey what do you 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-50410) Periods of high load cause "Invalid virtual machine image" exceptions
Title: Message Title Chenyang Liu commented on JENKINS-50410 Re: Periods of high load cause "Invalid virtual machine image" exceptions From Azure Docs "For each subscription and tenant, Resource Manager limits read requests to 15,000 per hour and write requests to 1,200 per hour. " You said high usage, so how many VMs do you provision in one hour. And if the frequency is really high so that hit the limit, we seems nothing can do to solve 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-49473) Unable to delete Azure VM Agent from Jenkins after having deleted agent directly on Azure
Title: Message Title Chenyang Liu commented on JENKINS-49473 Re: Unable to delete Azure VM Agent from Jenkins after having deleted agent directly on Azure Do you means you can't even delete the vm manually or can't be deleted by plugin automatically? 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-50410) Periods of high load cause "Invalid virtual machine image" exceptions
Title: Message Title Azure DevOps assigned an issue to Chenyang Liu Jenkins / JENKINS-50410 Periods of high load cause "Invalid virtual machine image" exceptions Change By: Azure DevOps Assignee: Azure DevOps 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-50403) Single agent limit allows for an inadvertent denial-of-services
Title: Message Title Azure DevOps assigned an issue to Chenyang Liu Jenkins / JENKINS-50403 Single agent limit allows for an inadvertent denial-of-services Change By: Azure DevOps Assignee: Azure DevOps 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-48049) Ability to use the Snippet Generator
Title: Message Title Allan BURDAJEWICZ updated JENKINS-48049 Jenkins / JENKINS-48049 Ability to use the Snippet Generator Change By: Allan BURDAJEWICZ 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-50162) NUnit test results don't encode characters correctly in unit test report
Title: Message Title Alex Earl commented on JENKINS-50162 Re: NUnit test results don't encode characters correctly in unit test report The reason the invalid xml stream was added was for the case of broken xml files. The plugin used to just break completely, this was a way to continue parsing if possible. I agree it is not the best solution, but the upper xml parsers and so forth didn't handle the issues that were run into. 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-50556) git polling succeeds even when origin/master has nothing new
Title: Message Title Jacob Keller edited a comment on JENKINS-50556 Re: git polling succeeds even when origin/master has nothing new It looks like this is performing polling in the workspace, so it happens that the workspace has master checked out at the older commit. I'm still unsure exactly why *that* happens, but some of the repositories appear to never actually check the branch out, so the revParse fails, while others do have it checked out. It looks like the workspace was requiring polling due to an extension. Removing the extension appears to have allowed it to work, but we now don't actually appear to check any of the extra repositories... 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-50556) git polling succeeds even when origin/master has nothing new
Title: Message Title Jacob Keller commented on JENKINS-50556 Re: git polling succeeds even when origin/master has nothing new It looks like this is performing polling in the workspace, so it happens that the workspace has master checked out at the older commit. I'm still unsure exactly why that happens, but some of the repositories appear to never actually check the branch out, so the revParse fails, while others do have it checked out. It looks like the workspace was requiring polling due to an extension. Removing the extension appears to have allowed it to work, but we now don't actually appear to check any of the extra repositories... 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Michael Neale commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Oleg Nenashev very true - I think Vivek Pandey was going to open a follow on ticket to fix up the JIRA plugin itself as a next step (inline the Atlassian stuff to not have that problem) - but this could be the ticket for that, given it doesn't explicitly mention blue ocean. 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-50379) Jenkins kills long running sh script with no output
Title: Message Title
Lee Webb commented on JENKINS-50379
Re: Jenkins kills long running sh script with no output
Travis does this sort of thing too, if there's no output for a while it just assumes the process is hung then stops the build. If you don't want to mess with Jenkins something like the following shell snippet can help. It forks your long running process & echo's dots to the console as long as it's still running:
# suppress command output unless there is a failure
function quiet() {
if [[ $- =~ x ]]; then set +x; XTRACE=1; fi
if [[ $- =~ e ]]; then set +e; ERREXIT=1; fi
tmp=$(mktemp) || return # this will be the temp file w/ the output
echo -ne "quiet running: ${@} "
ts_elapsed=0
ts_start=$(date +%s)
"${@}" > "${tmp}" 2>&1 &
cmd_pid=$!
while [ 1 ]; do
if [ `uname` == 'Linux' ]; then
ps -q ${cmd_pid} > /dev/null 2>&1
running=${?}
else
ps -ef ${cmd_pid} > /dev/null 2>&1
running=${?}
fi
if [ "${running}" -eq 0 ]; then
echo -ne '.'
sleep 3
continue
fi
break
done
wait ${cmd_pid}
ret=${?}
ts_end=$(date +%s)
let "ts_elapsed = ${ts_end} - ${ts_start}"
if [ "${ret}" -eq 0 ]; then
echo -ne " finished with code ${ret} in ${ts_elapsed} secs, last lines were:\n"
tail -n 4 "${tmp}"
else
cat "${tmp}"
fi
rm -f "${tmp}"
if [ "${ERREXIT}" ]; then unset ERREXIT; set -e; fi
if [ "${XTRACE}" ]; then unset XTRACE; set -x; fi
return "${ret}" # return the exit status of the command
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50162) NUnit test results don't encode characters correctly in unit test report
Title: Message Title
Shin-ichi Morita edited a comment on JENKINS-50162
Re: NUnit test results don't encode characters correctly in unit test report
Hi team, thank you for the valuable plugin.InvalidXmlInputStream.isValid seems to assume the input is a decoded character, but it is an encoded byte with the widening primitive conversion.According to [https://docs.oracle.com/javase/tutorial/java/nutsandbolts/datatypes.html]> The {{byte}} data type is an 8-bit *signed* two's complement integer. It has a minimum value of -128 and a maximum value of 127 (inclusive).Therefore, all the non-ascii bytes are converted to *negative* ints with the widening primitive conversion, and will be treated as invalid.In addition to that, I think InputStream cannot assume any character encoding.Character encoding should be handled by the above upper layers like XML parsers, TextReaders, although I don't know what mechanism Transformers use internally.Regards,
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-50556) git polling succeeds even when origin/master has nothing new
Title: Message Title Jacob Keller created an issue Jenkins / JENKINS-50556 git polling succeeds even when origin/master has nothing new Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2018-04-03 23:36 Priority: Minor Reporter: Jacob Keller I have a repository which is setup to perform git polling, and it always triggers, suggesting there are changes, even though there are not. In this case, the job has multiple checkouts using a pipeline, but I think it would only happen in the case of a single checkout as well. Specifically, the branch name is master, and it checks first all the "remote/branch" combinations, (in this case, "origin/master") and then fails to find anything new (as origin/master was already built). Then, it checks the branch name on its own, thinking that maybe it's a tag or some other ref. This results in reporting a separate commit (likely whatever master happens to be at when the polling was created), and thus reports a new commit to build. This causes the build to trigger every polling timeout, even though there aren't any real new changes. Here's a subset of the actual output with repository names and paths redacted. I have the VERBOSE logging enabled for more information. Started on Apr 3, 2018 4:01:00 PM Using strategy: Default [poll] Last Built Revision: Revision 72c4cea985bb5ff14813d27dac94f34887cbd841 (refs/remotes/origin/master) using GIT_SSH to set credentials > git ls-remote -h # timeout=10 Found 1 remote heads on [poll] Latest remote head revision on refs/heads/master is: 72c4cea985bb5ff14813d27dac94f34887cbd841 - already built by 1738 Using strategy: Default [poll] Last Built Revision: Revision cc24044526e9d460c74a59fcdeb12e43a446cb7d (origin/master) > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repositories > git config remote.origin.url # timeout=10
[JIRA] (JENKINS-50555) BlueOcean Pipeline View - Add build time information
Title: Message Title alan foster updated an issue Jenkins / JENKINS-50555 BlueOcean Pipeline View - Add build time information Change By: alan foster Within the BlueOcean Pipeline View the blue time information could be added to the graphs nodes to clearly highlight to a developer the slowest part of their CI pipeline.I have attached a mock-up of what this may look like :!example . png|width=726,height=464! We may be worried about cluttering the pipeline view with too many visuals, however the final missing component may just be the build information. If there is additional information that would be useful to add, we could potentially optimise the UX for that additional data, but for now I think the time spent on each stage would be useful. 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
[JIRA] (JENKINS-50555) BlueOcean Pipeline View - Add build time information
Title: Message Title alan foster created an issue Jenkins / JENKINS-50555 BlueOcean Pipeline View - Add build time information Issue Type: Improvement Assignee: Unassigned Attachments: example.png Components: blueocean-plugin Created: 2018-04-03 23:20 Priority: Minor Reporter: alan foster Within the BlueOcean Pipeline View the blue time information could be added to the graphs nodes to clearly highlight to a developer the slowest part of their CI pipeline. I have attached a mock-up of what this may look like. We may be worried about cluttering the pipeline view with too many visuals, however the final missing component may just be the build information. If there is additional information that would be useful to add, we could potentially optimise the UX for that additional data, but for now I think the time spent on each stage would be useful. Add Comment
[JIRA] (JENKINS-49795) Bad serialization of ParametersAction.parameterDefinitionNames
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-49795 Bad serialization of ParametersAction.parameterDefinitionNames Change By: Daniel Beck Labels: lts 2.107.2 - candidate fixed serialization xstream 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Mike Kozell commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume I have a dedicated test Jenkins master I can use for testing. I will just need to know where I can get the build and how to enable 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-50470) Cannot evaluate ArrayList.name inside Groovy Sandbox
Title: Message Title Jesse Glick commented on JENKINS-50470 Re: Cannot evaluate ArrayList.name inside Groovy Sandbox Would never have dreamed that this would be legal Groovy. Ugh. 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Sam Van Oort commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Piotr Paczyński Mike Kozell Would you by any chance be set up with a non-critical / test master and interested in trying out some SNAPSHOT builds of the proposed fixes? I think what we have now is more or less ready to go and would love to see how it plays for you guys in the wild. 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-49686) NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead
Title: Message Title Sam Van Oort updated JENKINS-49686 Jenkins / JENKINS-49686 NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead Change By: Sam Van Oort 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Sam Van Oort updated JENKINS-50199 Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Sam Van Oort 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Sam Van Oort started work on JENKINS-50199 Change By: Sam Van Oort 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-50407) NPE from SandboxContinuable.run0 after restart
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-50407 NPE from SandboxContinuable.run0 after restart Change By: Sam Van Oort Assignee: Sam Van Oort 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-50407) NPE from SandboxContinuable.run0 after restart
Title: Message Title Sam Van Oort started work on JENKINS-50407 Change By: Sam Van Oort 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-50407) NPE from SandboxContinuable.run0 after restart
Title: Message Title Sam Van Oort updated JENKINS-50407 Jenkins / JENKINS-50407 NPE from SandboxContinuable.run0 after restart Change By: Sam Van Oort 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-45585) WorkflowRun.onLoad need not eagerly load the FlowExecution of a completed build
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-45585 WorkflowRun.onLoad need not eagerly load the FlowExecution of a completed build Change By: Sam Van Oort Assignee: Sam Van Oort 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-45585) WorkflowRun.onLoad need not eagerly load the FlowExecution of a completed build
Title: Message Title Sam Van Oort started work on JENKINS-45585 Change By: Sam Van Oort 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-45585) WorkflowRun.onLoad need not eagerly load the FlowExecution of a completed build
Title: Message Title Sam Van Oort updated JENKINS-45585 Jenkins / JENKINS-45585 WorkflowRun.onLoad need not eagerly load the FlowExecution of a completed build Change By: Sam Van Oort 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-50407) NPE from SandboxContinuable.run0 after restart
Title: Message Title Jesse Glick commented on JENKINS-50407 Re: NPE from SandboxContinuable.run0 after restart In Review perhaps? 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-29150) CronTabTest is failing while building jenkins
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-29150 CronTabTest is failing while building jenkins Change By: Oleg Nenashev Assignee: 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-41565) "View Status" permission not assignable to a Global role (works in Matrix authorization)
Title: Message Title Oleg Nenashev commented on JENKINS-41565 Re: "View Status" permission not assignable to a Global role (works in Matrix authorization) Sorry, I managed to miss notification for this issue somehow. There is likely an issue with permission group processing in the core or in the Role Strategy plugin. I have never seen this permission in UIs, so it's hard to say for sure. But it should be easily reproducible. 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-49573) Matrix Configuration Parameter Plugin is affected by JEP-200
Title: Message Title Oleg Nenashev commented on JENKINS-49573 Re: Matrix Configuration Parameter Plugin is affected by JEP-200 The patch in the core has been backported to 2.107.2. Jesse Glick for the future it would be better to create separate issues to simplify the backporting process 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-49573) Matrix Configuration Parameter Plugin is affected by JEP-200
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49573 Matrix Configuration Parameter Plugin is affected by JEP-200 Change By: Oleg Nenashev Labels: 2.107.2-fixed JEP-200 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-49404) A way to force some settings on all jobs in the instance
Title: Message Title Javier Raez commented on JENKINS-49404 Re: A way to force some settings on all jobs in the instance I don't have tested. Oleg Nenashev. I'll give it a try. Thanks for the suggestion. 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-42909) OwnershipPlugin#resolveEmail() does not catch ClassCastException
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-42909 OwnershipPlugin#resolveEmail() does not catch ClassCastException Change By: Oleg Nenashev Assignee: 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-42909) OwnershipPlugin#resolveEmail() does not catch ClassCastException
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-42909 OwnershipPlugin#resolveEmail() does not catch ClassCastException Change By: Oleg Nenashev Labels: newbie-friendly 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-26465) Split JNLP slaves from core
Title: Message Title Oleg Nenashev commented on JENKINS-26465 Re: Split JNLP slaves from core No plan to work on it anytime soon. I am unassigning myself so that others could pick 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-26465) Split JNLP slaves from core
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-26465 Split JNLP slaves from core Change By: Oleg Nenashev Assignee: 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-41519) Post stages should have well defined order
Title: Message Title Eric Nelson commented on JENKINS-41519 Re: Post stages should have well defined order Andrew Bayer +1 for cleanup here as well. Solves the issue in most use cases I had in mind. Thanks! 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-47572) Custom Jenkins dashboard creation
Title: Message Title Oleg Nenashev resolved as Not A Defect Jenkins / JENKINS-47572 Custom Jenkins dashboard creation Change By: Oleg Nenashev Status: Open Resolved 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-47572) Custom Jenkins dashboard creation
Title: Message Title Oleg Nenashev commented on JENKINS-47572 Re: Custom Jenkins dashboard creation Please ask in the user or developer mailing list. It is a bugtracker, not a support site 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-50322) Option to select quality gate status to fail the build
Title: Message Title Marcos Nunes commented on JENKINS-50322 Re: Option to select quality gate status to fail the build Hi, I have version 1.3.0, but I do not find this option to fail the job only when the sonar status is Failed and not warning. Here is the print of configuration screen: 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-50322) Option to select quality gate status to fail the build
Title: Message Title Marcos Nunes updated an issue Jenkins / JENKINS-50322 Option to select quality gate status to fail the build Change By: Marcos Nunes Attachment: sonar-gates.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-50322) Option to select quality gate status to fail the build
Title: Message Title Marcos Nunes updated an issue Jenkins / JENKINS-50322 Option to select quality gate status to fail the build Change By: Marcos Nunes Attachment: sonar-gates.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-49029) Jenkins going down abruptly almost every day once
Title: Message Title Oleg Nenashev resolved as Incomplete No response from the reporter Jenkins / JENKINS-49029 Jenkins going down abruptly almost every day once Change By: Oleg Nenashev Status: Open Resolved Resolution: Incomplete 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-49361) I am not able to see any plugins under Manage plugins..and also getting below error while trying to install new plugins.
Title: Message Title Oleg Nenashev commented on JENKINS-49361 Re: I am not able to see any plugins under Manage plugins..and also getting below error while trying to install new plugins. Durgarao Paila has it been fixed on your side? 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-50322) Option to select quality gate status to fail the build
Title: Message Title Marcos Nunes updated an issue Jenkins / JENKINS-50322 Option to select quality gate status to fail the build Change By: Marcos Nunes Attachment: sonar-gates.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-49404) A way to force some settings on all jobs in the instance
Title: Message Title Oleg Nenashev commented on JENKINS-49404 Re: A way to force some settings on all jobs in the instance Javier Raez ping 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-49667) Swarm plugin should print to log if job fails because of full disk
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49667 Swarm plugin should print to log if job fails because of full disk Change By: Oleg Nenashev Component/s: _unsorted 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-50040) This Jenkins appears to have crashed", generating nullPointerException
Title: Message Title Oleg Nenashev commented on JENKINS-50040 Re: This Jenkins appears to have crashed", generating nullPointerException Meghali Dhoble any updates? 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-50136) Not able to get plugins
Title: Message Title Oleg Nenashev resolved as Incomplete No response from the reporter, there is not enough info to triage the issue Jenkins / JENKINS-50136 Not able to get plugins Change By: Oleg Nenashev Status: Open Resolved Resolution: Incomplete 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
[JIRA] (JENKINS-50234) jenkins showing oops
Title: Message Title Oleg Nenashev resolved as Duplicate No response from the reporter. Taking the evidence, closing as a duplicate of JENKINS-49258 Jenkins / JENKINS-50234 jenkins showing oops Change By: Oleg Nenashev 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" 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
[JIRA] (JENKINS-50383) iOS fastline build failed
Title: Message Title Oleg Nenashev resolved as Incomplete No response from the reporter. gang li please feel free to reopen the issue once you are ready to provide the requested info Jenkins / JENKINS-50383 iOS fastline build failed Change By: Oleg Nenashev Status: Open Resolved Resolution: Incomplete 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
[JIRA] (JENKINS-50546) Jenkins to connect a Mysql DB
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50546 Jenkins to connect a Mysql DB Change By: Oleg Nenashev Priority: Critical Minor 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-50546) Jenkins to connect a Mysql DB
Title: Message Title Oleg Nenashev commented on JENKINS-50546 Re: Jenkins to connect a Mysql DB I am not working on this, I have been just automatically assigned since the component is "_unsorted". There are Database plugins for Jenkins, e.g. https://wiki.jenkins.io/display/JENKINS/MySQL+Database+Plugin I do not understand what is exactly your need, so I cannot say whether this plugin is enough. Anyway, please ask questions in User mailing lists, this is a bugtracker. More info: https://wiki.jenkins.io/display/JENKINS/How+to+report+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-50274) Jenkins server is using more than 100% CPU utilization
Title: Message Title Oleg Nenashev resolved as Won't Do Closing it for now. If you see the issue after the upgrade, please reopen and update the information Jenkins / JENKINS-50274 Jenkins server is using more than 100% CPU utilization Change By: Oleg Nenashev Status: Open Resolved Resolution: Won't Do 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
[JIRA] (JENKINS-50475) Scope import dependencies
Title: Message Title Cyrille Le Clerc started work on JENKINS-50475 Change By: Cyrille Le Clerc 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-50494) Ensure registration is persisted to the database
Title: Message Title R. Tyler Croy started work on JENKINS-50494 Change By: R. Tyler Croy 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-44993) Post-Step should have "try-finally" semantics
Title: Message Title Andrew Bayer commented on JENKINS-44993 Re: Post-Step should have "try-finally" semantics Got it! The problem here is that we only end up throwing one exception per stage - because once we throw an exception, we're out of the stage. So if your stage has already failed before you get to post, any exception thrown by a post block never gets thrown further, because we propagate the initial exception instead. This means that the post block exception never gets logged, etc. I don't love this fix, but https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/259 - with this, we'll always log when we get an exception from a post block, with full stacktrace. I'm open to changing the exact details of what we log there, but we do still want to make sure that we're throwing the first exception encountered, so that visualization can tell where the build "failed" per se. This can lead to duplicate logging if the first error of the stage is from a post block, though, which I'm not happy about. 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-44993) Post-Step should have "try-finally" semantics
Title: Message Title Andrew Bayer started work on JENKINS-44993 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-44993) Post-Step should have "try-finally" semantics
Title: Message Title Andrew Bayer updated JENKINS-44993 Jenkins / JENKINS-44993 Post-Step should have "try-finally" semantics 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-41519) Post stages should have well defined order
Title: Message Title Stefan Thurnherr commented on JENKINS-41519 Re: Post stages should have well defined order Andrew Bayer +1 for the cleanup condition, would solve this issue for us since we mostly want to delete workspace 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Oleg Nenashev edited a comment on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API [~vivek] [~michaelneale] exclusion from BlueOcean does not fix the this issue (binary compat between JIRA Plugin and Apache HttpComponents 4 . x client). Yes it fixes BlueOcean on instances without JIRA plugin, but all users who have JIRA plugin are still affected. Independently from BlueOcean... 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Oleg Nenashev reopened an issue Vivek Pandey Michael Neale exclusion from BlueOcean does not fix the issue. Yes it fixes BlueOcean on instances without JIRA plugin, but all users who have JIRA plugin are still affected. Independently from BlueOcean... Jenkins / JENKINS-48357 Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Change By: Oleg Nenashev Resolution: Fixed Status: Resolved Reopened 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
[JIRA] (JENKINS-41519) Post stages should have well defined order
Title: Message Title Andrew Bayer commented on JENKINS-41519 Re: Post stages should have well defined order I think I have something that may help with this over in a PR for JENKINS-41239 - a new post condition, currently called cleanup (because I couldn't call it finally due to that being a reserved word in Groovy), which is like always (as in it'll run regardless of build status), but it runs after all other post conditions. So with this, always is the first post condition to run, and cleanup is the last, regardless of build status. So you can do things like deleteDir() etc in cleanup without problems. Does that sound like it'd do the trick here? 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-41239) Error during always block skips execution of remaining steps
Title: Message Title Andrew Bayer commented on JENKINS-41239 Re: Error during always block skips execution of remaining steps I've got a PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/258 that adds a new post condition, currently called cleanup, which runs regardless of build status but after all the other conditions have resolved. 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-41239) Error during always block skips execution of remaining steps
Title: Message Title Andrew Bayer started work on JENKINS-41239 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-41239) Error during always block skips execution of remaining steps
Title: Message Title Andrew Bayer updated JENKINS-41239 Jenkins / JENKINS-41239 Error during always block skips execution of remaining steps 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-50237) [JEP-200] java.lang.SecurityException: Rejected: org.apache.tools.ant.Location
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-50237 [JEP-200] java.lang.SecurityException: Rejected: org.apache.tools.ant.Location Change By: Daniel Beck Labels: 2.107.2-fixed JEP-200 lts-candidate regression 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-49737) Extras Executable WAR should warn everybody that Java 9 is not supported
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-49737 Extras Executable WAR should warn everybody that Java 9 is not supported Change By: Daniel Beck Labels: lts 2.107.2 - candidate fixed newbie-friendly 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-50177) Add Mercurial (hg) to the list of supported branchSources for multibranchPipelineJob
Title: Message Title Long Vu reopened an issue Hi Daniel Spilker, tried what you suggested and got this error ERROR: (Script1.groovy, line 7) No signature of method: javaposse.jobdsl.dsl.helpers.workflow.BranchSourcesContext.source() is applicable for argument types: (Script1$_run_closure1$_closure2$_closure3$_closure5) values: [Script1$_run_closure1$_closure2$_closure3$_closure5@661dccdc] Also, when looking at the source here https://github.com/jenkinsci/job-dsl-plugin/blob/ae6084c/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/workflow/BranchSourcesContext.groovy I do not see BranchSourcesContext supporting mercurial. But I do see it supports git and github, like the Job DSL API. Reopening the issue. Jenkins / JENKINS-50177 Add Mercurial (hg) to the list of supported branchSources for multibranchPipelineJob Change By: Long Vu Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49553) Parametrized publishing can no longer be configured
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49553 Re: Parametrized publishing can no longer be configured Code changed in jenkins User: Alex Earl Path: src/main/java/jenkins/plugins/publish_over/ParamPublish.java http://jenkins-ci.org/commit/publish-over-plugin/ce68dcdfb51a20d2ffc98ffa81adb5506730e317 Log: Fix JENKINS-49553 Add @DataBoundConstructor 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-50518) Use presigned URLs for upload
Title: Message Title Carlos Sanchez commented on JENKINS-50518 Re: Use presigned URLs for upload In review at https://github.com/jenkinsci/artifact-manager-s3-plugin/pull/4 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-50518) Use presigned URLs for upload
Title: Message Title Carlos Sanchez started work on JENKINS-50518 Change By: Carlos Sanchez 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-50518) Use presigned URLs for upload
Title: Message Title Carlos Sanchez updated JENKINS-50518 Jenkins / JENKINS-50518 Use presigned URLs for upload Change By: Carlos Sanchez 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-50518) Use presigned URLs for upload
Title: Message Title Carlos Sanchez assigned an issue to Carlos Sanchez Jenkins / JENKINS-50518 Use presigned URLs for upload Change By: Carlos Sanchez Assignee: Carlos Sanchez 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-49553) Parametrized publishing can no longer be configured
Title: Message Title Alex Earl commented on JENKINS-49553 Re: Parametrized publishing can no longer be configured I'll try and roll out a fixed version for this soon. I'll need to cherry pick some other edits so I don't break things completely. 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-50177) Add Mercurial (hg) to the list of supported branchSources for multibranchPipelineJob
Title: Message Title Long Vu commented on JENKINS-50177 Re: Add Mercurial (hg) to the list of supported branchSources for multibranchPipelineJob Hi Daniel Spilker then the Job DSL API https://jenkinsci.github.io/job-dsl-plugin/#path/multibranchPipelineJob-branchSources is out of date because it only lists git and github there. Thanks, will try that mercurial branch source now and report back. 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-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title
Simon Wydooghe commented on JENKINS-50525
Re: Error When Provisioning Slave: mountPath: Required value
WARNING: Error in provisioning; agent=KubernetesSlave name: jenkins-agent-github-drupal8-site-cms-nieuws-master-59-5b-cdvjx, template=PodTemplate{, name='jenkins-agent-github-drupal8-site-cms-nieuws-master-59-5bjkm', namespace='ops-prod', label='8a6f6637-d8e3-48e6-9c18-8a1f7082675d', serviceAccount='jenkins', nodeSelector='cloud.google.com/gke-preemptible=true,cloud.google.com/gke-local-ssd=true', nodeUsageMode=EXCLUSIVE, volumes=[org.csanchez.jenkins.plugins.kubernetes.volumes.HostPathVolume@63b25977], containers=[ContainerTemplate{name='jnlp', image='medialaan/jenkins-jnlp-slave:3.16-1', alwaysPullImage=true, workingDir='/home/jenkins', args='${computer.jnlpmac} ${computer.name}'}, ContainerTemplate{name='composer', image='medialaan/composer:1.0.0', alwaysPullImage=true, workingDir='/home/jenkins', command='cat', ttyEnabled=true}, ContainerTemplate{name='bazel', image='eu.gcr.io/medialaan-production/bazel:0.1.0', alwaysPullImage=true, workingDir='/home/jenkins', command='cat', ttyEnabled=true}, ContainerTemplate{name='gcp', image='eu.gcr.io/medialaan-production/gcp:0.1.0', alwaysPullImage=true, workingDir='/home/jenkins', command='cat', ttyEnabled=true, envVars=[KeyValueEnvVar [getValue()=$PWD/.kube/config, getKey()=KUBECONFIG], KeyValueEnvVar [getValue()=$PWD/.config, getKey()=CLOUDSDK_CONFIG], KeyValueEnvVar [getValue()=$PWD/.helm, getKey()=HELM_HOME]]}]}
io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: https://kubernetes.default/api/v1/namespaces/ops-prod/pods. Message: Pod "jenkins-agent-github-drupal8-site-cms-nieuws-master-59-5b-cdvjx" is invalid: [spec.containers[0].volumeMounts[1].mountPath: Invalid value: "/home/jenkins": must be unique, spec.containers[1].volumeMounts[1].mountPath: Invalid value: "/home/jenkins": must be unique, spec.containers[2].volumeMounts[1].mountPath: Invalid value: "/home/jenkins": must be unique, spec.containers[3].volumeMounts[1].mountPath: Invalid value: "/home/jenkins": must be unique]. Received status: Status(apiVersion=v1, code=422, details=StatusDetails(causes=[StatusCause(field=spec.containers[0].volumeMounts[1].mountPath, message=Invalid value: "/home/jenkins": must be unique, reason=FieldValueInvalid, additionalProperties={}), StatusCause(field=spec.containers[1].volumeMounts[1].mountPath, message=Invalid value: "/home/jenkins": must be unique, reason=FieldValueInvalid, additionalProperties={}), StatusCause(field=spec.containers[2].volumeMounts[1].mountPath, message=Invalid value: "/home/jenkins": must be unique, reason=FieldValueInvalid, additionalProperties={}), StatusCause(field=spec.containers[3].volumeMounts[1].mountPath, message=Invalid value: "/home/jenkins": must be unique, reason=FieldValueInvalid, additionalProperties={})], group=null, kind=Pod, name=jenkins-agent-github-drupal8-site-cms-nieuws-master-59-5b-cdvjx, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=Pod "jenkins-agent-github-drupal8-site-cms-nieuws-master-59-5b-cdvjx" is invalid: [spec.containers[0].volumeMounts[1].mountPath: Invalid value: "/home/jenkins": must be unique, spec.containers[1].volumeMounts[1].mountPath: Invalid value: "/home/jenkins": must be unique, spec.containers[2].volumeMounts[1].mountPath: Invalid value: "/home/jenkins": must be unique, spec.containers[3].volumeMounts[1].mountPath: Invalid value: "/home/jenkins":
[JIRA] (JENKINS-50554) Cant expand to multi lines "warnings to ignore" field
Title: Message Title David Levy created an issue Jenkins / JENKINS-50554 Cant expand to multi lines "warnings to ignore" field Issue Type: Bug Assignee: Ulli Hafner Attachments: warnings.png Components: warnings-plugin Created: 2018-04-03 19:03 Environment: jenkins 2.107.1 warnings 4.66 Labels: warnings Priority: Minor Reporter: David Levy When configuring the post build step "scan for compiler warnings" from warnings plugin, its not possible to expand "warnings to include" and "warnings to ignore" to multi lines. It prevents the user from entering several regular _expression_ to filter warnings Add Comment
[JIRA] (JENKINS-43038) Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins
Title: Message Title Sam Van Oort edited a comment on JENKINS-43038 Re: Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins [~msavlani1] [~shahmishal] [~tsvi] If you update to the latest Pipeline plugins and *especially* support-core plugin and use the suggested GC settings (https://jenkins.io/blog/2016/11/21/gc-tuning/) you should find that the InterruptedExceptions are pretty much gone -- they are the result of timeouts in remoting-related operations generally. The only cases they should happen now I believe are actual hardware/system/network issues. In the last quarter of 2017 we did a big change to the way Pipeline's durable tasks interact with remoting that should avoid many of these issues. Explanation Edit : There was an additional issue fixed around support-core that caused problems and was recently fixed. Specifically, support-core plugin in version 2.42 added heap histogram analysis for diagnostics but this had the unexpected side effect of introducing periodic catastrophically long GC pauses that made the Jenkins master unresponsive for long periods and triggered timeouts (and thus the InterruptedException here when Timeouts kick in). Please see https://issues.jenkins-ci.org/browse/JENKINS-49931 for more details of that. For now I'm going to transition this to "closed" because when working with several users showing this among other symptoms, the suggestions above successfully resolved the issues -- but I'm happy to re-open this if you all still experience problems after applying the above (please reply to note the same). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-46653) Jenkins configure system save and apply buttons missing
Title: Message Title Marcelo Filho commented on JENKINS-46653 Re: Jenkins configure system save and apply buttons missing Rashed Amiri actually there is no standard way to workaround this once looks very random. The source of the problem is that somehow the XML of the credentials is changed and the XML format is broken but even after many plugins installation and uninstallation the source plugin or cause was not found. My advise is to save a backup copy of you configuration XML and apply it again when this problem appear. I will dive into it soon and let you know if I get any new result. 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-50551) Trend Graph: Suppress First, Reference Build
Title: Message Title tcdan updated an issue Jenkins / JENKINS-50551 Trend Graph: Suppress First, Reference Build Change By: tcdan Jenkins uses a trend graph to display things like failed unit tests or compilation warnings as a function of build number. Is there a way Recommend an option to suppress only the first build OR to limit the height of the y-axis ? . * My Potential workflow* - create a copy of a Jenkins job for your particular branch - Build the branch without changes. This gives a baseline for the # of warnings in the code (it has very old code, so there are a LOT) - The branch then automatically builds daily. New warnings introduced by the developer show up in the Trend Graph.The Trend Graph is configured to show only new or fixed warnings. The problem is that the 1st build introduces a ton of "new" warnings. This pushes the +Y-axis max value to >1000. Any warnings fixed/introduced after that are not visible. *Solution* If we could somehow suppress showing just that first build, while still showing all subsequent builds, this would be fixed. Alternatively, if the +Y-axis could be limited to show numbers from 0-100, this would be fixed. The first option may be easier to implement. For people who also want existing functionality, you could add a checkbox in "Configure the trend graph": +Option+: Suppress reference build +Description+: If set warnings for the reference build are not displayed as 'new' for the graph type 'Distribution of new and fixed warnings'. Or you could change the default and make the current behavior optional, which probably makes more sense: +Option+: Display reference build Add Comment
[JIRA] (JENKINS-50551) Trend Graph: Suppress First, Reference Build
Title: Message Title tcdan updated an issue Jenkins / JENKINS-50551 Trend Graph: Suppress First, Reference Build Change By: tcdan Jenkins uses a trend graph to display things like failed unit tests or compilation warnings as a function of build number. Is there a way to suppress only the first build OR to limit the height of the y-axis? *My workflow*- create a copy of a Jenkins job for your particular branch- Build the branch without changes. This gives a baseline for the # of warnings in the code (it has very old code, so there are a LOT)- The branch then automatically builds daily. New warnings introduced by the developer show up in the Trend Graph. The Trend Graph is configured to show only new or fixed warnings.The problem is that the 1st build introduces a ton of "new" warnings. This pushes the +Y-axis max value to >1000. Any warnings fixed/introduced after that are not visible. *Solution*If we could somehow suppress showing just that first build, while still showing all subsequent builds, this would be fixed. Alternatively, if the +Y-axis could be limited to show numbers from 0-100, this would be fixed. The first option may be easier to implement. For people also who want existing functionality, you could add a checkbox in "Configure the trend graph":+Option+: Suppress reference build+Description+: If set warnings for the reference build are not displayed as 'new' for the graph type 'Distribution of new and fixed warnings'. Or you could change the default and make the current behavior optional, which probably makes more sense:+Option+: Display reference build Add Comment
[JIRA] (JENKINS-50551) Trend Graph: Suppress First, Reference Build
Title: Message Title tcdan updated an issue Jenkins / JENKINS-50551 Trend Graph: Suppress First, Reference Build Change By: tcdan Jenkins uses a trend graph to display things like failed unit tests or compilation warnings as a function of build number. Is there a way to suppress only the first build OR to limit the height of the y-axis? *My workflow* - create a copy of a Jenkins job for your particular branch - Build the branch without changes. This gives a baseline for the # of warnings in the code (it has very old code, so there are a LOT) - The branch then automatically builds daily. New warnings introduced by the developer show up in the Trend Graph.The Trend Graph is configured to show only new or fixed warnings. The problem is that the 1st build introduces a ton of "new" warnings. This pushes the +Y-axis max value to >1000. Any warnings fixed/introduced after that are not visible.*Solution* If we could somehow suppress showing just that first build, while still showing all subsequent builds, this would be fixed. Alternatively, if the +Y-axis could be limited to show numbers from 0-100, this would be fixed. The first option may be easier to implement. For people also who also want existing functionality, you could add a checkbox in "Configure the trend graph": +Option+: Suppress reference build +Description+: If set warnings for the reference build are not displayed as 'new' for the graph type 'Distribution of new and fixed warnings'. Or you could change the default and make the current behavior optional, which probably makes more sense: +Option+: Display reference build Add Comment
[JIRA] (JENKINS-43038) Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-43038 Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins Change By: Sam Van Oort Assignee: Sam Van Oort 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-43038) Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins
Title: Message Title Sam Van Oort closed an issue as Fixed Manish Sawlani mishal shah Tsvi Mostovicz If you update to the latest Pipeline plugins and especially support-core plugin and use the suggested GC settings (https://jenkins.io/blog/2016/11/21/gc-tuning/) you should find that the InterruptedExceptions are pretty much gone – they are the result of timeouts in remoting-related operations generally. The only cases they should happen now I believe are actual hardware/system/network issues. In the last quarter of 2017 we did a big change to the way Pipeline's durable tasks interact with remoting that should avoid many of these issues. Explanation: support-core plugin in version 2.42 added heap histogram analysis for diagnostics but this had the side effect of introducing periodic catastrophically long GC pauses that made the Jenkins master unresponsive for long periods and triggered timeouts (and thus the InterruptedException here when Timeouts kick in). Please see https://issues.jenkins-ci.org/browse/JENKINS-49931 for more details of that. For now I'm going to transition this to "closed" because when working with several users showing this among other symptoms, the suggestions above successfully resolved the issues – but I'm happy to re-open this if you all still experience problems after applying the above (please reply to note the same). Jenkins / JENKINS-43038 Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins Change By: Sam Van Oort Status: Open Closed Resolution: Fixed Add Comment
[JIRA] (JENKINS-50552) Pipeline projects do not trigger libvirt VM snapshot reverts.
Title: Message Title Zeta Syanthis updated an issue Jenkins / JENKINS-50552 Pipeline projects do not trigger libvirt VM snapshot reverts. Change By: Zeta Syanthis Configuring a snapshot revert within the project via the "Use Snapshots" checkbox or via the "Revert Snapshot" and "Before Snapshot" options on the node configuration does not appear to do anything on pipeline projects. They run exactly as though those settings were completely ignored. 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-50552) Pipeline projects do not trigger libvirt VM snapshot reverts.
Title: Message Title Zeta Syanthis updated an issue Jenkins / JENKINS-50552 Pipeline projects do not trigger libvirt VM snapshot reverts. Change By: Zeta Syanthis Configuring a snapshot revert within the project via the "Use Snapshots" checkbox or via the "Revert Snapshot" and "Before Snapshot" options on the node configuration does not appear to do anything on pipeline projects. They run exactly as though those settings were completely ignored. 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-50552) Pipeline projects do not trigger libvirt VM snapshot reverts.
Title: Message Title Zeta Syanthis updated an issue Jenkins / JENKINS-50552 Pipeline projects do not trigger libvirt VM snapshot reverts. Change By: Zeta Syanthis Environment: Ubuntu 16.04.3 LTS 64 bit (running directly on the hardware)OpenJDK 1.8.0_151Jenkins 2.107.1Libvirt-plugin 1.8.5No proxy.Connection method: "Launch Slave Agents via SSH"Firefox 59.0.1 and Chrome 64.0.3282.167 Configuring a snapshot revert within the project via the "Use Snapshots" checkbox or via the "Revert Snapshot" and "Before Snapshot" options on the node configuration does not appear to do anything on pipeline projects. They run exactly as though those settings were completely ignored. Jenkins version: 2.107.1Libvirt-plugin version: 1.8.5Connection method: "Launch Slave Agents via SSH" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49135) Support for reusable sharing Declarative directives
Title: Message Title Tobias Larscheid commented on JENKINS-49135 Re: Support for reusable sharing Declarative directives woops, what a can of worms I opened here thanks for your detailed explanation, if anything I at least understood it's way more complex than I was hoping. If I find the time I will give the code a look, happy to year that you are not averse to the idea itself. Thank you! 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-50553) Unable to move issues to version
Title: Message Title Ariel Einfeld created an issue Jenkins / JENKINS-50553 Unable to move issues to version Issue Type: Bug Assignee: Unassigned Attachments: configurations.PNG Components: jira-issue-updater-plugin, jira-plugin Created: 2018-04-03 17:53 Priority: Blocker Reporter: Ariel Einfeld Hey, i am using JIRA plugin version 2.5.0 and i am able to login and create a version. however, i want to move issues matching the JQL Query to the version and its not working. i'm using Jenkins version 2.107.1 and the "JIRA: Moves issues matching JQK to the specified version" is at the post build actions and not at the build. when i search the JQL at JIRA level, i see results. the issue status is open. Add Comment
