[JIRA] (JENKINS-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs
Title: Message Title Stephen Connolly commented on JENKINS-48571 Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs I think JENKINS-46290 is demonstrating the same issue as the Job DSL half of this. Andrew Bayer if you need to replicate a JobDSL configuration that is leaving the SCMSource.id == null I believe https://github.com/samrocketman/jervis/blob/b25af324cce229255fd34c9070f32da4d0d8b393/jobs/jenkins_job_multibranch_pipeline.groovy#L35-L62 is such an example. The fix to that should just be adding id 'some-value' within the github section. 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-46290) Project checkout fails (ERROR: Could not determine exact tip revision of master)
Title: Message Title
Stephen Connolly commented on JENKINS-46290
Re: Project checkout fails (ERROR: Could not determine exact tip revision of master)
This looks to be the exact situation of the second case I describe in https://issues.jenkins-ci.org/browse/JENKINS-48571?focusedCommentId=329111=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-329111 Namely the Job DSL plugin is being used to configure a branch source that has a null id. You must provide an ID: https://github.com/samrocketman/jervis/blob/b25af324cce229255fd34c9070f32da4d0d8b393/jobs/jenkins_job_multibranch_pipeline.groovy#L38-L52 Change
github {
//github
credentialsId 'github-user-and-token'
repoOwner project_folder
repository project_name
//behaviors not supported by job dsl
//additional behaviors
traits {
headWildcardFilterWithPR {
includes "${JERVIS_BRANCH}"
excludes ''
}
}
}
to
github {
//github
id 'anything-does-not-matter-as-only-one-source-configured'
credentialsId 'github-user-and-token'
repoOwner project_folder
repository project_name
//behaviors not supported by job dsl
//additional behaviors
traits {
headWildcardFilterWithPR {
includes "${JERVIS_BRANCH}"
excludes ''
}
}
}
And the problem should go away. Sam Gleske can you confirm the above?
Add Comment
[JIRA] (JENKINS-42509) authenticated team members should have read/build permissions when using Github Committer Authorization Strategy
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42509 Re: authenticated team members should have read/build permissions when using Github Committer Authorization Strategy Code changed in jenkins User: Christopher Williams Path: src/main/java/org/jenkinsci/plugins/GithubAuthenticationToken.java src/main/java/org/jenkinsci/plugins/GithubRequireOrganizationMembershipACL.java src/main/java/org/jenkinsci/plugins/GithubSecurityRealm.java src/test/java/org/jenkinsci/plugins/GithubRequireOrganizationMembershipACLTest.java src/test/java/org/jenkinsci/plugins/GithubSecurityRealmTest.java http://jenkins-ci.org/commit/github-oauth-plugin/7a4539f8c6f245b83c78b61acb3c94bfe43652b5 Log: JENKINS-42509 authenticated team members should have read/build (#91) JENKINS-42509 authenticated team members should have read/build permissions when using Github Committer Authorization Strategy On private repositories of which the user is not an owner, not a member of the owning organization - check for admin/push/pull permissions on the repository to determine permissions on the Jenkisn item. - Use a cache for loading repositories.- Guard against even trying to load repositories unless we have either the "repo" or "public_repo" oauth scopes. Add "repo" to the default set of oauth scopes requested. Add a wrapper POJO for storing GHRepository rights per-user in our cache. Make the repo cache an instance cache since it's specific to a user. Remove a coupel unnecessary final designations on method paramters. Add Comment
[JIRA] (JENKINS-46290) Project checkout fails (ERROR: Could not determine exact tip revision of master)
Title: Message Title Sam Gleske commented on JENKINS-46290 Re: Project checkout fails (ERROR: Could not determine exact tip revision of master) I would like to point out that this plugin is attempting to resolve the tip of my "jervis_simple" branch (as it should because I am building the jervis_simple branch) but for some reason is flailing about with the tip of master branch. Started by user Sam Gleske Running in Durability level: MAX_SURVIVABILITY Loading library Jervis Global Library@master Attempting to resolve master from remote references... > git --version # timeout=10 using GIT_ASKPASS to set credentials GitHub user and personal access token used by multibranch pipeline jobs for the GitHub API > git ls-remote -h -t https://github.com/samrocketman/jervis.git # timeout=10 Found match: refs/heads/master revision a82c0668ab31f0c992d26575e415971648c5c185 > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/samrocketman/jervis.git # timeout=10 Fetching without tags Fetching upstream changes from https://github.com/samrocketman/jervis.git > git --version # timeout=10 using GIT_ASKPASS to set credentials GitHub user and personal access token used by multibranch pipeline jobs for the GitHub API > git fetch --no-tags --progress https://github.com/samrocketman/jervis.git +refs/heads/*:refs/remotes/origin/* Checking out Revision a82c0668ab31f0c992d26575e415971648c5c185 (master) > git config core.sparsecheckout # timeout=10 > git checkout -f a82c0668ab31f0c992d26575e415971648c5c185 Commit message: "bump to snapshot" > git rev-list --no-walk a82c0668ab31f0c992d26575e415971648c5c185 # timeout=10 [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of jervis_simple Finished: FAILURE Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-46290) Project checkout fails (ERROR: Could not determine exact tip revision of master)
Title: Message Title Sam Gleske edited a comment on JENKINS-46290 Re: Project checkout fails (ERROR: Could not determine exact tip revision of master) I also encountered this in my project when building Jervis. Seems like odd behavior. If it can't compare to a previous revision then it should default to the git tip of the branch.This reliably happens to me. I shut down the service and start it. If I enter a branch and run it (after having already built it once) I get this issue. I'm using the pipeline multibranch plugin. Anybody can bootstrap my project with vagrant and replicate the behavior. https://github.com/samrocketman/jenkins-bootstrap-jervis 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-46290) Project checkout fails (ERROR: Could not determine exact tip revision of master)
Title: Message Title Sam Gleske edited a comment on JENKINS-46290 Re: Project checkout fails (ERROR: Could not determine exact tip revision of master) I also encountered this in my project when building Jervis. Seems like odd behavior. If it can't compare to a previous revision then it should default to the git tip of the branch.This reliably happens to me. I shut down the service and start it. If I enter a branch and run it (after having already built it once) I get this 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-46290) Project checkout fails (ERROR: Could not determine exact tip revision of master)
Title: Message Title Sam Gleske commented on JENKINS-46290 Re: Project checkout fails (ERROR: Could not determine exact tip revision of master) I also encountered this in my project when building Jervis. Seems like odd behavior. If it can't compare to a previous revision then it should default to the git tip of the branch. This reliably happens to me. I shut down the service and start it. If I enter a branch (after having already built it once) I get this 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-44292) Jcloud GCP network error
Title: Message Title Sebastien Gagnon commented on JENKINS-44292 Re: Jcloud GCP network error I guys, any news for a new release with this fix ? 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-48948) Convert To Pipeline Plugin missing link
Title: Message Title Danny Wong commented on JENKINS-48948 Re: Convert To Pipeline Plugin missing link Mohit Dharamshi, Vimal Patel, any updates??? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49613) SAML Plug org.pac4j.saml.exceptions.SAMLException: No valid subject assertion found in response
Title: Message Title Michael joye updated an issue Jenkins / JENKINS-49613 SAML Plug org.pac4j.saml.exceptions.SAMLException: No valid subject assertion found in response Change By: Michael joye Every time I try to setup Jenkins with Okta I keep on getting this error:org.pac4j.saml.exceptions.SAMLException: No valid subject assertion found in response at org.pac4j.saml.sso.impl.SAML2DefaultResponseValidator.validateSamlSSOResponse(SAML2DefaultResponseValidator.java:313) at org.pac4j.saml.sso.impl.SAML2DefaultResponseValidator.validate(SAML2DefaultResponseValidator.java:138) at org.pac4j.saml.sso.impl.SAML2WebSSOMessageReceiver.receiveMessage(SAML2WebSSOMessageReceiver.java:77) at org.pac4j.saml.sso.impl.SAML2WebSSOProfileHandler.receive(SAML2WebSSOProfileHandler.java:35) at org.pac4j.saml.client.SAML2Client.retrieveCredentials(SAML2Client.java:225) at org.pac4j.saml.client.SAML2Client.retrieveCredentials(SAML2Client.java:60) at org.pac4j.core.client.IndirectClient.getCredentials(IndirectClient.java:106) at org.jenkinsci.plugins.saml.SamlProfileWrapper.process(SamlProfileWrapper.java:53) at org.jenkinsci.plugins.saml.SamlProfileWrapper.process(SamlProfileWrapper.java:33) at org.jenkinsci.plugins.saml.OpenSAMLWrapper.get(OpenSAMLWrapper.java:65) at org.jenkinsci.plugins.saml.SamlSecurityRealm.doFinishLogin(SamlSecurityRealm.java:263) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:765) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:209) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at
[JIRA] (JENKINS-49613) SAML Plug org.pac4j.saml.exceptions.SAMLException: No valid subject assertion found in response
Title: Message Title Michael joye created an issue Jenkins / JENKINS-49613 SAML Plug org.pac4j.saml.exceptions.SAMLException: No valid subject assertion found in response Issue Type: Bug Assignee: Ivan Fernandez Calvo Attachments: Capture.PNG Components: saml-plugin Created: 2018-02-18 04:28 Environment: Window Server 2016 Jenkins 2.89.4 ace-editor 1.1 true ant 1.8 true antisamy-markup-formatter 1.5 true apache-httpcomponents-client-4-api 4.5.3-2.1 true authentication-tokens 1.3 true bouncycastle-api 2.16.2 true branch-api 2.0.18 true build-timeout 1.19 true cloudbees-folder 6.3 true command-launcher 1.2 true credentials 2.1.16 true credentials-binding 1.15 true display-url-api 2.2.0 true docker-commons 1.11 true docker-workflow 1.15.1 true durable-task 1.18 true email-ext 2.61 true external-monitor-job 1.7 true git 3.7.0 true git-client 2.7.1 true git-server 1.7 true github 1.29.0 true github-api 1.90 true github-branch-source 2.3.2 true gradle 1.28 true handlebars 1.1.1 true jackson2-api 2.8.11.1 true javadoc 1.4 true jquery-detached 1.2.1 true jsch 0.1.54.2 true junit 1.24 true ldap 1.19 true mailer 1.20 true mapdb-api 1.0.9.0 true matrix-auth 2.2 true matrix-project 1.12 true momentjs 1.1.1 true pam-auth 1.3 true perforce 1.3.36 true pipeline-build-step 2.7 true pipeline-github-lib 1.0 true pipeline-graph-analysis 1.6 true pipeline-input-step 2.8 true pipeline-milestone-step 1.3.1 true pipeline-model-api 1.2.7 true pipeline-model-declarative-agent 1.1.1 true pipeline-model-definition 1.2.7 true pipeline-model-extensions 1.2.7 true pipeline-rest-api 2.9 true pipeline-stage-step 2.3 true pipeline-stage-tags-metadata 1.2.7 true pipeline-stage-view 2.9 true plain-credentials 1.4 true resource-disposer 0.8 true saml 1.0.5 true scm-api 2.2.6 true script-security 1.41 true ssh-credentials 1.13 true ssh-slaves 1.25.1 true structs 1.14 true subversion 2.10.2 true timestamper 1.8.9 true token-macro 2.3 true windows-slaves 1.3.1 true workflow-aggregator 2.5 true workflow-api 2.25 true workflow-basic-steps 2.6 true workflow-cps 2.45 true workflow-cps-global-lib 2.9 true workflow-durable-task-step 2.19 true workflow-job 2.17 true workflow-multibranch 2.17 true workflow-scm-step 2.6 true workflow-step-api 2.14 true workflow-support 2.18 true ws-cleanup 0.34
[JIRA] (JENKINS-30113) Environment variables aren't passed to the docker container anymore
Title: Message Title Jon Hermansen assigned an issue to Jon Hermansen Jenkins / JENKINS-30113 Environment variables aren't passed to the docker container anymore Change By: Jon Hermansen Assignee: Nicolas De Loof Jon Hermansen 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-30919) Check Docker version
Title: Message Title Jon Hermansen assigned an issue to Jon Hermansen Jenkins / JENKINS-30919 Check Docker version Change By: Jon Hermansen Assignee: Nicolas De Loof Jon Hermansen 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-29239) Doesn't work when Jenkins itself is containerized
Title: Message Title Jon Hermansen assigned an issue to Jon Hermansen Jenkins / JENKINS-29239 Doesn't work when Jenkins itself is containerized Change By: Jon Hermansen Assignee: Nicolas De Loof Jon Hermansen 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-29677) Other build environment plugins aren't compatible with the Docker Build Environment Plugin
Title: Message Title Jon Hermansen assigned an issue to Jon Hermansen Jenkins / JENKINS-29677 Other build environment plugins aren't compatible with the Docker Build Environment Plugin Change By: Jon Hermansen Assignee: Nicolas De Loof Jon Hermansen 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-34361) Docker in Docker fix with JENKINS_HOME persistent volume
Title: Message Title Jon Hermansen assigned an issue to Jon Hermansen Jenkins / JENKINS-34361 Docker in Docker fix with JENKINS_HOME persistent volume Change By: Jon Hermansen Assignee: Nicolas De Loof Jon Hermansen 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-35497) If a docker image already exists, Docker Custom Build Environment will not pull a newer version of the image
Title: Message Title Jon Hermansen assigned an issue to Jon Hermansen Jenkins / JENKINS-35497 If a docker image already exists, Docker Custom Build Environment will not pull a newer version of the image Change By: Jon Hermansen Assignee: Nicolas De Loof Jon Hermansen 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-36886) Terminal escape sequences being shown
Title: Message Title Jon Hermansen assigned an issue to Jon Hermansen Jenkins / JENKINS-36886 Terminal escape sequences being shown Change By: Jon Hermansen Assignee: Nicolas De Loof Jon Hermansen 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-29946) Console Output blown up with refreshed line content
Title: Message Title Jon Hermansen assigned an issue to Jon Hermansen Jenkins / JENKINS-29946 Console Output blown up with refreshed line content Change By: Jon Hermansen Assignee: Nicolas De Loof Jon Hermansen 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-44791) Credentials for docker secured connection (TLS) not appliied
Title: Message Title Jon Hermansen assigned an issue to Jon Hermansen Jenkins / JENKINS-44791 Credentials for docker secured connection (TLS) not appliied Change By: Jon Hermansen Assignee: Nicolas De Loof Jon Hermansen 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-45998) Build failed when docker can't remove docker image
Title: Message Title Jon Hermansen closed an issue as Fixed Fixed in 754d9982d058d22604537e0b0c3cbd1bc164333d Jenkins / JENKINS-45998 Build failed when docker can't remove docker image Change By: Jon Hermansen Status: Open Closed Assignee: Nicolas De Loof Jon Hermansen Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message
[JIRA] (JENKINS-45998) Build failed when docker can't remove docker container
Title: Message Title Jon Hermansen updated an issue Jenkins / JENKINS-45998 Build failed when docker can't remove docker container Change By: Jon Hermansen Summary: Build failed when docker can't remove docker image container 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-37507) Add Pipeline Support for Publish over FTP
Title: Message Title Alex Earl commented on JENKINS-37507 Re: Add Pipeline Support for Publish over FTP I just released it this evening, should hit the update center within 24 hours. 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-37507) Add Pipeline Support for Publish over FTP
Title: Message Title Alex Earl commented on JENKINS-37507 Re: Add Pipeline Support for Publish over FTP I just released it this evening, should hit the update center within 24 hours. 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-37507) Add Pipeline Support for Publish over FTP
Title: Message Title Ed Lomonaco edited a comment on JENKINS-37507 Re: Add Pipeline Support for Publish over FTP is there a set date for this release? I'd love to switch to piplines pipelines , but this is blocking that 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-37507) Add Pipeline Support for Publish over FTP
Title: Message Title Ed Lomonaco commented on JENKINS-37507 Re: Add Pipeline Support for Publish over FTP is there a set date for this release? I'd love to switch to piplines, but this is blocking that 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-49612) Investigate behavior of positive-number validator in hudson-behavior JS
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-49612 Investigate behavior of positive-number validator in hudson-behavior JS Issue Type: Task Assignee: Unassigned Components: core Created: 2018-02-17 23:04 Priority: Minor Reporter: Oleg Nenashev It is a follow-up to the discussion in https://github.com/jenkinsci/jenkins/pull/3292#discussion_r168301766 (fix for JENKINS-49387 / JENKINS-49520). We need to investigate whether it is feasible to allow multi-zero prefixes before numbers. Add Comment
[JIRA] (JENKINS-49538) Release plugin doesn't appear at all
Title: Message Title Oleg Nenashev commented on JENKINS-49538 Re: Release plugin doesn't appear at all no worries, it happens. Thanks for the update! 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-34403) docker build fails if Dockerfile pip-installs simplejson
Title: Message Title Jon Hermansen assigned an issue to Jon Hermansen Jenkins / JENKINS-34403 docker build fails if Dockerfile pip-installs simplejson Change By: Jon Hermansen Assignee: Nicolas De Loof Jon Hermansen 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-31137) Dependency to Maven 2.12 is not optional
Title: Message Title Jon Hermansen commented on JENKINS-31137 Re: Dependency to Maven 2.12 is not optional I'll close this as done once I push a new version to the plugin repository. 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-31137) Dependency to Maven 2.12 is not optional
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31137 Re: Dependency to Maven 2.12 is not optional Code changed in jenkins User: Truc Nguyen Path: src/main/java/com/cloudbees/jenkins/plugins/docker_build_env/MavenPluginHelper.java http://jenkins-ci.org/commit/docker-custom-build-environment-plugin/93df66eea4d240b962b0295c2dac57d509e35ca0 Log: JENKINS-31137 avoid TcpSocketHostLocator NoClassDefError with optional maven-plugin 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-31137) Dependency to Maven 2.12 is not optional
Title: Message Title Jon Hermansen reopened an issue Jenkins / JENKINS-31137 Dependency to Maven 2.12 is not optional Change By: Jon Hermansen Resolution: Won't Fix Status: Closed 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-31137) Dependency to Maven 2.12 is not optional
Title: Message Title Jon Hermansen assigned an issue to Jon Hermansen Jenkins / JENKINS-31137 Dependency to Maven 2.12 is not optional Change By: Jon Hermansen Assignee: Nicolas De Loof Jon Hermansen 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-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs
Title: Message Title Stephen Connolly commented on JENKINS-48571 Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs So this is how BlueOcean creates its multibranch projects: https://github.com/jenkinsci/blueocean-plugin/blob/efb9de930e73454ebcda7625f168a426bc04f416/blueocean-pipeline-scm-api/src/main/java/io/jenkins/blueocean/scm/api/AbstractMultiBranchCreateRequest.java#L77-L78 In the case of GitSCMSource, no ID is assigned: https://github.com/jenkinsci/blueocean-plugin/blob/efb9de930e73454ebcda7625f168a426bc04f416/blueocean-git-pipeline/src/main/java/io/jenkins/blueocean/blueocean_git_pipeline/GitPipelineCreateRequest.java#L35-L44 In the case of GitHubSCMSource, we have https://github.com/jenkinsci/blueocean-plugin/blob/efb9de930e73454ebcda7625f168a426bc04f416/blueocean-github-pipeline/src/main/java/io/jenkins/blueocean/blueocean_github_pipeline/GithubPipelineCreateRequest.java#L51-L70 which would appear not to assign an ID (notice the null on this line: https://github.com/jenkinsci/blueocean-plugin/blob/efb9de930e73454ebcda7625f168a426bc04f416/blueocean-github-pipeline/src/main/java/io/jenkins/blueocean/blueocean_github_pipeline/GithubPipelineCreateRequest.java#L60 that should not be null)... let's check if anything else is helping us out along the code paths: https://github.com/jenkinsci/github-branch-source-plugin/blob/d60cc7617ee9ad56fd3ea3a3c3ad2569dc07c827/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSourceBuilder.java#L120-L127 nope, nothing there... https://github.com/jenkinsci/scm-api-plugin/blob/c63ce5d6406d48f3101f6ef3937e402e0bd0b3bf/src/main/java/jenkins/scm/api/SCMSource.java#L160-L166 nope nothing there either Bitbucket is the same: https://github.com/jenkinsci/scm-api-plugin/blob/c63ce5d6406d48f3101f6ef3937e402e0bd0b3bf/src/main/java/jenkins/scm/api/SCMSource.java#L160-L166 and again no id assigned https://github.com/jenkinsci/blueocean-plugin/blob/efb9de930e73454ebcda7625f168a426bc04f416/blueocean-bitbucket-pipeline/src/main/java/io/jenkins/blueocean/blueocean_bitbucket_pipeline/BitbucketPipelineCreateRequest.java#L64 Now this should only show up on Multibranch projects. If it is an org folder then the SCMNavigator is supposed to be assigning IDs based on a strict formula, e.g. https://github.com/jenkinsci/github-branch-source-plugin/blob/d60cc7617ee9ad56fd3ea3a3c3ad2569dc07c827/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java#L1560-L1564 and https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/9f5551b9c05e3bb51c9046204f8871157804401b/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketSCMNavigator.java#L874-L883 My analysis There are two separate issues here: The case of Multibranch Projects created by BlueOcean, in these cases BlueOcean is not assigning an ID and as a result, until the job has been reconfigured in the classic UI (should be sufficient to just open & save the job) the job will have the issue on every restart. IOW I claim a workaround of open and resave the multibranch project in classic UI. Please demonstrate otherwise. The case of Job DSL plugin being used incorrectly (no blame, just a statement of
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Code changed in jenkins User: Mostyn Bramley-Moore Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/d4e55360e2dd5f41bc556d7c181ecc29e4258109 Log: JENKINS-48258 add distinctive temp file prefix to aid debugging 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 SCM/JIRA link daemon commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/4241e818dbe27fb78093094f29ebcd2203166610 Log: Merge pull request #293 from mostynb/text_file_busy_debugging JENKINS-48258 add distinctive temp file prefix to aid debugging Compare: https://github.com/jenkinsci/git-client-plugin/compare/1bfc00f0d56a...4241e818dbe2 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-49538) Release plugin doesn't appear at all
Title: Message Title rherrick closed an issue as Not A Defect It turns out the problem was a rogue Puppet configuration that was configured to "restore" our Jenkins job configurations. Unfortunately it was "restoring" to a configuration that didn't have "Configure release build" turned on. So every time I'd work on the job configuration, Puppet would overwrite all my work. Sorry for the false alarm Jenkins / JENKINS-49538 Release plugin doesn't appear at all Change By: rherrick Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) --
[JIRA] (JENKINS-49538) Release plugin doesn't appear at all
Title: Message Title rherrick commented on JENKINS-49538 Re: Release plugin doesn't appear at all Oleg Nenashev No, nothing other than a couple of innocuous warnings. I've attached the contents of jenkins.log and health-checker.log recorded from start-up. The words "error", "warn", and "release" don't appear in any files in the ~jenkins/logs folder at all. 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-49538) Release plugin doesn't appear at all
Title: Message Title rherrick updated an issue Jenkins / JENKINS-49538 Release plugin doesn't appear at all Change By: rherrick Attachment: health-checker.log Attachment: jenkins.log 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-47958) Closed branches clone again and try build
Title: Message Title Joseph Petersen resolved as Fixed Fixed in Bitbucket Branch Source Plugin 2.2.10 Jenkins / JENKINS-47958 Closed branches clone again and try build Change By: Joseph Petersen 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-49561) FSSCM Does Not Update File Modifiers
Title: Message Title Jens Rogalli assigned an issue to Jens Rogalli Jenkins / JENKINS-49561 FSSCM Does Not Update File Modifiers Change By: Jens Rogalli Assignee: Oleg Nenashev Jens Rogalli 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-49561) FSSCM Does Not Update File Modifiers
Title: Message Title Jens Rogalli started work on JENKINS-49561 Change By: Jens Rogalli Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs
Title: Message Title Stephen Connolly commented on JENKINS-48571 Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs So looking at https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-git-pipeline/src/main/java/io/jenkins/blueocean/blueocean_git_pipeline/GitPipelineCreateRequest.java I note that it appears BlueOcean does not provide an ID when creating jobs (and BlueOcean bypasses the classic UI screen, so should be responsible for setting an ID) In the case of GitHub, BlueOcean is providing an ID: https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-github-pipeline/src/main/java/io/jenkins/blueocean/blueocean_github_pipeline/GithubPipelineCreateRequest.java (I cannot get line links from my phone, so I can only point at the files and I may be misreading on a small screen) R. Tyler Croy by any chance are you creating the jobs through BlueOcean? @all is it only GitSCMSource that is affected? 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-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs
Title: Message Title Alex Suter edited a comment on JENKINS-48571 Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs Hi [~stephenconnolly]I always create my multibranch build pipelines the following way: # Blue Ocean UI # Create new pipeline # Choose Git # Enter a git repository url from Bitbucket # CreateSo I always use the UI. Please let me know, if I can give any other informations. In my environement it is always reproducibale. (And I always use declarative pipelines) 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-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs
Title: Message Title Alex Suter commented on JENKINS-48571 Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs Hi Stephen Connolly I always create my multibranch build pipelines the following way: Blue Ocean UI Create new pipeline Choose Git Enter a git repository url from Bitbucket Create So I always use the UI. Please let me know, if I can give any other informations. In my environement it is always reproducibale. 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-7453) Quite Periode for File system SCM
Title: Message Title Ernst de Haan commented on JENKINS-7453 Re: Quite Periode for File system SCM The ticket description would benefit from: an explicit objective, and/or acceptance criteria, and/or test case(s) Currently if I would want to pick this up, I would have to do some significant research first, to determine what the issue is, and what would be an improved situation… 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-15496) Add Local module directory field like Subversion plugin
Title: Message Title Ernst de Haan commented on JENKINS-15496 Re: Add Local module directory field like Subversion plugin If and when this is implemented, seems like it would benefit from some unit tests, to cover the different cases properly. 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-15605) Add More Locations... button like Subversion plugin
Title: Message Title Ernst de Haan commented on JENKINS-15605 Re: Add More Locations... button like Subversion plugin Doesn't seem to be a Blocker for the FSSCM Plugin, as a product. Note that the priority refers to the product priority, not to the user's priority, see How to report an issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49560) FSSCM does not work with “checkout scm” on agent
Title: Message Title Ernst de Haan commented on JENKINS-49560 Re: FSSCM does not work with “checkout scm” on agent Seems this may be related to JENKINS-48769. Will link the tickets as related. 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-49523) archiveArtifacts excludes does not work with spaces
Title: Message Title
Stefan Drissen edited a comment on JENKINS-49523
Re: archiveArtifacts excludes does not work with spaces
And while accidentally leaving files to archive behind with a space, discovered that a space on includes will also fail the build: {code:java} ERROR: Whitespace can no longer be used as the separator. Please Use ‘,’ as the separator instead.Build step 'Archive the artifacts' changed build result to FAILURE {code}
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-49523) archiveArtifacts excludes does not work with spaces
Title: Message Title Stefan Drissen commented on JENKINS-49523 Re: archiveArtifacts excludes does not work with spaces And while accidentally leaving files to archive behind with a space, discovered that a space on includes will also fail the build: ERROR: Whitespace can no longer be used as the separator. Please Use ‘,’ as the separator instead. Build step 'Archive the artifacts' changed build result to FAILURE 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-12972) Add option to run 'git bisect' to find which commit added new bugs
Title: Message Title dor avraham assigned an issue to dor avraham Jenkins / JENKINS-12972 Add option to run 'git bisect' to find which commit added new bugs Change By: dor avraham Assignee: Andrey Belyaevskiy dor avraham 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-49611) Debian packaging: on upgrade jenkins should be re-started when idle instead immediately
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-49611 Debian packaging: on upgrade jenkins should be re-started when idle instead immediately Change By: Daniel Beck Issue Type: Bug Improvement 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-49611) Debian packaging: on upgrade jenkins should be re-started when idle instead immediately
Title: Message Title Daniel Beck commented on JENKINS-49611 Re: Debian packaging: on upgrade jenkins should be re-started when idle instead immediately Workaround would probably be to have long-running jobs use pipeline, whose running jobs survive restarts. I expect this won't see much traction any time soon because of that. 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-49611) Debian packaging: on upgrade jenkins should be re-started when idle instead immediately
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-49611 Debian packaging: on upgrade jenkins should be re-started when idle instead immediately Change By: Daniel Beck Summary: Debian packaging: on upgrade jenkins should be re-started when idle instead immediately 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-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs
Title: Message Title R. Tyler Croy commented on JENKINS-48571 Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs Stephen Connolly none of the Multibranch Pipelines I configure are "automated." They are however largely GitHub Organization Folders (see also). 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-49611) on upgrade jenkins should be re-started when idle instead immediately
Title: Message Title christof Schulze updated an issue Jenkins / JENKINS-49611 on upgrade jenkins should be re-started when idle instead immediately Change By: christof Schulze Summary: on upgrade jenkins should be re-started when idle instead immediately 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-49611) on upgrade jenkins should be re-started when idle
Title: Message Title christof Schulze created an issue Jenkins / JENKINS-49611 on upgrade jenkins should be re-started when idle Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: packaging Created: 2018-02-17 13:17 Labels: user-experience Priority: Major Reporter: christof Schulze whenever a new jenkins package is available and installed by apt-get install or unattended-upgrade, jenkins is immediately re-started. This is very intrusive because it immediately cancels running users jobs. This is especially annoying on long-running jobs over night. Package upgrades should not impact users processes. Fortunately jenkins has the option to re-start as soon as it is idle. when installing an upgrade that should be used instead of the immediate re-start. Add Comment
[JIRA] (JENKINS-49610) The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-49610 The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned Change By: Stephen Connolly Issue Type: Bug Improvement 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-49610) The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned
Title: Message Title Stephen Connolly commented on JENKINS-49610 Re: The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned There may also be other potential solutions. e.g. your original PR could be a potential solution if you want to put that in the assessment. Feel free to just take my two proposed candidate solutions or to investigate and come up with additional proposed solutions... you need to assess at least two solutions though, and I'd like the "throwing IllegalStateException" to be included in the assessment 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-49610) The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned
Title: Message Title
Stephen Connolly commented on JENKINS-49610
Re: The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned
Assessment criteria for selection of a proposed solution
I'm not looking for anything complex or a heavyweight process... could be as simple as "I'm going to setup a test system with a broken job-dsl script that doesn't assign {{id}}s and see which causes rebuilds" or could be as complex as 10 pages of various metrics (I would hope you err on the side of simple though) Just let's get the criteria agreed, documented and record the results and decision.
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-49610) The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned
Title: Message Title Stephen Connolly commented on JENKINS-49610 Re: The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned FTR my initial gut feeling is that throwing IllegalStateException is the better way to go as the UI code paths should always be pre-assigning an ID and this would catch users of e.g. JobDSL and present them with a meaningful exception that guides them to their solution. That would have the side-effect of breaking existing (IMHO already broken) systems... but the other approach would give those systems build storms which would be a much more subtle problem to notice 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-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs
Title: Message Title Stephen Connolly commented on JENKINS-48571 Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs I have created JENKINS-49610 and assigned it to Andrew Bayer. 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-49610) The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned
<<< text/html; charset="UTF-8": Unrecognized >>>
[JIRA] (JENKINS-49596) User session memory leak
Title: Message Title Oleg Nenashev updated JENKINS-49596 Jenkins / JENKINS-49596 User session memory leak Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49596) User session memory leak
Title: Message Title Oleg Nenashev assigned an issue to olamy Jenkins / JENKINS-49596 User session memory leak Change By: Oleg Nenashev Assignee: olamy 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-49596) User session memory leak
Title: Message Title Oleg Nenashev started work on JENKINS-49596 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49596) User session memory leak
Title: Message Title olamy commented on JENKINS-49596 Re: User session memory leak yup good catch sounds something to change in winstone and sessionCache configuration. I have updated https://github.com/jenkinsci/winstone/pull/44 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-49523) archiveArtifacts excludes does not work with spaces
Title: Message Title Stefan Drissen commented on JENKINS-49523 Re: archiveArtifacts excludes does not work with spaces Interestingly the includes fill-in has already had some ui treatment applied previously and shows: 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-49523) archiveArtifacts excludes does not work with spaces
Title: Message Title Stefan Drissen updated an issue Jenkins / JENKINS-49523 archiveArtifacts excludes does not work with spaces Change By: Stefan Drissen Attachment: image-2018-02-17-12-12-52-262.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49593) Document FSSCM License
Title: Message Title Ernst de Haan commented on JENKINS-49593 Re: Document FSSCM License 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-11283) JDepend Report Not Showing
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-11283 JDepend Report Not Showing Change By: Oleg Nenashev Assignee: Lewisham 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-37158) Pipeline support for jdepend
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-37158 Pipeline support for jdepend Change By: Oleg Nenashev Issue Type: Task 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-20137) Temporary directory deletion disabled
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-20137 Temporary directory deletion disabled Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20137) Temporary directory deletion disabled
Title: Message Title Oleg Nenashev started work on JENKINS-20137 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20137) Temporary directory deletion disabled
Title: Message Title Oleg Nenashev commented on JENKINS-20137 Re: Temporary directory deletion disabled https://github.com/jenkinsci/jdepend-plugin/pull/1 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-20137) Temporary directory deletion disabled
Title: Message Title Oleg Nenashev updated JENKINS-20137 Jenkins / JENKINS-20137 Temporary directory deletion disabled Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs
Title: Message Title
Stephen Connolly commented on JENKINS-48571
Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs
Action Items
R. Tyler Croy Can you provide details as to how you create the multibranch projects, specifically the code snippet where you set the sources on the multibranch project.
Leandro Narosky / Tristan Lewis / Ygor Almeida Can you confirm/deny whether you are using something like the JobDSL or other non-UI mechanism to create the affected multibranch projects. (if my theory is correct, the solution is completely in your hands by fixing your scripts to assign a non-null ID. The ID can be anything, e.g. dummy, as long as it is unique within that SCMSourceOwner. The purpose of the ID is to allow determining branch take-over in the case where multiple sources have been configured in the multi-branch project, which results from the original vision that things like pull requests would be discovered by using a second source rather than having the primary source discover them through traits.
Andrew Bayer The correct hack fix, if we need a fix (see note), should be in branch-api, we should be able to ensure that we call getId() on all sources before the save() which would prevent the issue on behalf of users that are unaware of the requirements to assign IDs.
There are two ways you could achieve this: 1. BranchSource's constructors could just call getId(). 2. MultibranchProject's save() could just iterate all the sources calling getId(). I'll let you decide whether you want to do one or both of these. With this done, you should have the minimum fix.
You may want to consider adding a reflection based pre-emptive fix for the special case where there is one and only one source without an ID.
Basically, in onLoad you could look at the sources and by reflection peek at id if exactly one of those inspected id}}s is {{null then you can look at all the child branches and see if there is exactly one unknown id among all the child projects (and that id should not be the special "dead branch" id)... if that set of conditions is met then you can assign the discovered id and trigger a save()
The above could be a lot of work, but it would benefit users as anyone affected by this issue and in the majority case of exactly one source would get their jobs fixed automatically on restart.
The above would be the maximal fix, which would be nicer in that it fixes things for users.
NOTE: R. Tyler Croy / Leandro Narosky / Tristan Lewis / Ygor Almeida if Andrew Bayer implements this then you will get build storms every time you reconfigure the project using whatever mechanism you are using to update the job configuration.
Assuming my theory is correct, and you are overwriting the sources periodically. Since the sources you are overwriting with do not have an id
[JIRA] (JENKINS-48725) Jenkins startup workflow can deadlock if exceptions occur during extensions lookup
Title: Message Title Oleg Nenashev updated JENKINS-48725 It has been released in Jenkins 2.105 Jenkins / JENKINS-48725 Jenkins startup workflow can deadlock if exceptions occur during extensions lookup Change By: Oleg Nenashev 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
[JIRA] (JENKINS-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs
Title: Message Title Stephen Connolly commented on JENKINS-48571 Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs So I suspect the affected users are not configuring jobs through the UI. When I configure the job via the UI, then the ID gets assigned correctly. So unless somebody can show otherwise, this smells a lot like "user error" (not necessarily that it is the user's fault for the error mind) Case in point, I took my own Jenkins and created a fresh multibranch project and added a GitSCMSource via the UI and saved => I inspected the config.xml on-disk manually and we have: "jenkins.branch.MultiBranchProject$BranchSourceList" plugin="branch-api@2.0.18"> "jenkins.plugins.git.GitSCMSource" plugin="git@3.7.0"> d3e70531-9f4d-4a7b-972f-339296b80997 "jenkins.branch.DefaultBranchPropertyStrategy"> "empty-list"/> "org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject" reference="../.."/> which matches exactly the id that is in memory. My initial suspect would be code like the job-dsl plugin. If the user was relying on an accidental side-effect that resulted in the id getting queried before the save, then that would explain things. As I understand, CodeValet uses some automatic configuration mechanism to define jobs... looks like that mechanism is not assigning an id before configuring the list of BranchSources. Now in https://github.com/jenkinsci/scm-api-plugin/blob/master/docs/consumer.adoc#scmsourceowner-contract we have Ensure that SCMSource.setOwner(owner) has been called before any SCMSource instance is returned from either SCMSourceOwner.getSCMSources() or SCMSourceOwner.getSCMSource(id). We should probably make more a explicit part of the contract of a SCMSourceOwner that all SCMSource instances that are added to the owner must have an id assigned before ownership is set (or we can fall back to ensuring an id has been assigned as a (minimal) side-effect of calling SCMSource.setOwner(owner). That would minimize the issue for users, but probably should be a separate ticket. I also thought I had documented somewhere (but I cannot find where... and https://github.com/jenkinsci/branch-api-plugin/blob/master/docs/user.adoc seems considerably more anemic than I thought I had left it) that it was critical - if using stuff like JobDSL - that you must assign an id... Hmmm https://github.com/jenkinsci/scm-api-plugin/blob/master/docs/implementation.adoc#implementing-jenkinsscmapiscmsource has a note on IDs... SCMSource IDs The SCMSource’s IDs are used to help track the SCMSource that a SCMHead instance originated from. If - and only if - you are certain that you can construct a definitive ID from the configuration details of your SCMSource then implementations are encouraged to use a computed ID. When instantiating an
[JIRA] (JENKINS-49206) Jenkins Timer threads could get a bogus classLoader
Title: Message Title Oleg Nenashev updated JENKINS-49206 It has been released in Jenkins 2.105, so that it will become available in 2.107.1 LTS Jenkins / JENKINS-49206 Jenkins Timer threads could get a bogus classLoader Change By: Oleg Nenashev 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
[JIRA] (JENKINS-45897) Remoting Request classes should offer better toString(), which allow identifying them
Title: Message Title Oleg Nenashev commented on JENKINS-45897 Re: Remoting Request classes should offer better toString(), which allow identifying them It has been released in Remoting 3.17 and Jenkins 2.106 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-49027) Improve diagnostics of rejected objects in Remoting
Title: Message Title Oleg Nenashev edited a comment on JENKINS-49027 Re: Improve diagnostics of rejected objects in Remoting It has been released in Remoting 3.17 and Jenkins 2. 107 106 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-27035) Request/response statistics
Title: Message Title Oleg Nenashev edited a comment on JENKINS-27035 Re: Request/response statistics It has been released in Remoting 3.17 and Jenkins 2. 107 106 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-27035) Request/response statistics
Title: Message Title Oleg Nenashev updated JENKINS-27035 It has been released in Remoting 3.17 and Jenkins 2.107 Jenkins / JENKINS-27035 Request/response statistics Change By: Oleg Nenashev 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-49027) Improve diagnostics of rejected objects in Remoting
Title: Message Title Oleg Nenashev resolved as Fixed It has been released in Remoting 3.17 and Jenkins 2.107 Jenkins / JENKINS-49027 Improve diagnostics of rejected objects in Remoting Change By: Oleg Nenashev 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
[JIRA] (JENKINS-49565) Update Jenkins CLI to Mina SSHD 1.7.0 and make it always similar to the Jenkins Core
Title: Message Title Oleg Nenashev resolved as Fixed Merged towards 2.108 Jenkins / JENKINS-49565 Update Jenkins CLI to Mina SSHD 1.7.0 and make it always similar to the Jenkins Core Change By: Oleg Nenashev 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
[JIRA] (JENKINS-49565) Update Jenkins CLI to Mina SSHD 1.7.0 and make it always similar to the Jenkins Core
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49565 Update Jenkins CLI to Mina SSHD 1.7.0 and make it always similar to the Jenkins Core Change By: Oleg Nenashev It is a follow up to https://github.com/jenkinsci/jenkins/pull/3278#issuecomment-365754422 2.107 has been released with new SSHD Core in SSHD Module, but I forgot to update the CLI client. Although it is perfectly safe, it may worth updating CLI in LTS so that the used versions are consistent. 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-49565) Update Jenkins CLI to Mina SSHD 1.7.0 and make it always similar to the Jenkins Core
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49565 Update Jenkins CLI to Mina SSHD 1.7.0 and make it always similar to the Jenkins Core Change By: Oleg Nenashev Labels: lts-candidate 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-49565) Update Jenkins CLI to Mina SSHD 1.7.0 and make it always similar to the Jenkins Core
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49565 Re: Update Jenkins CLI to Mina SSHD 1.7.0 and make it always similar to the Jenkins Core Code changed in jenkins User: Oleg Nenashev Path: cli/pom.xml http://jenkins-ci.org/commit/jenkins/54431a11e60e518dfd49a00e00c0054b37b5ee31 Log: Merge pull request #3296 from oleg-nenashev/sshd/JENKINS-49565 JENKINS-49565 - Update Jenkins CLI to Mina SSHD Core 1.7.0 Compare: https://github.com/jenkinsci/jenkins/compare/0e51e36023d0...54431a11e60e 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-49565) Update Jenkins CLI to Mina SSHD 1.7.0 and make it always similar to the Jenkins Core
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49565 Re: Update Jenkins CLI to Mina SSHD 1.7.0 and make it always similar to the Jenkins Core Code changed in jenkins User: Oleg Nenashev Path: cli/pom.xml http://jenkins-ci.org/commit/jenkins/36f7fc0d925338a2642553ec7e7a0eda938fb3f6 Log: JENKINS-49565 - Update Jenkins CLI to Mina SSHD Core 1.7.0 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 Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-49607 ssh-slaves-plugin should report the required java version when none found Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49607) ssh-slaves-plugin should report the required java version when none found
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49607 ssh-slaves-plugin should report the required java version when none found Change By: Oleg Nenashev Labels: newbie-friendly Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49607) ssh-slaves-plugin should report the required java version when none found
Title: Message Title Oleg Nenashev commented on JENKINS-49607 Re: ssh-slaves-plugin should report the required java version when none found Yes, it could. Sounds like a quick win 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-49593) Document FSSCM License
Title: Message Title Oleg Nenashev commented on JENKINS-49593 Re: Document FSSCM License Both work for me, 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-49593) Document FSSCM License
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49593 Re: Document FSSCM License Code changed in jenkins User: Ernst de Haan Path: LICENSE.txt http://jenkins-ci.org/commit/filesystem_scm-plugin/b9911aafe6877027363914b00e0affac3fae0f2d Log: JENKINS-49593: Updated LICENSE file to have same copyright owners as in README. 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-49593) Document FSSCM License
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49593 Re: Document FSSCM License Code changed in jenkins User: Ernst de Haan Path: LICENSE.txt README.md http://jenkins-ci.org/commit/filesystem_scm-plugin/bd59a80d0dce183f316d762411af3c09e2121d5e Log: JENKINS-49593: Added LICENSE.txt file, and documented license in README.md file. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49593) Document FSSCM License
Title: Message Title Oleg Nenashev closed an issue as Fixed Jenkins / JENKINS-49593 Document FSSCM License Change By: Oleg Nenashev Status: Resolved Closed 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-49593) Document FSSCM License
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49593 Re: Document FSSCM License Code changed in jenkins User: Ernst de Haan Path: README.md http://jenkins-ci.org/commit/filesystem_scm-plugin/0c10841a229e2f78552008e7bb9f8fbb928442a5 Log: JENKINS-49593: Processed PR review feedback: just referencing local LICENSE file. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49593) Document FSSCM License
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49593 Re: Document FSSCM License Code changed in jenkins User: Oleg Nenashev Path: LICENSE.txt README.md http://jenkins-ci.org/commit/filesystem_scm-plugin/d735e4f892a80b3c0ec411f71debaac06b296778 Log: Merge pull request #7 from znerd/JENKINS-49593 JENKINS-49593: Added LICENSE file, and documented license in README. Compare: https://github.com/jenkinsci/filesystem_scm-plugin/compare/78341c0048f9...d735e4f892a8 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.
