[JIRA] (JENKINS-36131) "Show all" link required anywhere a log is displayed
Title: Message Title Michael Neale commented on JENKINS-36131 Re: "Show all" link required anywhere a log is displayed James Dumay does this make sense to you? I think it will be needed due to the log being broken down by step Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36131) "Show all" link required anywhere a log is displayed
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-36131 "Show all" link required anywhere a log is displayed Issue Type: Improvement Assignee: James Dumay Components: blueocean-plugin Created: 2016/Jun/22 5:11 AM Priority: Minor Reporter: Michael Neale By default all logs only have the last 150KB shown. Classic jenkins has a "Show all" link, which works fine as it is a single log. This can still apply for freestyle, but for step-based jobs, then the "show all" link probably should only apply to that step, so the user can look back if needed (loading the content using ?start=0 will trigger loading of all). Add Comment
[JIRA] (JENKINS-36124) Build Parameters Corrupted sometimes in MultiJob Project
Title: Message Title Dominik Bartholdi commented on JENKINS-36124 Re: Build Parameters Corrupted sometimes in MultiJob Project added issue to list at https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36124) Build Parameters Corrupted sometimes in MultiJob Project
Title: Message Title Dominik Bartholdi assigned an issue to hagzag Jenkins / JENKINS-36124 Build Parameters Corrupted sometimes in MultiJob Project Change By: Dominik Bartholdi Assignee: Dominik Bartholdi hagzag Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36065) Icon alignment in step header is off
Title: Message Title Josh McDonald resolved as Fixed Fixed in JDL Jenkins / JENKINS-36065 Icon alignment in step header is off Change By: Josh McDonald Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34728) Pull Request pipeline fails to checkout successive commits
Title: Message Title Allan BURDAJEWICZ reopened an issue Jenkins / JENKINS-34728 Pull Request pipeline fails to checkout successive commits Change By: Allan BURDAJEWICZ Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34728) Pull Request pipeline fails to checkout successive commits
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-34728 Re: Pull Request pipeline fails to checkout successive commits Can still reproduce with the latest: branch-api:1.10 github-branch-source:1.7 github-pull-request-build:1.10 Reproduce I have a repo, a fork and an open PR: Create an GitHub Organization Folder for the support-team user Register WebHook on GHE for the repo Commit successively multiple changes to the fork very quickly - 5 seconds interval You should see the PR build failing with the following exception: hudson.plugins.git.GitException: Could not checkout 67615299b8ef9ae83a60c72af7ca37cbfc879d4f at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:1992) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1135) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:109) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:87) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:206) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: hudson.plugins.git.GitException: Command "git checkout -f 67615299b8ef9ae83a60c72af7ca37cbfc879d4f" returned status code 128: stdout: stderr: fatal: reference is not a tree: 67615299b8ef9ae83a60c72af7ca37cbfc879d4f at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1719) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:63) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:1984) ... 7 more Finished: FAILURE Add Comment
[JIRA] (JENKINS-35863) API to download the log as a text file or show in browser tab
Title: Message Title Ivan Meredith started work on JENKINS-35863 Change By: Ivan Meredith Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35876) Add tests that exercise REST API security
Title: Message Title Ivan Meredith stopped work on JENKINS-35876 Change By: Ivan Meredith Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35854) Add Rollbar error reporting
Title: Message Title Ivan Meredith started work on JENKINS-35854 Change By: Ivan Meredith Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36130) Show log for freestyle type projects
Title: Message Title Michael Neale assigned an issue to Thorsten Scherler Jenkins / JENKINS-36130 Show log for freestyle type projects Change By: Michael Neale Assignee: James Dumay Thorsten Scherler Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36130) Show log for freestyle type projects
Title: Message Title Michael Neale commented on JENKINS-36130 Re: Show log for freestyle type projects Thorsten Scherler I know this was already being tackled as part of https://issues.jenkins-ci.org/browse/JENKINS-36020 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36130) Show log for freestyle type projects
Title: Message Title Michael Neale started work on JENKINS-36130 Change By: Michael Neale Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36130) Show log for freestyle type projects
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36130 Show log for freestyle type projects Change By: Michael Neale Sprint: 1.0-m10 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36130) Show log for freestyle type projects
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-36130 Show log for freestyle type projects Issue Type: Bug Assignee: James Dumay Components: blueocean-plugin Created: 2016/Jun/22 3:23 AM Priority: Critical Reporter: Michael Neale When loading a freestyle job, there will be no stages/flow nodes, and no steps. In scope: The log should be shown (can show just last 150KB, as it does now in classic) as text Out of scope: Showing all of log - it can be obtained by clicking on the "open in new tab" pre-existing link. Add Comment
[JIRA] (JENKINS-36129) change port bug
Title: Message Title
liu niansheng created an issue
Jenkins / JENKINS-36129
change port bug
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
_unsorted
Created:
2016/Jun/22 3:20 AM
Priority:
Minor
Reporter:
liu niansheng
when I change my jenkins's port ,the jenkins api return the first start port url. example: request: http://172.16.200.157:8091/api/python result: {"_class":"hudson.model.Hudson","assignedLabels":[{}],"mode":"NORMAL","nodeDescription":"the master Jenkins node","nodeName":"","numExecutors":2,"description":None,"jobs":[ {"_class":"hudson.model.FreeStyleProject","name":"commercial-开发","url":"http://172.16.200.157:8080/job/commercial-%E5%BC%80%E5%8F%91/","color":"red"} , {"_class":"hudson.model.FreeStyleProject","name":"job-name","url":"http://172.16.200.157:8080/job/job-name/","color":"blue"} , {"_class":"hudson.model.FreeStyleProject","name":"test1","url":"http://172.16.200.157:8080/job/test1/","color":"notbuilt"} , {"_class":"hudson.model.FreeStyleProject","name":"test23","url":"http://172.16.200.157:8080/job/test23/","color":"notbuilt"} , {"_class":"hudson.model.FreeStyleProject","name":"农信钱包后台-开发","url":"http://172.16.200.157:8080/job/%E5%86%9C%E4%BF%A1%E9%92%B1%E5%8C%85%E5%90%8E%E5%8F%B0-%E5%BC%80%E5%8F%91/","color":"blue"} ],"overallLoad":{},"primaryView": {"_class":"hudson.model.AllView","name":"All","url":"http://172.16.200.157:8080/"} ,"quietingDown":False,"slaveAgentPort":0,"unlabeledLoad": {"_class":"jenkins.model.UnlabeledLoadStatistics"} ,"useCrumbs":False,"useSecurity":True,"views":[ {"_class":"hudson.model.AllView","name":"All","url":"http://172.16.200.157:8080/"} ]}
[JIRA] (JENKINS-35985) no @DataBoundConstructor on any constructor of class com.amazonaws.codepipeline.jenkinsplugin.AWSCodePipelineSCM
Title: Message Title Mark M commented on JENKINS-35985 Re: no @DataBoundConstructor on any constructor of class com.amazonaws.codepipeline.jenkinsplugin.AWSCodePipelineSCM Hello, any update on this? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12128) Expose releaseVersion and developmentVersion as environment variables
Title: Message Title Vipul Delwadia commented on JENKINS-12128 Re: Expose releaseVersion and developmentVersion as environment variables It seems like this is no longer working in Jenkins 2.10 + Maven Release Plug-in Plug-in 0.14.0 ? When I use MVN_RELEASE_VERSION during a release build determined using IS_M2RELEASEBUILD, the value of IS_M2RELEASEBUILD is true but MVN_RELEASE_VERSION is empty string. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12128) Expose releaseVersion and developmentVersion as environment variables
Title: Message Title Vipul Delwadia reopened an issue Jenkins / JENKINS-12128 Expose releaseVersion and developmentVersion as environment variables Change By: Vipul Delwadia Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35995) Prepare pom for release etc.
Title: Message Title Michael Neale resolved as Fixed Jenkins / JENKINS-35995 Prepare pom for release etc. Change By: Michael Neale Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36101) Use alpha version name for experimental update center
Title: Message Title Michael Neale resolved as Fixed Jenkins / JENKINS-36101 Use alpha version name for experimental update center Change By: Michael Neale Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36128) Duration never live reloads for running pipelines
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36128 Duration never live reloads for running pipelines Change By: James Dumay Sprint: 1.0-m10 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36128) Duration never live reloads for running pipelines
Title: Message Title James Dumay assigned an issue to Tom FENNELLY Jenkins / JENKINS-36128 Duration never live reloads for running pipelines Change By: James Dumay Assignee: James Dumay Tom FENNELLY Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36128) Duration never live reloads for running pipelines
Title: Message Title James Dumay created an issue Jenkins / JENKINS-36128 Duration never live reloads for running pipelines Issue Type: Bug Assignee: James Dumay Attachments: Jenkins Blue Ocean 2016-06-22 10-38-38.png Components: blueocean-plugin Created: 2016/Jun/22 12:43 AM Priority: Minor Reporter: James Dumay This run was executing for several minutes. It never automatically updates on the Activity or Pipeline Result screen. Add Comment
[JIRA] (JENKINS-35876) Add tests that exercise REST API security
Title: Message Title Ivan Meredith started work on JENKINS-35876 Change By: Ivan Meredith Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35797) API for running a branch and pull request
Title: Message Title Ivan Meredith resolved as Fixed Jenkins / JENKINS-35797 API for running a branch and pull request Change By: Ivan Meredith Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36127) ECR plugin throwing null pointer when attempt to configure docker build and publish
Title: Message Title martinfr62 created an issue Jenkins / JENKINS-36127 ECR plugin throwing null pointer when attempt to configure docker build and publish Issue Type: Bug Assignee: Nicolas De Loof Components: amazon-ecr-plugin Created: 2016/Jun/22 12:09 AM Environment: jenkins 1.651.1 Linux Priority: Blocker Reporter: martinfr62 So this is probably a 'bad' credential somewhere - but we don't get the error when the ecr plugin is not installed. A more helpful description of what's missing/badly set would help clarify what is causing the exception. Note when ecr plugin is removed - the credential list appears just fine. https://jenkins1.dev.citrixsaassbe.net/job/Developer_Productivity/job/Docker/job/TestECR2/descriptorByName/com.cloudbees.jenkins.plugins.docker_build_env.DockerBuildWrapper/fillDockerRegistryCredentialsItems java.lang.reflect.InvocationTargetException 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:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at
[JIRA] (JENKINS-58) Support patch submission
Title: Message Title Alex Earl commented on JENKINS-58 Re: Support patch submission Is this even needed anymore? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36122) Renaming a job does not get reflected
Title: Message Title ikedam assigned an issue to Oleg Nenashev The issue sounds that job B fails to detect promotions of job A after job A is renamed, and the issue sounds of promoted-builds plugin. Jenkins / JENKINS-36122 Renaming a job does not get reflected Change By: ikedam Component/s: promoted-builds-plugin Component/s: copyartifact-plugin Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33445) GitScmSource does not return tags via retrieve method
Title: Message Title Alastair D'Silva commented on JENKINS-33445 Re: GitScmSource does not return tags via retrieve method Fixed by pull request #407 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36122) Renaming a job does not get reflected
Title: Message Title ikedam commented on JENKINS-36122 Re: Renaming a job does not get reflected I suppose there are mistypes, and the following is the actual situation: configure job a to require manual promotion via a star configure job a to archive an artifact #configure job b to be triggered upon successful promotion to job b job a rename job a (to job c) trigger job a to job c promote job a job c Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35505) Modify Plugin to work in Pipeline
Title: Message Title Mike Caspar updated an issue Jenkins / JENKINS-35505 Modify Plugin to work in Pipeline Change By: Mike Caspar Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35626) SSL Certificate not working
Title: Message Title ikedam commented on JENKINS-35626 Re: SSL Certificate not working 1. Is is really an issue of UpdateSites Manager plugin? It looks an issue of Jenkins core to me. You can describe more about your setup. 2. It just looks that Jenkins fails to connect the server. Does the server actually support HTTPS? Does your network access to the Internet with HTTPS? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36107) RUN falsely showing up that running that isn't running at all
Title: Message Title Michael Neale commented on JENKINS-36107 Re: RUN falsely showing up that running that isn't running at all Vivek Pandey AH! ok yes thanks, didn't see that. That makes sense. Not related to blue ocean. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36114) Support Aggregate-only action
Title: Message Title ikedam commented on JENKINS-36114 Re: Support Aggregate-only action You can describe more details. What publisher do you use and what is the behavior you expect? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34763) Email-ext plugin (culprits and committers) in Jenkins Pipeline
Title: Message Title Michael Neale commented on JENKINS-34763 Re: Email-ext plugin (culprits and committers) in Jenkins Pipeline Sorin Sbarnea it's not docs, and not a good answer I know, but https://issues.jenkins-ci.org/browse/JENKINS-35365 has the exampels in the description. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36114) Support Aggregate-only action
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-36114 Support Aggregate-only action Change By: ikedam Assignee: bap ikedam Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36126) HTML Publisher plugin only publishes first of multiple configured reports on the build page
Title: Message Title trejkaz created an issue Jenkins / JENKINS-36126 HTML Publisher plugin only publishes first of multiple configured reports on the build page Issue Type: Bug Assignee: mcrooney Components: htmlpublisher-plugin Created: 2016/Jun/21 11:26 PM Environment: HTML Publisher 1.11, Jenkins 1.656 Priority: Minor Reporter: trejkaz We have two HTML reports configured for one of our jobs, Coverage and Code Metrics. On the job page (e.g. http://jenkins/job/portal/) it shows both Coverage and Code Metrics in the sidebar, but on the individual build page (e.g. http://jenkins/job/portal/1347/) only Coverage appears. Add Comment
[JIRA] (JENKINS-34898) Parameter not resolved in image tag of plugin docker-custom-build-environment since 2.3
Title: Message Title hector CALDERON closed an issue as Fixed the problem was in parametrized build trigger Jenkins / JENKINS-34898 Parameter not resolved in image tag of plugin docker-custom-build-environment since 2.3 Change By: hector CALDERON Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-36045) ATH Docker - opening cidfile too soon can cause failures
Title: Message Title Andrew Bayer commented on JENKINS-36045 Re: ATH Docker - opening cidfile too soon can cause failures So I haven't been able to reproduce this in local testing (on OS X with Docker for Mac beta, so...not exactly the same environment as a Linux box). I'm trying some experiments now with watching for this error condition in DockerContainerHolder and retrying if I see it, up to 5 times, with a 5 second sleep after the failure. Let's see if it works! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35771) Steps API to get all steps
Title: Message Title Michael Neale commented on JENKINS-35771 Re: Steps API to get all steps Vivek Pandey ah good catch Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36125) ATH custom workspace tests don't work if multiple advanced buttons on job page
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-36125 ATH custom workspace tests don't work if multiple advanced buttons on job page Issue Type: Bug Assignee: Andrew Bayer Components: acceptance-test-harness Created: 2016/Jun/21 10:44 PM Priority: Minor Reporter: Andrew Bayer The custom workspace tooling in the ATH expects the first advanced button on the job configure page to be for Advanced Project Options, but depending on the set of plugins in the test environment, there may be more than one, and one of them may be before the Advanced Project Options one. If so, it gets clicked and expanded while the Advanced Project Options never gets expanded, leading to custom workspace-related test failures. Add Comment
[JIRA] (JENKINS-35771) Steps API to get all steps
Title: Message Title Vivek Pandey reopened an issue Step log is not served Jenkins / JENKINS-35771 Steps API to get all steps Change By: Vivek Pandey Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34428) workflow-cps-global-lib: inheritance (extends) not working
Title: Message Title Zhelyan Panchev commented on JENKINS-34428 Re: workflow-cps-global-lib: inheritance (extends) not working I can extend abstract classes but calling super.somemethod() from the implementation throws StackOverflow exception Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32594) Bend the pipeline-plugin to Chuck's will
Title: Message Title Sergey Zhemzhitsky commented on JENKINS-32594 Re: Bend the pipeline-plugin to Chuck's will Hi, is it possible to merge this PR that fixes this issue? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36123) Provide a mechanism to for plugins to veto SCM polling on jobs
Title: Message Title stephenconnolly commented on JENKINS-36123 Re: Provide a mechanism to for plugins to veto SCM polling on jobs https://github.com/jenkinsci/jenkins/pull/2418 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36123) Provide a mechanism to for plugins to veto SCM polling on jobs
Title: Message Title stephenconnolly started work on JENKINS-36123 Change By: stephenconnolly Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26100) SCM steps should return revision state
Title: Message Title Jesse Glick commented on JENKINS-26100 Re: SCM steps should return revision state For a multibranch Pipeline job (Jenkinsfile), it would be straightforward to expose the SCMRevision as a special Groovy variable, as it is Serializable. Depending on the SCM source, you will get various available properties, such as hash in the case of Git branches (JENKINS-33161 would offer pullHash for pull request builds), though these would need to be marked @Whitelisted too. For general use including non-multibranch builds it would be desirable to get variables generically from the checkout step though this would require a core API change (JENKINS-24141). For the case of the git and svn convenience steps these could directly return the revision. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26100) SCM steps should return revision state
Title: Message Title Jesse Glick commented on JENKINS-26100 Re: SCM steps should return revision state Yes, as documented under env in Pipeline Syntax » Global Variables this is not yet supported. You need to git rev-parse HEAD etc. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36124) Build Parameters Corrupted sometimes in MultiJob Project
Title: Message Title Jonathon Lamon created an issue Jenkins / JENKINS-36124 Build Parameters Corrupted sometimes in MultiJob Project Issue Type: Bug Assignee: Dominik Bartholdi Components: conditional-buildstep-plugin, multijob-plugin, security Created: 2016/Jun/21 9:41 PM Environment: Jenkins 2.9 MultiJob Plugin 1.21 Conditional Build Step 1.3.5 Priority: Major Reporter: Jonathon Lamon Perhaps related to https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 We have several builds that are configured, pre plugin pipeline, using the MultiJob plugin and conditional build steps to build a webservice and its dependencies. The dependencies are only built if there are any SCM changes. The build is configured with several parameters indicating the environment (dev/prod) that the project is being built into. When the subjobs are run based off of changes in SCM, the original parameter selection becomes corrupted and they are not passed correctly to the final job, which needs them. However, if only the final job is built, then the parameters do not become corrupted and they are passed correctly. It appears that what is happening, due to the new security constraints, if the parameters do not exist in the sub project, they become corrupted in the Multi-Job project. It is not that they are being subjected to the security constraint, they are removed completely it seems and any defaults that might be set are used. Clicking the "Parameters" tab of such a build, the parameters are a blank blank page surrounded by the title, no listing. Clicking the "Parameters" tab of a build that did not build the other dependencies, the parameters entries are displayed as expected.
[JIRA] (JENKINS-36123) Provide a mechanism to for plugins to veto SCM polling on jobs
Title: Message Title stephenconnolly created an issue Jenkins / JENKINS-36123 Provide a mechanism to for plugins to veto SCM polling on jobs Issue Type: Improvement Assignee: stephenconnolly Components: core Created: 2016/Jun/21 9:37 PM Priority: Minor Reporter: stephenconnolly It can be useful to black-out SCM triggers during release builds as otherwise you will get a storm of SCM triggers that drown the Jenkins server. Plugins should be able to veto SCM trigger polling for specific jobs via an extension point Add Comment
[JIRA] (JENKINS-21670) Option to anonymize customer labels
Title: Message Title Arnaud Héritier commented on JENKINS-21670 Re: Option to anonymize customer labels Here are more feedbacks of what could be considered as “Sensitive/Non-Public”: 1/ System and network informations : processes, accounts, IPs, hostnames and everything related to the hosting system and its network configuration. -> Current status: Such informations are provided by different bundles options which can be already deactivated (Environment variables, File descriptors (Unix only), Networking Interface, Root CAs, System configuration (Linux only), System properties) but there are probably others places where they should be anonymised 2/ All kind of credentials -> Current status: Never stored in bundles. Should never appear in Jenkins logs (but ...). Should never appear in jobs logs (but ... it can - there are some known issues) but for now no job informations/logs are provided in bundles 3/ All kind of audit logs to know who did what -> Current status: it should be necessary to not bundle the audit plugin logs if it is installed (I don't know it very well thus I need to investigate). 4/ Users informations (Name, emails, logon, ...) -> Provided by option "About user (basic authentication details only)" but we may probably have to anonymise them in more locations Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33824) Multiple SCMs (all git repos) where one repo should not trigger a build still causes a build to be triggered
Title: Message Title nkcfan nkcfan updated an issue Jenkins / JENKINS-33824 Multiple SCMs (all git repos) where one repo should not trigger a build still causes a build to be triggered Change By: nkcfan nkcfan *strong text* I have a job which checks out multiple git repositories. Check ins to repository1 should trigger the build to run. Checkins to repository2 should not trigger the build to run. To convey this, repository2 is configured with "Don't trigger build on commit notifications" and "Polling ignores commits in certain paths" where .* is listed as the excluded path. When a check in is made to repository2, the build is still triggered. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36122) Renaming a job does not get reflected
Title: Message Title eamonn faherty created an issue Jenkins / JENKINS-36122 Renaming a job does not get reflected Issue Type: Bug Assignee: Unassigned Components: copyartifact-plugin Created: 2016/Jun/21 8:45 PM Priority: Major Reporter: eamonn faherty I am not sure this defect is raised for the correct component. I ran some tests and this only happens when I use the copy artifact and promoted builds plugins Steps to reproduce configure job a to require manual promotion via a star configure job a to archive an artifact configure job b to be triggered upon successful promotion to job b rename job a trigger job a to job c promote job a Expected results job b should be triggered Actual results Job b was not triggered Job b did not show job c as an upstream on the configure page - it showed job a
[JIRA] (JENKINS-36120) Parameterized build parameters no longer available during promotion
Title: Message Title
Patrick Conant updated an issue
Jenkins / JENKINS-36120
Parameterized build parameters no longer available during promotion
Change By:
Patrick Conant
Following a migration from Jenkins 1.x to 2.2.7, the 'promoted build' plugin stopped replacing most of the variables that we rely on. The PROMOTED_* built-in variables (like {{ $ { PROMOTED_USER_NAME }}} and {{ $ { PROMOTED_SVN_REVISION }}} ) still work just fine. And promotion parameters work fine, too.But parameters of the build being promoted are no longer replaced -- the parameter text ("${SERVICE_NAME}") remains unchanged in the tasks executed during the promotion. The build parameters _are_ still available during the initial build, but don't seem to be available during the promotion run. In our particular case, we're using the variables in the extended e-mail publisher during promotion, but I've also verified the same problem when using a simple shell script in the promotion.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36120) Parameterized build parameters no longer available during promotion
Title: Message Title
Patrick Conant updated an issue
Jenkins / JENKINS-36120
Parameterized build parameters no longer available during promotion
Change By:
Patrick Conant
Following a migration from Jenkins 1.x to 2.2.7, the 'promoted build' plugin stopped replacing most of the variables that we rely on. The PROMOTED_* built-in variables (like {{ ${PROMOTED_USER_NAME} }} and {{ ${PROMOTED_SVN_REVISION} }} ) still work just fine. And promotion parameters work fine, too.But parameters of the build being promoted are no longer replaced -- the parameter text ("${SERVICE_NAME}") remains unchanged in the tasks executed during the promotion. The build parameters _are_ still available during the initial build, but don't seem to be available during the promotion run. In our particular case, we're using the variables in the extended e-mail publisher during promotion, but I've also verified the same problem when using a simple shell script in the promotion.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Paul Becotte created an issue Jenkins / JENKINS-36121 Github Branch Source plugin trips api rate limit Issue Type: Bug Assignee: Jesse Glick Components: github-branch-source-plugin Created: 2016/Jun/21 8:31 PM Environment: Jenkins 2.10, github-branch-source-plugin 1.7 Labels: github Priority: Major Reporter: Paul Becotte We have quite a large organization in Github, lots of repos with lots of branches. Running the organization scan works well for a while, and then begins erroring out with org.jenkinsci.plugins.github_branch_source.RateLimitExceededException: GitHub API rate limit exceeded This is pretty rough since it always starts in the same place, and I haven't been able to figure out ANY way to add a project from the back of the list that recently added a Jenkinsfile. I am using a valid set of credentials (all the repos are private, so it wouldn't work otherwise anyway).
[JIRA] (JENKINS-36120) Parameterized build parameters no longer available during promotion
Title: Message Title
Patrick Conant created an issue
Jenkins / JENKINS-36120
Parameterized build parameters no longer available during promotion
Issue Type:
Bug
Assignee:
Unassigned
Components:
promoted-builds-plugin
Created:
2016/Jun/21 8:29 PM
Environment:
Jenkins ver. 2.7 Promoted Builds plugin ver 2.2.7
Priority:
Minor
Reporter:
Patrick Conant
Following a migration from Jenkins 1.x to 2.2.7, the 'promoted build' plugin stopped replacing most of the variables that we rely on. The PROMOTED_* built-in variables (like $ {PROMOTED_USER_NAME} and $ {PROMOTED_SVN_REVISION} ) still work just fine. And promotion parameters work fine, too. But parameters of the build being promoted are no longer replaced – the parameter text ("$ {SERVICE_NAME} ") remains unchanged in the tasks executed during the promotion. The build parameters are still available during the initial build, but don't seem to be available during the promotion run. In our particular case, we're using the variables in the extended e-mail publisher during promotion, but I've also verified the same problem when using a simple shell script in the promotion.
[JIRA] (JENKINS-23351) Tesflight Plugin: Add support for Custom URL
Title: Message Title Jonathon Lamon closed an issue as Won't Fix This can no longer be implemented as Apple bought Testflight and the old service is no longer available. Jenkins / JENKINS-23351 Tesflight Plugin: Add support for Custom URL Change By: Jonathon Lamon Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you 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-36104) Add Repo SCM support
Title: Message Title Boguslaw Klimas resolved as Fixed https://github.com/jenkinsci/git-parameter-plugin/pull/25 Jenkins / JENKINS-36104 Add Repo SCM support Change By: Boguslaw Klimas Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35033) Support for binding of port ranges
Title: Message Title Kurt Madel edited a comment on JENKINS-35033 Re: Support for binding of port ranges This has been release released : https://github.com/docker-java/docker-java/releases/tag/docker-java-3.0.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34180) Improve the status posted to GitHub when Jenkins validates the branch from a PR merge
Title: Message Title Jesse Glick resolved as Not A Defect This reflects a misunderstanding of what the GitHub status represents. When you run a PR build—and as of JENKINS-33161, you can choose whether that tries to merge with the base branch or not, or choose both—Jenkins reports on the status of the a PR head commit. GitHub will display the status associated with commits in the history of a PR. It also knows that if the head of an open PR has an associated status, it should be displayed as the status of the PR overall. It does not currently display any other commit statuses, including those of commits which are the result of merging a PR through the UI, though they are available from the API. If and when the PR is accepted, there may be a commit in the base branch which is similar to the commit built by a merge PR job (~ any PR job, prior to JENKINS-33161). It is not quite identical since the author and timestamp will be different, not to mention that GitHub might select a different merge algorithm than Jenkins did. Then there are people who “merge” PRs by squashing/rebasing commits in various ways, in which case the base branch commits are not even merge commits, though again the contents (file tree) are likely to be identical to what Jenkins built recently. Or a project administrator may git merge the PR branch, then do some local fixups, and push everything at once, in which case the base branch commit that Jenkins builds will be distinct from anything ever built as part of the PR status. Jenkins / JENKINS-34180 Improve the status posted to GitHub when Jenkins validates the branch from a PR merge Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment
[JIRA] (JENKINS-35033) Support for binding of port ranges
Title: Message Title Kurt Madel commented on JENKINS-35033 Re: Support for binding of port ranges This has been release: https://github.com/docker-java/docker-java/releases/tag/docker-java-3.0.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25832) Launch multiple slaves in parallel for jobs with same node label
Title: Message Title Maxwell Dribinsky reopened an issue Workaround doesn't launch slaves for each job in queue at once. It still launches one at a time, but slightly faster. The original issue persists. Jenkins / JENKINS-25832 Launch multiple slaves in parallel for jobs with same node label Change By: Maxwell Dribinsky Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from
[JIRA] (JENKINS-35453) Allow disabling the default commit status notifier
Title: Message Title Jesse Glick commented on JENKINS-35453 Re: Allow disabling the default commit status notifier Cf. comment in JENKINS-26522. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36119) GhprbBuilds creates wrong GhprbCause: merged vs. mergeable
Title: Message Title Jens Elkner created an issue Jenkins / JENKINS-36119 GhprbBuilds creates wrong GhprbCause: merged vs. mergeable Issue Type: Bug Assignee: Honza Brázdil Components: ghprb-plugin Created: 2016/Jun/21 7:56 PM Environment: jenkins 2.9, ghprb plugin 1.32.5 Priority: Blocker Reporter: Jens Elkner org.jenkinsci.plugins.ghprb.GhprbBuilds creates a GhprbCause, but unfortunately assigns the PR.isMergeable property to GhprbCause.merged (see line 58), which in turn causes other "wrong decisions" later (e.g. wrong sha1 env variable - see GhprbTrigger.java line 359). Add Comment
[JIRA] (JENKINS-33137) Per-job attributes for multibranch workflow jobs
Title: Message Title Jesse Glick commented on JENKINS-33137 Re: Per-job attributes for multibranch workflow jobs Currently you do need to inspect env.JOB_NAME. Note that CloudBees Jenkins Enterprise includes a related feature. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35668) Support configuring parameterized build
Title: Message Title Jesse Glick resolved as Not A Defect See Snippet Generator for the properties step. Jenkins / JENKINS-35668 Support configuring parameterized build Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35991) We would like control how pull requests are built on multi-branch pipelines
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-35991 We would like control how pull requests are built on multi-branch pipelines github-branch-source issue is JENKINS-33161. Change By: Jesse Glick Component/s: github-branch-source-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-5303) Upgrade Acegi Security to the latest Spring Security release
Title: Message Title Rob Winch commented on JENKINS-5303 Re: Upgrade Acegi Security to the latest Spring Security release Daniel Beck Thanks for the response and the link to the tester. I'm not sure I'm willing to commit to the work unless the work will be merged. I am even willing to entertain the idea of fixing the plugins that would break. However, I want to ensure that my work will not be in vain. Cheers, Rob Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33237) Failure to check out commit from a closed & reopened PR
Title: Message Title Jesse Glick commented on JENKINS-33237 Re: Failure to check out commit from a closed & reopened PR The current implementation of JENKINS-33161 fixes this as a side effect. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35559) Upgrade to Credentials 2.1.0+ API for populating credentials drop-down
Title: Message Title Vinod Kone resolved as Duplicate Resolved as duplicate of https://github.com/jenkinsci/mesos-plugin/issues/241 Jenkins / JENKINS-35559 Upgrade to Credentials 2.1.0+ API for populating credentials drop-down Change By: Vinod Kone Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For
[JIRA] (JENKINS-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587
Title: Message Title Sorin Sbarnea commented on JENKINS-26048 Re: Jenkins no longer cleaning up child processes when build stopped - as of 1.587 I faced the same bug with Jenkins 2.9 and some shell jobs started via pipelines. It does not always happen so I don't really know what is causing it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36117) OpenShift Deployment Verification Timeout not working
Title: Message Title Gabe Montero closed an issue as Fixed Jenkins / JENKINS-36117 OpenShift Deployment Verification Timeout not working Change By: Gabe Montero Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36117) OpenShift Deployment Verification Timeout not working
Title: Message Title Gabe Montero resolved as Fixed Jenkins / JENKINS-36117 OpenShift Deployment Verification Timeout not working Change By: Gabe Montero Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36117) OpenShift Deployment Verification Timeout not working
Title: Message Title Gabe Montero commented on JENKINS-36117 Re: OpenShift Deployment Verification Timeout not working Yep, your assumption is correct, and your welcome I'm going to go ahead and resolve / close this issue. Thanks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36117) OpenShift Deployment Verification Timeout not working
Title: Message Title Tom Larrow commented on JENKINS-36117 Re: OpenShift Deployment Verification Timeout not working That worked, thank you. I assume it'll default to that value if a waitTime parameter isn't passed in. That kind of gives us the best of both worlds, the ability to set a sane default value, and allow a different project to override if necessary. Thanks for your quick help on this issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36117) OpenShift Deployment Verification Timeout not working
Title: Message Title Gabe Montero commented on JENKINS-36117 Re: OpenShift Deployment Verification Timeout not working OK I've built a pre-release version of the plugin with the fix noted in 2) of my previous comment. That built plugin can be downloaded from here: https://ci.openshift.redhat.com/jenkins/job/openshift-pipeline-plugin/lastSuccessfulBuild/artifact/plugin/openshift-pipeline.hpi The associated commits are https://github.com/openshift/jenkins-plugin/commit/3b2a329809d7fdf1bbda764dcb5dd0ed602f17e4 https://github.com/jenkinsci/openshift-pipeline-plugin/commit/3b2a329809d7fdf1bbda764dcb5dd0ed602f17e4 Assuming the two follow ups above are in line with what you are doing, if possible, give the new plugin a try and let me know if they resolve this issue for you. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34426) Changing project-based settings for AD-Groups shows error
Title: Message Title Roger Myung commented on JENKINS-34426 Re: Changing project-based settings for AD-Groups shows error I am using AD 1.47, with Jenkins 1.651.3, and I see this error (or something similar). My message is FATAL: Authentication failed because there was a problem caching user ; nested exception is com.google.common.util.concurrent.UncheckedExecutionException: com4j.ComException: 8007203e The search filter cannot be recognized. : The search filter cannot be recognized. : .\invoke.cpp:517 hudson.plugins.active_directory.CacheAuthenticationException: Authentication failed because there was a problem caching user ; nested exception is com.google.common.util.concurrent.UncheckedExecutionException: com4j.ComException: 8007203e The search filter cannot be recognized. : The search filter cannot be recognized. : .\invoke.cpp:517 at hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:209) at hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:54) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36117) OpenShift Deployment Verification Timeout not working
Title: Message Title Gabe Montero started work on JENKINS-36117 Change By: Gabe Montero Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36117) OpenShift Deployment Verification Timeout not working
Title: Message Title Gabe Montero commented on JENKINS-36117 Re: OpenShift Deployment Verification Timeout not working OK, no worries. So two follow ups: 1) with the old Java based step invocation, there was no way to set the waiiTime as part of constructing the step, but with later versions, we now have pipeline DSL, and you can set 'waitTime' as a parameter. See the README and/or try to scriplet generator. 2) If you were using the global jenkins config panel, I do see where the DSL's were not accessing config set there. I'm working on a change to address that. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35911) CTest returning non-zero error code should not stop the build
Title: Message Title Martin Weber updated an issue Jenkins / JENKINS-35911 CTest returning non-zero error code should not stop the build Change By: Martin Weber Labels: feedback Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36117) OpenShift Deployment Verification Timeout not working
Title: Message Title Tom Larrow commented on JENKINS-36117 Re: OpenShift Deployment Verification Timeout not working Yes, I probably should have clarified, this is all being done with Pipeline groovy script. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36118) console output for a job run reports error
Title: Message Title Oliver Gondža assigned an issue to Steven G Brown Jenkins / JENKINS-36118 console output for a job run reports error Change By: Oliver Gondža Assignee: Oliver Gondža Steven G Brown Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36118) console output for a job run reports error
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-36118 console output for a job run reports error Change By: Oliver Gondža Component/s: timestamper-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36118) console output for a job run reports error
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-36118 console output for a job run reports error Change By: Oliver Gondža Component/s: core Component/s: acceptance-test-harness Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36118) console output for a job run reports error
Title: Message Title Vijay sundar updated an issue Jenkins / JENKINS-36118 console output for a job run reports error Change By: Vijay sundar Summary: console output for a jib job run reports error Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36118) console output for a jib run reports error
Title: Message Title Vijay sundar created an issue Jenkins / JENKINS-36118 console output for a jib run reports error Issue Type: Bug Assignee: Oliver Gondža Components: acceptance-test-harness Created: 2016/Jun/21 5:38 PM Priority: Critical Reporter: Vijay sundar Following error is seen when trying to view console output of a job run Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.9.jar!/hudson/model/Run/console.jelly:65:27: hudson.plugins.timestamper.TimestamperConfig.formatter(Lorg/kohsuke/stapler/StaplerRequest;)Lhudson/plugins/timestamper/format/TimestampFormatter; at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at
[JIRA] (JENKINS-32400) Import shared Groovy code
Title: Message Title Wayne Warren commented on JENKINS-32400 Re: Import shared Groovy code I should probably just RTFM, but is there a way to mark a particular stage as a flyweight task? It seems like the example shown in the description on this ticket could be done without consuming a full executor slot. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36099) Request to use alternate Queue Name regression failed
Title: Message Title Mike Caspar closed an issue as Fixed Jenkins / JENKINS-36099 Request to use alternate Queue Name regression failed Change By: Mike Caspar Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36099) Request to use alternate Queue Name regression failed
Title: Message Title Mike Caspar resolved as Fixed Jenkins / JENKINS-36099 Request to use alternate Queue Name regression failed Change By: Mike Caspar Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36099) Request to use alternate Queue Name regression failed
Title: Message Title Mike Caspar commented on JENKINS-36099 Re: Request to use alternate Queue Name regression failed 1.0.16 will have fix (v2.10 jenkins minimum) 1.0.17 will have fix (1.x version) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31155) Workflow shared library improvements
Title: Message Title Jesse Glick commented on JENKINS-31155 Re: Workflow shared library improvements JENKINS-26192 requested Grape support. Seems unlikely this would work but deserves investigation. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36117) OpenShift Deployment Verification Timeout not working
Title: Message Title
Gabe Montero commented on JENKINS-36117
Re: OpenShift Deployment Verification Timeout not working
Hi - just wanted to confirm, based on the `retry(3){}` snippet, that you are leveraging the deployment verification logic from a pipeline/workflow plugin groovy script, correct?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35641) Jenkins should always send usage statistics over HTTPs
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-35641 Jenkins should always send usage statistics over HTTPs Change By: Oliver Gondža Labels: 2.7.1-rejected lts-candidate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31915) Proxy settings in plugins page are ignored
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-31915 Proxy settings in plugins page are ignored Change By: Oliver Gondža Labels: 2.7.1-fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34763) Email-ext plugin (culprits and committers) in Jenkins Pipeline
Title: Message Title Sorin Sbarnea commented on JENKINS-34763 Re: Email-ext plugin (culprits and committers) in Jenkins Pipeline Where can we get some documentation (example!) on how to email developers and/or culprits using Jenkins pipelines? This bug is marked closed as fixed but it contains no information about how we are supposed to use it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32057) Installer test failure: Debian service script appears to allow multiple jenkins processes?
Title: Message Title Sam Van Oort resolved as Fixed Resolved with https://github.com/jenkinsci/packaging/pull/58 Jenkins / JENKINS-32057 Installer test failure: Debian service script appears to allow multiple jenkins processes? Change By: Sam Van Oort Status: Open Resolved Assignee: Sam Van Oort Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You
[JIRA] (JENKINS-32057) Installer test failure: Debian service script appears to allow multiple jenkins processes?
Title: Message Title Sam Van Oort commented on JENKINS-32057 Re: Installer test failure: Debian service script appears to allow multiple jenkins processes? Resolved by https://github.com/jenkinsci/packaging/pull/58 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33833) Lost the batch task history since 1.634
Title: Message Title Mikael Gaunin commented on JENKINS-33833 Re: Lost the batch task history since 1.634 Tom FENNELLY do not hesitate if you need help, I'll be there! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
