[JIRA] (JENKINS-46255) Windows Slave Plugin to support SMB Version 2 or greater
Title: Message Title Marcel Meschenmoser commented on JENKINS-46255 Re: Windows Slave Plugin to support SMB Version 2 or greater We have the same problem with windows 10 1709. Is there a workaround? 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-49526) SCM Polling frequency in Branch Source generated Multibranch projects seems hardcoded
Title: Message Title Jim Klimov commented on JENKINS-49526 Re: SCM Polling frequency in Branch Source generated Multibranch projects seems hardcoded So far my workaround was to add a job to regularly rescan MBPs that are inside folders : https://pastebin.com/xKM7CStM It still is sub-optimal and has its quirks, but at least seems to work. Thanks to Andrew Bayer and many others for hints on IRC 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-49526) SCM Polling frequency in Branch Source generated Multibranch projects seems hardcoded
Title: Message Title Jim Klimov edited a comment on JENKINS-49526 Re: SCM Polling frequency in Branch Source generated Multibranch projects seems hardcoded So far my workaround was to add a job to regularly rescan MBPs that are inside folders : https://pastebin.com/xKM7CStMIt still is sub-optimal and has its quirks, but at least seems to work.Thanks to [~abayer] and many others for hints on IRC , and to people asking good questions on StackOverflow et al :) 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-49746) Regex returns more matches than it should if errors are close together
Title: Message Title Richard Wilkinson commented on JENKINS-49746 Re: Regex returns more matches than it should if errors are close together Yes, a parsed file which only returns the expected number of matches plus the additional lines following the last expected match, the 5th match in this case. So your output looks exactly as I'd expect. 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-50194) Build userId missing for a job being built by other Jobs
Title: Message Title Naresh Rayapati edited a comment on JENKINS-50194 Re: Build userId missing for a job being built by other Jobs Merged above pull request, will release the artifact once after a bit of local testing. 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-50194) Build userId missing for a job being built by other Jobs
Title: Message Title Naresh Rayapati updated JENKINS-50194 Jenkins / JENKINS-50194 Build userId missing for a job being built by other Jobs Change By: Naresh Rayapati 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-50194) Build userId missing for a job being built by other Jobs
Title: Message Title Naresh Rayapati commented on JENKINS-50194 Re: Build userId missing for a job being built by other Jobs Merged above pull request, will release the artifact once after a bit of local testing. 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-46255) Windows Slave Plugin to support SMB Version 2 or greater
Title: Message Title Marcel Meschenmoser assigned an issue to Emilio Escobar Jenkins / JENKINS-46255 Windows Slave Plugin to support SMB Version 2 or greater Change By: Marcel Meschenmoser Assignee: Emilio Escobar 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-48420) Provide lightweight checkout capability for Subversion
Title: Message Title Jesús Malo Poyatos commented on JENKINS-48420 Re: Provide lightweight checkout capability for Subversion Andreas Magnusson: Thanks for the link to the GitHub project. Did you send the PR? 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-50191) Multibranch Pipeline tends to keep rebuilding same commits
Title: Message Title Daniel Beck commented on JENKINS-50191 Re: Multibranch Pipeline tends to keep rebuilding same commits Checkout needs to have finished for a build to be able to make subsequent SCM operations consider the commit already handled. Is this the problem? Huge checkouts, or perhaps even checkouts that aren't happening at the start of the build? 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-42582) ssh-agent not applied in kubernetes container
Title: Message Title Bernhard Kaszt commented on JENKINS-42582 Re: ssh-agent not applied in kubernetes container We also sometimes get the exactly same error. It often works, but randomly throws this error. And it's not clear why it fails then. There is no error message except that ssh-add failed to run. 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-47488) PortMapping does not work when configured in pipeline
Title: Message Title Timothy Clarke commented on JENKINS-47488 Re: PortMapping does not work when configured in pipeline I think your expectation here is wrong. sh 'curl http://localhost:9000' // works only with 10080 When you're in a container you're in a different routed environment than the host you're on. The command above is being run within the container so "localhost" (I assume you mean 127.0.0.1) is the loopback address of the POD, not the loopback address of the node The thing I have noticed (not sure if it's related) is that DNS names in the cluster are not being registered. I assume this may have been taken care of by k8s's now deprecated pod hostname. I think when you register a portMapping the name should be registered as a k8s svc name 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-47488) PortMapping does not work when configured in pipeline
Title: Message Title
Timothy Clarke edited a comment on JENKINS-47488
Re: PortMapping does not work when configured in pipeline
I think your expectation here is wrong.{code:java}sh 'curl http://localhost:9000' // works only with 10080{code}When you're in a container you're in a different routed environment than the host you're on.The command above is being run within the container so "localhost" (I assume you mean 127.0.0.1) is the loopback address of the POD, not the loopback address of the nodeThe thing I have noticed (not sure if it's related) is that DNS names in the cluster are not being registered. I assume this may have been taken care of by k8s's now deprecated pod hostname. I think when you register a portMapping the name should be registered as a k8s svc name To get to the hostport you would need to go through the node name
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-49449) Author basic smoke tests of the jenkins/evergreen container
Title: Message Title Baptiste Mathus resolved as Fixed Marking this as done as we now have https://github.com/jenkins-infra/evergreen/blob/dc621bdb94667e152c35ffd23392630e0ce51cdd/tests/tests.sh in place and though we don't have tests yet for the client (since, well, there's not really a functional client yet), we should be able to write tests for in a similar fashion. Jenkins / JENKINS-49449 Author basic smoke tests of the jenkins/evergreen container Change By: Baptiste Mathus Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You
[JIRA] (JENKINS-21336) ADMINISTER should not imply RUN_SCRIPTS
Title: Message Title Wadeck Follonier commented on JENKINS-21336 Re: ADMINISTER should not imply RUN_SCRIPTS Problem addressed in scriptler. 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-50211) Add an option to optionally reject connections from agents with unsupported Remoting versions
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-50211 Add an option to optionally reject connections from agents with unsupported Remoting versions Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-03-16 08:49 Labels: remoting Priority: Minor Reporter: Oleg Nenashev It is a follow-up to JENKINS-48766. That story adds warnings for unsupported agent versions, but it actually does not reject them. It would be useful to have such feature in the core or in Version Column Plugin. Core is preferable though this feature may be detached to a plugin later as a part of JENKINS-44100. Acceptance criteria: There is a Global Configuration entry for Remoting. An existing section for Remoting protocols may be used There is a checkbox in the configuration, which turns on rejection of unsupported versions SlaveComputer#setChannel() checks the option status. Depending on it, it may either accept or reject the connection
[JIRA] (JENKINS-49406) Prototype the Evergreen snapshotting data safety system
Title: Message Title Raul Arabaolaza commented on JENKINS-49406 Re: Prototype the Evergreen snapshotting data safety system I fully agree also. Just for openness and even if this has been already add to other sources this are the meeting notes of my conversation with Baptiste Mathus yesterday: RAUL: This is intended for development time, not for deployment validation Idea is Try an upgrade, test all works properly perform a rollback and test again all is working BAPTISTE: We are likely to be able to reuse the “health check” logic that will have to be developed for evergreen-client itself in production, to check if Jenkins is running fine. RAUL: critical: we need to test the health check QUESTION: Should we try to implement synthetic transactions here or go with ATH which already exists? PROPOSALS for Rollback testing: Make sure there is enough coverage that all possible rollback paths are covered Create a quality bar for rollbacks Make sure you are including some failing scenarios in the quality bar Not only test the happy path, for example: Made a failed upgrade, test that we are able to detect the upgrade as a failure, rollback and test that the instance is working perfectly Made a failed upgrade, test that we are able to detect the upgrade as a failure, made a failed rollback and test that we are able to detect the rollback failed Make sure that in case of different chained rollback strategies we test each and every one of them Create a healthcheck url to be invoked via CURL for example We can create a plugin that provides that healthcheck url and integrate with ST Maybe some work from metrics plugin can be reused Some possible testing flows: Upgrade run health check (ST), rollback, ST again ¿and ATH? No work yet on ST that I am aware of, but ST can be later reused for deployment testing Run ATH, rollback, ATH again Some work already done, but ATH is maybe too heavy and coverage is pretty poor and based on individual
[JIRA] (JENKINS-50213) SEVERE io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor Could not find execution for run
Title: Message Title James Nord created an issue Jenkins / JENKINS-50213 SEVERE io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor Could not find execution for run Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin, pipeline Created: 2018-03-16 09:37 Labels: pipeline blue-pipeline-scrub Priority: Minor Reporter: James Nord Log Spam in the logs when a garbage pipeline is run and then viewed in BO. Mar 15, 2018 4:51:36 PM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finish james1234/p1 #1 completed: FAILURE Mar 15, 2018 4:51:36 PM WARNING org.jenkinsci.plugins.workflow.flow.FlowExecutionList unregister Owner[james1234/p1/1:james1234/p1 #1] was not in the list to begin with: [] Mar 15, 2018 4:51:36 PM SEVERE io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor Could not find execution for run james1234/p1#1 Mar 15, 2018 4:51:36 PM SEVERE io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor Could not find execution for run james1234/p1#1 Mar 15, 2018 4:51:36 PM SEVERE io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor Could not find execution for run james1234/p1#1 Mar 15, 2018 4:51:38 PM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finish james1234/p1 #2 completed: FAILURE Mar 15, 2018 4:51:38 PM WARNING org.jenkinsci.plugins.workflow.flow.FlowExecutionList unregister Owner[james1234/p1/2:james1234/p1 #2] was not in the list to begin with: [] Mar 15, 2018 4:51:38 PM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finish james1234/p1 #3 completed: FAILURE Mar 15, 2018 4:51:38 PM WARNING
[JIRA] (JENKINS-50213) SEVERE io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor Could not find execution for run
Title: Message Title James Nord updated an issue Jenkins / JENKINS-50213 SEVERE io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor Could not find execution for run Change By: James Nord Environment: Jenkins 2.107 * blueocean:1.4.2 'Blue Ocean' * blueocean-autofavorite:1.2.2 'Autofavorite for Blue Ocean' * blueocean-bitbucket-pipeline:1.4.2 'Bitbucket Pipeline for Blue Ocean' * blueocean-commons:1.4.2 'Common API for Blue Ocean' * blueocean-config:1.4.2 'Config API for Blue Ocean' * blueocean-core-js:1.4.2 'Blue Ocean Core JS' * blueocean-dashboard:1.4.2 'Dashboard for Blue Ocean' * blueocean-display-url:2.1.1 'Display URL for Blue Ocean' * blueocean-events:1.4.2 'Events API for Blue Ocean' * blueocean-git-pipeline:1.4.2 'Git Pipeline for Blue Ocean' * blueocean-github-pipeline:1.4.2 'GitHub Pipeline for Blue Ocean' * blueocean-i18n:1.4.2 'i18n for Blue Ocean' * blueocean-jira:1.4.2 'JIRA Integration for Blue Ocean' * blueocean-jwt:1.4.2 'JWT for Blue Ocean' * blueocean-personalization:1.4.2 'Personalization for Blue Ocean' * blueocean-pipeline-api-impl:1.4.2 'Pipeline implementation for Blue Ocean' * blueocean-pipeline-editor:1.4.2 'Blue Ocean Pipeline Editor' * blueocean-pipeline-scm-api:1.4.2 'Pipeline SCM API for Blue Ocean' * blueocean-rest:1.4.2 'REST API for Blue Ocean' * blueocean-rest-impl:1.4.2 'REST Implementation for Blue Ocean' * blueocean-web:1.4.2 'Web for Blue Ocean' * pipeline-build-step:2.5.1 'Pipeline: Build Step' * pipeline-github-lib:1.0 'Pipeline: GitHub Groovy Libraries' * pipeline-graph-analysis:1.6 'Pipeline Graph Analysis Plugin' * pipeline-input-step:2.8 'Pipeline: Input Step' * pipeline-maven:3.4.3 'Pipeline Maven Integration Plugin' * pipeline-milestone-step:1.3.1 'Pipeline: Milestone Step' * pipeline-model-api:1.2.7 'Pipeline: Model API' * pipeline-model-declarative-agent:1.1.1 'Pipeline: Declarative Agent API' * pipeline-model-definition:1.2.7 'Pipeline: Declarative' * pipeline-model-extensions:1.2.7 'Pipeline: Declarative Extension Points API' * pipeline-rest-api:2.9 'Pipeline: REST API Plugin' * pipeline-stage-step:2.2 'Pipeline: Stage Step' * pipeline-stage-tags-metadata:1.2.7 'Pipeline: Stage Tags Metadata' * pipeline-stage-view:2.9 'Pipeline: Stage View Plugin'* workflow-aggregator:2.5 'Pipeline' * workflow-api:2.26 'Pipeline: API' * workflow-basic-steps:2.6 'Pipeline: Basic Steps' * workflow-cps:2.45 'Pipeline: Groovy' * workflow-cps-checkpoint:2.7 'CloudBees Pipeline: Groovy Checkpoint Plugin' * workflow-cps-global-lib:2.9 'Pipeline: Shared Groovy Libraries' * workflow-durable-task-step:2.18 'Pipeline: Nodes and Processes' * workflow-job:2.17 'Pipeline: Job' * workflow-multibranch:2.17 'Pipeline: Multibranch' * workflow-scm-step:2.6 'Pipeline: SCM Step' * workflow-step-api:2.14 'Pipeline: Step API' * workflow-support:2.18 'Pipeline: Supporting APIs'
[JIRA] (JENKINS-43100) bapSshPublisher closure requires sshCredentials in Jenkins DSL.
Title: Message Title Daniel Spilker assigned an issue to Alex Earl Jenkins / JENKINS-43100 bapSshPublisher closure requires sshCredentials in Jenkins DSL. Change By: Daniel Spilker Assignee: Daniel Spilker 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-50211) Add an option to optionally reject connections from agents with unsupported Remoting versions
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50211 Add an option to optionally reject connections from agents with unsupported Remoting versions Change By: Oleg Nenashev It is a follow-up to JENKINS-48766. That story adds warnings for unsupported agent versions, but it actually does not reject them. It would be useful to have such feature in the core or in Version Column Plugin. Core is preferable though this feature may be detached to a plugin later as a part of JENKINS-44100.Acceptance criteria:* There is a Global Configuration entry for Remoting. An existing section for Remoting protocols may be used* There is a checkbox in the configuration, which turns on rejection of unsupported versions* SlaveComputer#setChannel() checks the option status. Depending on it, it may either accept or reject the connection * Nice2have: Automatic test which confirms that the flag survives restarts * Nice2have: Automatic test which picks unsupported version of Remoting and confirms that it cannot connect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-45480) GIT Build with Parameters is not listing branches
Title: Message Title Marcel Dutt commented on JENKINS-45480 Re: GIT Build with Parameters is not listing branches Boguslaw Klimas We have a Bitbucket Server as git server instead of using github. But in order to reproduce the issue I requested to grant our build machines access to github.com so I can try to reproduce the issue with your configuration. Hopefully this will help us find the culprit. 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-50212) Xvnc.DescriptorImpl.allocators retains entries for deleted computers
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-50212 Xvnc.DescriptorImpl.allocators retains entries for deleted computers Issue Type: Bug Assignee: Levon Saldamli Components: xvnc-plugin Created: 2018-03-16 09:09 Priority: Minor Reporter: Oliver Gondža I have stumbled upon a production deployment with 7732 entries (1.7M) for cloud slaves that are gone for a long time. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50214) Add ability to unzip files using a wildcard as zip file name
Title: Message Title Christian Hilden created an issue Jenkins / JENKINS-50214 Add ability to unzip files using a wildcard as zip file name Issue Type: Improvement Assignee: Suresh Kumar Components: file-operations-plugin Created: 2018-03-16 09:45 Environment: Plugin version 1.7, regarding unzip operation Jenkins version 2.89.4 on Windows Labels: zip zipfile Priority: Minor Reporter: Christian Hilden It would be greate if it would be possible to use some kind of wildcard expession as zip file name in unzip operations e.g. target\some-name-*.zip. Use case: We have to download latest build artifacts from a gitlab instance (which we cannot control) and use them in our builds. Unfortunatly those artifacts include zipped files with version codes and build time included in the filename (e.g.: some_components_0.5.0.201803151319.zip). Currently using wildcards in zip file names leads to a fatal error.
[JIRA] (JENKINS-50196) Jenkins Kubernetes plugin - Running a sequence of podTemplate with inheritFrom
Title: Message Title
Mattia Mascia updated an issue
Jenkins / JENKINS-50196
Jenkins Kubernetes plugin - Running a sequence of podTemplate with inheritFrom
Change By:
Mattia Mascia
h4. Test case A Pipeline script job as follows, The aim of this pipeline is to show the feature of *inheritFrom* : {code:java}podTemplate(cloud: 'openshift', inheritFrom: 'nodejs', name: 'nodejs-p', label: 'nodejs-p', volumes: [ persistentVolumeClaim(mountPath: '/home/jenkins/.npm', claimName: 'nodejs', readOnly: false)]) { node("nodejs-p") { stage('BuildFrontend') { // some commands } }}podTemplate(cloud: 'openshift', inheritFrom: 'maven', name: 'maven-p', label: 'maven-p', volumes: [ persistentVolumeClaim(mountPath: '/home/jenkins/.m2', claimName: 'maven', readOnly: false)]) { node("maven-p") { stage('BuildBackend') { // some commands } } } {code} h4. Outcome The first podTemplate definition works as expected. The second podTemplate starts, but instead of using the inheritFrom defined ('*maven*') it is using the '*nodejs-p*' as parent. As you guess is wrong and because the *nodejs-p* template is temporary, the plugin starts the default *jenkins-slave* container. If you invert the podTemplate definitions inside the pipeline, so first *maven-p* and second *nodejs-p* you obtain the same behaviour. The first works as expected and the second fails. It looks like a race condition issue. {noformat}Plugin-Version: 0.10Hudson-Version: 2.7.4Jenkins-Version: 2.7.4{noformat} {noformat}Plugin-Version: 1.0Hudson-Version: 2.32.1Jenkins-Version: 2.32.1{noformat}
Add Comment
[JIRA] (JENKINS-50196) Jenkins Kubernetes plugin - Running a sequence of podTemplate with inheritFrom
Title: Message Title Mattia Mascia updated an issue Jenkins / JENKINS-50196 Jenkins Kubernetes plugin - Running a sequence of podTemplate with inheritFrom Change By: Mattia Mascia Attachment: Screen Shot 2018-03-16 at 09.30.05.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-50211) Add an option to optionally reject connections from agents with unsupported Remoting versions
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50211 Add an option to optionally reject connections from agents with unsupported Remoting versions Change By: Oleg Nenashev It is a follow-up to JENKINS-48766. That story adds warnings for unsupported agent versions, but it actually does not reject them. It would be useful to have such feature in the core or in Version Column Plugin. Core is preferable though this feature may be detached to a plugin later as a part of JENKINS-44100.Acceptance criteria:* There is a Global Configuration entry for Remoting. An existing section for Remoting protocols may be used* There is a checkbox in the configuration, which turns on rejection of unsupported versions* SlaveComputer#setChannel() checks the option status. Depending on it, it may either accept or reject the connection* Nice2have: Automatic test which confirms that the flag survives restarts* Nice2have: Automatic test which picks unsupported version of Remoting and confirms that it cannot connect . See examples in https://github.com/jenkinsci/jenkins/blob/master/test/src/test/java/jenkins/slaves/OldRemotingAgentTest.java Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50211) Add an option to optionally reject connections from agents with unsupported Remoting versions
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50211 Add an option to optionally reject connections from agents with unsupported Remoting versions 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-50211) Add an option to optionally reject connections from agents with unsupported Remoting versions
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50211 Add an option to optionally reject connections from agents with unsupported Remoting versions Change By: Oleg Nenashev Priority: Minor Major 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-26253) When use xvnc in job, occurred NPE
Title: Message Title Oliver Gondža closed an issue as Cannot Reproduce Jenkins / JENKINS-26253 When use xvnc in job, occurred NPE Change By: Oliver Gondža Status: Open Closed Resolution: Cannot Reproduce 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-49861) Disable master executors by default
Title: Message Title Baptiste Mathus updated JENKINS-49861 Jenkins / JENKINS-49861 Disable master executors by default Change By: Baptiste Mathus 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-50214) Add ability to unzip files using a wildcard as zip file name
Title: Message Title Christian Hilden updated an issue Jenkins / JENKINS-50214 Add ability to unzip files using a wildcard as zip file name Change By: Christian Hilden It would be greate if it would be possible to use some kind of wildcard expession as zip file name in unzip operations e.g. target\some-name-*.zip.Use case:We have to download latest build artifacts from a gitlab instance (which we cannot control) and use them in our builds. Unfortunatly those artifacts include zipped files with version codes and build time included in the filename (e.g.: some_components_0.5.0.201803151319.zip). Using target file name in the download operation does not solve the problem as the versiond zip files are contained in the downloaded zip file. -> We have to unzip the outer file first and the inner file second. Currently using wildcards in zip file names leads to a fatal error. 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
[JIRA] (JENKINS-50131) git parameter
Title: Message Title Mark Waite commented on JENKINS-50131 Re: git parameter guillermo casco be sure that your Jenkinsfile on the branch is not inadvertently specifying that it should checkout the master branch. 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Sam Van Oort commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Ernst de Haan Perhaps someone (you or someone else) can implement such a “hack” as a plugin – probably with a fat disclaimer indicating that many of the scenarios (as mentioned by Sam Van Oort) are not covered I was actually going to suggest that. Some of those experiments can provide new ideas for how to implement a comprehensive feature – and if they work really well they may even be requested to directly merge into the core of Pipeline. More often they provide inspiration that leads one of us to hack out the ultimate solution. Personally, I absolutely hate that we can't easily address this improvement, but past lessons have also taught us that a maintainable and robust solution is much better for this kind of challenge than a quick-and-dirty solution that opens up problems down the road. Maybe someone will be able to come up with a solution that does not impose those risks though. 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-50222) Maven Metadata plugin does not iterate over credentials in folders
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-50222 Maven Metadata plugin does not iterate over credentials in folders Issue Type: Bug Assignee: Gesh Markov Components: maven-metadata-plugin Created: 2018-03-16 15:44 Priority: Major Reporter: Alex Taylor When using the Maven Metadata plugin, it does not pull credentials which are configured on folders and will only pull global credentials. An example resolved similar issue is https://issues.jenkins-ci.org/browse/JENKINS-34825 but that is on the P4 plugin Add Comment
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Sam Van Oort commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Kevin Phillips Believe me, we know exactly how irritating these limitations of the Pipeline architecture are because we "drink our own champagne" internally and use test result reporting extensively in Jenkins Pipelines. The problem is that this is directly tied to the limitations of the Pipeline data model, which internally is pass/fail – everything else is computed in a logical way on the basis of ErrorActions, Input Actions, whether or not the FlowNode in question is the tip of a incomplete build (In-progress). Anything that modifies how we store status is unfortunately a permanent change because it would have to work by recording data in the model, either by Actions on FlowNodes, or by some internal state, or both. Thus any "hacks" we added would be a part of Pipeline forever – we could ignore the extra data but it would introduce compatibility issues. The extra level of complexity is that any behavior needs to be consistent across (potentially nested) parallels, nested blocks, and has to have something like a try/catch construct to let users override results – which has to behave logically in the face of a full & potentially complex graph structure. Take a look at Pipeline Graph Analysis plugin and you'll see what I mean about the complexity (also the APIs for working with the graph in https://github.com/jenkinsci/workflow-api-plugin/tree/master/src/main/java/org/jenkinsci/plugins/workflow/graphanalysis). The simple fix would be to simply not display an UNSTABLE status at the UI level in any situation for Pipelines, only at the overall build level. Would that be preferred? Because that's a change we can do without too much extra hassle. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49806) Describe criteria (JEP) for selecting plugins to include in Jenkins Essentials
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49806 Describe criteria (JEP) for selecting plugins to include in Jenkins Essentials Discussed some thoughts on pre-release security verifications we might be able to enforce for plugins considered "essential" with Daniel Beck today. Including a minimum quality bar for essential plugins should definitely be a key criteria 23:54 @ we already have some automation for that -- InjectedTest takes care of XSS on recent baselines, configRoundTrip takes care of password fields used for plain text values. The problem is these are opt in (the latter) and often opted out (the former). 00:03 @ rtyler perhaps -- I got started with https://github.com/jenkins-infra/jenkins.io/blame/master/content/doc/developer/plugin-development/build-process.adoc#L29 but including it in content would have required too much yak shaving 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
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Ernst de Haan commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Kevin Phillips Perhaps someone (you or someone else) can implement such a “hack” as a plugin – probably with a fat disclaimer indicating that many of the scenarios (as mentioned by Sam Van Oort) are not covered. That would at least reduce the pain a bit, and it would “buy some time” to get the real solution in place. Sam Van Oort: Your suggestion to […] simply not display an UNSTABLE status at the UI level in any situation […] may be of help to some people, for whom it may make sense to support that with an configuration flag somewhere. But for many (including myself) this would not add much value, if any. 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-50054) Dependencies trigger not working when depend on none primary packaging type
Title: Message Title Bing Shiao commented on JENKINS-50054 Re: Dependencies trigger not working when depend on none primary packaging type Cyrille Le Clerc upgrade from 3.3.2 to 3.4.3 works. This issue is resolved. 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-50218) Conan init fails when using Artifactory plugin
Title: Message Title
Ovidiu-Florin Bogdan created an issue
Jenkins / JENKINS-50218
Conan init fails when using Artifactory plugin
Issue Type:
Bug
Assignee:
Eyal Ben Moshe
Components:
artifactory-plugin
Created:
2018-03-16 13:30
Environment:
Jenkins 2.89.4 (using Official jenkins/jenkins:2.89.4 docker image) Artifactory plugin 2.15.0
Labels:
plugin pipeline
Priority:
Blocker
Reporter:
Ovidiu-Florin Bogdan
When using the Artifactory plugin in a Jenkins pipeline, the job fails because the conan_log.log file is missing. I guess this is happening during the initialization of the conan client. Pipeline:
pipeline {
agent none
stages {
stage('Build') {
parallel {
stage('Build Linux') {
agent {
docker {
image 'internalDockerImage'
label 'linux'
}
}
environment {
CONAN_USER_HOME = "${env.WORKSPACE}/conan_home"
}
steps {
script {
def client = Artifactory.newConanClient()
def server_name = client.remote.add server: server, repo: artifactory_repo
client.run(command: "config install https://git-repo/conan-settings/archive/master.zip")
client.run(command: "create --profile Linux-Release . ourteam/unstable")
client.run(command: "create --profile Linux-Debug . ourteam/unstable")
[JIRA] (JENKINS-46831) Not able to use a normal agent on stage when agent docker is declared globally
Title: Message Title wknapik wknapik commented on JENKINS-46831 Re: Not able to use a normal agent on stage when agent docker is declared globally Andrew Bayer thanks for the response. I don't really care where/how the agents are specified - I just need to run all the stages in docker containers. Are you saying that it's possible to run parallel stages in containers (on multiple slaves at the same time), if I change how the agents are specified in the Jenkinsfile ? 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-50195) Create a non root user for running Jenkins and the evergreen-client
Title: Message Title Baptiste Mathus commented on JENKINS-50195 Re: Create a non root user for running Jenkins and the evergreen-client Yes, Jenkins right now. And same for evergreen-client once it will exist as a process too. I think we should ideally run supervisord in userspace too, if it does not need to be root. 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-41127) Multiple pipeline instances running concurrently when concurrent execution disabled
Title: Message Title Andrew Bayer commented on JENKINS-41127 Re: Multiple pipeline instances running concurrently when concurrent execution disabled Got it to reproduce eventually, while I had some extra logging in Queue#getCauseOfBlockageForItem (and some other places, but that's the one that gave me something interesting). For the first few hundred jobs, everything was consistent: all the pending items would not be blocked by either Queue#getCauseOfBlockageForTask or QueueTaskDispatcher, they all were not BuildableItem, and they all had isConcurrentBuild() == false. The first item would not find its task in either buildables or pendings, and so would kick off. All the other pending items would find their tasks in pendings and so would stay queued. Yay, that's how it's supposed to be. But eventually...first item fine, many consecutive items fine, and then...one of them couldn't find its task in pendings and so kicked off too. That was followed by the rest of the queued items behaving like normal. I haven't yet navigated the Queue#maintain code enough to be sure what exactly the code path here is, but I'm fairly sure that the first item got removed from pendings before the queue processing was complete. I'm trying it again with some additional logging to try to make it more clear what's happening when. 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Ruben Perez commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Then your architecture is wrong. It cannot support something fundamentally needed. The sooner you change it, the better. This project goes nowhere without this. 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-37500) scm-syn-configuration issues with multi branch project
Title: Message Title Ethan Spoelstra commented on JENKINS-37500 Re: scm-syn-configuration issues with multi branch project I can confirm the hpi built by James Hogarth resolved this issue on one of our instances where we had been testing a multibranch job configuration via Bitbucket source. https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/49#issuecomment-273456696 The change has been merged, there just needs to be a release with the new functionality. 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-50215) Jenkins Plot Plugin is not plotting data.
Title: Message Title Veaceslav Gaidarji commented on JENKINS-50215 Re: Jenkins Plot Plugin is not plotting data. gulshan kumar hey. To be honest, I never used plot plugin via DSL syntax and don't really know yet if there's a difference. It works fine for freestyle/matrix/pipeline type of jobs. Could you please verify first if similar configuration works on other type of jobs? 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-49632) Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts")
Title: Message Title Cyrille Le Clerc closed an issue as Fixed Jenkins / JENKINS-49632 Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts") Change By: Cyrille Le Clerc 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-49632) Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts")
Title: Message Title Cyrille Le Clerc resolved as Fixed Jenkins / JENKINS-49632 Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts") Change By: Cyrille Le Clerc Status: Reopened 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-49852) Collect Pipeline usage telemetry
Title: Message Title R. Tyler Croy started work on JENKINS-49852 Change By: R. Tyler Croy 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-47789) Git BuildData entry leaks in from Gerrit event triggered builds in build.xml
Title: Message Title Jacob Keller commented on JENKINS-47789 Re: Git BuildData entry leaks in from Gerrit event triggered builds in build.xml This is a duplicate of 19022, though Gerrit makes this significantly worse. 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-41127) Multiple pipeline instances running concurrently when concurrent execution disabled
Title: Message Title Andrew Bayer commented on JENKINS-41127 Re: Multiple pipeline instances running concurrently when concurrent execution disabled So Queue#maintain() is running twice, one immediately after the other, in some cases - probably race conditiony, not yet sure how the two are getting called. Anyway, the first run is making the first item in the queue buildable and calls makeBuildable on the item, removing said item from blockedProjects, and, via makeFlyweightTaskBuildable and createFlyWeightTaskRunnable, starting the flyweight task and adding the first item to pendings. All is well and good. But then the next run of maintain starts - and it can't find the task for the item we just started (theoretically) and put in pendings on any executor...so it removes the item from pendings. Then it gets to checking the queue again, and the new first item doesn't have anything blocking it (i.e., nothing in buildables or pending) and so...it goes through the same process as the previous item did in the previous maintain run. End result: two builds get started at the same time. So - definitely a race condition. 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-41127) Multiple pipeline instances running concurrently when concurrent execution disabled
Title: Message Title Andrew Bayer commented on JENKINS-41127 Re: Multiple pipeline instances running concurrently when concurrent execution disabled fwiw, I think this likely only will happen with a flyweight task - so you could probably brew up a reproduction case with a matrix job, but I doubt you could do so with a freestyle job. 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-47496) No automatic builds for tags
Title: Message Title Leandro Lucarella commented on JENKINS-47496 Re: No automatic builds for tags you could have a build storm when checking out a repository I don't get this. What do you mean? I'm quite surprised by this design decision, other CI system build tags automatically and I never had any problems with it. Checking out the repository where could have a build storm? 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Sam Van Oort commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Ruben Perez It is a high priority to address this and in my personal upcoming work, but right now the highest priority is ensuring Pipeline does not cause system stability problems. As far as the architecture: I took the time to write up a detailed explanation of the situation in hopes it might lead to something productive (maybe even a PR), and it really is not constructive to simply say "your architecture is wrong." While you're entitled to your opinion, let me ask you this: how would you feel if you were putting many of your nights and weekends into improving something and someone said that to you? This is an open source project and we only have so many engineers no matter how hard we work – if you think you could improve upon the architecture you're more than welcome to submit PRs that accomplish this goal. 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-49406) Prototype the Evergreen snapshotting data safety system
Title: Message Title Baptiste Mathus commented on JENKINS-49406 Re: Prototype the Evergreen snapshotting data safety system FTR, meeting added in the repo as we'll do for all of them in the future: https://github.com/jenkins-infra/evergreen/tree/master/docs/meetings/2018-03-18-JENKINS-49406-quality-bar 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-50119) Dynamic DSL for workflowMultiBranchProjectFactory not working
Title: Message Title Steven Foster commented on JENKINS-50119 Re: Dynamic DSL for workflowMultiBranchProjectFactory not working I think the issue is multibranchPipelineJob should be using workflowBranchProjectFactory rather than workflowMultiBranchProject factory. I tried to implement it in monkey-see monkey-do fashion by creating a BranchProjectFactory context based on MultiBranchProjectFactoryContext, changing all references to MultiBranchProjectFactory to BranchProjectFactory, updating MultibranchWorkflowJob to use BranchProjectFactory, and updating a test. It's a bit over my head though and I'm hitting issues testing it out. It shows in the api viewer (which 404s in ./gradlew server) but if I try to make any kind of multibranchPipelineJob I get groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method groovy.util.XmlParser#parse. Cannot resolve which method to invoke for [null] due to overlapping prototypes between: [class java.io.File] [class java.io.InputStream] [class java.io.Reader] [class java.lang.String] [class org.xml.sax.InputSource] at groovy.lang.MetaClassImpl.chooseMostSpecificParams(MetaClassImpl.java:3263) at groovy.lang.MetaClassImpl.chooseMethodInternal(MetaClassImpl.java:3216) at groovy.lang.MetaClassImpl.chooseMethod(MetaClassImpl.java:3159) at groovy.lang.MetaClassImpl.getMethodWithCachingInternal(MetaClassImpl.java:1331) at groovy.lang.MetaClassImpl.createPojoCallSite(MetaClassImpl.java:3391) at org.codehaus.groovy.runtime.callsite.CallSiteArray.createPojoSite(CallSiteArray.java:132) at org.codehaus.groovy.runtime.callsite.CallSiteArray.createCallSite(CallSiteArray.java:166) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125) at javaposse.jobdsl.dsl.Folder.getNodeTemplate(Folder.groovy:110) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at org.codehaus.groovy.runtime.metaclass.MethodMetaProperty$GetBeanMethodMetaProperty.getProperty(MethodMetaProperty.java:76) at org.codehaus.groovy.runtime.callsite.GetEffectivePogoPropertySite.callGroovyObjectGetProperty(GetEffectivePogoPropertySite.java:68) at javaposse.jobdsl.dsl.Item.getNode(Item.groovy:45) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at org.codehaus.groovy.runtime.metaclass.MethodMetaProperty$GetBeanMethodMetaProperty.getProperty(MethodMetaProperty.java:76) at org.codehaus.groovy.runtime.callsite.GetEffectivePogoPropertySite.callGroovyObjectGetProperty(GetEffectivePogoPropertySite.java:68) at javaposse.jobdsl.dsl.Item.getXml(Item.groovy:34) at
[JIRA] (JENKINS-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title Mark Waite commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Thanks Bill Hamilton! 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title Bill Hamilton commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Mark WaiteStephen Connolly Guys, I just want to confirm the use cases that should be tested around this: Both the @Library directive, and the library() DSL step, should insure that specifying branches, PRs, tags, and hashes all work Thanks, -Bill 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-42435) Add support for Blue Ocean to Git Parameter plugin
Title: Message Title Mondane Woodworker updated an issue Jenkins / JENKINS-42435 Add support for Blue Ocean to Git Parameter plugin Change By: Mondane Woodworker Attachment: image-2018-03-16-13-40-17-949.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-50221) pipeline run task on node x or/and node y
Title: Message Title Ruud P updated an issue Jenkins / JENKINS-50221 pipeline run task on node x or/and node y Change By: Ruud P Summary: pipeline run task on node x or /and node y 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-50221) pipeline run task on node x or/and node y
Title: Message Title
Ruud P updated an issue
Jenkins / JENKINS-50221
pipeline run task on node x or/and node y
Change By:
Ruud P
its not possible to do likei add like 'a||b' or 'a&' it say there is no node with the name 'a&' i also try like 'a'&&'b' then the code is running only on a and not on b post \{ always \{ node(label: 'A' or 'B' or 'C') \{ foo()}
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-50221) pipeline run task on node x or node y
Title: Message Title Ruud P updated an issue Jenkins / JENKINS-50221 pipeline run task on node x or node y Change By: Ruud P its not possible to do likei add like 'a||b' or 'a&' it say there is no node with the name 'a&' i also try like 'a'&&'b' then the code is running only on a and not on b 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-50044) Run a task on node x or node y
Title: Message Title
Ruud P updated an issue
Jenkins / JENKINS-50044
Run a task on node x or node y
Change By:
Ruud P
it is not possible to run a post build on node A or Node B or C (anything that is available)post \{ always \{ node(label: 'A' or 'B' or 'C') \{ foo()}**when i add like 'a||b' or 'a&' it say there is no node with the name 'a&' i also try like 'a'&&'b' then the code is running only on node a and not on node b . I use declarative pipeline
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-50054) Dependencies trigger not working when depend on none primary packaging type
Title: Message Title Cyrille Le Clerc resolved as Fixed Implemented in v3.4.3 Jenkins / JENKINS-50054 Dependencies trigger not working when depend on none primary packaging type Change By: Cyrille Le Clerc Status: In Progress 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-46602) [JDK 9] Pipeline fails immediately - ASM illegal argument exception
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-46602 [JDK 9] Pipeline fails immediately - ASM illegal argument exception Change By: Baptiste Mathus Assignee: Baptiste Mathus 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-46602) [JDK 9] Pipeline fails immediately - ASM illegal argument exception
Title: Message Title Baptiste Mathus commented on JENKINS-46602 Re: [JDK 9] Pipeline fails immediately - ASM illegal argument exception Oleg Nenashev no. Unlikely enough time in the short term unfortunately. Unassigned myself to clarify anyone if free to chime in. 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-50219) Jenkins agent windows service fails to restart with an unhandled COMException in WinSw's log
Title: Message Title Oleg Nenashev commented on JENKINS-50219 Re: Jenkins agent windows service fails to restart with an unhandled COMException in WinSw's log Tom Manning Please also submit a ticket to https://github.com/kohsuke/winsw . That project is outside Jenkins governance 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-50131) git parameter
Title: Message Title guillermo casco updated an issue Jenkins / JENKINS-50131 git parameter Change By: guillermo casco Attachment: pip2.JPG 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-50131) git parameter
Title: Message Title guillermo casco updated an issue Jenkins / JENKINS-50131 git parameter Change By: guillermo casco Attachment: pipe1.JPG 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-46831) Not able to use a normal agent on stage when agent docker is declared globally
Title: Message Title wknapik wknapik commented on JENKINS-46831 Re: Not able to use a normal agent on stage when agent docker is declared globally Andrew Bayer I tried doing that (as described in JENKINS-47103), but it didn't work back then. Has something changed ? 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-50219) Jenkins agent windows service fails to restart with an unhandled COMException in WinSw's log
Title: Message Title Tom Manning created an issue Jenkins / JENKINS-50219 Jenkins agent windows service fails to restart with an unhandled COMException in WinSw's log Issue Type: Bug Assignee: Oleg Nenashev Components: windows-slave-installer-module Created: 2018-03-16 13:48 Environment: Jenkins 2.9.84 windows-slave-installer 1.9.2 jenkins-slave.exe running on Windows 10 + jre 1.8.0.161 under local admin credentials. Priority: Minor Reporter: Tom Manning We have noticed that our Windows 10 nodes have been intermittently failing to come back online after Jenkins / master restarts. The following entries are shown in WinSw's Jenkins-slave.wrapper.log file at the time of the failures. In particular it appears that the unhandled COMException is preventing the service restarting successfully. 2018-03-16 12:26:38,011 DEBUG - Starting ServiceWrapper in the CLI mode 2018-03-16 12:26:38,589 INFO - Restarting the service with id 'jenkinsslave-c__jenkins' 2018-03-16 12:26:38,682 DEBUG - Completed. Exit code is 0 2018-03-16 12:26:38,870 DEBUG - Starting ServiceWrapper in the CLI mode 2018-03-16 12:26:39,151 INFO - Restarting the service with id 'jenkinsslave-c__jenkins' 2018-03-16 12:26:39,276 INFO - Stopping jenkinsslave-c__jenkins 2018-03-16 12:26:39,292 DEBUG - ProcessKill 332 2018-03-16 12:26:39,386 INFO - Found child process: 420 Name: conhost.exe 2018-03-16 12:26:39,433 INFO - Stopping process 420 2018-03-16 12:26:39,448 INFO - Send SIGINT 420 2018-03-16 12:26:39,464 WARN - SIGINT to 420 failed - Killing as fallback 2018-03-16 12:26:39,464 INFO - Stopping process 332
[JIRA] (JENKINS-50220) Wrong link target for pipeline syntax link in pipeline jobs
Title: Message Title
Torsten Werner created an issue
Jenkins / JENKINS-50220
Wrong link target for pipeline syntax link in pipeline jobs
Issue Type:
Bug
Assignee:
Unassigned
Components:
build-pipeline-plugin
Created:
2018-03-16 13:55
Environment:
Jenkins
Priority:
Minor
Reporter:
Torsten Werner
In pipeline jobs exists a link "Pipeline Syntax" (sorry when I translate it not correctly, I've a German user interface). The link points to {Jenkins-URL}/job/{job}/pipeline-syntax. This is cauling a error. The link should go to {Jenkins-URL}/pipeline-syntax This link is working.
Add Comment
[JIRA] (JENKINS-50044) Run a task on node x or node y
Title: Message Title Ruud P updated an issue Jenkins / JENKINS-50044 Run a task on node x or node y Change By: Ruud P Issue Type: New Feature Bug 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-50044) Run a task on node x or node y
Title: Message Title Ruud P updated an issue Jenkins / JENKINS-50044 Run a task on node x or node y Change By: Ruud P Priority: Minor Major 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Kevin Phillips commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should So, we've been slowly adopting the new Pipeline APIs for all of our production builds across dozens of development teams. This build status issue is causing a very large amount of frustration and wastes a lot of developer time trying to dig through logs to deduce failure statuses. As such I'm hoping this is being considered a high-priroity item to be fixed regardless of how difficult it may be to do. That small rant aside, might I suggest that if the "correct" fix for this turns out to be something incredibly complex and difficult - which, again, suggests that it may be months or years before it is fixed - could you not find some reasonable substitution or workaround for the problem in the meantime? Like, for example, could you perhaps create a clone of the `stage()` function that maybe ignores all of the current build status logic completely but allows the build status to be explicitly set using a custom variable or method, something like `currentBuild.hackStagedResult = 'SUCCESS"`? In this way users that are experiencing this pain point would have some temporary workaround to ease the current pain while allowing you some time to fix the underlying problem correctly. NOTE: I'd even be happy if these "hacks" or "workarounds" were simply undocumented features that you put in place as temporary workarounds to this specific JIRA issue, with the expectation that once the underlying problems are fixed the "undocumented" functionality will simply be removed - and hence, no need to be maintained going forward. Thoughts? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50044) Run a task on node x or node y
Title: Message Title Ruud P reopened an issue i do it like that at this moment and it is working for 1 node.. but when i add like 'a||b' or 'a&' it say there is no node with the name 'a&' i also try like 'a'&&'b' then the code is running only on a and not on b Jenkins / JENKINS-50044 Run a task on node x or node y Change By: Ruud P Resolution: Won't Fix 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
[JIRA] (JENKINS-50044) Run a task on node x or node y
Title: Message Title
Ruud P updated an issue
Jenkins / JENKINS-50044
Run a task on node x or node y
Change By:
Ruud P
it is not possible to run a post build on node A or Node B or C (anything that is available)post \{ always \{ node(label: 'A' or 'B' or 'C') \{ foo()} **when i add like 'a||b' or 'a&' it say there is no node with the name 'a&' i also try like 'a'&&'b' then the code is running only on a and not on b
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-50208) 10min timeout for user built plugins
Title: Message Title Jason Hodges updated an issue Jenkins / JENKINS-50208 10min timeout for user built plugins Change By: Jason Hodges We are building a plugin for Jenkins to call a blue/green deployer that we created. For some of our larger Node apps , we are running into a hard 10min timeout when calling our plugin. We are able to adjust the timeout from 0-10 mins but anything after that we get a failed pipeline. I've seen a similar issue with the Git plugin but they were able to get around the issues. We've tried several different libraries for handling the call to our blue/greener but we run in to the same issue. Any help would be great, 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
[JIRA] (JENKINS-42435) Add support for Blue Ocean to Git Parameter plugin
Title: Message Title Mondane Woodworker commented on JENKINS-42435 Re: Add support for Blue Ocean to Git Parameter plugin Boguslaw Klimas sadly it doesn't work with 0.9.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-46831) Not able to use a normal agent on stage when agent docker is declared globally
Title: Message Title Andrew Bayer commented on JENKINS-46831 Re: Not able to use a normal agent on stage when agent docker is declared globally It's due to an inherent aspect of the Docker Pipeline plugin - we're working on a successor to Docker Pipeline over in JENKINS-48050, but I don't have a specific timeframe. For now, you just have to not use a top-level docker agent if you want to run stages, parallel or otherwise, on a different agent. 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-46639) autofavourite fails with git-client plugin and jgit 4.5.3
Title: Message Title Jesse Glick commented on JENKINS-46639 Re: autofavourite fails with git-client plugin and jgit 4.5.3 Any relation to JENKINS-43400? 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-41127) Multiple pipeline instances running concurrently when concurrent execution disabled
Title: Message Title
Andrew Bayer commented on JENKINS-41127
Re: Multiple pipeline instances running concurrently when concurrent execution disabled
I'm running a tweaked version of that now to see what happens - had to make some changes due to serialization.
@NonCPS
def getLastNum() {
def item = Jenkins.instance.getItemByFullName("bug-reproduction/jenkins-41127")
echo "${item}"
return item.getLastSuccessfulBuild().number
}
def lastNum = getLastNum()
if(lastNum == (currentBuild.number.toInteger()-1)) {//finding previous number
def number = params.TestString.toInteger()+1
node () {
stage ('Build') {
sleep 2
build job: 'jenkins-41127', parameters: [string(name: 'TestString', value: "${number}")], wait: false
}
stage ('Again'){
sleep 2
number = number+number
build job: 'jenkins-41127', parameters: [string(name: 'TestString', value: "${number}")], wait: false
}
}
}
else {
currentBuild.result == "SUCCESS"
def RunningBuildsString = getRunStr()
build job: 'jenkins-41127-fs', parameters: [string(name: 'PreviousBuild', value: "${lastNum}"), string(name: 'CurrentBuild', value: "${currentBuild.number.toInteger()}"), string(name: 'QueueStatus', value: "${RunningBuildsString}")]
}
@NonCPS
def getRunStr() {
def RunningBuildsString = ""
Jenkins.instance.getAllItems(Job).each{
def jobBuilds=it.getBuilds()
jobBuilds.each{
if (it.isBuilding()) { RunningBuildsString = (RunningBuildsString + it.toString() + " ") }
}
}
return RunningBuildsString
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50210) Kubernetes agent provisioned regardless of container cap
Title: Message Title Carlos Sanchez closed an issue as Duplicate Jenkins / JENKINS-50210 Kubernetes agent provisioned regardless of container cap Change By: Carlos Sanchez 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-50210) Kubernetes agent provisioned regardless of container cap
Title: Message Title Carlos Sanchez commented on JENKINS-50210 Re: Kubernetes agent provisioned regardless of container cap See JENKINS-38260 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-50221) pipeline run task on node x or node y
Title: Message Title Ruud P created an issue Jenkins / JENKINS-50221 pipeline run task on node x or node y Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 2018-03-16 14:59 Priority: Major Reporter: Ruud P 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
[JIRA] (JENKINS-50221) pipeline run task on node x or/and node y
Title: Message Title Ruud P closed an issue as Duplicate sorry did not know i could reopen my previous issue Jenkins / JENKINS-50221 pipeline run task on node x or/and node y Change By: Ruud P 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-50131) git parameter
Title: Message Title guillermo casco commented on JENKINS-50131 Re: git parameter Is this some kind of another bug or something? I implemented multibranch pipeline as you suggsted Mark Waite and is still running master . check images. Is there some kind of configuration I´m missing? 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-47919) Checking parameters of remote job build fails
Title: Message Title Jiri Meluzin commented on JENKINS-47919 Re: Checking parameters of remote job build fails I have creted new pull request which addresses one more issue https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/35. Please accept this pull request. 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-46639) autofavourite fails with git-client plugin and jgit 4.5.3
Title: Message Title Mark Waite closed an issue as Duplicate Jenkins / JENKINS-46639 autofavourite fails with git-client plugin and jgit 4.5.3 Change By: Mark Waite 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-43556) Stage View shows incorrect build result
Title: Message Title Christoph Amshoff commented on JENKINS-43556 Re: Stage View shows incorrect build result Same issue here for maybe one out of 30 builds; up to now this seems to happen just for the first successful build after a broken (failed) build. Build history is fine. logs don't show any issue, just the pipeline in stage view is rendered red. In Blue Ocean, everything looks good. I don't know if that heps, but when looking at the rendered HTML of stage view, I can see that tr has CSS classes "job FAILED", while all td's for the steps have classes "stage-cell stage-cell-x SUCCESS". We're using Jenkins 2.89.4, Pipeline Stage View Plugin 2.9 and Pipeline REST API plugin 2.9. 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-46602) [JDK 9] Pipeline fails immediately - ASM illegal argument exception
Title: Message Title Baptiste Mathus edited a comment on JENKINS-46602 Re: [JDK 9] Pipeline fails immediately - ASM illegal argument exception [~oleg_nenashev] no. Unlikely enough time in the short term unfortunately. Unassigned myself to clarify anyone if can feel free to chime in. 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-50044) Run a task on node x or node y
Title: Message Title
Ruud P updated an issue
Jenkins / JENKINS-50044
Run a task on node x or node y
Change By:
Ruud P
it is not possible to run a post build on node A or Node B or C (anything that is available)post \{ always \{ node(label: 'A' or 'B' or 'C') \{ foo()}
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-49866) Automatically configure Docker Cloud if the docker.sock is available
Title: Message Title Baptiste Mathus commented on JENKINS-49866 Re: Automatically configure Docker Cloud if the docker.sock is available R. Tyler Croy can you please slightly clarify some acceptance criterion/UX? I assume you mean this to work only if the socket is accessible before/while Jenkins is starting? Or do you want Jenkins to get the Docker cloud configuration as soon as the socket is made available? Also, about "Docker socket", I assume you mean "a Docker daemon is available"? I.e. if the docker socket is not mounted, but DOCKER_HOST is defined, I suppose you want to auto-work too? 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-47488) PortMapping does not work when configured in pipeline
Title: Message Title Carlos Sanchez closed an issue as Not A Defect As Timothy said, you are trying to connect to hostPost from inside the container, which is obviously not going to work Jenkins / JENKINS-47488 PortMapping does not work when configured in pipeline Change By: Carlos Sanchez Status: Open Closed Resolution: Not A Defect 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
[JIRA] (JENKINS-50221) pipeline run task on node x or/and node y
Title: Message Title
Ruud P updated an issue
Jenkins / JENKINS-50221
pipeline run task on node x or/and node y
Change By:
Ruud P
its not possible to do likei add like 'a||b' or 'a&' it say there is no node with the name 'a&' i also try like 'a'&&'b' then the code is running only on a and not on bpost \{ always \{ node(label: 'A ' or ' || B ' or ' || C') \{ foo()}
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-50044) Run a task on node x or node y
Title: Message Title
Ruud P updated an issue
Jenkins / JENKINS-50044
Run a task on node x or node y
Change By:
Ruud P
is it is not possible to run a post build on node A or Node B or C (anything that is available)post \{ always \{ node(label: 'A' or 'B' or 'C') \{ foo()}
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-50131) git parameter
Title: Message Title guillermo casco updated an issue Jenkins / JENKINS-50131 git parameter Change By: guillermo casco Attachment: pipe1.JPG 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-50131) git parameter
Title: Message Title guillermo casco updated an issue Jenkins / JENKINS-50131 git parameter Change By: guillermo casco Attachment: pip2.JPG 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-48007) Client error during trying to send rocket message
Title: Message Title
Phlegx Systems reopened an issue
This problem still appears for me now with newest Plugin version 1.2.0 and Rocketchat version 0.62.2. Since I didn't change the password/user and it was working previously I assume it might be a bug? ... SEVERE: Could not send message: Response{success=false, messages=null, message=null, users=null, user=null, channels=null, channel=null, info=null} java.io.IOException: The send of the message was unsuccessful. ...
Jenkins / JENKINS-48007
Client error during trying to send rocket message
Change By:
Phlegx Systems
Resolution:
Fixed
Status:
Closed Reopened
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42519) Closed pull requests, branch jobs are not cleaned up
Title: Message Title Joshua Noble edited a comment on JENKINS-42519 Re: Closed pull requests, branch jobs are not cleaned up Isn't the whole point of a multibranch pipeline (within the context of the GitHub Branch Source plugin) to build multiple branches of the same origin? I don't see how adding multiple origins is a valid example. 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.
