[JIRA] (JENKINS-49607) ssh-slaves-plugin should report the required java version when none found
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49607 Re: ssh-slaves-plugin should report the required java version when none found Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/plugins/sshslaves/SSHLauncher.java http://jenkins-ci.org/commit/ssh-slaves-plugin/5ce9b912ba6a82e67d7925ca9d8b5b9e5ecc44fe Log: Merge pull request #83 from rompic/master [FIXED JENKINS-49607] - Report required java version when none found Compare: https://github.com/jenkinsci/ssh-slaves-plugin/compare/025dcde12dc3...5ce9b912ba6a Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49670) SSHLauncherTest#upgrade is failing
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49670 Re: SSHLauncherTest#upgrade is failing Code changed in jenkins User: Francisco Javier Fernandez Gonzalez Path: pom.xml http://jenkins-ci.org/commit/ssh-slaves-plugin/f4df0136402e4b888ea20c7a2bbdd58a416d6c4c Log: JENKINS-49670 Upgrade docker-fixtures dependency Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49607) ssh-slaves-plugin should report the required java version when none found
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49607 Re: ssh-slaves-plugin should report the required java version when none found Code changed in jenkins User: Roman Pickl Path: src/main/java/hudson/plugins/sshslaves/SSHLauncher.java http://jenkins-ci.org/commit/ssh-slaves-plugin/654a7e2bd4c73b7365f3b94059d194c2b405313b Log: [FIXED JENKINS-49607] - Report required java version when none found Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49670) SSHLauncherTest#upgrade is failing
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49670 Re: SSHLauncherTest#upgrade is failing Code changed in jenkins User: Oleg Nenashev Path: http://jenkins-ci.org/commit/ssh-slaves-plugin/05842f86d1cfcbc486f2067fc48dc5aa2be40204 Log: Merge pull request #84 from fcojfernandez/JENKINS-49670 JENKINS-49670 SSHLauncherTest#upgrade is failing Compare: https://github.com/jenkinsci/ssh-slaves-plugin/compare/5ce9b912ba6a...05842f86d1cf Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49607) ssh-slaves-plugin should report the required java version when none found
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-49607 ssh-slaves-plugin should report the required java version when none found Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46487) Git Plugin only scans refs/heads on multibranch scan
Title: Message Title Dmitry Yunitsky commented on JENKINS-46487 Re: Git Plugin only scans refs/heads on multibranch scan Hello, seems that we are stuck with the exact same issue. We build pull-requests that are stored under "refs/pull-requests/*/merge" with our Bitbucket server. Now we use 3.4.1 plugin version and cannot update to 3.7.0 where the flow is broken. Is there any possible workaround or solution for that? Thanks. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title
Tomasz Śniatowski commented on JENKINS-48258
Re: git client plugin occasionally fails with "text file busy" error
We haven't seen the error since we implemented the local workaround, so that's over a month now. It looks like it has definitely helped. Unfortunately it's a shell wrapper and not really a usable patch:
$ which git
/usr/local/bin/git
$ cat /usr/local/bin/git
#!/bin/sh
# Wrapper to avoid "fatal: cannot exec '/tmp/aa': Text file busy" errors when
# git is called with GIT_SSH pointing to something that's still open for writing
# (see https://issues.jenkins-ci.org/browse/JENKINS-48258)
GIT_SSH_COPY=
if [ -n "$GIT_SSH" ]; then
GIT_SSH_COPY="$(mktemp "${GIT_SSH}.X")"
cp -a "$GIT_SSH" "$GIT_SSH_COPY"
GIT_SSH="$GIT_SSH_COPY"
fi
/usr/bin/git "$@"
RET=$?
if [ -n "$GIT_SSH_COPY" ]; then
rm -f "$GIT_SSH_COPY"
fi
exit $RET
I'm not quite sure how to solve this purely in Java in the git plugin code, as my tests indicate merely creating the file on the Java side introduces a race condition that can make this issue come back. A quick hacky workaround could make this go from a 0.1% issue to a 0.001% but still something that will occasionally break. Likely a more substantial change of approach on Linux is needed, to avoid the "write file then make GIT_SSH point to it" pattern altogether.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-32776) Jenkins shouldn't store API tokens in a recoverable format
Title: Message Title Wadeck Follonier commented on JENKINS-32776 Re: Jenkins shouldn't store API tokens in a recoverable format New API Token system proposed. User will have the capability to have multiple API Token (with a name) that are working like in GitHub, meaning they can see the token only after the creation. Only the SHA-256 hashes are stored in the server for the verification but the token cannot be displayed anymore. In order to keep the current (legacy) behavior, the users with a legacy token can still display its value. If the corresponding API Token Property Configuration option is enabled, they can create new legacy token even if they do not have one anymore (to ease migration) but once disabled and the users have no legacy token, there is no option to create new ones. See the attached PR to have more details. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49353) ERROR: Could not do lightweight checkout, falling back to heavyweight
Title: Message Title Seb Lie commented on JENKINS-49353 Re: ERROR: Could not do lightweight checkout, falling back to heavyweight The root cause seems to be that "PR-216" is not recognized by the Bitbucket API. If you replace PR-216 with "pull-requests/216/merge" or "pull-requests/216/from", you can download the Jenkinsfile without falling back to a full checkout (assuming it exists in the repo). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47972) hudson.plugins.claim.ClaimConfig: circular dependency
Title: Message Title Arnaud TAMAILLON commented on JENKINS-47972 Re: hudson.plugins.claim.ClaimConfig: circular dependency Could you provide a complete log of the error please? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23175) Add support for Credentials plugin supplied credentials
Title: Message Title Alex Earl commented on JENKINS-23175 Re: Add support for Credentials plugin supplied credentials This will be the next thing I look at for the publish over plugins after I get a release with pipeline support out the door. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24812) Allow downloading
Title: Message Title Alex Earl assigned an issue to Alex Earl Jenkins / JENKINS-24812 Allow downloading Change By: Alex Earl Assignee: bap Alex Earl Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49730) JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER
Title: Message Title Rex Coronel commented on JENKINS-49730 Re: JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER I was using the swarm-client-3.10.jar previously when I got the error. I've tried downgrading to ver. 3.3 but to no avail. Below is the logs of the build slave on the Jenkins Master: JNLP agent connected from ip-10-xx-xx-1.xx-southeast-1.compute.internal/10.xx.x.1 NOTE: It stays like this with the loading symbol but no progress. I'll try connecting to the build slave via SSH and see if I experience the same issues. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27963) Please add support for jenkins pipeline plugin to publish-over-ssh
Title: Message Title Alex Earl commented on JENKINS-27963 Re: Please add support for jenkins pipeline plugin to publish-over-ssh Yes, I'll be doing a release this week. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31803) Pipeline support for TFS plugin
Title: Message Title Andrew Gray commented on JENKINS-31803 Re: Pipeline support for TFS plugin Thank you Kellie Jos, looking forward to it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27963) Please add support for jenkins pipeline plugin to publish-over-ssh
Title: Message Title Ed Lomonaco commented on JENKINS-27963 Re: Please add support for jenkins pipeline plugin to publish-over-ssh I'm taking a guess this should be available in the very near future? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49615) multibranchPipelineJob: add property strategy & script path options
Title: Message Title matthew snoddy commented on JENKINS-49615 Re: multibranchPipelineJob: add property strategy & script path options PR Submitted: https://github.com/jenkinsci/job-dsl-plugin/pull/1109 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49444) JDK selection not overriding JAVA_HOME for builds
Title: Message Title Oleg Nenashev commented on JENKINS-49444 Re: JDK selection not overriding JAVA_HOME for builds Devin Nusbaum has some recent experience with JDK Installer. Likely something is just overriding the value. Which EnvInject version do you use by the way? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49476) Jenkins Error Code 7 on KDE Neon (Ubuntu 16.04LTS)
Title: Message Title Oleg Nenashev commented on JENKINS-49476 Re: Jenkins Error Code 7 on KDE Neon (Ubuntu 16.04LTS) Does not ring any bells, especially without service startup logs. "-ex" are standard shell options for Unix shells, so you can run service script with them manually Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49589) Global Tools Config not opeing
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49589 Global Tools Config not opeing Change By: Oleg Nenashev Component/s: _unsorted Component/s: global-build-stats-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49589) Global Tools Config not opeing
Title: Message Title Oleg Nenashev commented on JENKINS-49589 Re: Global Tools Config not opeing I doubt that Global Build Stats is responsible for that. Sounds like a Jenkins startup failure, not sure what causes that. I need a version and a system log at least Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49589) Global Tools Config not opeing
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-49589 Global Tools Config not opeing Change By: Oleg Nenashev Assignee: David Krischke Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49724) Option to propagate SCMTriggers to downstream projects
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49724 Option to propagate SCMTriggers to downstream projects Change By: Oleg Nenashev Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49724) Option to propagate SCMTriggers to downstream projects
Title: Message Title Oleg Nenashev commented on JENKINS-49724 Re: Option to propagate SCMTriggers to downstream projects IIUC it is a new feature request, not a defect. Probably it could be done in a plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49724) Option to propagate SCMTriggers to downstream projects
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49724 Option to propagate SCMTriggers to downstream projects Change By: Oleg Nenashev Component/s: plugin-proposals Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27963) Please add support for jenkins pipeline plugin to publish-over-ssh
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27963 Re: Please add support for jenkins pipeline plugin to publish-over-ssh Code changed in jenkins User: Alex Earl Path: pom.xml src/main/java/jenkins/plugins/publish_over_ssh/BapSshHostConfiguration.java src/main/java/jenkins/plugins/publish_over_ssh/BapSshPromotionPublisherPlugin.java src/main/java/jenkins/plugins/publish_over_ssh/BapSshPublisherPlugin.java src/main/java/jenkins/plugins/publish_over_ssh/BapSshTransfer.java src/main/java/jenkins/plugins/publish_over_ssh/descriptor/BapSshPublisherDescriptor.java src/main/java/jenkins/plugins/publish_over_ssh/descriptor/BapSshTransferDescriptor.java http://jenkins-ci.org/commit/publish-over-ssh-plugin/8a78eeb871f60cbfe37a05db1e95500c48badc60 Log: Fix JENKINS-27963 Added @Symbol annotations and cleaned up the constructors a bit. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49716) Publish Over SSH Pipeline Failure
Title: Message Title Alex Earl closed an issue as Duplicate Jenkins / JENKINS-49716 Publish Over SSH Pipeline Failure Change By: Alex Earl Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27963) Please add support for jenkins pipeline plugin to publish-over-ssh
Title: Message Title Alex Earl assigned an issue to Alex Earl Jenkins / JENKINS-27963 Please add support for jenkins pipeline plugin to publish-over-ssh Change By: Alex Earl Assignee: bap Alex Earl Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48596) Support for Docker Trusted Registry (DTR) webhooks
Title: Message Title Cagdas Cirit commented on JENKINS-48596 Re: Support for Docker Trusted Registry (DTR) webhooks Eric Smalling rsandell any update about the issue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47972) hudson.plugins.claim.ClaimConfig: circular dependency
Title: Message Title Andreas Skoog reopened an issue I got this exact error when upgrading from 2.13 to 2.14 Jenkins / JENKINS-47972 hudson.plugins.claim.ClaimConfig: circular dependency Change By: Andreas Skoog Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-49730) JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER
Title: Message Title Oleg Nenashev commented on JENKINS-49730 Re: JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER Would be great to also get Master logs. No idea what's going on so far, which Swarm client version were you using before the upgrade? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42460) EnvInject-Permission not shown/maintainable (after restart) correctly
Title: Message Title Oleg Nenashev commented on JENKINS-42460 Re: EnvInject-Permission not shown/maintainable (after restart) correctly You are responding to 1y old thread, so I would need to revover the context. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49731) p4-plugin viewFilter unusable
Title: Message Title
Takeshi Yaegashi created an issue
Jenkins / JENKINS-49731
p4-plugin viewFilter unusable
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-02-25 16:02
Environment:
Jenkins 2.89.4 p4-plugin 1.8.5
Priority:
Major
Reporter:
Takeshi Yaegashi
Since 1.8.5, I'm getting IllegalArgumentException with viewFilter():
checkout perforce(credential: 'anything', filter: [viewFilter('//depot/any/path')], ...)
java.lang.IllegalArgumentException: Arguments to class org.jenkinsci.plugins.p4.filters.FilterPatternListImpl have to be explicitly named
at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:276)
at org.jenkinsci.plugins.structs.describable.UninstantiatedDescribable.instantiate(UninstantiatedDescribable.java:168)
at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:394)
at org.jenkinsci.plugins.structs.describable.DescribableModel.coerceList(DescribableModel.java:485)
at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:387)
at org.jenkinsci.plugins.structs.describable.DescribableModel.buildArguments(DescribableModel.java:340)
at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:281)
[JIRA] (JENKINS-49730) JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER
Title: Message Title Rex Coronel commented on JENKINS-49730 Re: JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER Hi Oleg Nenashev, It is indicated as "Offline" and not temporary. I don't really know what caused the issue since the logs that is shown in the Jenkins Node only says "JNLP Connected" and the loading symbol. Also, the the swarm-client.jar that I'm using has been working for more or less a month now and on different ec2-instances but it suddenly stopped working. I've tried using a different version of the jar file (which I got from the artifact repository of repo.jenkins...) again on different ec2-instances and I ended up with the same result. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49730) JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER
Title: Message Title Oleg Nenashev commented on JENKINS-49730 Re: JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER Is it indicated as "offline" or "temporary offline"? In the latter case there may be a monitor which puts the agent temporary offline without disconnecting it Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49730) JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER
Title: Message Title Rex Coronel created an issue Jenkins / JENKINS-49730 JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER Issue Type: Bug Assignee: Giuseppe Landolfi Components: slave-setup-plugin, swarm-plugin Created: 2018-02-25 14:18 Environment: Jenkins ver. 2.73.3 Slave Java Version "1.8.0_151" Slave Java(TM_ SE RUNTIME ENVIRONMENT (build 1.8.0_151-b12) swarm-client-3.10.jar RHEL 3.10.0-693.11.1.el7.x86_64 EC2-Instance Priority: Critical Reporter: Rex Coronel On EC2-Instance (Jenkins Slave): INFO: Discovering Jenkins master SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Feb 25, 2018 10:09:29 PM hudson.plugins.swarm.Client run INFO: Attempting to connect to http://jenkins.x.x/ 5c53e911-2091-4f8e-8122-abb162ac8a06 with ID 056b83d1 Feb 25, 2018 10:09:29 PM hudson.remoting.jnlp.Main createEngine INFO: Setting up agent: dev-clone-056b83d1 Feb 25, 2018 10:09:29 PM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode. Feb 25, 2018 10:09:29 PM hudson.remoting.Engine startEngine WARNING: No Working Directory. Using the legacy JAR Cache location: /root/.jenkins/cache/jars Feb 25, 2018 10:09:29 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among http://jenkins.x.x/ Feb 25, 2018 10:09:29 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, JNLP-connect, Ping, JNLP2-connect] Feb 25, 2018 10:09:29 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Agent discovery successful Agent address: 10.X.X.X Agent port: 5 Identity:
[JIRA] (JENKINS-49634) Wrong escaping of quotes in the Setup Wizard
Title: Message Title Manuel Recena Soto updated JENKINS-49634 Jenkins / JENKINS-49634 Wrong escaping of quotes in the Setup Wizard Change By: Manuel Recena Soto Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49457) Git Parameter does not work as input in a scripted pipeline
Title: Message Title Boguslaw Klimas updated an issue Jenkins / JENKINS-49457 Git Parameter does not work as input in a scripted pipeline Change By: Boguslaw Klimas Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49457) Git Parameter does not work as input in a scripted pipeline
Title: Message Title Boguslaw Klimas updated an issue Jenkins / JENKINS-49457 Git Parameter does not work as input in a scripted pipeline Change By: Boguslaw Klimas Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49457) Git Parameter does not work as input in a scripted pipeline
Title: Message Title Boguslaw Klimas commented on JENKINS-49457 Re: Git Parameter does not work as input in a scripted pipeline Hi Magnus Jungsbluth Thanks for your request, unfortunately plugin doesn't support 'input-steps'. I changing the issue on a feature not a bug. I did small research and change in source code isn't simple. I will be able to come back this issue only at the beginning of April Regards Bogusław Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
