[JIRA] (JENKINS-55360) language bug
Title: Message Title lockheed qi created an issue Jenkins / JENKINS-55360 language bug Issue Type: Bug Assignee: lockheed qi Attachments: WechatIMG9.png Components: locale-plugin Created: 2018-12-29 07:40 Environment: jenkins Version:2.150.1 MacOSX:10.14.2 Tomcat:8.5.37 Priority: Major Reporter: lockheed qi hello,i am a developer from China.when I use the Long-term Support (LTS) Version,i found that my local language setting has some problem,part of my view are English ,and the other are Chinese,then i delete my Jenkins ,i install version 2.138.4,the problem has resolved. Add Comment
[JIRA] (JENKINS-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title Nikita Nadezhin updated an issue Jenkins / JENKINS-54557 hudson.AbortException: Ansible playbook execution failed Change By: Nikita Nadezhin Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29144) SimpleBuildStep to receive EnvVars
Title: Message Title
Jeremy Marshall commented on JENKINS-29144
Re: SimpleBuildStep to receive EnvVars
How come the CHANGE_URL env variable is defined in multi-branch pipeline jobs (PRs) and this is accessible by adding to a publish/post step
public boolean prepare(final Run run) {
Map env = null;
try {
env = getEnvironment(run, new LogTaskListener(LOGGER, Level.INFO));
env.forEach((k, v) -> log("key: " + k + " value:" + v));
.
.
.
but GIT_URL and GIT_BRANCH is not? I'm trying to push from the warnings post step to the PR in Github. So far I can do it from a freestyle job and a PR in a multi branch pipeline but not in a standard pipeline, mainly because I can't derive the github url or github branch
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-54724) ssh-credentials-plugin broken when using ssh-slaves-plugin 1.29.0
Title: Message Title cowwoc commented on JENKINS-54724 Re: ssh-credentials-plugin broken when using ssh-slaves-plugin 1.29.0 Nevermind. Upgrading to version 1.29.4 of this plugin fixes the problem. Thank you. 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-54724) ssh-credentials-plugin broken when using ssh-slaves-plugin 1.29.0
Title: Message Title cowwoc commented on JENKINS-54724 Re: ssh-credentials-plugin broken when using ssh-slaves-plugin 1.29.0 Ivan Fernandez Calvo I don't have trilead-api plugin installed and yet I am getting this error in version 1.29.2 of this plugin. Please reopen this bug. It is not 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-55325) System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline
Title: Message Title Daniel Qian commented on JENKINS-55325 Re: System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline Cyrille Le Clerc I don't know, but I keep the content part untouched. See figure below: BTW, I downgrade plugin to v3.6.5 no error shows 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-55325) System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline
Title: Message Title Daniel Qian edited a comment on JENKINS-55325 Re: System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline [~cleclerc] I don't know, but I keep the content part untouched. See figure below:!qq20181229-090...@2x.png|thumbnail!BTW, I downgrade plugin to v3.6.5 no error shows up 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-55325) System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline
Title: Message Title Daniel Qian updated an issue Jenkins / JENKINS-55325 System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline Change By: Daniel Qian Attachment: qq20181229-090...@2x.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-55328) recordIssues and ScanForIssues in Pipeline get NPE Errors
Title: Message Title Ulli Hafner updated JENKINS-55328 Jenkins / JENKINS-55328 recordIssues and ScanForIssues in Pipeline get NPE Errors Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: 1.0.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53104) Use symbols (Id) of parser rather than the class name of tool
Title: Message Title Ulli Hafner updated JENKINS-53104 Jenkins / JENKINS-53104 Use symbols (Id) of parser rather than the class name of tool Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 1.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-52463) Each SonarQube parser should skip files of other SonarQube parsers
Title: Message Title Ulli Hafner updated JENKINS-52463 Jenkins / JENKINS-52463 Each SonarQube parser should skip files of other SonarQube parsers Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 1.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-54759) Groovy Parsers - improve help text
Title: Message Title Ulli Hafner updated JENKINS-54759 Jenkins / JENKINS-54759 Groovy Parsers - improve help text Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 1.0.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53938) Warnings plugin 'Record static analysis results - GNU Make + GNU C Compiler (gcc)’ gives exception with Java 10
Title: Message Title Ulli Hafner updated JENKINS-53938 Jenkins / JENKINS-53938 Warnings plugin 'Record static analysis results - GNU Make + GNU C Compiler (gcc)’ gives exception with Java 10 Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 1.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-54398) Report encoding error if fingerprinter fails to read a source code
Title: Message Title Ulli Hafner updated JENKINS-54398 Jenkins / JENKINS-54398 Report encoding error if fingerprinter fails to read a source code Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 1.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-55293) Unable to set healthy levels to 0
Title: Message Title Ulli Hafner updated JENKINS-55293 Jenkins / JENKINS-55293 Unable to set healthy levels to 0 Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 1.0.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55328) recordIssues and ScanForIssues in Pipeline get NPE Errors
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55328 recordIssues and ScanForIssues in Pipeline get NPE Errors Change By: Ulli Hafner Released As: warnings-ng 1.0.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55337) MavenConsole tool reports errors with dead links.
Title: Message Title Ulli Hafner updated JENKINS-55337 Jenkins / JENKINS-55337 MavenConsole tool reports errors with dead links. Change By: Ulli Hafner 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-55359) Add view of Warning Results in Blue Ocean
Title: Message Title Ulli Hafner commented on JENKINS-55359 Re: Add view of Warning Results in Blue Ocean This requires that someone of the blue ocean team actually implements JEP203. I have a bad feeling about that, see mailing list discussion. 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-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-55356
Some workflow jobs fail after restart on Java 11 server
Change By:
Mark Waite
While running Java 11 based Jenkins in a docker container using a pre-release of the workflow support plugin which includes the fix for the null pointer exception, a {code}jenkins-url/safeRestart{code} will cause several of the Pipeline jobs that were running to fail when Jenkins tries to resume the jobs.Build log output from the failed builds has included messages like (seems to be windows specific):{noformat}07:40:50 [INFO] Running org.jenkinsci.plugins.gitclient.PushTestResuming build at Fri Dec 28 07:48:06 MST 2018 after Jenkins restartWaiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #6: Waiting for next available executor on ‘coleen-pc2-ssh’Ready to run at Fri Dec 28 07:48:49 MST 201807:48:49 Timeout set to expire in 17 min[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // node[Pipeline] }07:48:50 Failed in branch windows-8-2.150.1[Pipeline] // parallel[Pipeline] }[Pipeline] // timestamps[Pipeline] End of PipelineERROR: missing workspace C:\J\S\workspace\der_git-client-pipeline_beta-3.0 on coleen-pc2-ssh{noformat}and this (seems to fail on Windows and on Linux):{noformat}08:48:33 [INFO] [ hpi ]-Resuming build at Fri Dec 28 08:51:46 MST 2018 after Jenkins restartWaiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: Waiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: ??Waiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: ???Waiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: ???Ready to run at Fri Dec 28 08:52:07 MST 201808:52:07 Timeout set to expire in 54 min08:52:07 Timeout set to expire in 54 min08:52:07 Timeout set to expire in 54 min08:52:07 Timeout set to expire in 54 min[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] }[Pipeline] // stage[Pipeline] // withEnv[Pipeline] }[Pipeline] }[Pipeline] // timeout[Pipeline] // stage[Pipeline] }[Pipeline] }[Pipeline] // node[Pipeline] // timeout[Pipeline] }08:52:08 Failed in branch windows-8[Pipeline] }[Pipeline] // node[Pipeline] }08:52:08 Failed in branch windows-8-2.150.108:57:14 process apparently never started in /home/mwaite/testing-a.markwaite.net-agent/workspace/der_git-client-pipeline_beta-3.0@tmp/durable-3af9d572[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // timeout[Pipeline] }08:57:14 process apparently never started in /home/mwaite/testing-a.markwaite.net-agent/workspace/der_git-client-pipeline_beta-3.0@tmp/durable-1ba13955[Pipeline] // node[Pipeline] }08:57:14 Failed in branch linux-8[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] //
[JIRA] (JENKINS-54746) Can't connect via SSH on 1.29.1
Title: Message Title Darryl Pogue commented on JENKINS-54746 Re: Can't connect via SSH on 1.29.1 I've updated to 1.29.4, uninstalled the Trilead API plugin, and I'm still getting the same result. Downgrading the plugin fixes it. Unreadable data page says: ConversionException: Could not call com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$UsersPrivateKeySource.readResolve() : anonymous is missing the Overall/RunScripts permission : Could not call com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$UsersPrivateKeySource.readResolve() : anonymous is missing the Overall/RunScripts permission Debugging information message : Could not call com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$UsersPrivateKeySource.readResolve() : anonymous is missing the Overall/RunScripts permission cause-exception : com.thoughtworks.xstream.converters.reflection.ObjectAccessException cause-message : Could not call com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$UsersPrivateKeySource.readResolve() : anonymous is missing the Overall/RunScripts permission class : com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$UsersPrivateKeySource required-type : com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$UsersPrivateKeySource converter-type : hudson.util.RobustReflectionConverter path : /com.cloudbees.plugins.credentials.SystemCredentialsProvider/domainCredentialsMap/entry/java.util.concurrent.CopyOnWriteArrayList/com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey/privateKeySource line number : 21 --- Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55359) Add view of Warning Results in Blue Ocean
Title: Message Title Matthew Dews created an issue Jenkins / JENKINS-55359 Add view of Warning Results in Blue Ocean Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2018-12-28 22:26 Environment: Jenkins 2.150.1 warnings-ng 1.0.1 Priority: Minor Reporter: Matthew Dews In Blue Ocean I can view test results of a pipeline in the Test tab. But there is no way for me to view the Warnings report without going back to the classic Jenkins UI. Add Comment
[JIRA] (JENKINS-53931) Role Strategy: Configuration-as-Code compatibility
Title: Message Title Oleg Nenashev commented on JENKINS-53931 Re: Role Strategy: Configuration-as-Code compatibility I have also added this issue as an example of changes which could be done in the plugin for Google Summer of Code 2016 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-53931) Role Strategy: Configuration-as-Code compatibility
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53931 Role Strategy: Configuration-as-Code compatibility Change By: Oleg Nenashev Labels: gsoc-2019-project-idea jcasc-compatibility user-experience 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-54884) ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-54884 Re: ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working I could not replicate the issue but the cause seems clear, so I changed to use Trilead ssh2 from Jenkins Core and use Trilead API plugin only for test, you have to uninstall the Trilead API plugin is not used. it also needs to restart Jenkins Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54746) Can't connect via SSH on 1.29.1
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-54746 Re: Can't connect via SSH on 1.29.1 It is weird 1.29.4 does not have any ssh connection/authentication class all are in the trilead-ssh2 in the core now, Did you uninstall the Trilead API plugin (trilead-api)?it also needs to restart Jenkins Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55358) No issues found when parsing Eclipse ECJ output from console log during an ant build
Title: Message Title Michael Thompson created an issue Jenkins / JENKINS-55358 No issues found when parsing Eclipse ECJ output from console log during an ant build Issue Type: Bug Assignee: Ulli Hafner Attachments: console.log, java.log Components: warnings-ng-plugin Created: 2018-12-28 21:35 Environment: OS: Win 2008 Server R2 64bit Java: Oracle 1.8.0_171-b11 Jenkins: 2.150.1 warnings 5.0.0 warnings-ng 1.0.0 Priority: Major Reporter: Michael Thompson Activated Eclipse ECJ and normal Java Compiler after the upgrade and neither could find any issues from the console log (built via an ant script). This works with the old warnings plugin. I also tried having ant record the logging to a separate file and still no issues. Complete console log and the java-result log are attached. Searching for all files in 'C:\PCI_Dev\source\pcisvn\CUSTOMER\CUSTOMER_Market\Code\CUSTOMER_Market' that match the pattern '**/java-result.log' -> found 1 file Successfully parsed file C:\PCI_Dev\source\pcisvn\CUSTOMER\CUSTOMER_Market\Code\CUSTOMER_Market\bin\java-result.log -> found 0 issues (skipped 0 duplicates) Using reference build 'CUSTOMER_Market #83' to compute new, fixed, and outstanding issues Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0 Evaluating quality gates -> All quality gates have been passed Health report is disabled - skipping
[JIRA] (JENKINS-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Michael Thompson created an issue Jenkins / JENKINS-55357 Stack trace with JavaDoc log parsed from ant console log Issue Type: Bug Assignee: Ulli Hafner Attachments: trace.txt Components: warnings-ng-plugin Created: 2018-12-28 21:25 Environment: OS: Win 2008 Server R2 64bit Java: Oracle 1.8.0_171-b11 Jenkins: 2.150.1 warnings 5.0.0 warnings-ng 1.0.0 Priority: Minor Reporter: Michael Thompson After upgrading activated the new warnings plugin. It appears to parse the console log. Clicking on the link afterward in the project screen throws an error. [JavaDoc] Sleeping for 5 seconds due to JENKINS-32191... [JavaDoc] Parsing console log (workspace: 'C:\PCI_Dev\source\pcisvn\CUSTOMER\CUSTOMER_Market\Code\CUSTOMER_Market') [JavaDoc] Post processing issues on 'Master' with encoding 'windows-1252' [JavaDoc] Resolving absolute file names for all issues [JavaDoc] -> 0 resolved, 0 unresolved, 31 already resolved [JavaDoc] Copying affected files to Jenkins' build folder C:\Program Files (x86)\Jenkins\jobs\CUSTOMER_Market\builds\84 [JavaDoc] -> 31 copied, 0 not in workspace, 0 not-found, 0 with I/O error [JavaDoc] Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files) [JavaDoc] -> resolved module names for 65 issues [JavaDoc] Resolving package names (or namespaces) by parsing the affected files [JavaDoc] -> resolved package names of 32 affected files [JavaDoc] No filter has been set, publishing all 65 issues [JavaDoc] Creating fingerprints for all affected code blocks to track issues over different builds
[JIRA] (JENKINS-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-55356 Some workflow jobs fail after restart on Java 11 server Change By: Mark Waite Labels: java11-compatibility 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-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-55356 Some workflow jobs fail after restart on Java 11 server Issue Type: Bug Assignee: Unassigned Components: workflow-job-plugin Created: 2018-12-28 21:20 Environment: Jenkins JDK 11 docker image and current plugins Multibranch Pipeline builds for git plugin, git client plugin, and platformlabeler plugin Priority: Minor Reporter: Mark Waite While running Java 11 based Jenkins in a docker container using a pre-release of the workflow support plugin which includes the fix for the null pointer exception, a jenkins-url/safeRestart will cause several of the Pipeline jobs that were running to fail when Jenkins tries to resume the jobs. Build log output from the failed builds has included messages like (seems to be windows specific): 07:40:50 [INFO] Running org.jenkinsci.plugins.gitclient.PushTest Resuming build at Fri Dec 28 07:48:06 MST 2018 after Jenkins restart Waiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #6: Waiting for next available executor on ‘coleen-pc2-ssh’ Ready to run at Fri Dec 28 07:48:49 MST 2018 07:48:49 Timeout set to expire in 17 min [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] }
[JIRA] (JENKINS-55352) update net.i2p.crypto:eddsa
Title: Message Title Ivan Fernandez Calvo updated JENKINS-55352 Jenkins / JENKINS-55352 update net.i2p.crypto:eddsa Change By: Ivan Fernandez Calvo 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-55352) update net.i2p.crypto:eddsa
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-55352 Change By: Ivan Fernandez Calvo 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-54746) Can't connect via SSH on 1.29.1
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-54746 Re: Can't connect via SSH on 1.29.1 It is weird 1.29.4 does not have any ssh connection/authentication class all are in the trilead-ssh2 in the core now, Did you uninstall the Trilead API plugin (trilead-api)? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54724) ssh-credentials-plugin broken when using ssh-slaves-plugin 1.29.0
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-54724 Re: ssh-credentials-plugin broken when using ssh-slaves-plugin 1.29.0 if you upgrade from 1.29.X, you would have to uninstall trilead-api plugin is no longer used and it is the source of the classpath 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-55355) HTML no longer is parsed in Build Pipeline view after core security update
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-55355
HTML no longer is parsed in Build Pipeline view after core security update
Change By:
Mark Waite
Issue:When trying to create HTML within a build pipeline view(through either parameters or descriptions etc.) the HTML is no longer parsed by the markup formatterSteps to reproduce:* Create a new OSS jenkins Jenkins instance at least version 2.46* Install the build pipeline view plugin* Create 2 jobs(upstream and downstream)* Add a parameter to one of those jobs which has HTML(I used a string parameter)* Create a new build pipeline view to start with the upstream job* make sure you are displaying the parameters and variables within the viewObserved behavior:The HTML code is not parsed correctly and it treats it as a literal stringExpected behavior:The HTML code is parsed by the markup formatter and it appears as parsed HTMLYou can see with version 2.45 of Jenkins that the issue is not present and the HTML is parsed which means [this security update|https://jenkins.io/security/advisory/2018-10-10/] is the cause. Additionally no where nowhere else within the instance is unable to parse this HTML code but on that view.HTML code I used:{code:java}This is titleHello world{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are
[JIRA] (JENKINS-55355) HTML no longer is parsed in Build Pipeline view after core security update
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-55355 HTML no longer is parsed in Build Pipeline view after core security update Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 2018-12-28 20:21 Environment: Jenkins 2.46 and newer Latest Build Pipeline plugin Priority: Major Reporter: Alex Taylor Issue: When trying to create HTML within a build pipeline view(through either parameters or descriptions etc.) the HTML is no longer parsed by the markup formatter Steps to reproduce: Create a new OSS jenkins instance at least version 2.46 Install the build pipeline view plugin Create 2 jobs(upstream and downstream) Add a parameter to one of those jobs which has HTML(I used a string parameter) Create a new build pipeline view to start with the upstream job make sure you are displaying the parameters and variables within the view Observed behavior: The HTML code is not parsed correctly and it treats it as a literal string Expected behavior: The HTML code is parsed by the markup formatter and it appears as parsed HTML You can see with version 2.45 of Jenkins that the issue is not present and the HTML is parsed which means this security update is the cause. Additionally no where else within the instance is unable to parse this HTML code but on that
[JIRA] (JENKINS-54746) Can't connect via SSH on 1.29.1
Title: Message Title Darryl Pogue reopened an issue Jenkins / JENKINS-54746 Can't connect via SSH on 1.29.1 Change By: Darryl Pogue Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54746) Can't connect via SSH on 1.29.1
Title: Message Title Darryl Pogue commented on JENKINS-54746 Re: Can't connect via SSH on 1.29.1 I tried updating to 1.29.2, but I'm still seeing the same problem. After the upgrade, I have the warning that data is stored in an old format, and the SSH build agents fail to connect with "Authentication failed". 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-54974) Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2
Title: Message Title
Arnaud TAMAILLON commented on JENKINS-54974
Re: Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2
Hi Oleg Nenashev (and Daniel Beck as Oleg is stepping back at the moment from Core maintenance). From my analysis, and some of other issues reported speaking about deadlocks (JENKINS-20988, JENKINS-21034, JENKINS-31622, JENKINS-44564, JENKINS-49038, JENKINS-50663), the issue lies in the DescriptorExtensionList, especially in the way it acquires its load lock. The DescriptorExtensionList getLoadLock method documentation indicates that it is taking part in the real load activity, and that as such, it can lock on *this *rather than on the *singleton Lock *used by ExtensionList. However, many plugins rely on a GlobalConfiguration object, which is acquired through a code similar to the following (which is actually explicitly recommended in GlobalConfiguration documentation).
public static SpecificPluginConfig get() {
return GlobalConfiguration.all().get(SpecificPluginConfig.class);
}
(the all() method from the GlobalConfiguration is returning a DescriptorExtensionList) As the configuration for a plugin can be called from many places (initialization of plugin, http requests, ...), it is very easy to have at the same time a DescriptorExtensionList being instantiated, needing in return an ExtensionList, while at the same time, some injection code will have taken the ExtensionList lock and will require DescriptorExtensionList one. Of course, some other uses of DescriptorExtensionList, not related to GlobalConfiguration, can also create the same kind of issues. Taking in to account that the lock is only taken when the list is initialized for the first time (in ensureLoaded()), I would say that removing the override of getLoadLock in DescriptorExtensionList should solve the issue at a very minimal cost. What do you think about this proposal ? Do you see other unintended consequences ?
Add Comment
[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title Josh Soref commented on JENKINS-52946 Re: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2 Sorry. https://github.com/jenkinsci/envinject-plugin/pull/134 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-55183) New Relic deployment notifier plugin not showing all applications
Title: Message Title Matias Canessa assigned an issue to Mads Mohr Christensen Jenkins / JENKINS-55183 New Relic deployment notifier plugin not showing all applications Change By: Matias Canessa Assignee: Mads Mohr Christensen 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-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-52946 Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2 Change By: Josh Soref Assignee: Josh Soref 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-54724) ssh-credentials-plugin broken when using ssh-slaves-plugin 1.29.0
Title: Message Title Nenad Miksa commented on JENKINS-54724 Re: ssh-credentials-plugin broken when using ssh-slaves-plugin 1.29.0 This resurfaces back in 1.29.2. Downgrading to 1.29.1 solves the issue for me. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55354) Permissions issue in remoting image jenkins/slave:latest
Title: Message Title Thibault Doubliez created an issue Jenkins / JENKINS-55354 Permissions issue in remoting image jenkins/slave:latest Issue Type: Bug Assignee: Nicolas De Loof Components: docker-slaves-plugin, remoting Created: 2018-12-28 19:00 Environment: Jenkins 2.150.1 installed on CentOS 7.6.1810 using RPM package This build stage is run on the master since Docker Slaves plugin doesn't support running on slaves last time I checked. Java version: openjdk version "1.8.0_191" OpenJDK Runtime Environment (build 1.8.0_191-b12) OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode) The "jenkins" user on the machine has 996:993 uid:gid, which may be part of the issue? I had problems with that in the past. Priority: Minor Reporter: Thibault Doubliez Using jenkins/slave:latest remoting image in Docker Slaves plugin, our builds stopped working a few days ago with a permissions error when initializing the JAR Cache location. This is the relevant console output for the build: [Pipeline] dockerNode Start Docker container to host the build Unable to find image 'jenkins/slave:latest' locally latest: Pulling from jenkins/slave 54f7e8ac135a: Already exists d6341e30912f: Already exists 087a57faf949: Already exists 5d71636fb824: Already exists 9da6b28682cf: Already exists 203f1094a1e2: Already exists ee38d9f85cf6: Already exists 7f692fae02b6: Already exists eaa976dc543c: Already exists 173a06ff64cc: Pulling fs layer 28fc185aee23: Pulling fs layer e02013eddffd: Pulling fs layer cc49fe331e2e: Pulling fs layer cc49fe331e2e: Waiting 173a06ff64cc: Verifying Checksum 173a06ff64cc: Download
[JIRA] (JENKINS-55353) Upgrade Jenkins core to 2.121.3
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-55353 Upgrade Jenkins core to 2.121.3 Change By: Ivan Fernandez Calvo After tested the plugin to compile against different Jenkins core versions, I have detected some changes that I have to make to test it.* Update Jenkins file to compile an test on Jenkins core 2.121.3, 2.138.4, 2.150.1, and 2.156 (3 LTS and last weekly)* Compile and test weekly with JDK 11* Upgrade Jenkins core to 2.121.3, I will support 3 LTS versions* Remove JDKInstaler references, is not used in ssh-slaves and it is no longer in Jenkins core, it is in tool-jdk plugin* Remove deprecated constructors, all these constructors were marked with a warning in logs 6 months ago.* Remove unused code* Remove old fields related to deprecated constructors* Fix tests after changes Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55353) Upgrade Jenkins core to 2.121.3
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-55353 Upgrade Jenkins core to 2.121.3 Change By: Ivan Fernandez Calvo After tested the plugin to compile against different Jenkins core versions, I have detected some changes that I have to make to test it.* Update Jenkins file to compile an test on Jenkins core 2.121.3, 2.138.4, 2.150.1, and 2.156 (3 LTS and last weekly)* Upgrade Jenkins core to 2.121.3, I will support 3 LTS versions* Remove JDKInstaler references, is not used in ssh-slaves and it is no longer in Jenkins core, it is in tool-jdk plugin* Remove deprecated constructors, all these constructors were marked with a warning in logs 6 months ago.* Remove unused code* Remove old fields related to deprecated constructors* Fix tests after changes Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55353) Upgrade Jenkins core to 2.121.3
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-55353 Change By: Ivan Fernandez Calvo 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-55353) Upgrade Jenkins core to 2.121.3
Title: Message Title Ivan Fernandez Calvo created an issue Jenkins / JENKINS-55353 Upgrade Jenkins core to 2.121.3 Issue Type: Task Assignee: Ivan Fernandez Calvo Components: ssh-slaves-plugin Created: 2018-12-28 18:54 Priority: Minor Reporter: Ivan Fernandez Calvo After tested the plugin to compile against different Jenkins core versions, I have detected some changes that I have to make to test it. Upgrade Jenkins core to 2.121.3, I will support 3 LTS versions Remove JDKInstaler references, is not used in ssh-slaves and it is no longer in Jenkins core, it is in tool-jdk plugin Remove deprecated constructors, all these constructors were marked with a warning in logs 6 months ago. Remove unused code Remove old fields related to deprecated constructors Fix tests after changes
[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title Rick Liu edited a comment on JENKINS-52946 Re: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2 *Environment:**Ubuntu 16.04 (both master ans slaves)**Jenkins vers: 2.138.4**EnvInject 2.1.6**EnvInject API 1.5* All I did was disconnect the slave and reconnect again.The warning would always show up right before the line "Agent successfully connected and online". 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-55344) Allow to run Groovy scripts in JCasC
Title: Message Title Tomasz Szandała commented on JENKINS-55344 Re: Allow to run Groovy scripts in JCasC TBH I have tested this few dozen times and I did not notice aby issues. Could You try? I have made pull requested #687 with proposed feature. So far IT passed my tests... 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-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title Rick Liu reopened an issue Environment: Ubuntu 16.04 (both master ans slaves) Jenkins vers: 2.138.4 EnvInject 2.1.6 EnvInject API 1.5 Jenkins / JENKINS-52946 Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2 Change By: Rick Liu Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-52946 Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2 Change By: Rick Liu Attachment: Selection_010.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-55351) docker.build().inside() not run "inside" in Jenkins within Docker
Title: Message Title
Attila Szeremi updated an issue
Jenkins / JENKINS-55351
docker.build().inside() not run "inside" in Jenkins within Docker
Change By:
Attila Szeremi
My Jenkins is within a Docker container, and I try to run {{docker.build(...).inside(...) }} in it, but the inside bit does _not_ run within the newly built container}}{{ {{ . I know, because {{ pwd}} gives me: {{/var/jenkins_home/workspace/youtube-delete-tracker_jenkins}} which is clearly the Jenkins container.I've tried this both in imperative and declarative style.I have a lot more details in a StackOverflow question: [https://stackoverflow.com/questions/53950128/jenkins-within-docker-dockerfile-agent-happens-outside-new-container]
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-55351) docker.build().inside() not run "inside" in Jenkins within Docker
Title: Message Title
Attila Szeremi updated an issue
Jenkins / JENKINS-55351
docker.build().inside() not run "inside" in Jenkins within Docker
Change By:
Attila Szeremi
My Jenkins is within a Docker container, and I try to run {{docker.build(...).inside(...) }}in it, but the inside bit does _not_ run within the newly built containe container }} r {{{{ . I know, because {{pwd}} gives me: {{/var/jenkins_home/workspace/youtube-delete-tracker_jenkins}} which is clearly the Jenkins container.I've tried this both in imperative and declarative style.I have a lot more details in a StackOverflow question: [https://stackoverflow.com/questions/53950128/jenkins-within-docker-dockerfile-agent-happens-outside-new-container]
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-55351) docker.build().inside() not run "inside" in Jenkins within Docker
Title: Message Title
Attila Szeremi updated an issue
Jenkins / JENKINS-55351
docker.build().inside() not run "inside" in Jenkins within Docker
Change By:
Attila Szeremi
My Jenkins is within a Docker container, and I try to run {{docker.build(...).inside(...) }}in it, but the inside bit does _not_ run within the newly built container containe}}r . I know, because {{pwd}} }} gives me: {{/var/jenkins_home/workspace/youtube-delete-tracker_jenkins}} which is clearly the Jenkins container.I've tried this both in imperative and declarative style.I have a lot more details in a StackOverflow question: [https://stackoverflow.com/questions/53950128/jenkins-within-docker-dockerfile-agent-happens-outside-new-container]
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-55351) docker.build().inside() not run "inside" in Jenkins within Docker
Title: Message Title
Attila Szeremi updated an issue
Jenkins / JENKINS-55351
docker.build().inside() not run "inside" in Jenkins within Docker
Change By:
Attila Szeremi
My Jenkins is within a Docker container, and I try to run {{docker.build(...).inside(...) }}in it, but the inside bit does _not_ run within the newly built container. I know, because {{pwd}} }} gives me: {{/var/jenkins_home/workspace/youtube-delete-tracker_jenkins}} which is clearly the Jenkins container.I've tried this both in imperative and declarative style.I have a lot more details in a StackOverflow question: [https://stackoverflow.com/questions/53950128/jenkins-within-docker-dockerfile-agent-happens-outside-new-container]
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-55344) Allow to run Groovy scripts in JCasC
Title: Message Title Oleg Nenashev commented on JENKINS-55344 Re: Allow to run Groovy scripts in JCasC TBH I would advice against that for production instances until JCasC loading logic is improved. JCasC has a known issue with the initialization lifecycle. JCasC loading may be happening in parallel with Jobs loading, and there may be various race conditions if we run Groovy interpreter with its classloading magic. 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-53653) Logger is not assigned
Title: Message Title Ivan Fernandez Calvo updated JENKINS-53653 Jenkins / JENKINS-53653 Logger is not assigned Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Released As: trilead-ssh2-build-217-jenkins-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 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-53651) dequeue hanging when the packets.size=0
Title: Message Title Ivan Fernandez Calvo updated JENKINS-53651 Jenkins / JENKINS-53651 dequeue hanging when the packets.size=0 Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Released As: trilead-ssh2-build-217-jenkins-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 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-53645) Move SFTPClient class form SSH Slaves plugin
Title: Message Title Ivan Fernandez Calvo updated JENKINS-53645 Jenkins / JENKINS-53645 Move SFTPClient class form SSH Slaves plugin Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Released As: trilead-ssh2-build-217-jenkins-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 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-47603) SCP error response code should be printed in the logs
Title: Message Title Ivan Fernandez Calvo updated JENKINS-47603 Jenkins / JENKINS-47603 SCP error response code should be printed in the logs Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Released As: trilead-ssh2-build-217-jenkins-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 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-52493) Declarative: Steps don't run inside container with "dockerfile true"
Title: Message Title Attila Szeremi commented on JENKINS-52493 Re: Declarative: Steps don't run inside container with "dockerfile true" And I'm getting the same issue even if I'm running Jenkins outside of a container, and on my host. 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-55052) Different behavior accessing user credentials using RunAs Specific vs. Triggered User
Title: Message Title Michael Ahern updated JENKINS-55052 Closing this down; thanks for all of the insights. Jenkins / JENKINS-55052 Different behavior accessing user credentials using RunAs Specific vs. Triggered User Change By: Michael Ahern Status: Reopened Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17157) Enviroment variables are not loaded in ssh using cygwin
Title: Message Title Ivan Fernandez Calvo closed an issue as Cannot Reproduce Jenkins / JENKINS-17157 Enviroment variables are not loaded in ssh using cygwin Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7641) Slaves hang when archiving artifacts
Title: Message Title Ivan Fernandez Calvo closed an issue as Cannot Reproduce Jenkins / JENKINS-7641 Slaves hang when archiving artifacts Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14332) Repeated channel/timeout errors from Jenkins slave
Title: Message Title Ivan Fernandez Calvo closed an issue as Cannot Reproduce Jenkins / JENKINS-14332 Repeated channel/timeout errors from Jenkins slave Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14332) Repeated channel/timeout errors from Jenkins slave
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-14332 Re: Repeated channel/timeout errors from Jenkins slave because there is not recent info here and seems similar to JENKINS-53810 I will close 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-53079) Could not copy slave.jar into '' on slave
Title: Message Title
Ivan Fernandez Calvo updated an issue
Jenkins / JENKINS-53079
Could not copy slave.jar into '' on slave
Change By:
Ivan Fernandez Calvo
Attempting to start Linux node results in failure:{ code} { { 08/16/18 17:47:31] [SSH] Copying latest slave.jar...}} {{hudson.util.IOException2: Could not copy slave.jar into '/build' on slave}} {{ at hudson.plugins.sshslaves.SSHLauncher.copySlaveJar(SSHLauncher.java:1054)}} {{ at hudson.plugins.sshslaves.SSHLauncher.access$300(SSHLauncher.java:137)}} {{ at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:723)}} {{ at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:706)}} {{ at java.util.concurrent.FutureTask.run(FutureTask.java:266)}} {{ at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)}} {{ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)}} {{ at java.lang.Thread.run(Thread.java:748)}} {{Caused by: hudson.util.IOException2: Could not copy slave.jar to '/build/slave.jar' on slave}} {{ at hudson.plugins.sshslaves.SSHLauncher.copySlaveJar(SSHLauncher.java:1049)}} {{ ... 7 more}} {{Caused by: com.trilead.ssh2.SFTPException: Failure (SSH_FX_FAILURE: An error occurred, but no specific error code exists to describe the failure.)}} {{ at com.trilead.ssh2.SFTPv3Client.openFile(SFTPv3Client.java:1201)}} {{ at com.trilead.ssh2.SFTPv3Client.createFile(SFTPv3Client.java:1074)}} {{ at com.trilead.ssh2.SFTPv3Client.createFile(SFTPv3Client.java:1055)}} {{ at hudson.plugins.sshslaves.SFTPClient.writeToFile(SFTPClient.java:93)}} {{ at hudson.plugins.sshslaves.SSHLauncher.copySlaveJar(SSHLauncher.java:1039)}} {{ ... 7 more}} {code} Turns out root cause is file system went read-only:mount: warning: /etc/mtab is not writable (e.g. read-only filesystem). It's possible that information reported by mount(8) is not up to date. For actual information about system mount points check the /proc/mounts file.Reporting error because of the response in the logs:{{(SSH_FX_FAILURE: An error occurred, but no specific error code exists to describe the failure.)}}This is a different failure condition to other documented bugs ([JENKINS-42856|https://issues.jenkins-ci.org/browse/JENKINS-42856] , [JENKINS-42441|https://issues.jenkins-ci.org/browse/JENKINS-42441]) so worth mentioning and perhaps code can be fixed to provide more descriptive failure response
[JIRA] (JENKINS-54729) jenkins dashboard displays stacktrace
Title: Message Title Ivan Fernandez Calvo resolved as Fixed Jenkins / JENKINS-54729 jenkins dashboard displays stacktrace Change By: Ivan Fernandez Calvo Status: Open Resolved Resolution: Fixed Released As: ssh-slaves-1.29.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-54729) jenkins dashboard displays stacktrace
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-54729 jenkins dashboard displays stacktrace Change By: Ivan Fernandez Calvo Component/s: view-job-filters-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-44488) Free style projects/jobs not sending email notification if removed the slave with post build action groovy script enabled
Title: Message Title Francisco Fernández closed an issue as Duplicate Jenkins / JENKINS-44488 Free style projects/jobs not sending email notification if removed the slave with post build action groovy script enabled Change By: Francisco Fernández Status: Open Closed Resolution: Duplicate 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-54729) jenkins dashboard displays stacktrace
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-54729 jenkins dashboard displays stacktrace Change By: Ivan Fernandez Calvo Assignee: Sven Schoenung Ivan Fernandez Calvo 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-54018) Exception on UI after Manually uploading Plugins
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-54018 Exception on UI after Manually uploading Plugins Change By: Ivan Fernandez Calvo Component/s: ssh-slaves-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-37812) No notification re. failed job if agent goes offline during the build
Title: Message Title Francisco Fernández updated JENKINS-37812 Jenkins / JENKINS-37812 No notification re. failed job if agent goes offline during the build Change By: Francisco Fernández 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-54934) Max number of retries and retry wait time do not allow 0
Title: Message Title Ivan Fernandez Calvo updated JENKINS-54934 Jenkins / JENKINS-54934 Max number of retries and retry wait time do not allow 0 Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Released As: ssh-slaves-1.29.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-54746) Can't connect via SSH on 1.29.1
Title: Message Title Ivan Fernandez Calvo updated JENKINS-54746 I could not replicate the issue but the cause seems clear, so I changed to use Trilead ssh2 from Jenkins Core and use Trilead API plugin only for test, you have to uninstall the Trilead API plugin is not used. Jenkins / JENKINS-54746 Can't connect via SSH on 1.29.1 Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Released As: ssh-slaves-1.29.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,
[JIRA] (JENKINS-54884) ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working
Title: Message Title Ivan Fernandez Calvo updated JENKINS-54884 I could not replicate the issue but the cause seems clear, so I changed to use Trilead ssh2 from Jenkins Core and use Trilead API plugin only for test, you have to uninstall the Trilead API plugin is not used. Jenkins / JENKINS-54884 ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Released As: ssh-slaves-1.29.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
[JIRA] (JENKINS-54746) Can't connect via SSH on 1.29.1
Title: Message Title Ivan Fernandez Calvo updated JENKINS-54746 Jenkins / JENKINS-54746 Can't connect via SSH on 1.29.1 Change By: Ivan Fernandez Calvo 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-54884) ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-54884 Change By: Ivan Fernandez Calvo 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-54884) ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working
Title: Message Title Ivan Fernandez Calvo updated JENKINS-54884 Jenkins / JENKINS-54884 ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working Change By: Ivan Fernandez Calvo 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-53575) Configuration-as-Code compatibility
Title: Message Title René Scheibe started work on JENKINS-53575 Change By: René Scheibe 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-53575) Configuration-as-Code compatibility
Title: Message Title René Scheibe assigned an issue to René Scheibe Jenkins / JENKINS-53575 Configuration-as-Code compatibility Change By: René Scheibe Assignee: Stefan Wolf René Scheibe 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-55352) update net.i2p.crypto:eddsa
Title: Message Title Ivan Fernandez Calvo created an issue Jenkins / JENKINS-55352 update net.i2p.crypto:eddsa Issue Type: Task Assignee: Ivan Fernandez Calvo Components: trilead-api-plugin Created: 2018-12-28 14:23 Priority: Minor Reporter: Ivan Fernandez Calvo Jenkins core and tool-jdk updated to 0.3.0 so make sense to update the library Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-47458) Trilead-SSH2 fails with NPE when calling Connection#getReasonClosedCause()
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-47458 Re: Trilead-SSH2 fails with NPE when calling Connection#getReasonClosedCause() The PRs to the core is in place 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-55133) Debian Buster private keys rejected for ssh agents
Title: Message Title Ivan Fernandez Calvo updated JENKINS-55133 Jenkins / JENKINS-55133 Debian Buster private keys rejected for ssh agents Change By: Ivan Fernandez Calvo 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-55133) Debian Buster private keys rejected for ssh agents
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-55133 Re: Debian Buster private keys rejected for ssh agents The PR to update trilead-ssh2 in the Core is in place. 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-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title Nikita Nadezhin commented on JENKINS-54557 Re: hudson.AbortException: Ansible playbook execution failed 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-55351) docker.build().inside() not run "inside" in Jenkins within Docker
Title: Message Title
Attila Szeremi updated an issue
Jenkins / JENKINS-55351
docker.build().inside() not run "inside" in Jenkins within Docker
Change By:
Attila Szeremi
My Jenkins is within a Docker container, and I try to run ` {{ docker.build(...).inside(...) ` }} in it, but the inside bit does _not_ run within the newly built container. I know, because ` {{ pwd ` }} gives me: ` {{ /var/jenkins_home/workspace/youtube-delete-tracker_jenkins ` }} which is clearly the Jenkins container.I 've tried this both in imperative and declarative style.I have a lot more details in a StackOverflow question: [https://stackoverflow.com/questions/53950128/jenkins-within-docker-dockerfile-agent-happens-outside-new-container]
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-55351) docker.build().inside() not run "inside" in Jenkins within Docker
Title: Message Title Attila Szeremi created an issue Jenkins / JENKINS-55351 docker.build().inside() not run "inside" in Jenkins within Docker Issue Type: Bug Assignee: Unassigned Components: docker-workflow-plugin Created: 2018-12-28 13:42 Priority: Minor Reporter: Attila Szeremi My Jenkins is within a Docker container, and I try to run `docker.build(...).inside(...)` in it, but the inside bit does not run within the newly built container. I know, because `pwd` gives me: `/var/jenkins_home/workspace/youtube-delete-tracker_jenkins` which is clearly the Jenkins container. I have a lot more details in a StackOverflow question: https://stackoverflow.com/questions/53950128/jenkins-within-docker-dockerfile-agent-happens-outside-new-container Add Comment
[JIRA] (JENKINS-55023) Remote ssh slave disconnection
Title: Message Title Ivan Fernandez Calvo closed an issue as Cannot Reproduce I can not replicate the issue on version 1.29.2 with JDK 8 and Jenkins Core 2.89.4, this is the current version supported. Jenkins / JENKINS-55023 Remote ssh slave disconnection Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55133) Debian Buster private keys rejected for ssh agents
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-55133 Change By: Ivan Fernandez Calvo 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-54746) Can't connect via SSH on 1.29.1
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-54746 Change By: Ivan Fernandez Calvo 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-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title Nikita Nadezhin edited a comment on JENKINS-54557 Re: hudson.AbortException: Ansible playbook execution failed Hello! I have problem too.I ran playbook with ansible jenkins plugin. If all tasks are SUCCES, jenkins build is SUCCES too.BUT if any task is FAILED or UNREACHABLE, i see "hudson.AbortException Ansible playbook execution failed" in console.Is this error is the same that in start topic? –piipel 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-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title Nikita Nadezhin edited a comment on JENKINS-54557 Re: hudson.AbortException: Ansible playbook execution failed Hello! I have problem too.I ran playbook with ansible jenkins pluginю plugin. If all tasks are SUCCES, jenkins build is SUCCES too.BUT if any task is FAILED or UNREACHABLE, i see "hudson.AbortException Ansible playbook execution failed" in console.Is this error is the same that in start topic? -- – piipel 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-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title Nikita Nadezhin updated an issue Jenkins / JENKINS-54557 hudson.AbortException: Ansible playbook execution failed Change By: Nikita Nadezhin Comment: !Скриншот от 2018-12-28 16-03-56.jpg! 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-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title Nikita Nadezhin edited a comment on JENKINS-54557 Re: hudson.AbortException: Ansible playbook execution failed UPD . For some reason, I can't attach screenshot. I uploaded it [here https://photos.app.goo.gl/9gXvttYMPaAVxkex8|https://photos.app.goo.gl/9gXvttYMPaAVxkex8] !Скриншот от 2018-12-28 16-03-56.jpg! 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-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title Nikita Nadezhin commented on JENKINS-54557 Re: hudson.AbortException: Ansible playbook execution failed UPD 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-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title Nikita Nadezhin updated an issue Jenkins / JENKINS-54557 hudson.AbortException: Ansible playbook execution failed Change By: Nikita Nadezhin Comment: UPD.!Скриншот от 2018-12-28 16-03-56.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-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title Nikita Nadezhin commented on JENKINS-54557 Re: hudson.AbortException: Ansible playbook execution failed UPD. 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-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title Nikita Nadezhin edited a comment on JENKINS-54557 Re: hudson.AbortException: Ansible playbook execution failed Hello! I have problem too.I ran playbook with ansible jenkins pluginю If all tasks are SUCCES, jenkins build is SUCCES too.BUT if any task is FAILED or UNREACHABLE, i see "hudson.AbortException Ansible playbook execution failed" in console.Is this error is the same that in start topic? !Скриншот от 2018 - 12 - 28 16-03-56.png! piipel 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-55135) Can Not Connect Mac Slave Over SSH - error copying remoting.jar.
Title: Message Title Ivan Fernandez Calvo closed an issue as Incomplete Jenkins / JENKINS-55135 Can Not Connect Mac Slave Over SSH - error copying remoting.jar. Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Incomplete 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.
