[JIRA] (JENKINS-45007) git-plugin GitSCM does not support ssh credentials when using checkout in a Jenkinsfile
Title: Message Title Ilguiz Latypov commented on JENKINS-45007 Re: git-plugin GitSCM does not support ssh credentials when using checkout in a Jenkinsfile Was the source code analysis in the bug description flawed, then? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36652) Archive tests in Blue Ocean and Acceptance Test pipelines
Title: Message Title trejkaz edited a comment on JENKINS-36652 Re: Archive tests in Blue Ocean and Acceptance Test pipelines [~darwinjs] do you have a ticket ID for that one? We have the same problem. It happens on literally every project though, so the test project can probably be trivial. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57005) Security warning: Credentials stored in plain text
Title: Message Title Zach Olbrys commented on JENKINS-57005 Re: Security warning: Credentials stored in plain text Hi Mez Pahlan - looks good from my end. I installed the plugin and was able to upload to HockeyApp still, no change in behavior as far as I can tell. I still see the credentials warning, but I suspect that's due to Jenkins using the last released version when looking for security warnings, not necessarily the version I have installed (which I confirmed was 1.5.0-SNAPSHOT). 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title
Alisdair Robertson edited a comment on JENKINS-55075
Re: Pipeline: If job fails it will run again on next poll.
I've got an issue with the change to polling behaviour that appears to have been altered in this ticket.It seems that now in cases where polling shows no changes since the previous build we report no changes (good) but we also report no changes when there was a polling error, and don't take any action to correct or notify about the polling error (bad). This has caused a few branches of mine that are set to poll nightly to not be built for a few days before we noticed, with polling logs that look like this for each workspace used in the build (we use multiple {{p4sync}} steps in parallel stages):{quote} {{ P4: Polling on: master with:P4: Polling: No changes in previous build.P4: Polling error; no previous change. }} {quote}From looking at the code it looks to me as though this is caused by no changes being attached to the previous build for some unknown reason so https://github.com/jenkinsci/p4-plugin/blob/master/src/main/java/org/jenkinsci/plugins/p4/tagging/TagAction.java#L300 would return an empty arraylist. However I haven't actually done any debugging.While I can understand that builds being constantly triggered just because of a polling error is not desirable, I find it even more undesirable to almost silently skip triggering a build indefinitely without an administrator being made aware that there is a polling issue rather than just no changes being made in the workspace.Could there be limited (re)triggering on polling failures or an notification system so that an administrator can swoop in to diagnose issues or manually trigger the job anew as necessary in the event of polling failures?Note that I explicitly do not want to retry failed builds, because as far as I can tell from logs, although the build prior to the polling error was a failure in compilation, the perforce syncs in the job all completed successfully.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title
Alisdair Robertson commented on JENKINS-55075
Re: Pipeline: If job fails it will run again on next poll.
I've got an issue with the change to polling behaviour that appears to have been altered in this ticket. It seems that now in cases where polling shows no changes since the previous build we report no changes (good) but we also report no changes when there was a polling error, and don't take any action to correct or notify about the polling error (bad). This has caused a few branches of mine that are set to poll nightly to not be built for a few days before we noticed, with polling logs that look like this for each workspace used in the build (we use multiple p4sync steps in parallel stages):
{{P4: Polling on: master with: P4: Polling: No changes in previous build. P4: Polling error; no previous change.}}
From looking at the code it looks to me as though this is caused by no changes being attached to the previous build for some unknown reason so https://github.com/jenkinsci/p4-plugin/blob/master/src/main/java/org/jenkinsci/plugins/p4/tagging/TagAction.java#L300 would return an empty arraylist. However I haven't actually done any debugging. While I can understand that builds being constantly triggered just because of a polling error is not desirable, I find it even more undesirable to almost silently skip triggering a build indefinitely without an administrator being made aware that there is a polling issue rather than just no changes being made in the workspace. Could there be limited (re)triggering on polling failures or an notification system so that an administrator can swoop in to diagnose issues or manually trigger the job anew as necessary in the event of polling failures? Note that I explicitly do not want to retry failed builds, because as far as I can tell from logs, although the build prior to the polling error was a failure in compilation, the perforce syncs in the job all completed successfully.
Add Comment
This message was sent by
[JIRA] (JENKINS-50122) Incorrect permissions with non Multibranch based Pipeline jobs
Title: Message Title Jonathan Pigrée commented on JENKINS-50122 Re: Incorrect permissions with non Multibranch based Pipeline jobs I have the exact same problem. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57266) SCM Skip could use an option to not skip manual builds
Title: Message Title
Bryce Schober updated an issue
Jenkins / JENKINS-57266
SCM Skip could use an option to not skip manual builds
Change By:
Bryce Schober
It sure would be nice if the SCM Skip plugin had an option to *not* skip builds that were manually triggered by a user. Currently, my declarative pipeline has to do:{code}script { if ( currentBuild.getBuildCauses('hudson.model.Cause$UserIdCause') == null .size( ) > 0 ) {scmSkip(deleteBuild: true, skipPattern: '.*\\[(ci skip|skip ci)\\].*') }}{code}... which is a lot uglier than with this hypothetical feature:{code}scmSkip( alsoSkipManualBuilds: false, deleteBuild: true, skipPattern: '.*\\[(ci skip|skip ci)\\].*'){code}Note that I called it "alsoSkipManualBuilds" to avoid a double-negative; obviously the default should be current behavior, if you care.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57268) Unable to provision agent in google cloud
Title: Message Title
L Powers updated an issue
Jenkins / JENKINS-57268
Unable to provision agent in google cloud
Change By:
L Powers
After latest update (update ran on 2019-04-30 ~2100UTC), Jenkins no longer correctly builds agents when PR's are created in github. Not sure exactly which plugin causes this issue, but the logs continually dump the following:{noformat}Provisioning node from config com.google.jenkins.plugins.computeengine.InstanceConfiguration@626b7130 for excess workload of 1 units of label 'buildAgent'Apr 30, 2019 4:19:22 PM SEVERE hudson.triggers.SafeTimerTask runTimer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@42da5e15 failedjava.lang.NullPointerException at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:187) at com.google.common.collect.ImmutableMap.of(ImmutableMap.java:75) at com.google.jenkins.plugins.computeengine.ComputeEngineCloud.availableNodeCapacity(ComputeEngineCloud.java:333) at com.google.jenkins.plugins.computeengine.ComputeEngineCloud.provision(ComputeEngineCloud.java:261) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:715) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:320) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:62) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:809) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) {noformat} Note that provisioning an agent in the 'Nodes' tab with the 'Provision via gce' dropdown will provision an agent correctly and allow builds to run. But as soon as the agent expires (or if more builds come in) no further agents are created.
[JIRA] (JENKINS-57268) Unable to provision agent in google cloud
Title: Message Title
L Powers updated an issue
Jenkins / JENKINS-57268
Unable to provision agent in google cloud
Change By:
L Powers
After latest update (update ran on 2019-04-30 ~2100UTC), Jenkins no longer correctly builds agents when PR's are created in github. Not sure exactly which plugin causes this issue, but the logs continually dump the following:{noformat} Provisioning node from config com.google.jenkins.plugins.computeengine.InstanceConfiguration@626b7130 for excess workload of 1 units of label ' build-agent buildAgent 'Apr 30, 2019 4:19:22 PM SEVERE hudson.triggers.SafeTimerTask runTimer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@42da5e15 failedjava.lang.NullPointerException at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:187) at com.google.common.collect.ImmutableMap.of(ImmutableMap.java:75) at com.google.jenkins.plugins.computeengine.ComputeEngineCloud.availableNodeCapacity(ComputeEngineCloud.java:333) at com.google.jenkins.plugins.computeengine.ComputeEngineCloud.provision(ComputeEngineCloud.java:261) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:715) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:320) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:62) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:809) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){noformat}
Add Comment
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title James F. commented on JENKINS-57257 Re: No commit found for SHA after updating github branch source plugin Liam, For sure, I can give it a try tomorrow morning and will report my findings. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57268) Unable to provision agent in google cloud
Title: Message Title L Powers created an issue Jenkins / JENKINS-57268 Unable to provision agent in google cloud Issue Type: Bug Assignee: Evan Brown Components: google-compute-engine-plugin Created: 2019-04-30 23:33 Environment: ace-editor 1.1 antisamy-markup-formatter 1.5 apache-httpcomponents-client-4-api 4.5.5-3.0 authentication-tokens 1.3 basic-branch-build-strategies 1.3.1 bouncycastle-api 2.17 branch-api 2.4.0 build-environment 1.6 build-timeout 1.19 cloudbees-folder 6.8 command-launcher 1.3 credentials 2.1.18 credentials-binding 1.18 display-url-api 2.3.1 docker-commons 1.14 docker-workflow 1.18 durable-task 1.29 email-ext 2.66 embeddable-build-status 2.0.1 external-monitor-job 1.7 git 4.0.0-rc git-client 3.0.0-rc git-server 1.7 github 1.29.4 github-api 1.95 github-branch-source 2.5.0 github-coverage-reporter 1.5 github-oauth 0.32 github-organization-folder 1.6 github-pullrequest 0.2.4 global-slack-notifier 1.5 google-compute-engine 3.1.0 google-login 1.4 google-metadata-plugin 0.2 google-oauth-plugin 0.8 google-storage-plugin 1.2 gradle 1.31 handlebars 1.1.1 icon-shim 2.0.3 jackson2-api 2.9.8 javadoc 1.5 jdk-tool 1.2 jquery-detached 1.2.1 jsch 0.1.55 junit 1.27 ldap 1.20 lockable-resources 2.5 mailer 1.23 mapdb-api 1.0.9.0 matrix-auth 2.4.1 matrix-project 1.14 momentjs 1.1.1 oauth-credentials 0.3 pam-auth 1.5 pipeline-build-step 2.9 pipeline-github-lib 1.0 pipeline-githubnotify-step 1.0.4 pipeline-graph-analysis 1.9 pipeline-input-step 2.10 pipeline-milestone-step 1.3.1 pipeline-model-api 1.3.8 pipeline-model-declarative-agent 1.1.1 pipeline-model-definition 1.3.8 pipeline-model-extensions 1.3.8 pipeline-rest-api 2.11 pipeline-stage-step 2.3 pipeline-stage-tags-metadata 1.3.8 pipeline-stage-view 2.11 plain-credentials 1.5 resource-disposer 0.12 scm-api 2.4.1 script-security 1.58 slack 2.23 ssh 2.6.1 ssh-agent 1.17 ssh-credentials 1.16 ssh-slaves 1.29.4 structs 1.19 subversion 2.12.1 timestamper 1.9 token-macro 2.7 windows-slaves 1.4 workflow-aggregator 2.6 workflow-api 2.33 workflow-basic-steps 2.15 workflow-cps 2.67 workflow-cps-global-lib 2.13 workflow-durable-task-step 2.30 workflow-job 2.32 workflow-multibranch 2.21 workflow-scm-step 2.7 workflow-step-api 2.19 workflow-support 3.3 ws-cleanup 0.37 Labels: plugin
[JIRA] (JENKINS-57267) Rebuild's "Remember Password" remembers Non-Stored Password Parameters
Title: Message Title Matthew Smith updated an issue Jenkins / JENKINS-57267 Rebuild's "Remember Password" remembers Non-Stored Password Parameters Change By: Matthew Smith Summary: Rebuild's "Remember Password" remembers non Non - stored Stored Password Parameters 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57267) Rebuild's "Remember Password" remembers non-stored Password Parameters
Title: Message Title
Matthew Smith updated an issue
Jenkins / JENKINS-57267
Rebuild's "Remember Password" remembers non-stored Password Parameters
Change By:
Matthew Smith
When Jenkins is configured to remember passwords on a Rebuild, it remembers Non-Stored Password Parameters as well as normal Password Parameters. According to the description of the configuration option, it should not remember Non-Stored Passwords:{quote}If the remember password option is checked, the rebuild plugin will use the stored password parameter when a rebuild is triggered. If the remember password option is unchecked, the user will be prompted to enter the password every time a rebuild is triggered. This only applies for a parameterized build with parameters of type password.{quote} !password_remember.PNG|thumbnail! A simple test shows that this option also remembers Non-Stored Password Parameters.1. Set up a simple job with a Non-Stored Password ParameterExample code:{code}node("master") {println(params.PASSWORD)}{code}2. Build the job once as User A with parameter "test"3. See "test" printed to console4. Rebuild the first build5. See "test" printed to console6. Switch to User B7. Rebuild the build8. See "test" printed to consoleThe Non-Stored Password should not persist across Rebuilds. This issue is marked as "Minor" because the workaround is to disable the top-level configuration to Remember Passwords.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57267) Rebuild's "Remember Password" remembers non-stored Password Parameters
Title: Message Title Matthew Smith created an issue Jenkins / JENKINS-57267 Rebuild's "Remember Password" remembers non-stored Password Parameters Issue Type: Bug Assignee: ragesh_nair Attachments: password_remember.PNG Components: mask-passwords-plugin, rebuild-plugin Created: 2019-04-30 23:05 Environment: Jenkins 2.164.1 Rebuild Plugin 1.29 Mask Passwords Plugin 2.12.0 Labels: rebuild mask-passwords Priority: Minor Reporter: Matthew Smith When Jenkins is configured to remember passwords on a Rebuild, it remembers Non-Stored Password Parameters as well as normal Password Parameters. According to the description of the configuration option, it should not remember Non-Stored Passwords: If the remember password option is checked, the rebuild plugin will use the stored password parameter when a rebuild is triggered. If the remember password option is unchecked, the user will be prompted to enter the password every time a rebuild is triggered. This only applies for a parameterized build with parameters of type password. A simple test shows that this option also remembers Non-Stored Password Parameters. 1. Set up a simple job with a Non-Stored Password Parameter Example code:
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title Liam Newman commented on JENKINS-57257 Re: No commit found for SHA after updating github branch source plugin Caleb D James F. If you're willing, please try this plugin on your Jenkins. https://drive.google.com/open?id=1v06oUnCiN0KSZF47JXjteByPxIS6FBZ1 It incorporates the code from https://github.com/jenkinsci/github-branch-source-plugin/pull/222 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57143) JNLP4 error: "Connection closed before acknowledgement sent"
Title: Message Title Jeff Thompson assigned an issue to Unassigned Jenkins / JENKINS-57143 JNLP4 error: "Connection closed before acknowledgement sent" Change By: Jeff Thompson Assignee: 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57143) JNLP4 error: "Connection closed before acknowledgement sent"
Title: Message Title Jeff Thompson updated an issue Jenkins / JENKINS-57143 JNLP4 error: "Connection closed before acknowledgement sent" Change By: Jeff Thompson Component/s: remoting 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57143) JNLP4 error: "Connection closed before acknowledgement sent"
Title: Message Title Jeff Thompson commented on JENKINS-57143 Re: JNLP4 error: "Connection closed before acknowledgement sent" I'm glad you were able to isolate it. I'll remove Remoting from the components. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57266) SCM Skip could use an option to not skip manual builds
Title: Message Title
Bryce Schober created an issue
Jenkins / JENKINS-57266
SCM Skip could use an option to not skip manual builds
Issue Type:
Bug
Assignee:
Gregor Plavčak
Components:
scmskip-plugin
Created:
2019-04-30 21:24
Environment:
Latest Jenkins LTS and SCM Skip v1.0.1
Priority:
Minor
Reporter:
Bryce Schober
It sure would be nice if the SCM Skip plugin had an option to not skip builds that were manually triggered by a user. Currently, my declarative pipeline has to do:
script {
if ( currentBuild.getBuildCauses('hudson.model.Cause$UserIdCause') == null ) {
scmSkip(deleteBuild: true, skipPattern: '.*\\[(ci skip|skip ci)\\].*')
}
}
... which is a lot uglier than with this hypothetical feature:
scmSkip( alsoSkipManualBuilds: false, deleteBuild: true,
skipPattern: '.*\\[(ci skip|skip ci)\\].*')
Note that I called it "alsoSkipManualBuilds" to avoid a double-negative; obviously the default should be current behavior, if you care.
[JIRA] (JENKINS-57218) NPE from SymbolLookup after job-dsl update without configuration-as-code
Title: Message Title Daniel Spilker updated JENKINS-57218 Jenkins / JENKINS-57218 NPE from SymbolLookup after job-dsl update without configuration-as-code Change By: Daniel Spilker 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57143) JNLP4 error: "Connection closed before acknowledgement sent"
Title: Message Title Alexey Shein commented on JENKINS-57143 Re: JNLP4 error: "Connection closed before acknowledgement sent" It turns out the issue was in Github OAuth plugin. After downgrading 0.32 version to 0.31, everything seems to work fine. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57143) JNLP4 error: "Connection closed before acknowledgement sent"
Title: Message Title Alexey Shein updated an issue Jenkins / JENKINS-57143 JNLP4 error: "Connection closed before acknowledgement sent" Change By: Alexey Shein Component/s: github-oauth-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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Dax Games edited a comment on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 Same issue here on 1.15.1 and 1.15.2 will see if I can try the PR and report back. I am seeing a slave spin every 10 seconds until one connects. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55013) support for App Center
Title: Message Title Mez Pahlan commented on JENKINS-55013 Re: support for App Center Right, some more updates. I'm going to share what I've got publicly so you can see where it is going and the process is more visible for everyone. I have an appcenter-plugin repo and a branch feature/initial-structure that I'm working on. I want to complete the various API interactions before I can consider publishing this as an alpha candidate. I also need to transfer this over to the main Jenkins CI or on Github but they want to see a working plugin first rather than an empty master branch and a work in progress feature branch. And yes, this means a brand new plugin. The old one has become a crutch to support But my thoughts are that it will be easier to attract contributions on a cleaner code base. Dominik Bartholdi, Marc Steiner, Daniel Adams, Abel Berhane, hicham bagui, Stephan Wezel 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Dax Games commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 Same issue here on 1.15.1 and 1.15.2 will see if I can try the PR and report back. 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. 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 updated an issue Jenkins / JENKINS-56981 VM failed to provision when use Pool Retention Strategy Change By: di wang Attachment: Screen Shot 2019-04-30 at 4.50.40 PM.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. 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 commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy With more testing, I config the max vm nunmber is 4 which the pool size is 1. I submit a branch of requests to trigger it. As it thinks test-vm407940 was failed, then it provisioned another 4 vm. So total is 5 now, more than the max vm number I 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. 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 commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy Oops, please ignore my last comment. Even the same error appears, but the vm provisioned successfully this time. I saw it in the jenkins agent list. However, Cloud Statistics report it failed and no further report of it(test-vm407940), like "Operation time" and etc. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title Andrew Bayer assigned an issue to Liam Newman Jenkins / JENKINS-57257 No commit found for SHA after updating github branch source plugin Change By: Andrew Bayer Assignee: Liam Newman 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46697) Pipeline hangs on allocate node step
Title: Message Title Boris Giftge edited a comment on JENKINS-46697 Re: Pipeline hangs on allocate node step Any update on this? It happens quite frequently for us. (Version 2.164.2) 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. 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
Built a snapshot plugin based on [https://github.com/jenkinsci/azure-vm-agents-plugin/commit/82829b83854244c8e203e67fff7689056a8fd515]Upload the azure-vm-agents.hpi, then restart Jenkins. Check the new pic I uploaded. It is the same error. See new attached pic. From jenkins log, it looks like it thinks it provisioned successfully, but it actually didn't. The latest provision failed but no more attempts after it. Check attached new pic. {quote}Apr 30, 2019 4:17:09 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentApr 30, 2019 4:17:09 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentINFO: AzureVMManagementServiceDelegate: createDeployment: Initializing deployment for agentTemplate test-vmApr 30, 2019 4:17:09 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentINFO: AzureVMManagementServiceDelegate: createDeployment: Creating a new deployment test-vm0430161709407 with VM base name test-vm40794Apr 30, 2019 4:17:10 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentINFO: AzureVMManagementServiceDelegate: createDeployment: Use embedded deployment template (with managed) /referenceImageIDTemplateWithManagedDisk.jsonApr 30, 2019 4:17:10 PM com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask$DeploymentRegistrar registerDeploymentINFO: AzureVMAgentCleanUpTask: registerDeployment: Registering deployment test-vm0430161709407 in cardinal-jenkins-testApr 30, 2019 4:17:13 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgentINFO: AzureVMCloud: createProvisionedAgent: Waiting for deployment test-vm0430161709407 to be completedApr 30, 2019 4:17:43 PM com.microsoft.aad.adal4j.AuthenticationAuthority doInstanceDiscoveryINFO: [Correlation ID: 90fe5df5-b8e3-403c-b4c8-5ad1e8b43a32] Instance discovery was successfulApr 30, 2019 4:17:43 PM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?Apr 30, 2019 4:18:07 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgentINFO: AzureVMCloud: createProvisionedAgent: Deployment test-vm0430161709407 not yet finished (Running): Microsoft.Compute/virtualMachines:test-vm407940 - waited 30 secondsApr 30, 2019 4:18:37 PM com.microsoft.aad.adal4j.AuthenticationAuthority doInstanceDiscoveryINFO: [Correlation ID: 22087788-162d-4386-b453-f33292ef2516] Instance discovery was successfulApr 30, 2019 4:18:38 PM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?Apr 30, 2019 4:18:48 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgentINFO: AzureVMCloud: createProvisionedAgent: VM available: test-vm407940Apr 30, 2019 4:18:49 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate parseResponseINFO: AzureVMManagementServiceDelegate: parseDeploymentResponse: found agent test-vm407940 OS type Linux number of executors 1Apr 30, 2019 4:18:51 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate setVirtualMachineDetailsINFO: The Azure agent doesn't have a public IP. Will use the private IPApr 30, 2019 4:18:51 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate setVirtualMachineDetailsINFO: Azure agent details:nodeNametest-vm407940adminUserName=azure-jenkinsshutdownOnIdle=falseretentionTimeInMin=0labels=packerApr 30, 2019 4:18:51 PM com.microsoft.azure.vmagent.AzureVMCloud$3 callINFO: Azure Cloud: provision: Adding agent test-vm407940 to Jenkins nodesApr 30, 2019 4:18:51 PM
[JIRA] (JENKINS-46697) Pipeline hangs on allocate node step
Title: Message Title Boris Giftge commented on JENKINS-46697 Re: Pipeline hangs on allocate node step Any update on this? It happens quite frequently for us. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title Liam Newman updated JENKINS-57257 Jenkins / JENKINS-57257 No commit found for SHA after updating github branch source plugin Change By: Liam Newman 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. 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
Built a snapshot plugin based on [https://github.com/jenkinsci/azure-vm-agents-plugin/commit/82829b83854244c8e203e67fff7689056a8fd515]Upload the azure-vm-agents.hpi, then restart Jenkins. Check the new pic I uploaded. It is the same error. See new attached pic. From jenkins log, it looks like it thinks it provisioned successfully, but it actually didn't. Check attached new pic. {quote}Apr 30, 2019 4:17:09 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentApr createDeploymentApr 30, 2019 4:17:09 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentINFO: AzureVMManagementServiceDelegate: createDeployment: Initializing deployment for agentTemplate test- vmApr vmApr 30, 2019 4:17:09 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentINFO: AzureVMManagementServiceDelegate: createDeployment: Creating a new deployment test-vm0430161709407 with VM base name test- vm40794Apr vm40794Apr 30, 2019 4:17:10 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentINFO: AzureVMManagementServiceDelegate: createDeployment: Use embedded deployment template (with managed) /referenceImageIDTemplateWithManagedDisk. jsonApr jsonApr 30, 2019 4:17:10 PM com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask$DeploymentRegistrar registerDeploymentINFO: AzureVMAgentCleanUpTask: registerDeployment: Registering deployment test-vm0430161709407 in cardinal-jenkins- testApr testApr 30, 2019 4:17:13 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgentINFO: AzureVMCloud: createProvisionedAgent: Waiting for deployment test-vm0430161709407 to be completedApr completedApr 30, 2019 4:17:43 PM com.microsoft.aad.adal4j.AuthenticationAuthority doInstanceDiscoveryINFO: [Correlation ID: 90fe5df5-b8e3-403c-b4c8-5ad1e8b43a32] Instance discovery was successfulApr successfulApr 30, 2019 4:17:43 PM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? Apr 30, 2019 4:18:07 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgentINFO: AzureVMCloud: createProvisionedAgent: Deployment test-vm0430161709407 not yet finished (Running): Microsoft.Compute/virtualMachines:test-vm407940 - waited 30 secondsApr secondsApr 30, 2019 4:18:37 PM com.microsoft.aad.adal4j.AuthenticationAuthority doInstanceDiscoveryINFO: [Correlation ID: 22087788-162d-4386-b453-f33292ef2516] Instance discovery was successfulApr successfulApr 30, 2019 4:18:38 PM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? Apr 30, 2019 4:18:48 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgentINFO: AzureVMCloud: createProvisionedAgent: VM available: test- vm407940Apr vm407940Apr 30, 2019 4:18:49 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate parseResponseINFO: AzureVMManagementServiceDelegate: parseDeploymentResponse: found agent test-vm407940 OS type Linux number of executors 1Apr 1Apr 30, 2019 4:18:51 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate setVirtualMachineDetailsINFO: The Azure agent doesn't have a public IP. Will use the private IPApr IPApr 30, 2019 4:18:51 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate setVirtualMachineDetailsINFO: Azure agent details:nodeNametest-vm407940adminUserName=azure-jenkinsshutdownOnIdle=falseretentionTimeInMin=0labels= packerApr packerApr 30, 2019 4:18:51 PM
[JIRA] (JENKINS-57254) pipelines view shows 49 years ago -- unix time zero
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-57254 pipelines view shows 49 years ago -- unix time zero Change By: Jesse Glick Component/s: blueocean-plugin Component/s: core Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title Liam Newman started work on JENKINS-57257 Change By: Liam Newman 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. 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 commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy Built a snapshot plugin based on https://github.com/jenkinsci/azure-vm-agents-plugin/commit/82829b83854244c8e203e67fff7689056a8fd515 Upload the azure-vm-agents.hpi, then restart Jenkins. Check the new pic I uploaded. It is the same error. See new attached pic. From jenkins log, it looks like it thinks it provisioned successfully, but it actually didn't. Check attached new pic. Apr 30, 2019 4:17:09 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentApr 30, 2019 4:17:09 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentINFO: AzureVMManagementServiceDelegate: createDeployment: Initializing deployment for agentTemplate test-vmApr 30, 2019 4:17:09 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentINFO: AzureVMManagementServiceDelegate: createDeployment: Creating a new deployment test-vm0430161709407 with VM base name test-vm40794Apr 30, 2019 4:17:10 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentINFO: AzureVMManagementServiceDelegate: createDeployment: Use embedded deployment template (with managed) /referenceImageIDTemplateWithManagedDisk.jsonApr 30, 2019 4:17:10 PM com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask$DeploymentRegistrar registerDeploymentINFO: AzureVMAgentCleanUpTask: registerDeployment: Registering deployment test-vm0430161709407 in cardinal-jenkins-testApr 30, 2019 4:17:13 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgentINFO: AzureVMCloud: createProvisionedAgent: Waiting for deployment test-vm0430161709407 to be completedApr 30, 2019 4:17:43 PM com.microsoft.aad.adal4j.AuthenticationAuthority doInstanceDiscoveryINFO: [Correlation ID: 90fe5df5-b8e3-403c-b4c8-5ad1e8b43a32] Instance discovery was successfulApr 30, 2019 4:17:43 PM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?Apr 30, 2019 4:18:07 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgentINFO: AzureVMCloud: createProvisionedAgent: Deployment test-vm0430161709407 not yet finished (Running): Microsoft.Compute/virtualMachines:test-vm407940 - waited 30 secondsApr 30, 2019 4:18:37 PM com.microsoft.aad.adal4j.AuthenticationAuthority doInstanceDiscoveryINFO: [Correlation ID: 22087788-162d-4386-b453-f33292ef2516] Instance discovery was successfulApr 30, 2019 4:18:38 PM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?Apr 30, 2019 4:18:48 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgentINFO: AzureVMCloud: createProvisionedAgent: VM available: test-vm407940Apr 30, 2019 4:18:49 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate parseResponseINFO: AzureVMManagementServiceDelegate: parseDeploymentResponse: found agent test-vm407940 OS type Linux number of executors 1Apr 30, 2019 4:18:51 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate setVirtualMachineDetailsINFO: The Azure agent doesn't have a public IP. Will use the private IPApr 30, 2019 4:18:51 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate setVirtualMachineDetailsINFO: Azure agent details:nodeNametest-vm407940adminUserName=azure-jenkinsshutdownOnIdle=falseretentionTimeInMin=0labels=packerApr 30, 2019 4:18:51 PM com.microsoft.azure.vmagent.AzureVMCloud$3 callINFO: Azure Cloud: provision: Adding agent test-vm407940 to
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang updated an issue Jenkins / JENKINS-56981 VM failed to provision when use Pool Retention Strategy Change By: di wang Attachment: Screen Shot 2019-04-30 at 4.31.45 PM.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. 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 updated an issue Jenkins / JENKINS-56981 VM failed to provision when use Pool Retention Strategy Change By: di wang Attachment: Screen Shot 2019-04-30 at 4.24.13 PM.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. 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 updated an issue Jenkins / JENKINS-56981 VM failed to provision when use Pool Retention Strategy Change By: di wang Attachment: Screen Shot 2019-04-30 at 4.20.06 PM.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57107) SafeURLStreamHandler does not overwrite openConnection(URL u, Proxy p)
Title: Message Title Jeff Thompson updated JENKINS-57107 Jenkins / JENKINS-57107 SafeURLStreamHandler does not overwrite openConnection(URL u, Proxy p) Change By: Jeff Thompson Status: In Review Resolved Resolution: Fixed Released As: Remoting 3.30 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57107) SafeURLStreamHandler does not overwrite openConnection(URL u, Proxy p)
Title: Message Title Jeff Thompson updated JENKINS-57107 Jenkins / JENKINS-57107 SafeURLStreamHandler does not overwrite openConnection(URL u, Proxy p) Change By: Jeff Thompson 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57107) SafeURLStreamHandler does not overwrite openConnection(URL u, Proxy p)
Title: Message Title Jeff Thompson started work on JENKINS-57107 Change By: Jeff Thompson 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46515) Launcher will retry connections forever under some irrecoverable status
Title: Message Title Jeff Thompson updated JENKINS-46515 Jenkins / JENKINS-46515 Launcher will retry connections forever under some irrecoverable status Change By: Jeff Thompson Status: In Review Closed Resolution: Fixed Released As: Remoting 3.30 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48067) workspace-volume should be optional
Title: Message Title
Bernardo Corrêa edited a comment on JENKINS-48067
Re: workspace-volume should be optional
[~csanchez] Wouldn't adding subPath solve the issue (under Secret Volume)? Then we would be able to specify a subpath and mount secrets as shown bellow: {code:java}volumeMounts: - name: jenkins mountPath: "/home/jenkins/.npmrc" subPath: npmrc readOnly: false volumes: - name: jenkins secret: secretName: jenkins{code} We have a bunch of configuration files under JENKINS_HOME. Would also be nice to be able to have SecurityContext. Or if you have any suggestions on how to get around this issue... Or allowing users to change from emptyDir to secret or ConfigMap... Thanks in advance.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57254) pipelines view shows 49 years ago -- unix time zero
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-57254 pipelines view shows 49 years ago -- unix time zero Change By: Josh Soref Issue Type: New Feature Bug 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57254) pipelines view shows 49 years ago -- unix time zero
Title: Message Title Josh Soref commented on JENKINS-57254 Re: pipelines view shows 49 years ago -- unix time zero The ScoveragePublisher appears to have broken our builds. It caused them to die w/o any remotely helpful explanation. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57254) pipelines view shows 49 years ago -- unix time zero
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-57254 pipelines view shows 49 years ago -- unix time zero Change By: Josh Soref Component/s: scoverage-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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57254) pipelines view shows 49 years ago -- unix time zero
Title: Message Title Josh Soref commented on JENKINS-57254 Re: pipelines view shows 49 years ago -- unix time zero 0 0 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57254) pipelines view shows 49 years ago -- unix time zero
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-57254 pipelines view shows 49 years ago -- unix time zero Change By: Josh Soref Attachment: build.xml 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48067) workspace-volume should be optional
Title: Message Title
Bernardo Corrêa edited a comment on JENKINS-48067
Re: workspace-volume should be optional
[~csanchez] Wouldn't adding subPath solve the issue (under Secret Volume)? Then we would be able to specify a subpath and mount secrets as shown bellow: {code:java}volumeMounts: - name: jenkins mountPath: "/home/jenkins/.npmrc" subPath: npmrc readOnly: false volumes: - name: jenkins secret: secretName: jenkins{code} We have a bunch of configuration that go files under JENKINS_HOME. Would also be nice to be able to have SecurityContext. Or if you have any suggestions on how to get around this issue... Thanks in advance.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48067) workspace-volume should be optional
Title: Message Title Bernardo Corrêa commented on JENKINS-48067 Re: workspace-volume should be optional Carlos Sanchez Wouldn't adding subPath solve the issue (under Secret Volume)? Then we would be able to specify a subpath and mount secrets as shown bellow: volumeMounts: - name: jenkins mountPath: "/home/jenkins/.npmrc" subPath: npmrc readOnly: false volumes: - name: jenkins secret: secretName: jenkins We have a bunch of configuration that go under JENKINS_HOME. Would also be nice to be able to have SecurityContext. Or if you have any suggestions on how to get around this issue... Thanks in advance. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57265) SCM Skip doesn't abort my docker builds until much later
Title: Message Title
Bryce Schober created an issue
Jenkins / JENKINS-57265
SCM Skip doesn't abort my docker builds until much later
Issue Type:
Bug
Assignee:
Gregor Plavčak
Components:
scmskip-plugin
Created:
2019-04-30 19:51
Environment:
Latest LTS Jenkins & plugins SCM Skip v1.01
Priority:
Minor
Reporter:
Bryce Schober
My declarative pipeline builds don't get aborted until much later, for some reason that I don't understand. My Jenkinsfile looks something like:
pipeline {
// Any SkyView Docker agent can build this.
agent {
docker {
label 'docker-host'
image '...'
...
}
}
options {
timestamps()
disableConcurrentBuilds()
buildDiscarder ...
}
environment {
...
}
stages {
stage('Prepare') {
steps {
// Set some options that can't be done in multibranch config GUI, like code browser
checkout(...)
scmSkip(deleteBuild: true, skipPattern: '.*\\[(ci skip|skip ci)\\].*')
}
}
stage ('Unit Tests') {
steps {
...
}
}
stage ('Build') {
steps {
// run the long build script that also commits build number/version files with "[skip ci]"
}
}
stage ('Integration Tests') {
steps {
...
}
}
} // stages
// Post-build steps
post {
always {
// Notify rules
}
success {
archiveArtifacts ...
// Trigger downstream job(s)
}
}
}
My build output looks something
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title Caleb D commented on JENKINS-57257 Re: No commit found for SHA after updating github branch source plugin My observations match James F.. Liam Newman, you're right, the merge commit exists. I can even see it in the GitHub web UI at https://github.com/MY-GITHUB-ORG/REPO/commit/abec08e96270c1de09bb GitHub Branch Source is trying to get commit details by hitting https://api.github.com/repos/MY-GITHUB-USERNAME/REPO/commits/abec08e96270c1de09bb when it seems it should be hitting MY-GITHUB-ORG. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57005) Security warning: Credentials stored in plain text
Title: Message Title Mez Pahlan commented on JENKINS-57005 Re: Security warning: Credentials stored in plain text Hi there Zach Olbrys, sorry for the delay would you mind testing this out if you can grab the built plugin from here https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fhockeyapp-plugin/detail/master/30/artifacts 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57235) Seed job (job-dsl) runs trigger a rebuild of all multibranch pipelines branches
Title: Message Title Jonathan Pigrée updated an issue Jenkins / JENKINS-57235 Seed job (job-dsl) runs trigger a rebuild of all multibranch pipelines branches Change By: Jonathan Pigrée Summary: Seed job (job-dsl) runs trigger a rebuild of all multibranch pipelines branches 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title James F. commented on JENKINS-57257 Re: No commit found for SHA after updating github branch source plugin No problem at all, thanks for working on it! Let me know if you want me to do any more tests/provide any further details about my environment. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57254) pipelines view shows 49 years ago -- unix time zero
Title: Message Title Jesse Glick commented on JENKINS-57254 Re: pipelines view shows 49 years ago -- unix time zero Missing or in build.xml? Hard to know what went wrong here without steps to 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57254) pipelines view shows 49 years ago -- unix time zero
Title: Message Title Jesse Glick commented on JENKINS-57254 Re: pipelines view shows 49 years ago -- unix time zero Missing or in build.xml? Hard to know what went wrong here without steps to 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title Liam Newman commented on JENKINS-57257 Re: No commit found for SHA after updating github branch source plugin James F. Thank you that is really useful information. This is good progress. I think I see where the problem is. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57264) accessing file credential in pipeline causes nullPointerException
Title: Message Title
Mike Alberghini updated an issue
Jenkins / JENKINS-57264
accessing file credential in pipeline causes nullPointerException
Change By:
Mike Alberghini
After a plugin update, one of my pipelines stopped working. It's a groovy script that kicks off packer, which uses ansible to configure an AWS system. After a bit of pairing down, I determined that the pipeline was crashing at the withCredentials([file bit. I stripped the code down to a simple pipeline that demonstrates the error. {quote}pipeline { Unknown macro: \{ agent \ { label 'AWS-Pipeline-Executor' } stages { stage('Build') { steps { withCredentials([file(credentialsId: 'ansible-vault', variable: 'VAULT_PASS_FILE')]) Unknown macro: \ { echo "Inside creds loop" } } } } } {quote} The only output is: [Pipeline] Start of Pipeline[Pipeline] nodeRunning on [AWS-Pipeline-Executor|http://woodhouse.atl.is.keysight.com:8080/computer/AWS-Pipeline-Executor/] in /home/asdc-jenkins/jenkins/workspace/.DevOps/MikeTest[Pipeline] {[Pipeline] stage[Pipeline] { (Build)[Pipeline] } [Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.lang.NullPointerExceptionFinished: FAILURE Attached is the Jenkins log showing the error thrown.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
[JIRA] (JENKINS-57264) accessing file credential in pipeline causes nullPointerException
Title: Message Title Mike Alberghini updated an issue Jenkins / JENKINS-57264 accessing file credential in pipeline causes nullPointerException Change By: Mike Alberghini Attachment: jenkins.log 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title James F. commented on JENKINS-57257 Re: No commit found for SHA after updating github branch source plugin $ git fetch upstream pull/12/head:pr-12-head $ git fetch upstream pull/12/merge:pr-12-merge $ git checkout pr-12-merge Switched to branch 'pr-12-merge' $ git show commit xxxd41940bbc762409886a5e84ef (HEAD -> pr-12-merge) Merge: 4721939 e6f1a82 Author: xx <32715263+x...@users.noreply.github.com> Date: Tue Apr 30 17:09:11 2019 + Merge 5096722968a844f45447 into xx14faf2f0db4199a06cfb17440c209b7 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57264) accessing file credential in pipeline causes nullPointerException
Title: Message Title
Mike Alberghini created an issue
Jenkins / JENKINS-57264
accessing file credential in pipeline causes nullPointerException
Issue Type:
Bug
Assignee:
Unassigned
Components:
credentials-plugin, plain-credentials-plugin
Created:
2019-04-30 18:32
Environment:
Ubuntu 18.04.2 Jenkins 2.175 Credentials Plugin 2.1.18 Plain Credentials Plugin 1.5
Priority:
Major
Reporter:
Mike Alberghini
After a plugin update, one of my pipelines stopped working. It's a groovy script that kicks off packer, which uses ansible to configure an AWS system. After a bit of pairing down, I determined that the pipeline was crashing at the withCredentials([file bit. I stripped the code down to a simple pipeline that demonstrates the error.
pipeline
Unknown macro: { agent { label 'AWS-Pipeline-Executor' }
stages { stage('Build') { steps { withCredentials([file(credentialsId: 'ansible-vault', variable: 'VAULT_PASS_FILE')])
Unknown macro: { echo "Inside creds loop" }
} } } }
The only output is: [Pipeline] Start of Pipeline[Pipeline]
[JIRA] (JENKINS-56996) null permission lookup when pull-request's origin repo/branch is deleted on github
Title: Message Title Christian Höltje commented on JENKINS-56996 Re: null permission lookup when pull-request's origin repo/branch is deleted on github So, the issue is that the updating of all PRs stops, not that this one PR doesn't refresh (which is understandable). Is that correct? The scanning for the entire organization folder (and down) stops, nothing new gets added or removed. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title James F. commented on JENKINS-57257 Re: No commit found for SHA after updating github branch source plugin Liam, I am indeed working on a private repo in the examples I've provided. To me it looks like the query is going to the user the repo is forked by and the commit does not exist there. https://api.github.com/repos/MY-GITHUB-USERNAME/repo/commits/xx5c2b7cd41940bbc762409886a5e84ef <-- this is what is shown in the jenkins error. A query for that commit results in a not found message from the github api but works if I do the same query against my github ORG's username 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title
Liam Newman edited a comment on JENKINS-57257
Re: No commit found for SHA after updating github branch source plugin
[~calebd] [~silverorange] Thanks for taking the time to do this.Are you working on a private repo? I assume that is why you are redacting repo, org, and commit info. I wonder if there's some problem private repo's. [~calebd] " {quote} The produced commit abec08e96270c1de09bb doesn't exist in GitHub. " {quote} I believe the commit does exist, and this feature depends on it existing.Let's see if we can verify that. On a local clone (not on Jenkins): { { git fetch REMOTE pull/PR_ID/head:pr-PR_ID-head ) }} { { git fetch REMOTE pull/PR_ID/merge:pr-PR_ID-merge ) }} REMOTE = remote where the PR is (not your fork, but it's upstream)PR_ID = the PR numberThen if you {git checkout pr-PR_ID-merge} , it should have the SHA. If it doesn't... Well, I'll be very confused. (Based on [ https://help.github.com/en/articles/checking-out-pull-requests-locally ] but with one modification)[~silverorange]{quote}Jenkins is looking for the SHA on the GitHub user the repo was forked by (in which the commits were pushed from). I.e. [ https://api.github.com/repos/MY-GITHUB-USER ] {quote} Could you be a bit more specific? The query should be going to the repo the pull is in not the forked repo. But what you're saying is that the "not found" is coming from the fork?
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title
Liam Newman commented on JENKINS-57257
Re: No commit found for SHA after updating github branch source plugin
Caleb D James F. Thanks for taking the time to do this. Are you working on a private repo? I assume that is why you are redacting repo, org, and commit info. I wonder if there's some problem private repo's. Caleb D "The produced commit abec08e96270c1de09bb doesn't exist in GitHub." I believe the commit does exist, and this feature depends on it existing. Let's see if we can verify that. On a local clone (not on Jenkins): {git fetch REMOTE pull/PR_ID/head:pr-PR_ID-head) {git fetch REMOTE pull/PR_ID/merge:pr-PR_ID-merge) REMOTE = remote where the PR is (not your fork, but it's upstream) PR_ID = the PR number Then if you {git checkout pr-PR_ID-merge} , it should have the SHA. If it doesn't... Well, I'll be very confused. (Based on https://help.github.com/en/articles/checking-out-pull-requests-locally but with one modification) James F.
Jenkins is looking for the SHA on the GitHub user the repo was forked by (in which the commits were pushed from). I.e. https://api.github.com/repos/MY-GITHUB-USER
Could you be a bit more specific? The query should be going to the repo the pull is in not the forked repo. But what you're saying is that the "not found" is coming from the fork?
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57263) Java java.lang.ClassNotFoundException on Jenkins Startup
Title: Message Title
Alex Tol updated an issue
Jenkins / JENKINS-57263
Java java.lang.ClassNotFoundException on Jenkins Startup
Change By:
Alex Tol
Environment:
V 2.164.2, JDK 1.8.0_211, JDK 1.8.0_20 , Tomcat 8.0.14
On startup, Jenkins displays the following errors: {code:java}java.lang.ClassNotFoundException: groovy.grape.GrapeIvyFailed to instantiate optional component hudson.plugins.build_timeout.operations.AbortAndRestartOperation$DescriptorImpl; skippinghudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 errorFailed to instantiate Key[type=org.jenkinsci.plugins.matrixauth.AuthorizationMatrixNodeProperty$DescriptorImpl, annotation=[none]]; skipping this componentjava.lang.ClassNotFoundException: io.jenkins.plugins.casc.BaseConfigurator{code} I have JDK 1.8.0_211 along with JDK 1.8.0_20 and JAVA_HOME set to "C:\Program Files\Java\jdk1.8.0_211" Jenkins is reporting version 1.8.0_20 in System Information. Jenkins is running under Tomcat 8.0.14.
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
[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 I've created a step and implemented the String argumentsToString(Map namedArgs) method and it works most of the time, but it seems that if the argument has and env value in it the argument passed is empty. Is there a way to disable this behaviour or override it? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57263) Java java.lang.ClassNotFoundException on Jenkins Startup
Title: Message Title Alex Tol created an issue Jenkins / JENKINS-57263 Java java.lang.ClassNotFoundException on Jenkins Startup Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-04-30 18:14 Environment: V 2.164.2, JDK 1.8.0_211, JDK 1.8.0_20 Labels: jenkins Priority: Minor Reporter: Alex Tol On startup, Jenkins displays the following errors: java.lang.ClassNotFoundException: groovy.grape.GrapeIvy Failed to instantiate optional component hudson.plugins.build_timeout.operations.AbortAndRestartOperation$DescriptorImpl; skipping hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error Failed to instantiate Key[type=org.jenkinsci.plugins.matrixauth.AuthorizationMatrixNodeProperty$DescriptorImpl, annotation=[none]]; skipping this component java.lang.ClassNotFoundException: io.jenkins.plugins.casc.BaseConfigurator I have JDK 1.8.0_211 along with JDK 1.8.0_20 and JAVA_HOME set to "C:\Program Files\Java\jdk1.8.0_211" Jenkins is reporting version 1.8.0_20 in System Information.
[JIRA] (JENKINS-57249) Can't send message if empty filepath field
Title: Message Title Anton Potsyus updated JENKINS-57249 Jenkins / JENKINS-57249 Can't send message if empty filepath field Change By: Anton Potsyus Status: Fixed but Unreleased Closed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57249) Can't send message if empty filepath field
Title: Message Title Anton Potsyus updated JENKINS-57249 Jenkins / JENKINS-57249 Can't send message if empty filepath field Change By: Anton Potsyus Status: Open Fixed but Unreleased 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title Caleb D edited a comment on JENKINS-57257 Re: No commit found for SHA after updating github branch source plugin After double checking I can confirm the same behavior on my side as [~silverorange] observed. The commit can be seen from the org repo but not the PR author's repo fork. GitHub Branch Source 2.5.0 looks to be querying against the PR author's repo fork which leads to the error . 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title Caleb D edited a comment on JENKINS-57257 Re: No commit found for SHA after updating github branch source plugin After double checking I can confirm the same behavior on my side as [~silverorange] observed. The commit can be seen from the org repo but not the PR author's repo fork. GitHub Branch Source 2.5.0 looks to be querying against the PR author's repo fork. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title Caleb D commented on JENKINS-57257 Re: No commit found for SHA after updating github branch source plugin After double checking I can confirm the same behavior on my side as Sys Admin observed. The commit can be seen from the org repo but not the PR author's repo fork. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Matthew Hall edited a comment on JENKINS-56595 Re: Regression: higher than usual CPU usage with 2.164.1 This sounds almost exactly like our failed upgrade attempt from 2.121.3 to 2.150.3. We were comfortably running with 4GB heap, and then suddenly the CPU was pegged, UI was slow to unresponsive. Had to revert back to 2.121.3. I did grab 1 threaddump [^threaddump-1552681298816.tdump] before reverting. But if you're looking for root cause changes, may want to include >= 2.121.3. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title
Caleb D edited a comment on JENKINS-57257
Re: No commit found for SHA after updating github branch source plugin
In my case, the pull request that I first noticed with this issue existed before updating to 2.5.0. Before 2.5.0 the pipeline timed out while waiting for an approval.After upgrading to 2.5.0 the PR couldn't be built because it immediately failed on the first attempt to interact with GitHub. Builds failed regardless of how the build was triggered, via GitHub webhook or as a rerun inside Jenkins.I also made a brand new PR with different commits and it failed the same way, both via webhook and rerun attempts.Here is a stacktrace with some of the details made private:{noformat}Pull request #1 updated14:14:01 Connecting to https://api.github.com using xx/**GitHub has been notified of this commit’s build resultjava.io.FileNotFoundException: https://api.github.com/repos/xx/xx/commits/abec08e96270c1de09bb at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at org.kohsuke.github.Requester.parse(Requester.java:625) at org.kohsuke.github.Requester.parse(Requester.java:607) at org.kohsuke.github.Requester._to(Requester.java:285)Caused: org.kohsuke.github.GHFileNotFoundException: {"message":"No commit found for SHA: abec08e96270c1de09bb","documentation_url":"https://developer.github.com/v3/repos/commits/#get-a-single-commit"} at org.kohsuke.github.Requester.handleApiError(Requester.java:699) at org.kohsuke.github.Requester._to(Requester.java:306) at org.kohsuke.github.Requester.to(Requester.java:247) at org.kohsuke.github.GHRepository.getCommit(GHRepository.java:973) at org.jenkinsci.plugins.github_branch_source.PullRequestSCMRevision.validateMergeHash(PullRequestSCMRevision.java:118) at org.jenkinsci.plugins.github_branch_source.GitHubSCMFileSystem.(GitHubSCMFileSystem.java:91) at org.jenkinsci.plugins.github_branch_source.GitHubSCMFileSystem$BuilderImpl.build(GitHubSCMFileSystem.java:296) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:294) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:103) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{noformat}From the pull request event log:{noformat}Changes detected: PR-1 (723d39265d8c2206c7f9+e1ca98cf39f9c2c75b54 (UNKNOWN_MERGE_STATE) → 0b218e1baa39a7af38ca+e1ca98cf39f9c2c75b54 (abec08e96270c1de09bb))Scheduled build for branch: PR-1{noformat}Where {{e1ca98cf39f9c2c75b54}} is the master branch commit.The produced commit {{abec08e96270c1de09bb}} doesn exists as part of the org but not the PR author ' t exist in GitHub s repo fork .
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Matthew Hall edited a comment on JENKINS-56595 Re: Regression: higher than usual CPU usage with 2.164.1 This sounds almost exactly like our failed upgrade attempt from 2.121.3 to 2.150.3. We were comfortably running with 4GB heap, and then suddenly the CPU was pegged, UI was slow to unresponsive. Had to revert back to 2.121.3. Sadly, I did not grab any thread dumps at the time 1 threaddump before reverting . But if you're looking for root cause changes, may want to include >= 2.121.3. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Matthew Hall updated an issue Jenkins / JENKINS-56595 Regression: higher than usual CPU usage with 2.164.1 Change By: Matthew Hall Attachment: threaddump-1552681298816.tdump 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title Sys Admin edited a comment on JENKINS-57257 Re: No commit found for SHA after updating github branch source plugin So to add a little more information here. Forgive me, I'm not an expert on this subject. Jenkins is looking for the SHA on the GitHub user the repo was forked by (in which the commits were pushed from). I.e. [https://api.github.com/repos/MY-GITHUB-USER|https://api.github.com/repos/jaymefSO/emrap-corependium/commits/a34ba369c5c2b7cd41940bbc762409886a5e84ef] If I query the github API for htps://api.github.com/repos/[MY-GITHUB-USER|https://api.github.com/repos/jaymefSO/emrap-corependium/commits/a34ba369c5c2b7cd41940bbc762409886a5e84ef]/MY-REPO/pulls I get nothing returned (because there are no PRs under my fork). If I query the user (our org's github username) in which the commits were pushed to I get results returned. Could this issue be related to how the PR is opened from a user's fork? I get info about the commit SHA if I query: api.github.com/repos/MY-ORGS-GITHUB-ACCOUNT/xx/commits/xx7cd41940bbc762409886a5e84ef but not if I query my user account in which the PR was opened from: // api.github.com/repos/MY-GITHUB-USER/x/commits/7cd41940bbc762409886a5e84ef 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title Sys Admin edited a comment on JENKINS-57257 Re: No commit found for SHA after updating github branch source plugin So to add a little more information here. Forgive me, I'm not an expert on this subject. Jenkins is looking for the SHA on the GitHub user the repo was forked by (in which the commits were pushed from). I.e. [https://api.github.com/repos/MY-GITHUB-USER|https://api.github.com/repos/jaymefSO/emrap-corependium/commits/a34ba369c5c2b7cd41940bbc762409886a5e84ef] If I query the github API for htps://api.github.com/repos/[MY-GITHUB-USER|https://api.github.com/repos/jaymefSO/emrap-corependium/commits/a34ba369c5c2b7cd41940bbc762409886a5e84ef]/MY-REPO/pulls I get nothing returned (because there are no PRs under my fork). If I query the user (our org's github username) in which the commits were pushed to I get results returned. Could this issue be related to how the PR is opened from a user's fork? I get info about the commit SHA if I query: api.github.com/repos/MY-ORGS-GITHUB-ACCOUNT/xx/commits/xx7cd41940bbc762409886a5e84ef but not if I query my user account in which the PR was opened from: //api.github.com/repos/MY-GITHUB-USER/x/commits/7cd41940bbc762409886a5e84ef 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Matthew Hall commented on JENKINS-56595 Re: Regression: higher than usual CPU usage with 2.164.1 This sounds almost exactly like our failed upgrade attempt from 2.121.3 to 2.150.3. We were comfortably running with 4GB heap, and then suddenly the CPU was pegged, UI was slow to unresponsive. Had to revert back to 2.121.3. Sadly, I did not grab any thread dumps at the time. But if you're looking for root cause changes, may want to include >= 2.121.3. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title Sys Admin edited a comment on JENKINS-57257 Re: No commit found for SHA after updating github branch source plugin So to add a little more information here. Forgive me, I'm not an expert on this subject. Jenkins is looking for the SHA on the GitHub user the repo was forked by (in which the commits were pushed from). I.e. [https://api.github.com/repos/MY-GITHUB-USER|https://api.github.com/repos/jaymefSO/emrap-corependium/commits/a34ba369c5c2b7cd41940bbc762409886a5e84ef] If I query the github API for htps://api.github.com/repos/[MY-GITHUB-USER|https://api.github.com/repos/jaymefSO/emrap-corependium/commits/a34ba369c5c2b7cd41940bbc762409886a5e84ef]/MY-REPO/pulls I get nothing returned (because there are no PRs under my fork). If I query the user (our org's github username) in which the commits were pushed to I get results returned. Could this issue be related to how the PR is opened from a user's fork? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title Sys Admin edited a comment on JENKINS-57257 Re: No commit found for SHA after updating github branch source plugin So to add a little more information here. Forgive me, I'm not an expert on this subject. Jenkins is looking for the SHA on the GitHub user the repo was forked by (in which the commits were pushed from). I.e. [https://api.github.com/repos/MY-GITHUB-USER|https://api.github.com/repos/jaymefSO/emrap-corependium/commits/a34ba369c5c2b7cd41940bbc762409886a5e84ef] If I query the github API for htps://api.github.com/repos/[MY-GITHUB-USER|https://api.github.com/repos/jaymefSO/emrap-corependium/commits/a34ba369c5c2b7cd41940bbc762409886a5e84ef]/MY-REPO/pulls I get nothing returned (because there are no PRs under my fork). If I query the user (our org's github username) in which the commits were pushed to I get results returned. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title Sys Admin commented on JENKINS-57257 Re: No commit found for SHA after updating github branch source plugin So to add a little more information here. Forgive me, I'm not an expert on this subject. Jenkins is looking for the SHA on the GitHub user the repo was forked by (in which the commits were pushed from). I.e. https://api.github.com/repos/MY-GITHUB-USER If I query the github API for htps://api.github.com/repos/MY-GITHUB-USER/MY-REPO/pulls I get nothing returned (because there are no PRs under my fork). If I query the user in which the commits were pushed to I get results returned. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title
Caleb D edited a comment on JENKINS-57257
Re: No commit found for SHA after updating github branch source plugin
In my case, the pull request that I first noticed with this issue existed before updating to 2.5.0. Before 2.5.0 it failed due to the pipeline timed out while waiting for an actual code issue approval . After upgrading to 2.5.0 the PR couldn't be built because it immediately failed on the first attempt to interact with GitHub. Builds failed regardless of how the build was triggered, via GitHub webhook or as a rerun inside Jenkins.I also made a brand new PR with different commits and it failed the same way, both via webhook and rerun attempts.Here is a stacktrace with some of the details made private:{noformat}Pull request #1 updated14:14:01 Connecting to https://api.github.com using xx/**GitHub has been notified of this commit’s build resultjava.io.FileNotFoundException: https://api.github.com/repos/xx/xx/commits/abec08e96270c1de09bb at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at org.kohsuke.github.Requester.parse(Requester.java:625) at org.kohsuke.github.Requester.parse(Requester.java:607) at org.kohsuke.github.Requester._to(Requester.java:285)Caused: org.kohsuke.github.GHFileNotFoundException: {"message":"No commit found for SHA: abec08e96270c1de09bb","documentation_url":"https://developer.github.com/v3/repos/commits/#get-a-single-commit"} at org.kohsuke.github.Requester.handleApiError(Requester.java:699) at org.kohsuke.github.Requester._to(Requester.java:306) at org.kohsuke.github.Requester.to(Requester.java:247) at org.kohsuke.github.GHRepository.getCommit(GHRepository.java:973) at org.jenkinsci.plugins.github_branch_source.PullRequestSCMRevision.validateMergeHash(PullRequestSCMRevision.java:118) at org.jenkinsci.plugins.github_branch_source.GitHubSCMFileSystem.(GitHubSCMFileSystem.java:91) at org.jenkinsci.plugins.github_branch_source.GitHubSCMFileSystem$BuilderImpl.build(GitHubSCMFileSystem.java:296) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:294) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:103) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{noformat}From the pull request event log:{noformat}Changes detected: PR-1 (723d39265d8c2206c7f9+e1ca98cf39f9c2c75b54 (UNKNOWN_MERGE_STATE) → 0b218e1baa39a7af38ca+e1ca98cf39f9c2c75b54 (abec08e96270c1de09bb))Scheduled build for branch: PR-1{noformat}Where {{e1ca98cf39f9c2c75b54}} is the master branch commit.The produced commit {{abec08e96270c1de09bb}} doesn't exist in GitHub.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title
Caleb D edited a comment on JENKINS-57257
Re: No commit found for SHA after updating github branch source plugin
In my case, the pull request that I first noticed with this issue existed before updating to 2.5.0. Before 2.5.0 it failed due to an actual code issue. After upgrading to 2.5.0 the PR couldn't be built because it immediately failed on the first attempt to interact with GitHub. Builds failed regardless of how the build was triggered, via GitHub webhook or as a rerun inside Jenkins.I also made a brand new PR with different commits and it failed the same way, both via webhook and rerun attempts.Here is a stacktrace with some of the details made private:{noformat}Pull request #1 updated14:14:01 Connecting to https://api.github.com using ** xx /**GitHub has been notified of this commit’s build resultjava.io.FileNotFoundException: https://api.github.com/repos/ ** xx / ** xx /commits/ abec08e96270c1de09bb abec08e96270c1de09bb at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at org.kohsuke.github.Requester.parse(Requester.java:625) at org.kohsuke.github.Requester.parse(Requester.java:607) at org.kohsuke.github.Requester._to(Requester.java:285)Caused: org.kohsuke.github.GHFileNotFoundException: {"message":"No commit found for SHA: abec08e96270c1de09bb abec08e96270c1de09bb ","documentation_url":"https://developer.github.com/v3/repos/commits/#get-a-single-commit"} at org.kohsuke.github.Requester.handleApiError(Requester.java:699) at org.kohsuke.github.Requester._to(Requester.java:306) at org.kohsuke.github.Requester.to(Requester.java:247) at org.kohsuke.github.GHRepository.getCommit(GHRepository.java:973) at org.jenkinsci.plugins.github_branch_source.PullRequestSCMRevision.validateMergeHash(PullRequestSCMRevision.java:118) at org.jenkinsci.plugins.github_branch_source.GitHubSCMFileSystem.(GitHubSCMFileSystem.java:91) at org.jenkinsci.plugins.github_branch_source.GitHubSCMFileSystem$BuilderImpl.build(GitHubSCMFileSystem.java:296) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:294) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:103) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{noformat}From the pull request event log:{noformat}Changes detected: PR-1 ( 723d39265d8c2206c7f9 723d39265d8c2206c7f9 + e1ca98cf39f9c2c75b54 e1ca98cf39f9c2c75b54 (UNKNOWN_MERGE_STATE) → 0b218e1baa39a7af38ca 0b218e1baa39a7af38ca + e1ca98cf39f9c2c75b54 e1ca98cf39f9c2c75b54 ( abec08e96270c1de09bb abec08e96270c1de09bb ))Scheduled build for branch: PR-1{noformat}Where {{ e1ca98cf39f9c2c75b54 e1ca98cf39f9c2c75b54 }} is the master branch commit.The produced commit {{ abec08e96270c1de09bb abec08e96270c1de09bb }} doesn't exist in GitHub.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title
Caleb D commented on JENKINS-57257
Re: No commit found for SHA after updating github branch source plugin
In my case, the pull request that I first noticed with this issue existed before updating to 2.5.0. Before 2.5.0 it failed due to an actual code issue. After upgrading to 2.5.0 the PR couldn't be built because it immediately failed on the first attempt to interact with GitHub. Builds failed regardless of how the build was triggered, via GitHub webhook or as a rerun inside Jenkins. I also made a brand new PR with different commits and it failed the same way, both via webhook and rerun attempts. Here is a stacktrace with some of the details made private:
Pull request #1 updated
14:14:01 Connecting to https://api.github.com using **/**
GitHub has been notified of this commit’s build result
java.io.FileNotFoundException: https://api.github.com/repos/**/**/commits/abec08e96270c1de09bb
at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243)
at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210)
at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25)
at org.kohsuke.github.Requester.parse(Requester.java:625)
at org.kohsuke.github.Requester.parse(Requester.java:607)
at org.kohsuke.github.Requester._to(Requester.java:285)
Caused: org.kohsuke.github.GHFileNotFoundException: {"message":"No commit found for SHA: abec08e96270c1de09bb","documentation_url":"https://developer.github.com/v3/repos/commits/#get-a-single-commit"}
at org.kohsuke.github.Requester.handleApiError(Requester.java:699)
at org.kohsuke.github.Requester._to(Requester.java:306)
at org.kohsuke.github.Requester.to(Requester.java:247)
at org.kohsuke.github.GHRepository.getCommit(GHRepository.java:973)
at org.jenkinsci.plugins.github_branch_source.PullRequestSCMRevision.validateMergeHash(PullRequestSCMRevision.java:118)
at org.jenkinsci.plugins.github_branch_source.GitHubSCMFileSystem.(GitHubSCMFileSystem.java:91)
at org.jenkinsci.plugins.github_branch_source.GitHubSCMFileSystem$BuilderImpl.build(GitHubSCMFileSystem.java:296)
at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:294)
at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:103)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Finished: FAILURE
From the pull request event log:
Changes detected: PR-1 (723d39265d8c2206c7f9+e1ca98cf39f9c2c75b54 (UNKNOWN_MERGE_STATE) → 0b218e1baa39a7af38ca+e1ca98cf39f9c2c75b54 (abec08e96270c1de09bb))
Scheduled build for branch: PR-1
Where e1ca98cf39f9c2c75b54 is the master branch commit. The produced commit
[JIRA] (JENKINS-57235) Seed job runs trigger a rebuild of all multibranch pipelines branches
Title: Message Title Jonathan Pigrée updated an issue Jenkins / JENKINS-57235 Seed job runs trigger a rebuild of all multibranch pipelines branches Change By: Jonathan Pigrée I have a fully configured as code jenkins deployed in GKE using the official Helm [chart|[https://github.com/helm/charts/tree/master/stable/jenkins]] (version 0.33.1). I also use a seed job (pre-installed by the chart) which creates all the other jobs.My problem is that each time someone triggers the seed job, it triggers a branch indexing in every existing multibranch pipelines. Those branch indexing trigger a build for every branches discovered even when they were already previously discovered and build before .The consequence is that we get huge build spikes each time someone runs the jenkins seed. I searched the web for months for a fix but all I could find was workarounds. The latest I put in place is to install the "Basic Branch Strategy plugin" and enforce the newly added "skip initial build on first branch indexing" strategy on all my multibranch pipelines. It fixed my problem but the downside is that, my newly discovered branches stopped building automatically so the workaround isn't satisfying.From what I understood, the seed job recreates all its managed jobs it manages every time it is run, so I guess the problem must come from there but I don't know how to confirm it.I can debug this further but I will need a bit of help (debugging tips).To me the solutions are: * Fix either the seed or the way the multibranch pipelines handles recreation. * Create a basic branch strategy which filters an initial trigger when the branch was already built before and the current commit is the same than the previous build's.I can provide further information if needed. I can even submit a fix if it is trivial/simple (I am not a Java developer). Thanks for your help! Add Comment
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title
Sys Admin edited a comment on JENKINS-57257
Re: No commit found for SHA after updating github branch source plugin
Liam, here are the steps I followed. Hope this is helpful: # Updated github branch source plugin to 2.5.0 again # Closed PR #12 (same PR as mentioned in original post). # Re-opened PR #12In jenkins the closing of the PR spawned a CI check which failed with similar error as before. Pull request #12 closedConnecting to [ https://api.github.com |https://api.github.com/] using /** ( sogitbot Github Personal Access Token) GitHub has been notified of this commit’s build resultjava.io.FileNotFoundException: [ https://api.github.com/repos/xx/x/commits/dbe80d1e82bf97cb9e6ae867 ] at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at org.kohsuke.github.Requester.parse(Requester.java:625) at org.kohsuke.github.Requester.parse(Requester.java:607) at org.kohsuke.github.Requester._to(Requester.java:285)Caused: org.kohsuke.github.GHFileNotFoundException: \{"message":"No commit found for SHA: c14dbe80d1e82bf97cb9e6ae867","documentation_url":"https://developer.github.com/v3/repos/commits/#get-a-single-commit"} at org.kohsuke.github.Requester.handleApiError(Requester.java:699) at org.kohsuke.github.Requester._to(Requester.java:306) at org.kohsuke.github.Requester.to(Requester.java:247) at org.kohsuke.github.GHRepository.getCommit(GHRepository.java:973) at org.jenkinsci.plugins.github_branch_source.PullRequestSCMRevision.validateMergeHash(PullRequestSCMRevision.java:118) at org.jenkinsci.plugins.github_branch_source.GitHubSCMFileSystem.(GitHubSCMFileSystem.java:91) at org.jenkinsci.plugins.github_branch_source.GitHubSCMFileSystem$BuilderImpl.build(GitHubSCMFileSystem.java:296) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:294) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:103) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE The GitHub PR re-open process did not seem to spawn a new CI run so I added a new commit, the new commit spawned CI which also failed: Pull request #12 updatedConnecting to [ https://api.github.com |https://api.github.com/] using xx/** (x Github Personal Access Token)GitHub has been notified of this commit’s build resultjava.io.FileNotFoundException: [ https://api.github.com/repos/xxx/xxx/commits/c2b7cd41940bbc762409886a5e84ef ] at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at org.kohsuke.github.Requester.parse(Requester.java:625) at org.kohsuke.github.Requester.parse(Requester.java:607) at org.kohsuke.github.Requester._to(Requester.java:285)Caused: org.kohsuke.github.GHFileNotFoundException: \{"message":"No commit found for SHA: xxx7cd41940bbc762409886a5e84ef","documentation_url":"https://developer.github.com/v3/repos/commits/#get-a-single-commit"} at org.kohsuke.github.Requester.handleApiError(Requester.java:699)
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title
Sys Admin commented on JENKINS-57257
Re: No commit found for SHA after updating github branch source plugin
Liam, here are the steps I followed. Hope this is helpful:
Updated github branch source plugin to 2.5.0 again
Closed PR #12 (same PR as mentioned in original post).
Re-opened PR #12
In jenkins the closing of the PR spawned a CI check which failed with similar error as before. Pull request #12 closed Connecting to https://api.github.com using /** (sogitbot Github Personal Access Token) GitHub has been notified of this commit’s build result java.io.FileNotFoundException: https://api.github.com/repos/xx/x/commits/dbe80d1e82bf97cb9e6ae867 at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at org.kohsuke.github.Requester.parse(Requester.java:625) at org.kohsuke.github.Requester.parse(Requester.java:607) at org.kohsuke.github.Requester._to(Requester.java:285) Caused: org.kohsuke.github.GHFileNotFoundException: {"message":"No commit found for SHA: c14dbe80d1e82bf97cb9e6ae867","documentation_url":"https://developer.github.com/v3/repos/commits/#get-a-single-commit"} at org.kohsuke.github.Requester.handleApiError(Requester.java:699) at org.kohsuke.github.Requester._to(Requester.java:306) at org.kohsuke.github.Requester.to(Requester.java:247) at org.kohsuke.github.GHRepository.getCommit(GHRepository.java:973) at org.jenkinsci.plugins.github_branch_source.PullRequestSCMRevision.validateMergeHash(PullRequestSCMRevision.java:118) at org.jenkinsci.plugins.github_branch_source.GitHubSCMFileSystem.(GitHubSCMFileSystem.java:91) at org.jenkinsci.plugins.github_branch_source.GitHubSCMFileSystem$BuilderImpl.build(GitHubSCMFileSystem.java:296) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:294) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:103) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE The GitHub PR re-open process did not seem to spawn a new CI run so I added a new commit, the new commit spawned CI which also failed: Pull request #12 updated Connecting to https://api.github.com using xx/** (x Github Personal Access Token) GitHub has been notified of this commit’s build result java.io.FileNotFoundException: https://api.github.com/repos/xxx/xxx/commits/c2b7cd41940bbc762409886a5e84ef at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at org.kohsuke.github.Requester.parse(Requester.java:625) at org.kohsuke.github.Requester.parse(Requester.java:607) at org.kohsuke.github.Requester._to(Requester.java:285) Caused: org.kohsuke.github.GHFileNotFoundException: {"message":"No commit
[JIRA] (JENKINS-57116) Version 1.15.1 does not create pods
Title: Message Title Carlos Sanchez commented on JENKINS-57116 Re: Version 1.15.1 does not create pods This error is caused by empty yaml fields but I don't see how it is triggered. In any case I added some safeguards in a PR that should fix it https://github.com/jenkinsci/kubernetes-plugin/pull/462 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57116) Version 1.15.1 does not create pods
Title: Message Title Carlos Sanchez updated JENKINS-57116 Jenkins / JENKINS-57116 Version 1.15.1 does not create pods Change By: Carlos Sanchez 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title
Liam Newman edited a comment on JENKINS-57257
Re: No commit found for SHA after updating github branch source plugin
[~calebd]Stack trace would be helpful. Also, is this occurring when scanning the PR or from github hook? Has the PR that is failing been around a while untouched or has it been opened/updated recently? [~silverorange], [~calebd]The commit sha that 2.5.0 is looking for is the {merge_commit_sha} of the PR. If you query the PR via the GitHub API, that is where you will see this SHA. The reason I'm asking you to try closing and reopening the PR in question is that I believe closing and reopening will cause GitHub to generate a new {merge_commit_sha} that is valid. Could you please give that a try? To be clear, there is still a bug here and I'm working on that, but I want to make sure my theory is correct so I'm fixing the right thing.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57262) scmSkip could provide a multi-branch pipeline build strategy
Title: Message Title Bryce Schober created an issue Jenkins / JENKINS-57262 scmSkip could provide a multi-branch pipeline build strategy Issue Type: Bug Assignee: Gregor Plavčak Components: scmskip-plugin Created: 2019-04-30 17:04 Environment: Latest Jenkins LTS Priority: Minor Reporter: Bryce Schober It sure would be nice if the SCM Skip plugin could present a unified method across SCM types for skipping multibranch pipeline commits based on commit message. Currently, the SVN plugin doesn't support its commit message or author exclusions as multibranch pipeline build strategies, and the Git plugin's support for them is not extended across SCMs. Add Comment
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title
Liam Newman edited a comment on JENKINS-57257
Re: No commit found for SHA after updating github branch source plugin
[~calebd]Stack trace would be helpful. Also, is this occurring when scanning the PR or from github hook? [~silverorange] , [~calebd]The commit sha that 2.5.0 is looking for is the {merge_commit_sha} of the PR. If you query the PR via the GitHub API, that is where you will see this SHA. The reason I'm asking you to try closing and reopening the PR in question is that I believe closing and reopening will cause GitHub to generate a new {merge_commit_sha} that is valid. Could you please give that a try? To be clear, there is still a bug here and I'm working on that, but I want to make sure my theory is correct so I'm fixing the right thing.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57257) No commit found for SHA after updating github branch source plugin
Title: Message Title
Liam Newman commented on JENKINS-57257
Re: No commit found for SHA after updating github branch source plugin
Caleb D Stack trace would be helpful. Also, is this occurring when scanning the PR or from github hook? Sys AdminCaleb D The commit sha that 2.5.0 is looking for is the {merge_commit_sha} of the PR. If you query the PR via the GitHub API, that is where you will see this SHA. The reason I'm asking you to try closing and reopening the PR in question is that I believe closing and reopening will cause GitHub to generate a new {merge_commit_sha} that is valid. Could you please give that a try? To be clear, there is still a bug here and I'm working on that, but I want to make sure my theory is correct so I'm fixing the right thing.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57261) Can't use pipeline job as promotion criterion
Title: Message Title Ben Gottesman created an issue Jenkins / JENKINS-57261 Can't use pipeline job as promotion criterion Issue Type: Bug Assignee: Devin Nusbaum Components: core, pipeline, promoted-builds-plugin Created: 2019-04-30 16:41 Environment: Jenkins ver. 2.164.2 Priority: Major Reporter: Ben Gottesman If you configure a job to have a promotion process, and a criterion for promotion is that a downstream project builds successfully, then that criterion is ignored if that downstream project is a pipeline project. I suspect that this has the same underlying cause as JENKINS-45912, namely that the upstream/downstream link between the jobs is lost somehow. Add Comment
[JIRA] (JENKINS-56558) Environment variables get polluted from nodes
Title: Message Title Amos Hason commented on JENKINS-56558 Re: Environment variables get polluted from nodes Workaround: use HTTPS credentials. 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. For more options, visit https://groups.google.com/d/optout.
