[JIRA] (JENKINS-57351) Support for making Jenkins a "GitHub App"
Title: Message Title Andreas Sieferlinger commented on JENKINS-57351 Re: Support for making Jenkins a "GitHub App" The exact steps are described at https://developer.github.com/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app In terms of things that are needed for Jenkins: A new credential type (storing the private PEM key, App ID, ...) Authenticating as App and fetching Installation Tokens Checking the validity of the installation token and renew if required (they are only short lived) Using the installation token to Authorize (which is just setting the correct HTTP header for all calls to GitHub) (see https://developer.github.com/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation ) I'm not sure how exactly the authentication currently works in the context of this plugin. The change to use GitHub App tokens for other things i've worked on often wasn't too difficult. I could help with writing docs and testing of this. 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.199127.1557217283000.23110.1557467040159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57364) jenkins cannot provision new agent with openstack-cloud-plugin
Title: Message Title Oliver Gondža commented on JENKINS-57364 Re: jenkins cannot provision new agent with openstack-cloud-plugin Thanks for the report, though I am afraid the information are incomplete to diagnose the cause. Are the nodes provisioned based on demand in queue (IOW, when you do not provisioned manually)? Can you attach actual log file instead of the UI logger screenshot? Also, note the "provisioning started" is displayed even when there is a failure (https://github.com/jenkinsci/openstack-cloud-plugin/issues/254). 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.199144.155729319.23108.1557466320200%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Amir Barkal commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Liam Newman Not really sure how to reproduce this - can you post instructions? We’re using Multibranch pipeline repository with GitHub branch source configured to build PRs, branches and tags. 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.194753.1539776248000.23042.1557466141245%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57387) Openstack Auth credentials not properly working since openstack-cloud-plugin 2.46
Title: Message Title Oliver Gondža edited a comment on JENKINS-57387 Re: Openstack Auth credentials not properly working since openstack-cloud-plugin 2.46 This is a regression introduced in https://github.com/jenkinsci/openstack-cloud-plugin/issues/230, thanks for reporting it so promptly!Proposed fix: https://github.com/jenkinsci/openstack-cloud-plugin/ issues pull / 230 257EDIT: fix the PR link 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.199169.155740270.23038.1557464940111%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57171) Permissive script security plugin is broken after updating to script security 1.58
Title: Message Title Oliver Gondža commented on JENKINS-57171 Re: Permissive script security plugin is broken after updating to script security 1.58 Jeff Care, be more specific. The problem this issue addresses is that even when the signature is explicitly whitelisted, it is still reported/blocked (depending on your config). Is that signature whitelisted on your instance? How is the plugin configured? 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.198922.1556125514000.23025.1557464640324%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57171) Permissive script security plugin is broken after updating to script security 1.58
Title: Message Title Jeff Care commented on JENKINS-57171 Re: Permissive script security plugin is broken after updating to script security 1.58 We are still seeing Scripts not permitted to use staticMethod org.jenkinsci.plugins.workflow.cps.Safepoint safepoint. even after applying 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.198922.1556125514000.23013.1557464040460%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53179) Direct link to tests page in Blue Ocean
Title: Message Title Marcello de Sales commented on JENKINS-53179 Re: Direct link to tests page in Blue Ocean I have the same need and I tried the same! The UI shows the page "Tests" and "Artifacts"... Not consistent so far... 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.193200.1534904839000.23006.1557460080332%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36195) Pipeline polling ignores special polling rules
Title: Message Title Kyle Leinen edited a comment on JENKINS-36195 Re: Pipeline polling ignores special polling rules From reading the original ticket notes belong to along with the responses, I think this one is more in regard to alignment with special rules around a single repository and not multiple repos. 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.172167.1466697529000.22914.1557457261414%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36195) Pipeline polling ignores special polling rules
Title: Message Title Jackie Xiao commented on JENKINS-36195 Re: Pipeline polling ignores special polling rules For multibranch pipeline jobs, are there any workarounds for Subversion with the 'checkout' step (includedRegions/excludedRegions)? Something like: def scm = checkout scm: [ $class:'SubversionSCM', extensions: [ [$class: 'PathRestriction', excludedRegions: '', includedRegions: '.+\\.java'] ] ] 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.172167.1466697529000.22912.1557456542810%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57153) Allow building forks in addition to main repo and PRs
Title: Message Title Liam Newman commented on JENKINS-57153 Re: Allow building forks in addition to main repo and PRs Is not quite the same as building PRs. PR commits are ultimately found in the target branch's repo, whereas the fork branches are not. This can be done, however doing this well would require a good deal of design work to do well. 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.198902.155600774.22819.1557454380107%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57153) Allow building forks in addition to main repo and PRs
Title: Message Title Liam Newman edited a comment on JENKINS-57153 Re: Allow building forks in addition to main repo and PRs Is not quite the same as building PRs. PR commits are ultimately found in the target branch's repo, whereas the fork branches are not. This can be done, however doing this well would require a good deal of design work to do well . 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.198902.155600774.22821.1557454440109%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56996) null permission lookup when pull-request's origin repo/branch is deleted on github
Title: Message Title
Liam Newman edited a comment on JENKINS-56996
Re: null permission lookup when pull-request's origin repo/branch is deleted on github
Wow. I did 't some digging on this and it is not particularly easy.I'd love to be able to simply catch and swallow some error locally, but if we do that it may result in jobs being deleted (or marked for deletion) simply because there was an error while reading them. I looked pretty carefully and I didn't see a way to address this safely in a small/local change.The core problem is that the code that controls how child items are created and maintained is spread across several other plugins, including folders, scm-api and branch-api.My thought is that we'll need to add a no-op {{preserve(String itemName)}} method to {{[SCMHeadObserver|https://github.com/jenkinsci/scm-api-plugin/blob/6a044fe60143278ed26f8d91b0ec1cee116617d6/src/main/java/jenkins/scm/api/SCMHeadObserver.java#L43]}}. Then we can wire through an implementation in {{[MultiBranchProject.SCMHeadObserverImpl|https://github.com/jenkinsci/branch-api-plugin/blob/ed229d8e1392645c99e5686b8bd652a14ec87f4a/src/main/java/jenkins/branch/MultiBranchProject.java#L1948]}}. Finally, we'd expose that in github-branch-source for the {{GitHubSCMSource}} to call when an error occurs.I suppose it would okay for PRs specifically to simply be deleted on {{FileNotFoundException}} specifically, but not great behavior.
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.198693.1555102536000.22815.1557453720179%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17116) graceful job termination
Title: Message Title Owen Mehegan commented on JENKINS-17116 Re: graceful job termination Martin d'Anjou possibly a question for Jeff Thompson. 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.147946.136265659.22813.1557452281817%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17116) graceful job termination
Title: Message Title Owen Mehegan assigned an issue to Unassigned Jenkins / JENKINS-17116 graceful job termination Change By: Owen Mehegan Assignee: Robin Jarry 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.147946.136265659.22714.1557452101211%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56854) ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub
Title: Message Title Liam Newman edited a comment on JENKINS-56854 Re: ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub The way I understand it, is that non-fast-forward cases will always have a merge commit. The GIT_COMMIT will be the sha1 of that merge commit. If you want to test this, try this scenario on two different agents. In that case GIT_COMMIT will be different on each agent by-design. In older freestyle jobs GIT_COMMIT was equal to the head commit. If you want that to be the case again you can change the configuration of your pipeline to used the source branch head instead of merging. However, that also means you won't be testing the merged state. 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.198514.155421873.22711.1557448980086%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56854) ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub
Title: Message Title Liam Newman commented on JENKINS-56854 Re: ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub The way I understand it, is that non-fast-forward cases will always have a merge commit. The GIT_COMMIT will be the sha1 of that merge commit. If you want to test this, try this scenario on two different agents. In that case GIT_COMMIT will be different on each agent by-design. In older freestyle jobs GIT_COMMIT was equal to the head commit. If you want that to be the case again you can change the configuration of your pipeline to used the source branch head instead of merging. However, that also means you won't be testing the merged state. 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.198514.155421873.22709.1557448920092%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Liam Newman commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Josh Soref Okay, so to be clear this is still an experiment/exploration. The point of this exploration is to see if switching to using okhttp3 will address the FileNotFound issues. We're going to need more reports before we can release it. Ebrahim Moshaya, Amir Barkal, David Sanftenberg, Aleksey Smyrnov (and anyone else) Please give this version of the plug a try: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2.5.3-rc841.52a0b90bff37/ 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.194753.1539776248000.22643.1557448321287%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52005) catchError should give a visual hint in which stage the error occurred
Title: Message Title
Craig Rodrigues commented on JENKINS-52005
Re: catchError should give a visual hint in which stage the error occurred
I can reproduce this problem with this pipeline:
pipeline {
agent any
stages {
stage("Remove file which does not exist") {
steps {
catchError {
sh("rm /nonexistent")
}
}
}
stage("Hello!") {
steps {
sh("echo Hello1")
}
}
}
}
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.191506.1529326312000.22626.1557446880333%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52005) catchError should give a visual hint in which stage the error occurred
Title: Message Title Craig Rodrigues updated an issue Jenkins / JENKINS-52005 catchError should give a visual hint in which stage the error occurred Change By: Craig Rodrigues Attachment: bad_nodes.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.191506.1529326312000.22624.1557446880311%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41676) Support Kotlin scripts wherever Groovy scripts are offered
Title: Message Title trejkaz commented on JENKINS-41676 Re: Support Kotlin scripts wherever Groovy scripts are offered I was going to request the same thing after being burned by Groovy's lack of a decent type system too many times to count. I'd settle for a way to refactor stuff out into Java in some other way, but I'm guessing the only way to do this is by writing plugins? 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.178506.1486067616000.22632.1557447120358%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52005) catchError should give a visual hint in which stage the error occurred
Title: Message Title
Craig Rodrigues edited a comment on JENKINS-52005
Re: catchError should give a visual hint in which stage the error occurred
I can reproduce this problem with this pipeline:{noformat}pipeline {agent anystages {stage("Remove file which does not exist") {steps { catchError {sh("rm /nonexistent")}}}stage("Hello!") {steps {sh("echo Hello1")}}}}{noformat} !bad_nodes.png|thumbnail!The *Remove file which does not exist* node should be red, but it is green.
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.191506.1529326312000.22629.1557446940172%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Matthieu Brucher commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost I see this happening with github as well, so not just related to bitbucket. Could be indeed related to unauthorized user and then the branches get cleaned. 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.196298.154504211.22616.1557444360199%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37341) Add support of z/OS USS to sh step
Title: Message Title Anu George commented on JENKINS-37341 Re: Add support of z/OS USS to sh step I am curious, do we need all three plugins for this to work. I do have all, but just checking. thanks . I need to check whether IBM1047 is supported. 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.173437.1470921081000.22611.1557442080152%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57351) Support for making Jenkins a "GitHub App"
Title: Message Title Liam Newman commented on JENKINS-57351 Re: Support for making Jenkins a "GitHub App" Andreas Sieferlinger This sounds interesting. What would be involved in do this? 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.199127.1557217283000.22609.1557441660120%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57392) AWS API timeout
Title: Message Title Sean Zou commented on JENKINS-57392 Re: AWS API timeout Proposed fix: https://github.com/jenkinsci/ec2-plugin/pull/350 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.199174.1557437303000.22607.1557437760090%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50474) ArrayIndexOutOfBoundsException cause job "hang"
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-50474
Re: ArrayIndexOutOfBoundsException cause job "hang"
FWIW I ran into this trying to reproduce a totally different issue. The following (contrived) test in workflow-cps reproduces it somewhat consistently for me. Changing my {{nonBlocking}} step for a simpler block-scope step like {{timeout}} made the problem go away , so perhaps this only happens if the step execution is some kind of non-blocking execution that runs on a separate thread. {code}@Issue("JENKINS-56890") // The otherwise unrelated issue I was investigating.@Test public void generalNonBlockingStepExecutionCpsThreadSafety() {rr.then(r -> {WorkflowJob p = r.jenkins.createProject(WorkflowJob.class, "demo");p.setDefinition(new CpsFlowDefinition("Map branches = [failFast: false]\n" +"for (int i = 0; i < 250; i++) {\n" + // Increasing this value seems to make JENKINS-50474 more likely. " branches[\"branch${i}\"] = {\n" +"nonBlocking {\n" +" sleep(time: Math.random() * 100, unit: 'MILLISECONDS')\n" +"}\n" +" }\n" +"}\n" +"parallel(branches)\n", false));WorkflowRun b = r.buildAndAssertSuccess(p);});}/** * Step that uses {@link StepContext} in GeneralNonBlockingStepExecution.TailCall while not on the CPS VM thread * to demonstrate a concurrency issue in {@link CpsStepContext}. */public static class NonBlockingStep extends Step {@DataBoundConstructorpublic NonBlockingStep() { }@Overridepublic StepExecution start(StepContext context) throws Exception {return new Execution(context);}private static class Execution extends GeneralNonBlockingStepExecution {public Execution(StepContext context) {super(context);}@Overridepublic boolean start() throws Exception {run(() -> {getContext().newBodyInvoker().withCallback(new Callback()).start();});return false;}private final class Callback extends TailCall {@Overrideprotected void finished(StepContext context) throws Exception {Run run = context.get(Run.class);TaskListener listener = context.get(TaskListener.class);listener.getLogger().println("Finished executing nonBlockingStep in " + run);}}}@TestExtension("generalNonBlockingStepExecutionThreadSafety")public static class DescriptorImpl extends StepDescriptor {@Overridepublic String getFunctionName() {return "nonBlocking";}@Overridepublic boolean takesImplicitBlockArgument() {return true;}@Overridepublic Set> getRequiredContext() {return ImmutableSet.of(Run.class, TaskListener.class);}}}{code}In addition to the exception in the issue description I have also seen this one:{noformat}java.util.ConcurrentModificationExceptionat java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909)at java.util.ArrayList$Itr.next(ArrayList.java:859)at org.jenkinsci.plugins.workflow.cps.DSL$ThreadTaskImpl.invokeBody(DSL.java:623)at org.jenkinsci.plugins.workflow.cps.DSL$ThreadTaskImpl.eval(DSL.java:593)at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:184)at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:348)at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:93)at
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-56890
Re: IOException: "cannot find current thread"
Thanks everyone for the detailed investigation! From what I can tell it looks like the root cause is that steps using the new {{GeneralNonBlockingStepExecution}} API (JENKINS-49337) introduced in Pipeline: Step API 2.18 that interact with {{StepContext}} inside of their completion callback will do so not on the CPS VM thread, leading to the unsafe access of the {{TreeMap}} and the reported issue.I'll take a look at the [submitted PR|https://github.com/jenkinsci/workflow-cps-plugin/pull/287]. It looks ok to me at a glance, although I wonder if there could be other problems with running the completion callback in {{GeneralNonBlockingStepExecution }} on a separate thread (maybe we need to fix that instead of just making the collection thread safe), and I'm not sure if it fixes the reported issue. If anyone seeing the issue has a Jenkins instance on which you are comfortable testing pre-release plugins and are able to consistently reproduce the issue, feel free to install the .hpi file [here|https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/workflow/workflow-cps/2.68-rc2272.ba3575b51e37/] which is a build of the plugin that includes that that PR and let us know whether it seems to help or not. If anyone has a standalone (ideally minimal) Pipeline that reproduces the issue somewhat consistently I would be interested to see it so that we can test the proposed fix. I tried to reproduce the problem in a test but was only able to reproduce JENKINS-50474.
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
[JIRA] (JENKINS-57391) Id for Snipped Generator Page
Title: Message Title Tanja Roithmeier created an issue Jenkins / JENKINS-57391 Id for Snipped Generator Page Issue Type: Story Assignee: Ulli Hafner Attachments: Screenshot from 2019-05-09 23-16-50.png Components: warnings-plugin Created: 2019-05-09 21:25 Priority: Minor Reporter: Tanja Roithmeier For the page object of the snippet Generator a unique id or name for the 'select' Element for the tool selection is required. (cf. attached screenshot) The item can not be identified by class name cause 'setting-input dropdownList' is not unique. Add Comment
[JIRA] (JENKINS-50474) ArrayIndexOutOfBoundsException cause job "hang"
Title: Message Title
Devin Nusbaum commented on JENKINS-50474
Re: ArrayIndexOutOfBoundsException cause job "hang"
FWIW I ran into this trying to reproduce a totally different issue. The following (contrived) test in workflow-cps reproduces it somewhat consistently for me. Changing my nonBlocking step for a simpler block-scope step like timeout made the problem go away
@Issue("JENKINS-56890") // The otherwise unrelated issue I was investigating.
@Test public void generalNonBlockingStepExecutionCpsThreadSafety() {
rr.then(r -> {
WorkflowJob p = r.jenkins.createProject(WorkflowJob.class, "demo");
p.setDefinition(new CpsFlowDefinition(
"Map branches = [failFast: false]\n" +
"for (int i = 0; i < 250; i++) {\n" + // Increasing this value seems to make JENKINS-50474 more likely.
" branches[\"branch${i}\"] = {\n" +
"nonBlocking {\n" +
" sleep(time: Math.random() * 100, unit: 'MILLISECONDS')\n" +
"}\n" +
" }\n" +
"}\n" +
"parallel(branches)\n", false));
WorkflowRun b = r.buildAndAssertSuccess(p);
});
}
/**
* Step that uses {@link StepContext} in GeneralNonBlockingStepExecution.TailCall while not on the CPS VM thread
* to demonstrate a concurrency issue in {@link CpsStepContext}.
*/
public static class NonBlockingStep extends Step {
@DataBoundConstructor
public NonBlockingStep() { }
@Override
public StepExecution start(StepContext context) throws Exception {
return new Execution(context);
}
private static class Execution extends GeneralNonBlockingStepExecution {
public Execution(StepContext context) {
super(context);
}
@Override
public boolean start() throws Exception {
run(() -> {
getContext().newBodyInvoker().withCallback(new Callback()).start();
});
return false;
}
private final class Callback extends TailCall {
@Override
protected void finished(StepContext context) throws Exception {
Run run = context.get(Run.class);
TaskListener listener = context.get(TaskListener.class);
listener.getLogger().println("Finished executing nonBlockingStep in " + run);
}
}
}
@TestExtension("generalNonBlockingStepExecutionThreadSafety")
public static class DescriptorImpl extends StepDescriptor {
@Override
public String getFunctionName() {
return "nonBlocking";
}
@Override
public boolean takesImplicitBlockArgument() {
return true;
}
@Override
public Setextends Class> getRequiredContext() {
return ImmutableSet.of(Run.class, TaskListener.class);
}
}
}
In addition to the exception in the issue description I have also seen this one:
java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909)
at java.util.ArrayList$Itr.next(ArrayList.java:859)
at
[JIRA] (JENKINS-57392) AWS API timeout
Title: Message Title Sean Zou created an issue Jenkins / JENKINS-57392 AWS API timeout Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-05-09 21:28 Priority: Major Reporter: Sean Zou Exception during provisioning java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream.read(SocketInputStream.java:171) at java.net.SocketInputStream.read(SocketInputStream.java:141) at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) at sun.security.ssl.InputRecord.read(InputRecord.java:503) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) at org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:137) at org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer(SessionInputBufferImpl.java:153) at org.apache.http.impl.io.SessionInputBufferImpl.readLine(SessionInputBufferImpl.java:282) at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:138) at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56) at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:259) at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:163) at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:165) at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:273) at
[JIRA] (JENKINS-50474) ArrayIndexOutOfBoundsException cause job "hang"
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-50474 ArrayIndexOutOfBoundsException cause job "hang" Change By: Devin Nusbaum Labels: pipeline 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.189534.1522310533000.22576.1557437100305%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title Dax Games updated an issue Jenkins / JENKINS-55123 Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API Change By: Dax Games Comment: Carlos/Plugin Maintainers,Can we have a way to pass proxy and no_proxy settings from the Jenkins master to the Kubernetes slave?Thanks. 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.196186.1544542592000.22563.1557435420190%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title Dax Games commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API I found this code that passes the master env vars related to proxy settings to the slave. The problem is the pod never starts because the plugin can't talk to the Kubernetes API because it ignores the no_proxy settings. 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.196186.1544542592000.22558.1557435300164%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57351) Support for making Jenkins a "GitHub App"
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-57351 Support for making Jenkins a "GitHub App" Change By: Liam Newman Summary: Support authentication as for making Jenkins a " GitHub App " 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.199127.1557217283000.22551.1557434820147%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title Dax Games updated an issue Jenkins / JENKINS-55123 Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API Change By: Dax Games Summary: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API 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.196186.1544542592000.22553.1557435060294%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Liam Newman edited a comment on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub [~jsoref], [~synalogik], [~amirbarkal], [~dbsanfte], [~soar]Here's the updated plugin with okio (thanks Josh!). https://repo.jenkins - ci.org/incrementals/org/jenkins Removed - ci/plugins/github-branch-source/2.5.2-rc836.bde357341ecd/ 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.194753.1539776248000.22485.1557434521303%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38104) Configure proxy for connexion to Kubernetes
Title: Message Title Dax Games commented on JENKINS-38104 Re: Configure proxy for connexion to Kubernetes I can confirm this does not fix it. See: JENKINS-55123 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.174257.1473430953000.22482.1557434521267%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57195) Scan organization fails with FileNotFoundException
Title: Message Title
Liam Newman edited a comment on JENKINS-57195
Re: Scan organization fails with FileNotFoundException
{quote}java.io.FileNotFoundException: https://api.github.com/repos/elifesciences/sciencebeam-trainer-grobid{quote}If you can, when you see this error immedately try that URL (with credentials such as API key) we could check that url is actually available. also when you see this you might try clearing the Jenkin network cache as suggested here: https://issues.jenkins-ci.org/browse/JENKINS-54126?focusedCommentId=352154=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-352154Note that you'll need to delete a different folder name specific to this error instead of the one there, not sure which one. If you are willing to experiment a little, you could try the okhttp3 version of the plugin (also mentioned in that issue) to see if that makes this problem go away.
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.198949.1556274194000.22479.1557434400180%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57195) Scan organization fails with FileNotFoundException
Title: Message Title Liam Newman commented on JENKINS-57195 Re: Scan organization fails with FileNotFoundException java.io.FileNotFoundException: https://api.github.com/repos/elifesciences/sciencebeam-trainer-grobid If you can, when you see this error immedately try that URL (with credentials such as API key) we could check that url is actually available. 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.198949.1556274194000.22477.1557433620816%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57390) Enable credentials in triggers using declarative pipelines
Title: Message Title Tomas Bjerre assigned an issue to Unassigned Jenkins / JENKINS-57390 Enable credentials in triggers using declarative pipelines Change By: Tomas Bjerre Assignee: Tomas Bjerre 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.199172.155743169.22475.1557431820046%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57390) Enable credentials in triggers using declarative pipelines
Title: Message Title
Tomas Bjerre updated an issue
Jenkins / JENKINS-57390
Enable credentials in triggers using declarative pipelines
Change By:
Tomas Bjerre
h1. BackgroundThis issue originates from this issue in Generic Webhook Trigger Plugin: [https://github.com/jenkinsci/generic-webhook-trigger-plugin/issues/107]The reporter is using declarative pipeline.The user wants to get the credential, secret text, and use it when configuring triggers. More specifically as value of the 'token' configuration parameter in the plugin.Something like this:{code:java}... environment {JENKINS_TOKEN = credentials('JENKINS_TOKEN') } triggers {GenericTrigger( genericVariables: [ ... ], causeString: 'Triggered by $image', token: env.JENKINS_TOKEN, printContributedVariables: true, printPostContent: true) }...{code}h1. ProblemThe problem is that the credential, or variables form the environment block, is not available in the triggers block.
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
[JIRA] (JENKINS-57390) Enable credentials in triggers using declarative pipelines
Title: Message Title
Tomas Bjerre created an issue
Jenkins / JENKINS-57390
Enable credentials in triggers using declarative pipelines
Issue Type:
Improvement
Assignee:
Tomas Bjerre
Components:
generic-webhook-trigger-plugin, pipeline-model-definition-plugin
Created:
2019-05-09 19:54
Labels:
pipeline
Priority:
Major
Reporter:
Tomas Bjerre
Background This issue originates from this issue in Generic Webhook Trigger Plugin: https://github.com/jenkinsci/generic-webhook-trigger-plugin/issues/107 The reporter is using declarative pipeline. The user wants to get the credential, secret text, and use it when configuring triggers. More specifically as value of the 'token' configuration parameter in the plugin. Something like this:
...
environment {
JENKINS_TOKEN = credentials('JENKINS_TOKEN')
}
triggers {
GenericTrigger(
genericVariables: [
...
],
causeString: 'Triggered by $image',
token: env.JENKINS_TOKEN,
printContributedVariables: true,
printPostContent: true
)
}
...
Problem The problem is that credential, variables form the environment block, is not available in the triggers block.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations
Title: Message Title Dax Games edited a comment on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations Carlos/Plugin Maintainers,Can we have a way to pass proxy and no_proxy settings from the Jenkins master to the Kubernetes slave?Thanks. 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.196186.1544542592000.22469.1557431100136%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations
Title: Message Title Dax Games commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations Carlos/Plugin Maintainers, Can we have a way to pass proxy settings from the Jenkins master to the Kubernetes slave? Thanks. 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.196186.1544542592000.22464.1557430620225%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57389) Cannot upgrade JCasC plugin other than 1.4
Title: Message Title girish palaparty created an issue Jenkins / JENKINS-57389 Cannot upgrade JCasC plugin other than 1.4 Issue Type: Story Assignee: Ewelina Wilkosz Components: configuration-as-code-plugin Created: 2019-05-09 19:15 Labels: jenkins configuration-as-code Priority: Minor Reporter: girish palaparty Currently running JcasC plugin 1.4 on jenkins openshift environment - Jenkins ver. 2.121.3 When I upgrade to any version of configuration-as-code the jenkins instance stops and fails to load after restart. I then have to downgrade it to 1.4 to start jenkins successfully. Any idea what to do here ? SEVERE: Failed to initialize JenkinsSEVERE: Failed to initialize Jenkinshudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.WebAppMain$3.run(WebAppMain.java:250)Caused by: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:282) at jenkins.InitReactorRunner.run(InitReactorRunner.java:48) at jenkins.model.Jenkins.executeReactor(Jenkins.java:1102) at jenkins.model.Jenkins.(Jenkins.java:904) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233)Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1068) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Liam Newman edited a comment on JENKINS-57371 Re: error message when building PR [~nickez]I certainly don't want you to break your CI, but there isn't enough information here to be able to debug this. The rescan is not generally needed, I'm just trying to get more information and see if there's a reasonable workaround. To explain more fully: this failure occurs when the plugin detects that the merge_commit_sha provided by github is not the immediate child of the head commit of the source branch and the head commit of the base branch.This can happen when the base branch is updated after the PR job is queued but before the PR starts. Usually that would mean another PR job is also queued after this one and it will have consistent values and run successfully. It is a safety measure to ensure accurate CI runs.That fact that you're getting this (even on new PRs) indicates something is changing the commit structure (or at least that Jenkins believes they are changing). This definitely is not happening to everyone - 2.5.1 was confirmed to work by several reporters of a previous regression. So, there's something different about your configuration. We need to figure out what that is before we can address/fix it. Questions: So Is this happen on jobs triggered by webhook?What happens when you do a scan of the repo? (Can you provide the scan log?)For an open PR , what happens when you manually run the pipeline job? (Double checking) Did this also happened error happen on new PR's that you opened after the upgrade? Are you doing anything of note to your repo (pushing or amending commits) as you start PRs? Did you say you (Double checking)You tried closing and reopening the PR on GitHub ? When you did that were the commit sha values in the error different after close and reopen?For each of the sha values in that error line I need to see the result of the following:what is the result from this api query:https://api.github.com/repos/YOURORG/YOURREPO/commits/COMMITSHAI could also use the info from: https://api.github.com/repos/YOURORG/YOURREPO/pulls/PULLNUMBERFor a private repo, you'll need pass credentials or an api key to access these. It would bIf If you'd rather chat on https://gitter.im/bitwiseman (or some other chat platform), we can do that too. Add Comment
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Liam Newman edited a comment on JENKINS-57371 Re: error message when building PR [~nickez]I certainly don't want you to break your CI, but there isn't enough information here to be able to debug this.The rescan is not generally needed, I'm just trying to get more information and see if there's a reasonable workaround. Can To explain more fully: this failure occurs when the plugin detects that the merge_commit_sha provided by github is not the immediate child of the head commit of the source branch and the head commit of the base branch.This can happen when the base branch is updated after the PR job is queued but before the PR starts. Usually that would mean another PR job is also queued after this one and it will have consistent values and run successfully. Questions:So, this also happened on new PR's that you answer opened after the questions above upgrade ? Are you doing anything of note to your repo as you start PRs? Did you say you tried closing and reopening? When you did that were the commit sha values different after close and reopen? For each of the sha values in that error line I need to see the result of the following:what is the result from this api query:https://api.github.com/repos/YOURORG/YOURREPO/commits/COMMITSHAI could also use the info from: https://api.github.com/repos/YOURORG/YOURREPO/pulls/PULLNUMBERFor a private repo, you'll need pass credentials or an api key to access these. It would bIf you'd rather chat on https://gitter.im/bitwiseman (or some other chat platform), we can do that too. 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
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Liam Newman edited a comment on JENKINS-57371 Re: error message when building PR [~nickez]I certainly don't want you to break your CI, but there isn't enough information here to be able to debug this.Can you answer the questions above? Did you say you tried closing and reopening? When you did that were the commit sha values different after close and reopen? For each of the sha values in that error line I need to see the result of the following: what is the result from this api query: If https://api.github.com/repos/YOURORG/YOURREPO/commits/COMMITSHAI could also use the info from: https://api.github.com/repos/YOURORG/YOURREPO/pulls/PULLNUMBERFor a private repo, you' ll need pass credentials or an api key to access these. It would bIf you' d rather chat on https://gitter.im/bitwiseman (or some other chat platform), we can do that too. 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.199152.155732120.22453.1557423540120%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Liam Newman edited a comment on JENKINS-57371 Re: error message when building PR [~nickez]I certainly don't want you to break your CI, but there isn't enough information here to be able to debug this. Can you answer the questions above? Did you say you tried closing and reopening? When you did that were the commit sha values different after close and reopen? If you'd rather chat on https:// gitter.im /bitwiseman (or some other chat platform) , we can do that too. 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.199152.155732120.22450.1557422940141%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36195) Pipeline polling ignores special polling rules
Title: Message Title Kyle Leinen commented on JENKINS-36195 Re: Pipeline polling ignores special polling rules From reading the original ticket notes belong to the responses, I think this one is more in regard to special rules around a single repository and not multiple repos. 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.172167.1466697529000.22360.1557422581280%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36195) Pipeline polling ignores special polling rules
Title: Message Title smekkley smekkley commented on JENKINS-36195 Re: Pipeline polling ignores special polling rules Does this issue also aim to solve the issue where you can't poll multiple git repository with pipeline jobs? 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.172167.1466697529000.22270.1557422161390%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18342) jnlpCredentials exposed on slave.jar command-line
Title: Message Title smekkley smekkley commented on JENKINS-18342 Re: jnlpCredentials exposed on slave.jar command-line It works. Thank you. You actually see from jenkins ui that you have to run it in a full command line. It's probably better that the example command there gets replaced. People would just run it blindly following the example. 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.149649.1371156652000.22265.1557421920167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56909) Allow to unlock/lock keychain on demand
Title: Message Title Mathieu Delrocq commented on JENKINS-56909 Re: Allow to unlock/lock keychain on demand Kazuhide Takahashi, I'm afraid that making keychains a credential will allow to access to the password using withcredential(...) command. We don't want to make it visible for jenkins users. And it will be a problem for the backward compatibility with the actual configuration of the plugin. 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.198582.155446542.22263.1557420360105%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57278) Console Log View
Title: Message Title Veronika Zwickenpflug updated JENKINS-57278 Jenkins / JENKINS-57278 Console Log View Change By: Veronika Zwickenpflug Status: In Progress Review 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.199044.1556741728000.22261.1557420120136%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18342) jnlpCredentials exposed on slave.jar command-line
Title: Message Title
Jeff Thompson edited a comment on JENKINS-18342
Re: jnlpCredentials exposed on slave.jar command-line
The capability is already there, it's just not well documented.It's built into the command-line processing library the Remoting agent library uses.If a command-line argument begins with a '@' ( ampersand at symbol ), then the rest of that argument is interpreted as the path to a file. Each line in the file is inserted as a command-line argument.Using the `-secret` parameter, you would create a file with a single line containing the secret key. Then reference it in the command-line something like this: "java -jar agent.jar -jnlpUrl -secret @".You could also create a four line file something like this: {quote} -jnlpUrl[http://somewhere/xx.jnlp]-secret {quote} and then invoke it like this: "java -jar agent.jar @"It would be nice to assemble some better documentation on this if someone gets a chance. I've got a note to do it if I can get the time.
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.149649.1371156652000.22256.155742228%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57282) Overview Carousel (in Details View)
Title: Message Title Artem Polovyi started work on JENKINS-57282 Change By: Artem Polovyi Status: Open In Progress 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.199048.1556744575000.22254.1557419880123%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57280) Source Control Table (in Details Tab)
Title: Message Title Veronika Zwickenpflug started work on JENKINS-57280 Change By: Veronika Zwickenpflug Status: Open In Progress 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.199046.1556742198000.22252.1557419280203%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57292) Folder Plugin
Title: Message Title Veronika Zwickenpflug started work on JENKINS-57292 Change By: Veronika Zwickenpflug Status: Open In Progress 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.199058.1556746895000.22249.1557419220178%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Liam Newman commented on JENKINS-57371 Re: error message when building PR Niklas Claesson I certainly don't want you to break your CI, but there isn't enough information here to be able to debug this. Can you answer the questions above? If you'd rather chat on gitter.im, we can do that too. 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.199152.155732120.22245.1557418860208%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57278) Console Log View
Title: Message Title Florian Hageneder started work on JENKINS-57278 Change By: Florian Hageneder Status: Open In Progress 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.199044.1556741728000.22243.1557417840307%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54469) Unable to set Thread Executor Size when configuring Jira Plugin
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-54469 Unable to set Thread Executor Size when configuring Jira Plugin Change By: Radek Antoniuk Labels: jira-plugin-3.0.5 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.195234.1541437984000.9.1557417120447%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54116) Jenkins Jira Plugin - Unable to add version
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-54116 Jenkins Jira Plugin - Unable to add version Change By: Radek Antoniuk Labels: jira- plugin -3.0.5 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.194742.1539757445000.22237.1557417180412%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54116) Jenkins Jira Plugin - Unable to add version
Title: Message Title Radek Antoniuk closed an issue as Fixed Fixed in 3.0.5 Jenkins / JENKINS-54116 Jenkins Jira Plugin - Unable to add version Change By: Radek Antoniuk Status: Open Closed 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.194742.1539757445000.22235.1557417180388%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54469) Unable to set Thread Executor Size when configuring Jira Plugin
Title: Message Title Radek Antoniuk closed an issue as Fixed I just checked this with 3.0.7 and all works fine for me, feel free to reopen if this still applies. Jenkins / JENKINS-54469 Unable to set Thread Executor Size when configuring Jira Plugin Change By: Radek Antoniuk Status: Open Closed 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.195234.1541437984000.7.1557417120420%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55982) JIRA Plugin does not respect proxy in some requests
Title: Message Title Radek Antoniuk commented on JENKINS-55982 Re: JIRA Plugin does not respect proxy in some requests Can you check the current version of plugin (3.0.7) and make sure you define the proxy in Manage Jenkins > Manage Plugins > Advanced ? 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.197394.1549394874000.4.1557416760104%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56417) Jenkins cannot release Jira version 'No content to map to Object due to end of input'
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-56417 Jenkins cannot release Jira version 'No content to map to Object due to end of input' Change By: Radek Antoniuk Environment: Jenkins 2.166 withjira-plugin version 306 and Jira version 3.0.6JIRA 8.0.1 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.198008.1551797348000.0.1557416520163%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56417) Jenkins cannot release Jira version 'No content to map to Object due to end of input'
Title: Message Title Radek Antoniuk edited a comment on JENKINS-56417 Re: Jenkins cannot release Jira version 'No content to map to Object due to end of input' Since you mentioned a change in your configuration (I'm assuming on the JIRA side), can you make sure all /rest/ requests are passed correctly to JIRA? (Try looking up what flows between Jenkins and JIRA with tcpdump/tcpick or wireshark). Also, is this JIRA Server or Cloud? 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.198008.1551797348000.2.1557416520185%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56417) Jenkins cannot release Jira version 'No content to map to Object due to end of input'
Title: Message Title Radek Antoniuk commented on JENKINS-56417 Re: Jenkins cannot release Jira version 'No content to map to Object due to end of input' Since you mentioned a change in your configuration (I'm assuming on the JIRA side), can you make sure all /rest/ requests are passed correctly to JIRA? (Try looking up what flows between Jenkins and JIRA with tcpdump/tcpick or wireshark). 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.198008.1551797348000.22218.1557416460094%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57352) Test connection fails and also unable to get K8s pods via Jenkins using service account
Title: Message Title Carlos Sanchez commented on JENKINS-57352 Re: Test connection fails and also unable to get K8s pods via Jenkins using service account what kubernetes ? EKS? GKE?...? Roles are here https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/kubernetes/service-account.yml 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.199130.1557226492000.22216.1557416400103%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56857) Unable to add Jira site in jenkins
Title: Message Title Radek Antoniuk commented on JENKINS-56857 Re: Unable to add Jira site in jenkins That usually means that there is a problem with accessing your JIRA instance (yeah, I know, the info is not too informative now). Are you integrating with standalone JIRA or Cloud? Can you try checking a curl request from your Jenkins host if it correctly returns JSON with the credentials you provided? See authentication info. 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.198519.1554240962000.22198.1557416040413%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57352) Test connection fails and also unable to get K8s pods via Jenkins using service account
Title: Message Title Harsha GV commented on JENKINS-57352 Re: Test connection fails and also unable to get K8s pods via Jenkins using service account K8s: Client v1.11.5 Server v1.13.5 Jenkins deployed in K8s. Also could you please point me to any documentation to get the minimum roles and rolebindings needs to be assigned to a Jenkins service account - used by k8s plugin to to dynamically provision a Jenkins agent, run a single build, then tear-down that agent? 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.199130.1557226492000.22208.1557416040574%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56577) Unable to add Jira Site
Title: Message Title Radek Antoniuk commented on JENKINS-56577 Re: Unable to add Jira Site Also can you try current Jenkins(2.176) and Jira plugin version (3.0.7) on a test instance? 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.198192.1552639896000.22214.1557416340096%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title Ian Katz commented on JENKINS-53649 Re: Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable I also question this String/GStringImpl correlation. You can reproduce this issue by echoing a static string multiple times, as shown in the original attachment for this issue. In my own case, echoing the exact same static string multiple times produced inconsistent results. 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.194144.1537309242000.22186.1557415860388%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56857) Unable to validate JIRA site
Title: Message Title
Radek Antoniuk updated an issue
Jenkins / JENKINS-56857
Unable to validate JIRA site
Change By:
Radek Antoniuk
After adding the Jira URL, validate settings shows below error: {code:java} java.lang.NullPointerException at hudson.plugins.jira.JiraSite$DescriptorImpl.doValidate(JiraSite.java:1179) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:243) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:99) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at
[JIRA] (JENKINS-56677) Jenkins build failed with java.lang.NullPointerException caused:java.io.IOException: Failed to parse changelog
Title: Message Title Radek Antoniuk commented on JENKINS-56677 Re: Jenkins build failed with java.lang.NullPointerException caused:java.io.IOException: Failed to parse changelog hudson.plugins.jira.JiraSite.createSession(JiraSite.java:295) This means that probably Jenkins has trouble connecting to your JIRA instance. Does JIRA integration work fine in other places in Jenkins? Can you try VALIDATE button in Jenkins JIRA site settings? 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.198314.1553248627000.22212.1557416220084%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56677) Jenkins build failed with java.lang.NullPointerException caused:java.io.IOException: Failed to parse changelog
Title: Message Title
Radek Antoniuk updated an issue
Jenkins / JENKINS-56677
Jenkins build failed with java.lang.NullPointerException caused:java.io.IOException: Failed to parse changelog
Change By:
Radek Antoniuk
{code: java }java .lang.NullPointerException at hudson.plugins.jira.JiraSite.createSession(JiraSite.java:295) at hudson.plugins.jira.JiraSite.getSession(JiraSite.java:278) at io.jenkins.blueocean.service.embedded.jira.JiraSCMListener.onChangeLogParsed(JiraSCMListener.java:38) at hudson.model.listeners.SCMListener.onChangeLogParsed(SCMListener.java:120) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590)Caused: java.io.IOException: Failed to parse changelog at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:592) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1815) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) {code}
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
[JIRA] (JENKINS-57352) Test connection fails and also unable to get K8s pods via Jenkins using service account
Title: Message Title Harsha GV edited a comment on JENKINS-57352 Re: Test connection fails and also unable to get K8s pods via Jenkins using service account K8s: Client v1.11.5Server v1.13.5Jenkins deployed in K8s. And also could you please point me to any documentation to get the minimum roles and rolebindings needs to be assigned to a Jenkins service account - used by k8s plugin to to dynamically provision a Jenkins agent, run a single build, then tear-down that agent. 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.199130.1557226492000.22202.1557416040477%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56857) Unable to validate JIRA site
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-56857 Unable to validate JIRA site Change By: Radek Antoniuk Summary: Unable to add Jira validate JIRA site in jenkins 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.198519.1554240962000.22200.1557416040439%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57352) Test connection fails and also unable to get K8s pods via Jenkins using service account
Title: Message Title Harsha GV updated an issue Jenkins / JENKINS-57352 Test connection fails and also unable to get K8s pods via Jenkins using service account Change By: Harsha GV Comment: K8s: Client v1.11.5Server v1.13.5Jenkins deployed in K8s.And also could you please point me to any documentation to get the minimum roles and rolebindings needs to be assigned to a Jenkins service account - used by k8s plugin to to dynamically provision a Jenkins agent, run a single build, then tear-down that agent. 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.199130.1557226492000.22206.1557416040552%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57004) Error with jira plugin: Request cannot be executed; I/O reactor status: STOPPED
Title: Message Title Radek Antoniuk commented on JENKINS-57004 Re: Error with jira plugin: Request cannot be executed; I/O reactor status: STOPPED That's interesting, can you try upgrading to 3.0.7 and restarting Jenkins instance and see if the problem persists? 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.198705.1555286407000.22184.1557415800101%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33101) JIRA Jenkins integration
Title: Message Title Radek Antoniuk closed an issue as Cannot Reproduce The stacktrace mentions "com.marvelution.jenkins.plugins.jira.filter" which is a Marvelution plugin, not the Open Source Jenkins JIRA plugin. Please contact Marvelution support. Jenkins / JENKINS-33101 JIRA Jenkins integration Change By: Radek Antoniuk 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.168468.1456230079000.22180.1557415440271%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57352) Test connection fails and also unable to get K8s pods via Jenkins using service account
Title: Message Title Harsha GV commented on JENKINS-57352 Re: Test connection fails and also unable to get K8s pods via Jenkins using service account K8s: Client v1.11.5 Server v1.13.5 Jenkins deployed in K8s. 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.199130.1557226492000.22182.1557415680091%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title Hilario Fernandes commented on JENKINS-53649 Re: Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable Marcello de Sales i do not think this is related to GStrings. I've tested with pure hardcoded strings and if any part of the string matches a value of an enviroment variable the string is not shown. 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.194144.1537309242000.22174.1557415080473%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57239) Error while integrating jenkins and jira
Title: Message Title Radek Antoniuk commented on JENKINS-57239 Re: Error while integrating jenkins and jira The stacktrace you posted doesn't even mention the plugin, it doesn't even mention hudson/jenkins, but you can see java.lang.ClassNotFoundException. Can you add more info? Jenkins and plugin version? when are you executing getting this stracktrace? 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.199002.1556612051000.22176.1557415080492%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57239) Error while integrating jenkins and jira
Title: Message Title
Radek Antoniuk updated an issue
Jenkins / JENKINS-57239
Error while integrating jenkins and jira
Change By:
Radek Antoniuk
{code: java }java .lang.ClassCastException: Cannot cast com.att.aft.dme2.internal.jersey.core.impl.provider.header.LocaleProvider to com.sun.jersey.spi.HeaderDelegateProvider at java.lang.Class.cast(Class.java:3369) at com.sun.jersey.spi.service.ServiceFinder$LazyObjectIterator.hasNext(ServiceFinder.java:833) at com.sun.jersey.core.spi.factory.AbstractRuntimeDelegate.(AbstractRuntimeDelegate.java:76) at com.sun.ws.rs.ext.RuntimeDelegateImpl.(RuntimeDelegateImpl.java:56) at sun.reflect.GeneratedConstructorAccessor303.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.Class.newInstance(Class.java:442) at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:65)Caused: java.lang.ClassNotFoundException: Provider com.sun.ws.rs.ext.RuntimeDelegateImpl could not be instantiated at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:69) at javax.ws.rs.ext.FactoryFinder.find(FactoryFinder.java:155) at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:105) {code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
[JIRA] (JENKINS-57388) Status page does not show "Show all failed tests >>>" link when 11 tests have failed
Title: Message Title Yoshinori Ehara created an issue Jenkins / JENKINS-57388 Status page does not show "Show all failed tests >>>" link when 11 tests have failed Issue Type: Bug Assignee: Unassigned Attachments: status.png Components: junit-plugin Created: 2019-05-09 14:50 Environment: JUnit Plugin 1.27 Priority: Minor Reporter: Yoshinori Ehara If exact 11 tests have failed, the status page shows only 10 failures and no "Show all failed tests >>>" link. Add Comment
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy Jie, do we have a fix for this? 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.198672.1554998321000.22142.1557411420701%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang edited a comment on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy Jie, do we have a fix for this? [~jieshe] 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.198672.1554998321000.22144.1557411421177%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title
Devin Nusbaum commented on JENKINS-56890
Re: IOException: "cannot find current thread"
Thanks everyone for the detailed investigation! From what I can tell it looks like the root cause is that steps using the new GeneralNonBlockingStepExecution API (JENKINS-49337) introduced in Pipeline: Step API 2.18 that interact with StepContext inside of their completion callback will do so not on the CPS VM thread, leading to the unsafe access of the TreeMap and the reported issue. I'll take a look at the submitted PR. It looks ok to me at a glance, although I wonder if there could be other problems with running the completion callback in {{GeneralNonBlockingStepExecution }} on a separate thread (maybe we need to fix that instead of just making the collection thread safe), and I'm not sure if it fixes the reported issue. If anyone seeing the issue has a Jenkins instance on which you are comfortable testing pre-release plugins and are able to consistently reproduce the issue, feel free to install the .hpi file here which is a build of the plugin that includes that that PR and let us know whether it seems to help or not.
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.198561.1554419267000.22120.1557410820422%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49729) Deleted jobs and builds look the same as everything else
Title: Message Title rsandell assigned an issue to rsandell Jenkins / JENKINS-49729 Deleted jobs and builds look the same as everything else Change By: rsandell Assignee: rsandell 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.188671.151953024.22115.1557410040554%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49729) Deleted jobs and builds look the same as everything else
Title: Message Title rsandell started work on JENKINS-49729 Change By: rsandell Status: Open In Progress 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.188671.151953024.22117.1557410040602%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title William F commented on JENKINS-56890 Re: IOException: "cannot find current thread" I just created this PR: https://github.com/jenkinsci/workflow-cps-plugin/pull/287. As noted in the PR summary, I haven't done any testing to confirm that this fixes the issue – or, for that matter, to definitively identify the root cause. But that change does partially address some glaring thread-safety issues, so hopefully it will get picked up. (and as to Lee Webb's experiences with different version combinations: as you say, perhaps the root cause lies in another component altogether, but OTOH, if the issue is indeed non-threadsafe manipulation of a collection, such bugs can often manifest in ways that are surprisingly subtle – and, in some cases, the particular manifestation can be affected by apparently unrelated changes) 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.198561.1554419267000.22093.1557409860558%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-56890 IOException: "cannot find current thread" Change By: Devin Nusbaum Component/s: workflow-cps-plugin Component/s: pipeline 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.198561.1554419267000.22066.1557409081869%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57386) Durations calculated inaccurately in inactive tabs
Title: Message Title Nikita Lobachev updated an issue Jenkins / JENKINS-57386 Durations calculated inaccurately in inactive tabs Change By: Nikita Lobachev [TimeDuration component|https://github.com/jenkinsci/blueocean-plugin/blob/master/jenkins-design-language/src/js/components/TimeDuration.jsx] relies on timers which aren't accurate and may not fire at all if the browser tab is inactive or if I close my laptop. Therefore, if I start a long build, switch to another tab for 10 minutes and then switch back, I'll see durations several minutes behind their actual values. PR: https://github.com/jenkinsci/blueocean-plugin/pull/1959 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.199168.1557400664000.22091.1557409200061%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57386) Durations calculated inaccurately in inactive tabs
Title: Message Title Nikita Lobachev updated JENKINS-57386 Jenkins / JENKINS-57386 Durations calculated inaccurately in inactive tabs Change By: Nikita Lobachev Status: In Progress Review 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.199168.1557400664000.22090.1557409140177%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57386) Durations calculated inaccurately in inactive tabs
Title: Message Title Nikita Lobachev started work on JENKINS-57386 Change By: Nikita Lobachev Status: Open In Progress 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.199168.1557400664000.22089.1557409140115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-56890 IOException: "cannot find current thread" Change By: Devin Nusbaum Labels: pipeline 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.198561.1554419267000.22068.1557409081891%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57116) MismatchedInputException: No content to map due to end-of-input
Title: Message Title Carlos Sanchez updated JENKINS-57116 Jenkins / JENKINS-57116 MismatchedInputException: No content to map due to end-of-input Change By: Carlos Sanchez Status: In Review 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.198865.1555666948000.22035.1557407820714%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57387) Openstack Auth credentials not properly working since openstack-cloud-plugin 2.46
Title: Message Title Oliver Gondža started work on JENKINS-57387 Change By: Oliver Gondža Status: Open In Progress 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.199169.155740270.22032.1557406740329%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57387) Openstack Auth credentials not properly working since openstack-cloud-plugin 2.46
Title: Message Title Oliver Gondža commented on JENKINS-57387 Re: Openstack Auth credentials not properly working since openstack-cloud-plugin 2.46 This is a regression introduced in https://github.com/jenkinsci/openstack-cloud-plugin/issues/230, thanks for reporting it so promptly! Proposed fix: https://github.com/jenkinsci/openstack-cloud-plugin/issues/230 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.199169.155740270.22030.1557406740307%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
