[JIRA] (JENKINS-40987) Exception when saving the job configuration
Title: Message Title Dominik Bartholdi commented on JENKINS-40987 Re: Exception when saving the job configuration why do you think this has anything to do with the config-file-provider plugin? I don't see anything related to it in the stacktrace. please provide more information about the issue, maybe read https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue on how to report an issue. e.g. describe how this issue can be reproduced which version of jenkins? which plugins are installed? which versions? ... the best thing would be to collect most of this information with this plugin: https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+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-12114) Flexible file editing permissions
Title: Message Title Dominik Bartholdi commented on JENKINS-12114 Re: Flexible file editing permissions no plans so far... 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-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title Daniel Beck commented on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time I started with a branch into which I had purposely introduced a failure. I created a new branch, and pushed it without modification The idea I mentioned was to create the branch from a master/trunk that builds successfully, so the first build of the branch is identical to master/trunk, and only then introduce changes that could break things. As there's no previous build for the branch, Jenkins has nothing to compare it to to determine who should be emailed. The developer of the last commit? May not be the culprit if there's several changes pushed. Everyone in the history of the branch? Too many false positives. It would be nice if there were metadata from e.g. comparing the branch to master/trunk, but that's SCM specific. Not sure whether SCM API could do that, and whether the email plugins could take that into account. Stephen Connolly? 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-40470) Jobs didn't finish on Solaris 11 Intel node
Title: Message Title Lubos Kosco commented on JENKINS-40470 Re: Jobs didn't finish on Solaris 11 Intel node thnx guys! 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-34367) Add support for empty sendTo field for extendedEmail plugin
Title: Message Title
Daniel Spilker commented on JENKINS-34367
Re: Add support for empty sendTo field for extendedEmail plugin
I tried to replicate the defaults of the email-ext plugin in Job DSL, but missed the fact that it must be possible to remove the defaults. But some people may rely on the current behavior and I do not want to break compatibility. So this is hard to fix. But you can use the Automatically Generated DSL to create the desired configuration:
job('example') {
publishers {
extendedEmailPublisher {
project_recipient_list('generic@something.com')
project_content_type('default')
project_default_subject('$DEFAULT_SUBJECT')
project_default_content('$DEFAULT_CONTENT')
project_attachments('')
project_presend_script('$DEFAULT_PRESEND_SCRIPT')
project_attach_buildlog(0)
project_replyto('$DEFAULT_REPLYTO')
project_save_output(false)
project_triggers {
successTrigger {
recipientList('succ...@something.com')
replyTo('$PROJECT_DEFAULT_REPLYTO')
subject('$PROJECT_DEFAULT_SUBJECT')
body('$PROJECT_DEFAULT_CONTENT')
attachmentsPattern('')
attachBuildLog(0)
contentType('project')
}
}
matrixTriggerMode('BOTH')
project_disabled(false)
}
}
}
The Automatically Generated DSL does not create any triggers or recipient providers by default. But unfortunately the email-ext marks most options as required by using @DataBoundConstructor instead of @DataBoundSetter. But that can easily be fixed in email-ext.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41004) Credentials Binding does not guarantee folder credential with a given ID will be returned over global credential with same ID
Title: Message Title Daniel Beck commented on JENKINS-41004 Re: Credentials Binding does not guarantee folder credential with a given ID will be returned over global credential with same ID multiple providers supplying different credentials for the same ID Is that even a supported use case? 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-40894) setting not persistent for "ERRORLEVEL to set build unstable"
Title: Message Title Daniel Beck updated JENKINS-40894 Fixed towards 2.41 Jenkins / JENKINS-40894 setting not persistent for "ERRORLEVEL to set build unstable" Change By: Daniel Beck Status: In Review 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-40894) setting not persistent for "ERRORLEVEL to set build unstable"
Title: Message Title Daniel Beck commented on JENKINS-40894 Re: setting not persistent for "ERRORLEVEL to set build unstable" Oliver Gondža FYI for your consideration into 2.32.2. This one will be late but might be worth 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-12114) Flexible file editing permissions
Title: Message Title Daniel Mueller commented on JENKINS-12114 Re: Flexible file editing permissions I have a meeting in a few days to discuss our jenkins setup. This ticket is the last missing piece of the puzzle which would allow us to use just one jenkins master with independant regional or peoject folders (own config files, own credentials). My plan is to get some budget to implement this feature. I'll let you know if and when we can start to work 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-40703) Support injection of maven-gpg-plugin:sign config params in Maven Settings files
Title: Message Title Dominik Bartholdi commented on JENKINS-40703 Re: Support injection of maven-gpg-plugin:sign config params in Maven Settings files hmm, yeah - strange situation. ...to be honest: as a user, I don't like the withXXX wrapper stuff - all this nested wrapping of code within the different closers are awkward and make the pipeline scripts very hard to read. 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-39570) Maven job type's "module" shown on dashboard
Title: Message Title Michael Neale commented on JENKINS-39570 Re: Maven job type's "module" shown on dashboard I can't work out how to set up this to test it - any one know how? I have installed the plugin but it complains there is no maven setup 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-38606) Jenkins creates AllView with a localized name on on initial startup
Title: Message Title Daniel Beck resolved as Fixed Resolved in 2.37 as JENKINS-39300 Jenkins / JENKINS-38606 Jenkins creates AllView with a localized name on on initial startup Change By: Daniel Beck 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-41020) CloudBees Docker Build and Publish - Environment Variables
Title: Message Title
Yaniv Eliash created an issue
Jenkins / JENKINS-41020
CloudBees Docker Build and Publish - Environment Variables
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
docker-build-publish-plugin
Created:
2017/Jan/12 8:56 AM
Priority:
Blocker
Reporter:
Yaniv Eliash
I'm trying to push to a custom repository, however we have several repositories around the globe. I've the plugin 'This project is parameterized' I've set 2 parameters : 1. TAG 2. REPOSITORY When executing a prebuild that do a simple 'eval docker login $REPOSITORY --username=x --password=x' all works perfect However, Inside cloudbess docker build and publish I've set the repository equal to $REPOSITORY (tried also ${} and $()) that give me an exception as the variable isn't parsed :
10:37:19 + eval docker login $REPOSITORY --username=x --password=x
10:37:19 + docker login https://nexus.x.y.com:5000 --username=x --password=x
10:37:21 Login Succeeded
10:37:21 ERROR: no protocol: ${REPOSITORY}
10:37:21 java.net.MalformedURLException: no protocol: ${REPOSITORY}
10:37:21 at java.net.URL.(URL.java:593)
10:37:21 at java.net.URL.(URL.java:490)
10:37:21 at java.net.URL.(URL.java:439)
10:37:21 at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.getEffectiveUrl(DockerRegistryEndpoint.java:136)
10:37:21 at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.imageName(DockerRegistryEndpoint.java:233)
10:37:21 at com.cloudbees.dockerpublish.DockerBuilder.getRepo(DockerBuilder.java:252)
10:37:21 at com.cloudbees.dockerpublish.DockerBuilder$Perform.getImageTags(DockerBuilder.java:336)
10:37:21 at com.cloudbees.dockerpublish.DockerBuilder$Perform.buildAndTag(DockerBuilder.java:370)
10:37:21 at com.cloudbees.dockerpublish.DockerBuilder$Perform.exec(DockerBuilder.java:311)
10
[JIRA] (JENKINS-41020) CloudBees Docker Build and Publish - Environment Variables
Title: Message Title
Yaniv Eliash updated an issue
Jenkins / JENKINS-41020
CloudBees Docker Build and Publish - Environment Variables
Change By:
Yaniv Eliash
I'm trying to push to a custom repository,however we have several repositories around the globe and I would like the developer to choose to which repo to push .I've the plugin 'This project is parameterized'I've set 2 parameters :1. TAG2. REPOSITORYWhen executing a prebuild that do a simple 'eval docker login $REPOSITORY --username=x --password=x' all works perfectHowever,Inside cloudbess docker build and publish I've set the repository equal to $REPOSITORY (tried also ${} and $()) that give me an exception as the variable isn't parsed :{code:java}10:37:19 + eval docker login $REPOSITORY --username=x --password=x10:37:19 + docker login https://nexus.x.y.com:5000 --username=x --password=x10:37:21 Login Succeeded10:37:21 ERROR: no protocol: ${REPOSITORY}10:37:21 java.net.MalformedURLException: no protocol: ${REPOSITORY}10:37:21 at java.net.URL.(URL.java:593)10:37:21 at java.net.URL.(URL.java:490)10:37:21 at java.net.URL.(URL.java:439)10:37:21 at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.getEffectiveUrl(DockerRegistryEndpoint.java:136)10:37:21 at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.imageName(DockerRegistryEndpoint.java:233)10:37:21 at com.cloudbees.dockerpublish.DockerBuilder.getRepo(DockerBuilder.java:252)10:37:21 at com.cloudbees.dockerpublish.DockerBuilder$Perform.getImageTags(DockerBuilder.java:336)10:37:21 at com.cloudbees.dockerpublish.DockerBuilder$Perform.buildAndTag(DockerBuilder.java:370)10:37:21 at com.cloudbees.dockerpublish.DockerBuilder$Perform.exec(DockerBuilder.java:311)10:37:21 at com.cloudbees.dockerpublish.DockerBuilder$Perform.access$100(DockerBuilder.java:291)10:37:21 at com.cloudbees.dockerpublish.DockerBuilder.perform(DockerBuilder.java:262)10:37:21 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)10:37:21 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)10:37:21 at hudson.model.Build$BuildExecution.build(Build.java:205)10:37:21 at hudson.model.Build$BuildExecution.doRun(Build.java:162)10:37:21 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)10:37:21 at hudson.model.Run.execute(Run.java:1741)10:37:21 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)10:37:21 at hudson.model.ResourceController.execute(ResourceController.java:98)10:37:21 at hudson.model.Executor.run(Executor.java:410)10:37:21 Build step 'Docker Build and Publish' marked build as failure10:37:21 [ssh-agent] Stopped.10:37:21 Finished: FAILURE{code}
[JIRA] (JENKINS-41021) Not possible to change hudson.slaves.WorkspaceList in runtime
Title: Message Title Marcus Ahlberg created an issue Jenkins / JENKINS-41021 Not possible to change hudson.slaves.WorkspaceList in runtime Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Jan/12 9:05 AM Environment: Jenkins ver. 1.651.1 in docker Labels: concurrent workspace path Priority: Minor Reporter: Marcus Ahlberg As many others before us we have problems with @ in workspace paths for concurrent jobs. Setting the property hudson.slaves.WorkspaceList in JAVA_OPTS works but is a bit of a hassle and requires some extra tweaking in our docker setup script. A better way for us is to use System.setProperty() to set it in the startup script but that has no effect. System.getProperty() verifies the new value but the default value is still used. I consider this a bug. An even better way would be to promote this to a normal setting. The system property documentation mentions "In general, these switches are often experimental in nature, and subject to change without notice. If you find some of those useful, please file a ticket to promote it to the official feature." and a lot of people seem to be interested in changing this property so it should be promoted to an official setting. This would then be a feature request.
[JIRA] (JENKINS-41004) Credentials Binding does not guarantee folder credential with a given ID will be returned over global credential with same ID
Title: Message Title Cyrille Le Clerc commented on JENKINS-41004 Re: Credentials Binding does not guarantee folder credential with a given ID will be returned over global credential with same ID Daniel Beck I think so: credentials defined at the top level could be overwritten at the folder level. 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-37177) surefire concurrency inappropriate default causes random build failures
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-37177 surefire concurrency inappropriate default causes random build failures Change By: Baptiste Mathus Summary: surefire concurrency inappropriate default inappropraite causes random build failures 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-41022) windows slave can't run, Unexpected error in launching an agent
Title: Message Title adam huang created an issue Jenkins / JENKINS-41022 windows slave can't run, Unexpected error in launching an agent Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: windows-slaves-plugin Created: 2017/Jan/12 9:10 AM Environment: jre6, windows 7(slave), ubuntu 16.04 x64 (master) Priority: Blocker Reporter: adam huang server is : Jenkins ver. 2.40 ubuntu 16.04 x64 slave is :Jenkins ver. 2.40 windows 7 x64 Windows 7 Jenkins and Jenkins Slave can be run. [2017-01-12 17:02:57] [windows-slaves] Connecting to 192.168.2.117 Checking if Java exists java -version returned 1.6.0. [2017-01-12 17:03:00] [windows-slaves] Copying jenkins-slave.xml [2017-01-12 17:03:00] [windows-slaves] Copying slave.jar [2017-01-12 17:03:00] [windows-slaves] Starting the service ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.lang.reflect.UndeclaredThrowableException at com.sun.proxy.$Proxy69.start(Unknown Source) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:340) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:261) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: 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.Me
[JIRA] (JENKINS-40971) the gatling plugin 95% tile displays the 50% tile value instead
Title: Message Title Cédric Cousseran commented on JENKINS-40971 Re: the gatling plugin 95% tile displays the 50% tile value instead We haven't planned a new release, so I can't give you a date yet. You will be able to update the plugin in the Manage Jenkins section. You can't configure the plugin to add new trends. If you still want to add them, the plugin is open-source (https://github.com/jenkinsci/gatling-plugin), or you can use our entreprise extension to Gatling: link FrontLine 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-41023) Fix JobConfigHistoryPluginTest#show_difference_in_config_history test
Title: Message Title
Evaristo Gutierrez created an issue
Jenkins / JENKINS-41023
Fix JobConfigHistoryPluginTest#show_difference_in_config_history test
Issue Type:
Task
Assignee:
Evaristo Gutierrez
Components:
acceptance-test-harness
Created:
2017/Jan/12 9:25 AM
Priority:
Minor
Reporter:
Evaristo Gutierrez
java.lang.AssertionError:
Expected: contains element that matches By.xpath: //td[@class='diff_original']/pre[normalize-space(text())='#{original}']
but: was at "http://172.17.0.5:60368/job/assertive_crossing/jobConfigHistory/showDiffFiles?timestamp1=2017-01-03_16-00-12×tamp2=2017-01-03_16-00-22"
at plugins.JobConfigHistoryPluginTest.show_difference_in_config_history(JobConfigHistoryPluginTest.java:110)
Add Comment
[JIRA] (JENKINS-41023) Fix JobConfigHistoryPluginTest#show_difference_in_config_history test
Title: Message Title Evaristo Gutierrez started work on JENKINS-41023 Change By: Evaristo Gutierrez 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-41023) Fix JobConfigHistoryPluginTest#show_difference_in_config_history test
Title: Message Title Evaristo Gutierrez updated JENKINS-41023 Jenkins / JENKINS-41023 Fix JobConfigHistoryPluginTest#show_difference_in_config_history test Change By: Evaristo Gutierrez Status: In Progress Review 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-40987) Exception when saving the job configuration
Title: Message Title M Z commented on JENKINS-40987 Re: Exception when saving the job configuration Hi, I am sorry, but I don't know Jenkins architecture so I can say that picking config-file-privder was a shot, probably missed. I don't know how can I reproduce that on different environments, I know only that I can reproduce it every time when I am trying to save that concrete Job. Others are saving without problems. There is a dump from a Support Core Plugin, I hope there is a rest of missing informations: https://www.dropbox.com/s/gigm5mwmhn5a3ec/support_2017-01-12_08.47.49.tar.gz?dl=0 Please let me know if I can help you somehow. 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-40907) Can't save jenkins system config
Title: Message Title Jonas Jonsson commented on JENKINS-40907 Re: Can't save jenkins system config I can CONFIRM this bug, all of a sudden I had it on our master too (2.35). Did a "emergency reboot" (upgraded ALL plugins before restart). Slaves are running Ubuntu 14.04.5 LTS and Ubuntu 16.04.1 LTS, all updated and rebooted. The problem is still there, we're now on 2.40 of jenkins.war. 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-40832) Primary branches should have their name in bold
Title: Message Title Stephen Connolly updated JENKINS-40832 Jenkins / JENKINS-40832 Primary branches should have their name in bold Change By: Stephen Connolly Status: In Review 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 options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40828) Provide a way for tests using MockSCMController to inject failures
Title: Message Title Stephen Connolly updated JENKINS-40828 Jenkins / JENKINS-40828 Provide a way for tests using MockSCMController to inject failures Change By: Stephen Connolly Status: In Review 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 options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40827) Clarify the content of ObjectMetadataAction's getDescription() and getDisplayName()
Title: Message Title Stephen Connolly updated JENKINS-40827 Jenkins / JENKINS-40827 Clarify the content of ObjectMetadataAction's getDescription() and getDisplayName() Change By: Stephen Connolly Status: In Review 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 options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40907) Can't save jenkins system config
Title: Message Title Jonas Jonsson edited a comment on JENKINS-40907 Re: Can't save jenkins system config I can CONFIRM this bug, all of a sudden I had it on our master too (2.35). Did a "emergency reboot" (upgraded ALL plugins before restart). Slaves are running Ubuntu 14.04.5 LTS and Ubuntu 16.04.1 LTS, all updated and rebooted. The problem is still there, we're now on 2.40 of jenkins.war. Jenkins master is running on Ubuntu 14.04.5 LTS (4.4.0-59 kernel).java version "1.8.0_77"Java(TM) SE Runtime Environment (build 1.8.0_77-b03)Java HotSpot(TM) 64-Bit Server VM (build 25.77-b03, mixed mode)Artifactory plugin 2.8.2 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-40829) Provide an API to retrieve a SCMSource from a given Item
Title: Message Title Stephen Connolly updated JENKINS-40829 Jenkins / JENKINS-40829 Provide an API to retrieve a SCMSource from a given Item Change By: Stephen Connolly Status: In Review 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 options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40826) Do not do long running tasks in a QueueListener
Title: Message Title Stephen Connolly updated JENKINS-40826 Jenkins / JENKINS-40826 Do not do long running tasks in a QueueListener Change By: Stephen Connolly Status: In Review 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 options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40722) Poll SCM results in a Pipeline run every interval (unnecessarily)
Title: Message Title Stephen Connolly resolved as Won't Do You should not use polling triggers when a job is part of an Organization Folder. The Organization Folder will trigger builds for you as it controls the SCM revision that is being checked out when you run a build (in other words, even when the polling triggers a build, that build will be for the last revision detected by the MultiBranch project not the revision that polling has detected) Jenkins / JENKINS-40722 Poll SCM results in a Pipeline run every interval (unnecessarily) Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40584) Choosing "Build origin branches" does not add "Push" webhook
Title: Message Title Stephen Connolly closed an issue as Won't Fix Probably fixed in the 2.0 series of GitHub Branch Source. Please re-open against GitHub Branch Source if not fixed there. Closing this issue as with the 2.0 series of GitHub Branch Source the GitHub Organization Folders plugin is dead (functionality moved to GitHub Branch Source) Jenkins / JENKINS-40584 Choosing "Build origin branches" does not add "Push" webhook Change By: Stephen Connolly 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
[JIRA] (JENKINS-40575) Allow custom tabs in github-organization-folder
Title: Message Title Stephen Connolly closed an issue as Won't Fix Probably addressed somewhat with the categorization of branches in the 2.0 series of GitHub Branch Source. Please re-open against GitHub Branch Source if not fixed there. Closing this issue as with the 2.0 series of GitHub Branch Source the GitHub Organization Folders plugin is dead (functionality moved to GitHub Branch Source) Jenkins / JENKINS-40575 Allow custom tabs in github-organization-folder Change By: Stephen Connolly Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40482) Support promoted-builds plugin
Title: Message Title Ebrahim Moshaya commented on JENKINS-40482 Re: Support promoted-builds plugin Hi Boguslaw Klimas have you had a chance yet to look at this feature request? Thanks Ebs 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-40907) Can't save jenkins system config
Title: Message Title
Jonas Jonsson edited a comment on JENKINS-40907
Re: Can't save jenkins system config
I can CONFIRM this bug, all of a sudden I had it on our master too (2.35). Did a "emergency reboot" (upgraded ALL plugins before restart). Slaves are running Ubuntu 14.04.5 LTS and Ubuntu 16.04.1 LTS, all updated and rebooted. The problem is still there, we're now on 2.40 of jenkins.war.Jenkins master is running on Ubuntu 14.04.5 LTS (4.4.0-59 kernel).java version "1.8.0_77"Java(TM) SE Runtime Environment (build 1.8.0_77-b03)Java HotSpot(TM) 64-Bit Server VM (build 25.77-b03, mixed mode)Artifactory plugin 2.8.2 Stack trace:{{java.io.InvalidClassException: org.jfrog.hudson.pipeline.docker.proxy.BuildInfoProxyManager$1; local class incompatible: stream classdesc serialVersionUID = 3391376971919256168, local class serialVersionUID = 1809589100624711481java.io.InvalidClassException: org.jfrog.hudson.pipeline.docker.proxy.BuildInfoProxyManager$1; local class incompatible: stream classdesc serialVersionUID = 3391376971919256168, local class serialVersionUID = 1809589100624711481 at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:699) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1706) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1601) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1874) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1433) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:429) at hudson.remoting.UserRequest.deserialize(UserRequest.java:217) at hudson.remoting.UserRequest.perform(UserRequest.java:131) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:336) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:274) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627) at java.lang.Thread.run(Thread.java:809) at ..remote call to SLES12-compile(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:822) at org.jfrog.hudson.pipeline.docker.proxy.BuildInfoProxyManager.stopAll(BuildInfoProxyManager.java:69) at org.jfrog.hudson.ArtifactoryBuilder$DescriptorImpl.configureProxy(ArtifactoryBuilder.java:227) at org.jfrog.hudson.ArtifactoryBuilder$DescriptorImpl.configure(ArtifactoryBuilder.java:198) at jenkins.model.Jenkins.configureDescriptor(Jenkins.java:3648) at jenkins.model.Jenkins.doConfigSubmit(Jenkins.java:3611) 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.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:335) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:175) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:108) 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.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServl
[JIRA] (JENKINS-40058) Jobs not removed when branch gets removed in case of orphaned item strategy set
Title: Message Title Stephen Connolly resolved as Not A Defect The strategy for removal of builds is controlled by the Jenkinsfile, e.g. something like properties([buildDiscarder(logRotator(artifactNumToKeepStr: '5', numToKeepStr: env.BRANCH_NAME=='master'?'10':'5'))]) which will keep the last 10 builds of master and the last 5 builds of all other branches (but obviously each branch could instead have its own value hard-coded as long as you are careful with merge conflicts between branches Jenkins / JENKINS-40058 Jobs not removed when branch gets removed in case of orphaned item strategy set Change By: Stephen Connolly Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40232) Git Parameter Plugin doesn't need to clone
Title: Message Title Ebrahim Moshaya commented on JENKINS-40232 Re: Git Parameter Plugin doesn't need to clone Hi Boguslaw Klimas I see you've started work on this on a POC branch. Have you had any chance to test out your changes? will it be ready for release soon? I'm very eager for this to be released as all our slaves are cloud based and terminate over night..In the morning, they lose all their workspaces and therefore this plugin can't be used with this setup. 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-34367) Add support for empty sendTo field for extendedEmail plugin
Title: Message Title Tom Reichelt commented on JENKINS-34367 Re: Add support for empty sendTo field for extendedEmail plugin Hi Daniel, thx for the answer! Unfortunately I've left the project so Iam not able to recheck. If a fix might break compatibility please feel free to close the ticket as won't fix. Kind regards! 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-39838) CHANGE_ variables are missing
Title: Message Title Stephen Connolly closed an issue as Not A Defect Seems like this was a configuration error (that the configuration options are non-obvious is a separate issue)... Closing this issue in any case as with the 2.0 series of GitHub Branch Source the GitHub Organization Folders plugin is dead (functionality moved to GitHub Branch Source) Jenkins / JENKINS-39838 CHANGE_ variables are missing Change By: Stephen Connolly Status: Open Closed 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 subs
[JIRA] (JENKINS-40907) Can't save jenkins system config
Title: Message Title Jonas Jonsson commented on JENKINS-40907 Re: Can't save jenkins system config I notice that the 'reporter' of the issue also have a "remote call" in the stack trace ... 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-40127) GDSL for Declarative
Title: Message Title rsandell assigned an issue to rsandell Jenkins / JENKINS-40127 GDSL for Declarative Change By: rsandell Assignee: Andrew Bayer rsandell 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-39837) scm: Browser isn't set to GithubWeb
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39837 Re: scm: Browser isn't set to GithubWeb Code changed in jenkins User: Stephen Connolly Path: src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/36154403f21b0adc1edeb001d0d4a4ceb5aa14b1 Log: JENKINS-39837 We need to be able to set the browser after instantiation 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-39837) scm: Browser isn't set to GithubWeb
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39837 Re: scm: Browser isn't set to GithubWeb Code changed in jenkins User: Stephen Connolly Path: src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/7b8460c1af808528fb0268b32c937db6396344c9 Log: JENKINS-39837 We need to be able to set the browser after instantiation 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-40879) Locked areas are executed multiple times in parallel
Title: Message Title
Daniel Wilmer edited a comment on JENKINS-40879
Re: Locked areas are executed multiple times in parallel
The *UPDATE* Maybe this information can help: { code}private static final class Callback extends BodyExecutionCallback.TailCall { LockStepExecution . Callback . finished}} method calls . protected void finished(StepContext context) throws Exception { { LockableResourcesManager.get().unlockNames(this.resourceNames, context.get(Run.class), this.inversePrecedence); context.get(TaskListener.class).getLogger().println("Lock released on resource [" + resourceDescription + "]");LOGGER.finest("Lock released on [" + resourceDescription + "]"); } ...{code } * I have seen that in the first runs " {{this.resourceNames}} " only contains a single stage ( e.g. [test-stage-2] ) . * But then in further executions it suddenly contains all three stages of this example , ( e.g. [test-stage-1, test-stage-2, test-stage-3] ) . Then * Next there are two loggers which print that a lock on " {{resourceDescription}} " is released :{code}context.get(TaskListener.class).getLogger().println( , although " Lock released on resource [" + resourceDescription + "]");LOGGER.finest("Lock released on [" + resourceDescription + "]"); { code}So:* { {resourceDescription}} contains the correct stage name to release (e this . g. [test-stage-2]).* But {{unlockNames resourceNames }} " is called with [test-stage-1, test-stage-2, test-stage-3] what is really released .I don't have enough background information to decide wether this is correct or not, but maybe I changed the implementation as follows and it worked (for this observation can help. usecase): I tried to change from {code} protected void finished(StepContext context) throws Exception { { LockableResourcesManager.get().unlockNames( this.resourceNames singletonList(resourceDescription) , context.get(Run.class), this.inversePrecedence); }} to:{{LockableResourcesManager context .get( TaskListener.class ). unlockNames getLogger ( asList ).println ( "Lock released on resource [" + resourceDescription + "]" ) , context ;LOGGER . get finest ( Run.class "Lock released on [" + resourceDescription + "]" ) , this.inversePrecedence) ; } {code } and the issue was gone. Maybe this can help finding the right solution.Regards, Daniel
Add Comment
[JIRA] (JENKINS-40879) Locked areas are executed multiple times in parallel
Title: Message Title
Daniel Wilmer edited a comment on JENKINS-40879
Re: Locked areas are executed multiple times in parallel
*UPDATE* Maybe this information can help:{code}private static final class Callback extends BodyExecutionCallback.TailCall {...protected void finished(StepContext context) throws Exception {LockableResourcesManager.get().unlockNames(this.resourceNames, context.get(Run.class), this.inversePrecedence);context.get(TaskListener.class).getLogger().println("Lock released on resource [" + resourceDescription + "]");LOGGER.finest("Lock released on [" + resourceDescription + "]");}...{code} * I have seen that in the first runs "{{this.resourceNames}}" only contains a single stage (e.g. [test-stage-2]). * But then in further executions it suddenly contains all three stages of this example (e.g. [test-stage-1, test-stage-2, test-stage-3]). * Next there are two loggers which print that a lock on "{{resourceDescription}}" is released, although "{{this.resourceNames}}" is what is really released.I don't have enough background information to decide wether this is correct or not, but I changed the implementation as follows and it worked (for this usecase):{code}protected void finished(StepContext context) throws Exception {LockableResourcesManager.get().unlockNames(singletonList(resourceDescription), context.get(Run.class), this.inversePrecedence);context.get(TaskListener.class).getLogger().println("Lock released on resource [" + resourceDescription + "]");LOGGER.finest("Lock released on [" + resourceDescription + "]");}{code}Maybe this can help finding the right solution.Regards, Daniel
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40977) "Uncaught SyntaxError: Unexpected identifier" on karaoke
Title: Message Title Thorsten Scherler started work on JENKINS-40977 Change By: Thorsten Scherler 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-40977) "Uncaught SyntaxError: Unexpected identifier" on karaoke
Title: Message Title Thorsten Scherler commented on JENKINS-40977 Re: "Uncaught SyntaxError: Unexpected identifier" on karaoke Michael Neale I will debug it, when having the sse event debug trace on I see a relation between sse-events coming in and the occurrence of the 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-40670) Input status indicator is off
Title: Message Title Thorsten Scherler stopped work on JENKINS-40670 Change By: Thorsten Scherler 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-38495) Add "waiting for input" state to favourite card
Title: Message Title Thorsten Scherler updated JENKINS-38495 Jenkins / JENKINS-38495 Add "waiting for input" state to favourite card Change By: Thorsten Scherler Status: In Review 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 options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40448) Allow S3 artifacts to be created by multiple steps
Title: Message Title Julian Cook assigned an issue to Julian Cook Jenkins / JENKINS-40448 Allow S3 artifacts to be created by multiple steps Change By: Julian Cook Assignee: Alexander A Julian Cook 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-40448) Allow S3 artifacts to be created by multiple steps
Title: Message Title Julian Cook updated JENKINS-40448 Jenkins / JENKINS-40448 Allow S3 artifacts to be created by multiple steps Change By: Julian Cook Status: In Progress Review 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-40448) Allow S3 artifacts to be created by multiple steps
Title: Message Title Julian Cook started work on JENKINS-40448 Change By: Julian Cook 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-40448) Allow S3 artifacts to be created by multiple steps
Title: Message Title Julian Cook assigned an issue to Alexander A Jenkins / JENKINS-40448 Allow S3 artifacts to be created by multiple steps Change By: Julian Cook Assignee: Julian Cook Alexander A 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-40977) "Uncaught SyntaxError: Unexpected identifier" on karaoke
Title: Message Title Thorsten Scherler commented on JENKINS-40977 Re: "Uncaught SyntaxError: Unexpected identifier" on karaoke javax.servlet.ServletException: java.lang.NoSuchFieldError: job_run_unpaused at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) 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$3.doDispatch(MetaClass.java:196) 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$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$3.doDispatch(MetaClass.java:196) 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$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$3.doDispatch(MetaClass.java:196) 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$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$3.doDispatch(MetaClass.java:196) 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$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$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$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.Stapler.tryInvoke(Stapler.java:686) 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.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 org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:206) at hudson.util.Pl
[JIRA] (JENKINS-39837) scm: Browser isn't set to GithubWeb
Title: Message Title Stephen Connolly updated JENKINS-39837 Jenkins / JENKINS-39837 scm: Browser isn't set to GithubWeb Change By: Stephen Connolly Status: In Progress Review 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-39837) scm: Browser isn't set to GithubWeb
Title: Message Title Stephen Connolly started work on JENKINS-39837 Change By: Stephen Connolly 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-39837) scm: Browser isn't set to GithubWeb
Title: Message Title Stephen Connolly assigned an issue to Stephen Connolly Jenkins / JENKINS-39837 scm: Browser isn't set to GithubWeb Change By: Stephen Connolly Assignee: Kohsuke Kawaguchi Stephen Connolly 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-39837) scm: Browser isn't set to GithubWeb
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-39837 scm: Browser isn't set to GithubWeb Change By: Stephen Connolly Component/s: github-branch-source-plugin Component/s: github-organization-folder-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-39616) Discard old items strategy - not working
Title: Message Title Stephen Connolly closed an issue as Not A Defect Jenkins / JENKINS-39616 Discard old items strategy - not working Change By: Stephen Connolly Status: Reopened Closed 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-39285) Add options to display the pull request title
Title: Message Title Stephen Connolly resolved as Fixed In GitHub Branch Source 2.0.x the PR title is available as a tool-tip, see the screenshot in https://github.com/jenkinsci/branch-api-plugin/pull/69 Jenkins / JENKINS-39285 Add options to display the pull request title Change By: Stephen Connolly 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 jenki
[JIRA] (JENKINS-41014) Input step not refreshed after input is accepted.
Title: Message Title Thorsten Scherler started work on JENKINS-41014 Change By: Thorsten Scherler 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-41009) [Declarative Pipeline] Stage view displays un-executed stages as success
Title: Message Title Baptiste Mathus edited a comment on JENKINS-41009 Re: [Declarative Pipeline] Stage view displays un-executed stages as success And https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/88, though does not fix fixing the visual _wrongness_ _weirdness_ , should clarify this a bit. Thanks Andrew for that again 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-41009) [Declarative Pipeline] Stage view displays un-executed stages as success
Title: Message Title Baptiste Mathus commented on JENKINS-41009 Re: [Declarative Pipeline] Stage view displays un-executed stages as success And https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/88, though does not fix the visual wrongness, should clarify this a bit. Thanks Andrew for that again 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-34367) Add support for empty sendTo field for extendedEmail plugin
Title: Message Title Daniel Spilker commented on JENKINS-34367 Re: Add support for empty sendTo field for extendedEmail plugin Edgar Yu are you working on this? I would like to close this as "Won't Fix" as suggested by Tom Reichelt. 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-40876) ObjectMetadataAction objectUrl never gets populated for PRs or Branches
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40876 Re: ObjectMetadataAction objectUrl never gets populated for PRs or Branches Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/branch/ItemColumn.java src/main/resources/jenkins/branch/ItemColumn/column.jelly http://jenkins-ci.org/commit/branch-api-plugin/99647e920bbee58a30fcc50ae0bf869a0195d908 Log: Merge pull request #69 from stephenc/jenkins-40876 JENKINS-40876 Fixes to display of object metadata Compare: https://github.com/jenkinsci/branch-api-plugin/compare/d55f2b4369e0...99647e920bbe 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-40876) ObjectMetadataAction objectUrl never gets populated for PRs or Branches
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40876 Re: ObjectMetadataAction objectUrl never gets populated for PRs or Branches Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/branch/ItemColumn.java src/main/resources/jenkins/branch/ItemColumn/column.jelly http://jenkins-ci.org/commit/branch-api-plugin/982d7e1171d61c704dcf013936c0f89c0b871691 Log: JENKINS-40876 Fixes to display of object metadata < /td> 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-39114) Comparing repo owner in webhook with SCM source should be case-insensitive
Title: Message Title Stephen Connolly updated JENKINS-39114 Jenkins / JENKINS-39114 Comparing repo owner in webhook with SCM source should be case-insensitive Change By: Stephen Connolly Status: In Progress Review 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-39114) Comparing repo owner in webhook with SCM source should be case-insensitive
Title: Message Title Stephen Connolly assigned an issue to Stephen Connolly Jenkins / JENKINS-39114 Comparing repo owner in webhook with SCM source should be case-insensitive Change By: Stephen Connolly Assignee: Stephen Connolly 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-39114) Comparing repo owner in webhook with SCM source should be case-insensitive
Title: Message Title Stephen Connolly started work on JENKINS-39114 Change By: Stephen Connolly 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-40833) Report primary branch
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40833 Re: Report primary branch Code changed in jenkins User: Stephen Connolly Path: src/test/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSourceTest.java http://jenkins-ci.org/commit/github-branch-source-plugin/0f11bca98e5f3ec14cd41bb728637748faa10ffc Log: JENKINS-40833 Fix test 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-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title
squalou jenkins commented on JENKINS-37584
Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Update using 2.32.1, p4 plugin 1.4.12, all on a windows laptop, fresh install, still doesn't work here's the pipeline snippet and the output
node('master'){
println env.P4_CHANGELIST
def populateClassName = 'SyncOnlyImpl'
def p4ws='squalou-test-hell'
def viewMapping='''//depot/project/pom.xml //squalou-test-hell/project/pom.xml'''
checkout([$class: 'PerforceScm', credential: 'PERFORCE-READONLY',
populate: [$class: populateClassName, have: false, quiet: true],
workspace: [
$class: 'ManualWorkspaceImpl',
name: p4ws,
spec: [view: viewMapping]
]
])
println env.P4_CHANGELIST
}
output
Running on master in C:\Users\squalou\.jenkins\workspace\p4Hell
[Pipeline] {
[Pipeline] echo
null
[Pipeline] checkout
... p4 client -o squalou-test-hell
+
... p4 info
+
... p4 client -o squalou-test-hell
+
... p4 client -i
+
... client: squalou-test-hell
... p4 client -o squalou-test-hell
+
... p4 info
+
... p4 counter change
+
... p4 changes -m1 -ssubmitted //squalou-test-hell/...
+
Change 3832207 on 2017/01/06 by someone@something ' tadada'
Building on Node: master
... p4 client -o squalou-test-hell
+
... p4 info
+
P4 Task: establishing connection.
... server: perforce:1666
... node: SQUALOU
P4 Task: syncing files at change: 3832207
... p4 sync -p -q C:\Users\squalou\.jenkins\workspace\p4Hell/...@3832207
+
duration: (209ms)
P4 Task: saving built changes.
Found last change 3832207 on syncID squalou-test-hell
... p4 client -o squalou-test-hell
+
... p4 info
+
... p4 client -o squalou-test-hell
+
... p4 info
+
... done
[Pipeline] echo
null
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Add Comment
[JIRA] (JENKINS-40487) OPTIMIZATION: Pre-load Run data on fresh load of the Run Details
Title: Message Title Tom FENNELLY updated JENKINS-40487 Jenkins / JENKINS-40487 OPTIMIZATION: Pre-load Run data on fresh load of the Run Details Change By: Tom FENNELLY Status: In Review 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-40933) Optimize cold load time by concatinating common JS files
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-40933 Optimize cold load time by concatinating common JS files Change By: Tom FENNELLY Priority: Major Minor 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-41024) Cannot provision new nodes with OpenStack plugin
Title: Message Title
Steve Mason updated an issue
Jenkins / JENKINS-41024
Cannot provision new nodes with OpenStack plugin
Change By:
Steve Mason
I see this error when trying to provision a new VM:{{ code}} javax.servlet.ServletException: java.lang.NoSuchMethodError: jenkins.plugins.openstack.compute.UserDataConfig$UserDataConfigProvider.getConfigById(Ljava/lang/String;)Lorg/jenkinsci/lib/configprovider/model/Config; at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:236) 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 hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilte
[JIRA] (JENKINS-41024) Cannot provision new nodes with OpenStack plugin
Title: Message Title Steve Mason created an issue Jenkins / JENKINS-41024 Cannot provision new nodes with OpenStack plugin Issue Type: Bug Assignee: Oliver Gondža Components: openstack-cloud-plugin Created: 2017/Jan/12 11:12 AM Priority: Major Reporter: Steve Mason I see this error when trying to provision a new VM: code javax.servlet.ServletException: java.lang.NoSuchMethodError: jenkins.plugins.openstack.compute.UserDataConfig$UserDataConfigProvider.getConfigById(Ljava/lang/String;)Lorg/jenkinsci/lib/configprovider/model/Config; at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:236) 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 hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Tom FENNELLY commented on JENKINS-39794 Re: API to check that MBP indexing has completed Experiments under way with Cliff. Waiting for feedback on https://github.com/jenkinsci/blueocean-plugin/pull/700 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-41024) Cannot provision new nodes with OpenStack plugin
Title: Message Title
Steve Mason updated an issue
Jenkins / JENKINS-41024
Cannot provision new nodes with OpenStack plugin
Change By:
Steve Mason
I see this error when trying to provision a new VM:{{javax.servlet.ServletException: java.lang.NoSuchMethodError: jenkins.plugins.openstack.compute.UserDataConfig$UserDataConfigProvider.getConfigById(Ljava/lang/String;)Lorg/jenkinsci/lib/configprovider/model/Config; at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:236) 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 hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(Chaine
[JIRA] (JENKINS-41025) 'GitLab commit status publisher' causes unreadable project configuration
Title: Message Title Marti R. created an issue Jenkins / JENKINS-41025 'GitLab commit status publisher' causes unreadable project configuration Issue Type: Bug Assignee: Javier Palacios Components: gitlab-hook-plugin Created: 2017/Jan/12 11:13 AM Environment: Jenkins ver. 2.32.1 ruby-runtime 0.13 gitlab-hook 1.4.2 java version "1.8.0_112" Java(TM) SE Runtime Environment (build 1.8.0_112-b15) Java HotSpot(TM) 64-Bit Server VM (build 25.112-b15, mixed mode) Priority: Minor Reporter: Marti R. Whenever I add the "GitLab commit status publisher" post-build action to my freestyle project and restart Jenkins, on the next startup Jenkins complains "You have data stored in an older format and/or unreadable data". This fragment is added to the project config.xml: "Jenkins::Tasks::PublisherProxy" pluginid="gitlab-hook"> "GitlabNotifier" pluginid="gitlab-hook"/> "gitlab-hook" ruby-class="String">gitlab-hook The "Manage Old Data" screen says: Type: hudson.model.FreeStyleProject Name: semic-test Error: NoSuchMethodError: org.jruby.RubyClass.getVariableAccessorForWrite(Ljava/lang/String;)Lorg/jruby/RubyClass$VariableAccessor;, CannotResolveClassException: pluginid, InstantiationError: null
[JIRA] (JENKINS-41024) Cannot provision new nodes with OpenStack plugin
Title: Message Title Oliver Gondža started work on JENKINS-41024 Change By: Oliver Gondža 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-41024) Cannot provision new nodes with OpenStack plugin
Title: Message Title Oliver Gondža commented on JENKINS-41024 Re: Cannot provision new nodes with OpenStack plugin This is known problem with compatibility breakage in config-file-provider 2.14+. We are working on a fix so openstack-cloud would support the latest version. Meanwhile, it is necessary to downgrade the config-file-provider to 2.13 or older but it will not load your saved config files any longer. 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-40722) Poll SCM results in a Pipeline run every interval (unnecessarily)
Title: Message Title Daniel Beck commented on JENKINS-40722 Re: Poll SCM results in a Pipeline run every interval (unnecessarily) Besides making no sense, is this documented anywhere? 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-41024) Cannot provision new nodes with OpenStack plugin
Title: Message Title Oliver Gondža started work on JENKINS-41024 Change By: Oliver Gondža 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-41024) Cannot provision new nodes with OpenStack plugin
Title: Message Title Oliver Gondža stopped work on JENKINS-41024 Change By: Oliver Gondža 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-37854) Docker Build and Publish not building
Title: Message Title Lucas Chigami edited a comment on JENKINS-37854 Re: Docker Build and Publish not building I'm having the same problem with my Jenkins server. Running the WAR inside a Tomcat8 server.UPDATE: In my case, the problem was an archive located at /usr/share/tomcat8 named .dockercfgI don't know why, but when the credentials were inserted in the job at Jenkins to upload the docker image to my self-hosted Registry service, this file was always blank. So I deleted this file, ran again the Jenkins job, and voila, success! 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-39112) Move GitHubLibraryResolver to its own plugin
Title: Message Title Stephen Connolly updated JENKINS-39112 Jenkins / JENKINS-39112 Move GitHubLibraryResolver to its own plugin Change By: Stephen Connolly Status: In Review 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-41026) Jenkins failed to connect to GIT repository
Title: Message Title Nithan Ramegowda created an issue Jenkins / JENKINS-41026 Jenkins failed to connect to GIT repository Issue Type: Bug Assignee: Kirill Merkushev Attachments: Selection_039.png, Selection_040.png Components: github-plugin, jenkins-tracker Created: 2017/Jan/12 11:20 AM Labels: git-plugin jenkins2.0 eclipse Priority: Blocker Reporter: Nithan Ramegowda When i am creating new item in jenkins, if i put repository url as "g...@github.com:Nithanjr/Nithan_JR_coding.git" getting error. Please help me to create new projects in jenkins. Error - Failed to connect to repository : Error performing command: git ls-remote -h g...@github.com:Nithanjr/Nithan_JR_coding.git HEAD Add Comment
[JIRA] (JENKINS-39082) Record the "default branch" of the Github repository
Title: Message Title Stephen Connolly closed an issue as Duplicate Jenkins / JENKINS-39082 Record the "default branch" of the Github repository Change By: Stephen Connolly Status: Open Closed 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 more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41027) File input parameter to HTTP PUT task
Title: Message Title Rudi Minty created an issue Jenkins / JENKINS-41027 File input parameter to HTTP PUT task Issue Type: New Feature Assignee: Janario Oliveira Components: http-request-plugin Created: 2017/Jan/12 11:22 AM Environment: jenkins - 2.7.1 http-request-plugin - 1.8.13 Labels: file-parameter http Priority: Minor Reporter: Rudi Minty In the "Advanced / Body" section of the HTTP Request step, add an option to specify a file name to send as the body of a PUT request. Add Comment
[JIRA] (JENKINS-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title Paul Allen commented on JENKINS-37584 Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline) Try removing the first println env.P4_CHANGELIST as this is defining a 'null' entry, before the variable is used and the environment is not overriding it. This looks like a Jenkins Core bug as I just extend the environment. 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-39346) Cryptic serialization error when SimpleBuildWrapper throws AbortException in pipeline
Title: Message Title Hans Bogaards commented on JENKINS-39346 Re: Cryptic serialization error when SimpleBuildWrapper throws AbortException in pipeline How can this be a duplicate of a closed bug if it still doesn't work with the latest versions of Jenkins and all plugins? Or is this actually a Sonar plugin bug? 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-41024) Cannot provision new nodes with OpenStack plugin
Title: Message Title Steve Mason commented on JENKINS-41024 Re: Cannot provision new nodes with OpenStack plugin Ah I see - it looks like there's progress on https://github.com/jenkinsci/openstack-cloud-plugin/pull/121 so I'll hold on for a new version (I don't like the sound of losing my configs) 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-41028) Simple way to switch between marker file's enabled pipeline and existing Jenkinsfile from source
Title: Message Title
Baptiste Mathus created an issue
Jenkins / JENKINS-41028
Simple way to switch between marker file's enabled pipeline and existing Jenkinsfile from source
Issue Type:
Bug
Assignee:
Unassigned
Components:
github-branch-source-plugin
Created:
2017/Jan/12 12:16 PM
Priority:
Minor
Reporter:
Baptiste Mathus
As a developer, I would like to be able to define a default Pipeline, but have a simple way to use existing Jenkinsfile if found in the repository. Right now, to do that, one has to script the switch in the default Pipeline, like :
echo "Checking Jenkinsfile existence"
try {
def jenkinsFile = readTrusted 'Jenkinsfile'
echo "Existing Jenkinsfile found, using it instead of the default one!"
evaluate jenkinsfile
return
} catch (e) {
echo "No Jenkinsfile found, using default behaviour"
}
// here follows the default pipeline
It would be great to be able to just click a checkbox in the config to achieve that. Note: this should probably be opt-in, not opt-out. As one generally wants standard things when enabling this, so allowing to use something different must be a conscious choice.
[JIRA] (JENKINS-40969) java.lang.NoSuchMethodError on hitting TestConnection
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40969 Re: java.lang.NoSuchMethodError on hitting TestConnection Code changed in jenkins User: parvathy-g Path: pom.xml http://jenkins-ci.org/commit/docker-build-step-plugin/208ef9c9a85af03ef9bb281efbb9f6b670242242 Log: Update pom.xml To introduce httpclient-4.5.2 . ISSUE NO JENKINS-40969 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-28466) Can't use environment variables like JENKINS_URL、JOB_URL、BUILD_URL in a new jenkins before it's save-button which is in system settings is clicked
Title: Message Title Barry Laffoy commented on JENKINS-28466 Re: Can't use environment variables like JENKINS_URL、JOB_URL、BUILD_URL in a new jenkins before it's save-button which is in system settings is clicked I'm also affected by this bug while trying to set up a Jenkins instance for development, testing, and acceptance testing. While using the official jenkinsci/docker image, the Jenkins instance in my container has a value visible at the page myjenkins.mycompany.com:8080/configure under "Jenkins Location" -> "Jenkins URL" of http://myjenkins.mycompany.com:8080. This value is present immediately after provisioning the container. However, this value is not accessible to jobs unless you first open that page and click save. Creating `jenkins.model.JenkinsLocationConfiguration.xml` as part of the provisioning of the instance is an acceptable workaround. But it is a workaround to a bug. I'm baffled as to how anyone would say that this is not a bug. 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-41029) Promotions aren't copies when job generated with DSL
Title: Message Title
Elad Shmitanka created an issue
Jenkins / JENKINS-41029
Promotions aren't copies when job generated with DSL
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin, promoted-builds-plugin
Created:
2017/Jan/12 12:26 PM
Environment:
Jenkins 2.40 Promoted Build Plugin version: 2.28
Priority:
Major
Reporter:
Elad Shmitanka
Sample DSL:
freeStyleJob('test1') {
properties {
promotions {
promotion {
name('promotion 1')
icon('Silver white star')
conditions {
manual('admin')
}
actions {
shell "echo test"
}
}
}
}
}
freeStyleJob('test2') {
using('test1')
}
test1 is built fine XML for test2:
"1.0" encoding="UTF-8"?>
false
"promoted-builds@2.28">
promotion 1
"hudson.scm.NullSCM"/>
true
false
false
false
false
however, no promotions:
# ls test2/prom
[JIRA] (JENKINS-28466) Can't use environment variables like JENKINS_URL、JOB_URL、BUILD_URL in a new jenkins before it's save-button which is in system settings is clicked
Title: Message Title Daniel Beck commented on JENKINS-28466 Re: Can't use environment variables like JENKINS_URL、JOB_URL、BUILD_URL in a new jenkins before it's save-button which is in system settings is clicked This value is present immediately after provisioning the container. … and it's based on the request URL that is only available in the context of a request. If Jenkins is running on a different port, or you access it with a different host name, those would be reflected here. You opening the config page: In an HTTP request context. A build running: Not in an HTTP request context. So your argument based on this form value doesn't make sense. FWIW just setting 'localhost:8080' as the default would be wrong for pretty much all deployments to production, and not allow the automatism of filling the Configure System form field with a real default. 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-38718) Add an extension point so github et al can expose their default branches via scm api
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-38718 Add an extension point so github et al can expose their default branches via scm api Change By: Stephen Connolly Component/s: blueocean-plugin Component/s: scm-api-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-41030) Add input "Abort" button on input form too
Title: Message Title Tom FENNELLY created an issue Jenkins / JENKINS-41030 Add input "Abort" button on input form too Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2017/Jan/12 12:36 PM Labels: usability Priority: Minor Reporter: Tom FENNELLY There is a small abort button/icon at the top level on the run itself, on the activity row. There's no abort option once you go down to the input form and that can be confusing for people new to the feature (as it was for me - TF). Please add an "Abort" button on the input form too (beside the "Proceed" button). Add Comment
[JIRA] (JENKINS-38348) GitHub API errors result in jobs being incorrectly deleted
Title: Message Title Stephen Connolly resolved as Won't Fix This was an issue in the GitHub Org Folders plugin because it was not assigning persistent source IDs. The GitHub Org Folders functionality has been moved to GitHub Branch Source starting from 2.0.x of GH-Branch Source and the GitHub Org Folders plugin is being tombstoned Please re-open this issue against GitHub Branch Source if this is not resolved by GitHub Branch Source 2.0.0 Closing this issue as Won't Fix because we will not be fixing in GitHub Org Folders, rather we are killing off GitHub Org Folders Jenkins / JENKINS-38348 GitHub API errors result in jobs being incorrectly deleted Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38212) We should only get the Jenkinsfile from github, not the whole repository
Title: Message Title Stephen Connolly closed an issue as Duplicate Jenkins / JENKINS-38212 We should only get the Jenkinsfile from github, not the whole repository Change By: Stephen Connolly Status: Open Closed 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 more options, visit https://groups.google.com/d/optout.
