[JIRA] (JENKINS-60118) Jenkins Telemetry initializer runs too early in the initialization cycle
Title: Message Title Freddy AN commented on JENKINS-60118 Re: Jenkins Telemetry initializer runs too early in the initialization cycle WARNING: 20-Mar-2020 14:12:02.085 INFO [pool-6-thread-3] jenkins.InitReactorRunner$1.onAttained Started initialization20-Mar-2020 14:12:02.094 WARNING [UserLanguages.setUpFilter] hudson.util.PluginServletFilter.addFilter Filter instance is registered too early: jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter@2a java.lang.Exception at hudson.util.PluginServletFilter.addFilter(PluginServletFilter.java:108) at jenkins.telemetry.impl.UserLanguages.setUpFilter(UserLanguages.java:102) 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 hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1122) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)20-Mar-2020 14:12:02.145 INFO [pool-6-thread-2] jenkins.InitReactorRunner$1.onAttained Listed all plugins20-Mar-2020 14:12:03.791 INFO [pool-6-thread-1] jenkins.InitReactorRunner$1.onAttained Prepared all plugins20-Mar-2020 14:12:03.801 INFO [pool-6-thread-1] jenkins.InitReactorRunner$1.onAttained Started all plugins20-Mar-2020 14:12:03.831 INFO [pool-6-thread-2] jenkins.InitReactorRunner$1.onAttained Augmented all extensions20-Mar-2020 14:12:03.845 WARNING [ResourceDomainFilter.init] hudson.util.PluginServletFilter.addFilter Filter instance is registered too early: jenkins.security.ResourceDomainFilter@389c25af java.lang.Exception at hudson.util.PluginServletFilter.addFilter(PluginServletFilter.java:108) at jenkins.security.ResourceDomainFilter.init(ResourceDomainFilter.java:57) 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 hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1122) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) INSTALL ENV： [root@jenkins bin]# hostnamectl Static hostname: localhost.localdomainTransient hostname: jenkins Icon name: computer-vm Chassis: vm Machine ID: f4f19ddef3584e6691a83b8f5f5c3de3 Boot ID: d8e5e1006bb44dc5aaa357d5ad30a9d3 Virtualization: vmware Operating System: CentOS Linux 7 (Core) CPE OS Name: cpe:/o:centos:centos:7 Kernel: Linux 3.10.0-327.10.1.el7.x86_64 Architecture: x86-64[root@jenkins bin]# java -versionjava version "1.8.0_241"Java(TM) SE Runtime Environment (build 1.8.0_241-b07)Java HotSpot(TM) 64-Bit Ser
[JIRA] (JENKINS-60118) Jenkins Telemetry initializer runs too early in the initialization cycle
Title: Message Title Freddy AN edited a comment on JENKINS-60118 Re: Jenkins Telemetry initializer runs too early in the initialization cycle * WARNING * :20-Mar-2020 14:12:02.085 INFO [pool-6-thread-3] jenkins.InitReactorRunner$1.onAttained Started initialization20 initialization20 -Mar-2020 14:12:02.094 WARNING [UserLanguages.setUpFilter] hudson.util.PluginServletFilter.addFilter Filter instance is registered too early: jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter@2a java.lang.Exception at hudson.util.PluginServletFilter.addFilter(PluginServletFilter.java:108) at jenkins.telemetry.impl.UserLanguages.setUpFilter(UserLanguages.java:102) 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 hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1122) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) 20-Mar-2020 14:12:02.145 INFO [pool-6-thread-2] jenkins.InitReactorRunner$1.onAttained Listed all plugins20 plugins20 -Mar-2020 14:12:03.791 INFO [pool-6-thread-1] jenkins.InitReactorRunner$1.onAttained Prepared all plugins20 plugins20 -Mar-2020 14:12:03.801 INFO [pool-6-thread-1] jenkins.InitReactorRunner$1.onAttained Started all plugins20 plugins20 -Mar-2020 14:12:03.831 INFO [pool-6-thread-2] jenkins.InitReactorRunner$1.onAttained Augmented all extensions20 extensions20 -Mar-2020 14:12:03.845 WARNING [ResourceDomainFilter.init] hudson.util.PluginServletFilter.addFilter Filter instance is registered too early: jenkins.security.ResourceDomainFilter@389c25af java.lang.Exception at hudson.util.PluginServletFilter.addFilter(PluginServletFilter.java:108) at jenkins.security.ResourceDomainFilter.init(ResourceDomainFilter.java:57) 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 hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1122) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) * INSTALL ENV * ：[root@jenkins bin]# hostnamectl Static hostname: localhost. localdomainTransient localdomainTransient hostname: jenkins Icon na
[JIRA] (JENKINS-61598) Coloring leaks over non script related lines
Title: Message Title
Raihaan Shouhell created an issue
Jenkins / JENKINS-61598
Coloring leaks over non script related lines
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
image-2020-03-20-15-47-43-973.png, image-2020-03-20-16-04-29-103.png
Components:
ansicolor-plugin
Created:
2020-03-20 08:04
Environment:
ansi color 0.6.3 jenkins 2.176.2
Priority:
Minor
Reporter:
Raihaan Shouhell
Line colouring bleeds to unrelated lines Reproducible example:
node('linux') {
wrap([$class: 'AnsiColorBuildWrapper', 'colorMapName': 'XTerm']) {
sh "echo -e \"\\e[33mYellow words, white background.\""
sh "echo -e \"\\e[35mMagenta words, white background.\""
}
}
Gives the outputOlder versions give the output (0.5.3)
[JIRA] (JENKINS-61587) don't create remote directory when there are no files to publish
Title: Message Title
Jimmy Praet commented on JENKINS-61587
Re: don't create remote directory when there are no files to publish
As a workaround I added execCommand: "rmdir -p --ignore-fail-on-non-empty ${remoteDirectory}"
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205284.1584626952000.9885.1584696960056%40Atlassian.JIRA.
[JIRA] (JENKINS-61521) "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11
Title: Message Title CloudBees Foundation Security commented on JENKINS-61521 Re: "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11 K Z Why did you put back the ticket to in progress status? Thanks Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205218.1584602993000.9888.1584697320198%40Atlassian.JIRA.
[JIRA] (JENKINS-61518) update notice odd spacing before closing parenthesis
Title: Message Title Félix Queiruga Balado commented on JENKINS-61518 Re: update notice odd spacing before closing parenthesis The issue comes from the fact that the HTML code for the monitors popup is located within the header and the .page-headerhyperlinks div. I already needed to make a hack so that the header styles would not apply here (https://github.com/jenkinsci/jenkins/blob/144550b2fc4ef59ce1af0abe4dace9e4fe394c89/core/src/main/resources/jenkins/management/AdministrativeMonitorsDecorator/resources.css#L92). A solution would come from resetting the margin there as well. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205214.158457919.9891.1584697620199%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Steven Gardell edited a comment on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script This same behavior is seen with scripted pipelines and it can be worked around - with increased pain as the functional complexity of a pipeline grows. Does anyone have any insight as to whether this is a core groovy or java limitation? Rather than spending a ton of time working around this it would be really nice just to make the limit 10 times as big... It would also be helpful to have a little more insight into the contributors to this. For example jenkins scripts, whether declarative or pipeline, often have substantial blocks of text directly scripting the node (e.g. bash or whatever). Does the size of such scripting reflect directly on groovy code size or are each of these treated as an opaque data blob who's size doesn't matter? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.9894.1584698221883%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Steven Gardell edited a comment on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script This same behavior is seen with scripted pipelines and it can be worked around - with increased pain as the functional complexity of a pipeline grows. Does anyone have any insight as to whether Apparently this is due to a core groovy or java jvm limitation ? of 64K methods on compiled byte-code. Which is unfortunate in a code-generation world. Rather than spending a ton of time working around this it would be really nice just to make the limit 10 times as big...It would also be helpful to have a little more insight into the contributors to this. For example jenkins scripts, whether declarative or pipeline, often have substantial blocks of text directly scripting the node (e.g. bash or whatever). Does the size of such scripting reflect directly on groovy /java code size or are each of these treated as an opaque data blob who's size doesn't really matter? Is there some logging that enables me to see the current 'method size?'One does have to wonder. Is groovy really the proper vehicle for defining pipelines then? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgi
[JIRA] (JENKINS-57736) SiteMonitor jobs fail if not re-saved after latest update
Title: Message Title Tapio Reijonen commented on JENKINS-57736 Re: SiteMonitor jobs fail if not re-saved after latest update Any update. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199680.155913035.10070.1584699360210%40Atlassian.JIRA.
[JIRA] (JENKINS-61599) Git Repository not saved in configure
Title: Message Title Srinivas K created an issue Jenkins / JENKINS-61599 Git Repository not saved in configure Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2020-03-20 11:30 Environment: Jenkkins Version- 2.224, git plugin version-4.1.1, ubuntu Priority: Major Reporter: Srinivas K i have a question regarding Jenkins configure of job. When i provide git repository url in source code management and save then if i open configure, there will be no git repo url was saved, it shows empty and asking to enter git repository again. someone help to fix the issue. Add Comment
[JIRA] (JENKINS-61600) Stop using shaded snakeyaml from configuration-as-code plugin
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-61600 Stop using shaded snakeyaml from configuration-as-code plugin Issue Type: Task Assignee: Stefan Wolf Components: gradle-plugin Created: 2020-03-20 11:56 Priority: Minor Reporter: Emilio Escobar Please consider using https://github.com/jenkinsci/snakeyaml-api-plugin instead of configuration-as-code snakeyaml module when code base version https://github.com/jenkinsci/gradle-plugin/blob/master/build.gradle#L27 is 2.204 or greater, Add Comment
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title Lakshmi Prasanna Damineni commented on JENKINS-61586 Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 Hi John, it is not passing Machine type credentials from job to Ansible tower Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205283.1584626324000.10097.1584705900161%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title Lakshmi Prasanna Damineni commented on JENKINS-61586 Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 can you please provide me the solution as soon as possible here the issue is critical Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205283.1584626324000.10099.1584706027938%40Atlassian.JIRA.
[JIRA] (JENKINS-61600) Stop using shaded snakeyaml from configuration-as-code plugin
Title: Message Title Tim Jacomb commented on JENKINS-61600 Re: Stop using shaded snakeyaml from configuration-as-code plugin Its more you shouldn't need to use snakeyaml directly in the test that's currently using it, just needs updating to a more recent method of verifying the export test: https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/docs/PLUGINS.md#model-export-test https://github.com/jenkinsci/gradle-plugin/blob/921f5c91ec573e0292cc1999b1dc8dc75b1adc87/src/test/groovy/hudson/plugins/gradle/ConfigurationAsCodeTest.groovy#L47 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205298.1584705382000.10102.1584706144339%40Atlassian.JIRA.
[JIRA] (JENKINS-61601) Unable to trigger job on deletion of branch when configured with job DSL.
Title: Message Title
Neha Singh created an issue
Jenkins / JENKINS-61601
Unable to trigger job on deletion of branch when configured with job DSL.
Issue Type:
Bug
Assignee:
Aytunc BEKEN
Components:
multibranch-action-triggers-plugin
Created:
2020-03-20 12:16
Environment:
multibranch-action-triggers@1.8
Priority:
Minor
Reporter:
Neha Singh
MultiBranch pipeline configured with job dsl , fails to trigger job on branch deletion with the multibranch-action-trigger-plugin, however with manual configuration it seems to be working fine intermittently. Job dsl
def job_path = "${new File(__FILE__).parent}"
def jenkinsfile = job_path + "/Jenkinsfile"
configFiles {
customConfig
{
id('feat_deploy')
name('feat_deploy')
comment('Used in the Deploy-Feature multibranch job.')
content(readFileFromWorkspace(jenkinsfile))
}
}
multibranchPipelineJob('Deploy-Feature') {
branchSources {
git {
id('123454321')
remote('g...@github.com:xyz/abc.git')
credentialsId('git-ssh-key')
includes('feat/*')
}
}
orphanedItemStrategy {
discardOldItems {
daysToKeep(0)
numToKeep(0)
}
}
factory {
pipelineBranchDefaultsProjectFactory {
scriptId('feat_deploy')
useSandbox(true)
}
}
properties{
pipelineTriggerProperty {
createActionJobsToTrigger('')
deleteActionJobsToTrigger('Remove-Feature')
}
}
triggers{
periodicFolderTrigger {
interval('5m') }
}
}
Failed to send event to listener warning in logs sometime.
[JIRA] (JENKINS-57351) Support for making Jenkins a "GitHub App"
Title: Message Title Jesse Glick updated JENKINS-57351 Jenkins / JENKINS-57351 Support for making Jenkins a "GitHub App" Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.6.1 or later Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199127.1557217283000.10119.1584708181536%40Atlassian.JIRA.
[JIRA] (JENKINS-57351) Support for making Jenkins a "GitHub App"
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-57351 Support for making Jenkins a "GitHub App" Change By: Jesse Glick Released As: 2. 6 7 . 1 or later 0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199127.1557217283000.10141.1584708541925%40Atlassian.JIRA.
[JIRA] (JENKINS-57351) Support for making Jenkins a "GitHub App"
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-57351 Support for making Jenkins a "GitHub App" Change By: Jesse Glick Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199127.1557217283000.10163.1584708542216%40Atlassian.JIRA.
[JIRA] (JENKINS-61597) FreeBSD OS version label is wrong in a FreeBSD jail
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61597 FreeBSD OS version label is wrong in a FreeBSD jail Change By: Mark Waite Labels: newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205294.1584676136000.10184.1584709380156%40Atlassian.JIRA.
[JIRA] (JENKINS-61597) FreeBSD OS version label is wrong in a FreeBSD jail
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61597 FreeBSD OS version label is wrong in a FreeBSD jail Change By: Mark Waite My FreeNAS 11.3.U1 server hosts a FreeNAS 10 based jail that runs a git server. The platformlabeler on that jail reports 11.3 (the kernel version) instead of 10 (the version of the operating system environment). It should report the version of utilities in the jail, not the version of the FreeBSD kernel that is hosting the jail.The platformlabeler should report the version of the utilities in the jail (FreeNAS 10 in this case) to be consistent with Docker containers. In a Docker container, the operating system is reported based on the utilities running the operating system (/etc/os-release), not based on the operating system hosting the container. Since most uses of a platform label tend to be connected to the versions of the utilities on the operating system rather than the kernel, users will prefer to have the generated labels match the utilities more than the kernel. When running on FreeBSD, the `freebsd-version` command should take precedence over the `uname` command when creating the operating system label. The `freebsd-version` command reports the jail version information, while `uname` reports kernel information. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61597) FreeBSD OS version label is wrong in a FreeBSD jail
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-61597
FreeBSD OS version label is wrong in a FreeBSD jail
Change By:
Mark Waite
My FreeNAS 11.3.U1 server hosts a FreeNAS 10 based jail that runs a git server. The platformlabeler on that jail reports 11.3 (the kernel version) instead of 10 (the version of the operating system environment). It should report the version of utilities in the jail, not the version of the FreeBSD kernel that is hosting the jail.The platformlabeler should report the version of the utilities in the jail (FreeNAS 10 in this case) to be consistent with Docker containers. In a Docker container, the operating system is reported based on the utilities running the operating system (/etc/os-release), not based on the operating system hosting the container. Since most uses of a platform label tend to be connected to the versions of the utilities on the operating system rather than the kernel, users will prefer to have the generated labels match the utilities more than the kernel.When running on FreeBSD, the ` {{ freebsd-version ` }} command should take precedence over the ` {{ uname ` }} command when creating the operating system label. The ` {{ freebsd-version ` }} command reports the jail version information, while ` {{ uname ` }} reports kernel information.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-60903) Include information about number of CPUs and memory in the node view
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-60903 Include information about number of CPUs and memory in the node view Change By: Mark Waite Assignee: lifeless Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204294.1580302479000.10193.1584709620284%40Atlassian.JIRA.
[JIRA] (JENKINS-61597) FreeBSD OS version label is wrong in a FreeBSD jail
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61597 FreeBSD OS version label is wrong in a FreeBSD jail Change By: Mark Waite Assignee: lifeless Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205294.1584676136000.10190.1584709620232%40Atlassian.JIRA.
[JIRA] (JENKINS-61597) FreeBSD OS version label is wrong in a FreeBSD jail
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61597 FreeBSD OS version label is wrong in a FreeBSD jail Change By: Mark Waite Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205294.1584676136000.10194.1584709740082%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott commented on JENKINS-61586 Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 Could you please provide more details as to what is happening? Are you getting an error back from the plugin? Is your playbook throwing an error? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205283.1584626324000.10196.1584710220148%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title Lakshmi Prasanna Damineni commented on JENKINS-61586 Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 Hi John, while I am trying to push machine type credentials from Jenkins job to ansible tower ,Credentials are not displaying in ansible tower job template.only I have this issue with machine type credentials . currently I am using ansible tower plugin version 0.10 and ansible tower version 3.6 while I am trying with ansible tower plugin version with 0.14.0 getting Java Null Pointer exception can you please help me to get out of this issue Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205283.1584626324000.10198.1584710880201%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title Lakshmi Prasanna Damineni assigned an issue to Lakshmi Prasanna Damineni Jenkins / JENKINS-61586 Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 Change By: Lakshmi Prasanna Damineni Assignee: John Westcott Lakshmi Prasanna Damineni Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205283.1584626324000.10200.1584710940107%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title Lakshmi Prasanna Damineni assigned an issue to John van der Kamp Jenkins / JENKINS-61586 Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 Change By: Lakshmi Prasanna Damineni Assignee: Lakshmi Prasanna Damineni John van der Kamp Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205283.1584626324000.10203.1584711000150%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title Lakshmi Prasanna Damineni assigned an issue to Lakshmi Prasanna Damineni Jenkins / JENKINS-61586 Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 Change By: Lakshmi Prasanna Damineni Assignee: John van der Kamp Lakshmi Prasanna Damineni Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205283.1584626324000.10205.1584711360164%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title Lakshmi Prasanna Damineni commented on JENKINS-61586 Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 Hi this comment by mistake assigned to me john can you please take look on it Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205283.1584626324000.10208.1584711420112%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title Lakshmi Prasanna Damineni assigned an issue to John Westcott Jenkins / JENKINS-61586 Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 Change By: Lakshmi Prasanna Damineni Assignee: Lakshmi Prasanna Damineni John Westcott Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205283.1584626324000.10210.1584711540120%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott commented on JENKINS-61586 Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 We want to be using the latest version of the plugin. Are you getting a stack trace along with the Null Pointer Exception? If so, can you send that along? Also, are you referencing the credential by ID or by name? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205283.1584626324000.10213.1584712380097%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title Lakshmi Prasanna Damineni commented on JENKINS-61586 Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 Hi John, we are referencing credential by name, while using latest version plugin I am getting below error java.lang.NullPointerException at org.jenkinsci.plugins.ansible_tower.util.TowerConnector.processCredentials(TowerConnector.java:518) at org.jenkinsci.plugins.ansible_tower.util.TowerConnector.submitTemplate(TowerConnector.java:564) at org.jenkinsci.plugins.ansible_tower.AnsibleTowerRunner.runJobTemplate(AnsibleTowerRunner.java:184) at org.jenkinsci.plugins.ansible_tower.AnsibleTowerStep$AnsibleTowerStepExecution.run(AnsibleTowerStep.java:266) at org.jenkinsci.plugins.ansible_tower.AnsibleTowerStep$AnsibleTowerStepExecution.run(AnsibleTowerStep.java:202) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Finished: FAILURE Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subsc
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title Lakshmi Prasanna Damineni commented on JENKINS-61586 Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 we are giving credentials in pipeline like below credential: 'nameofcredential' Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205283.1584626324000.10217.1584713220098%40Atlassian.JIRA.
[JIRA] (JENKINS-60143) Behavior SSH Checkout not working after Jenkins restart
Title: Message Title Vincent Letarouilly commented on JENKINS-60143 Re: Behavior SSH Checkout not working after Jenkins restart Hi, first of all: thanks for this awesome plugin ! Unfortunately I ran into the same problem. Jenkins version 2.226 Gitlab branch source plugin version 1.4.4 I found two workarounds: Save the configuration manually again (as Laurent Michenaud mentioned in the description) Triggered one of the branch by webhook Parichay Barpanda maybe this should be updated to Major priority ? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203004.1573562285000.10220.1584714720365%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott commented on JENKINS-61586 Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 Thanks for the stack trace, it looks like the plugin was unable to determine the version of Tower you are connecting to. Can you go to Jenkins => Manage Jenkins => Configure System. On this page find the Ansible Tower section and check the "Enable Debugging" option next to the Tower installation you are running. After thats enabled tail your Jenkins log file and run your Jenkins job again. In the log file you should see messages that begin with the string `[Ansible-Tower]` like: ``` [Ansible-Tower] Building GET request to https://10.0.1.24/api/v2/ping/ [Ansible-Tower] Forcing cert trust [Ansible-Tower] Request completed with (200) [Ansible-Tower] Ping page loaded [Ansible-Tower] Successfully got version 3.6.2 [Ansible-Tower] Connecting to Tower version: 3.6.2 ``` Please attach those first couple of lines so we can see if we are getting anything back. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205283.1584626324000.10225.1584715200118%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title Lakshmi Prasanna Damineni commented on JENKINS-61586 Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 I did all above steps but again I am getting below error java.lang.NullPointerException at org.jenkinsci.plugins.ansible_tower.util.TowerConnector.processCredentials(TowerConnector.java:518) at org.jenkinsci.plugins.ansible_tower.util.TowerConnector.submitTemplate(TowerConnector.java:564) at org.jenkinsci.plugins.ansible_tower.AnsibleTowerRunner.runJobTemplate(AnsibleTowerRunner.java:184) at org.jenkinsci.plugins.ansible_tower.AnsibleTowerStep$AnsibleTowerStepExecution.run(AnsibleTowerStep.java:266) at org.jenkinsci.plugins.ansible_tower.AnsibleTowerStep$AnsibleTowerStepExecution.run(AnsibleTowerStep.java:202) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Finished: FAILURE Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" grou
[JIRA] (JENKINS-61599) Git Repository not saved in configure
Title: Message Title Mark Waite updated JENKINS-61599 Jenkins / JENKINS-61599 Git Repository not saved in configure Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205297.1584703857000.10246.1584717720584%40Atlassian.JIRA.
[JIRA] (JENKINS-61599) Git Repository not saved in configure
Title: Message Title Mark Waite updated JENKINS-61599 Sorry that the regression in Jenkins 2.224 hit you. Refer to the Jenkins 2.224 changelog where it describes JENKINS-61398. The fix is to use Jenkins 2.225 or Jenkins 2.226. There are some nice user interface improvements in Jenkins 2.226 "Manage Jenkins" and in alerts. I recommend it for those who are running the weekly releases. If you are running a production server, you probably want the long term support releases instead. Jenkins / JENKINS-61599 Git Repository not saved in configure Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Duplicate Released As: Jenkins 2.225 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61602) Passing script parameters with "|" works on Linux but fails Windows
Title: Message Title
Dirk Heinrichs created an issue
Jenkins / JENKINS-61602
Passing script parameters with "|" works on Linux but fails Windows
Issue Type:
Bug
Assignee:
vjuranek
Components:
groovy-plugin
Created:
2020-03-20 15:26
Environment:
Windows
Priority:
Minor
Reporter:
Dirk Heinrichs
When executing a Groovy script build step, where one of the "Script parameters" arguments contains a "|", the Groovy build step fails. Sample Groovy script (for Groovy 3.x; comment out lines 2 and 3 for lower versions):
// Get dependencies
@GrabConfig(systemClassLoader=true)
@Grab('info.picocli:picocli-groovy:4.2.0')
// Import external modules
import groovy.cli.picocli.CliBuilder
// Parse command line options
def cli = new CliBuilder(name: 'theScript.groovy')
cli.h(type: Boolean, longOpt: 'help', usageHelp: true, required: false, 'Show usage information')
cli.r(type: String, longOpt: 'regex', required: true, args: 1, 'Regular _expression_ (required)')
def opts = cli.parse(args)
opts || System.exit(1)
if(opts.h) {
cli.usage()
System.exit(0)
}
println('Regex: ' + opts.r)
With "Script parameters" given as "-r foo|bar", this executes the script on Linux and thus prints
Regex: foo|bar
[JIRA] (JENKINS-61602) Passing script parameters with "|" works on Linux but fails Windows
Title: Message Title Dirk Heinrichs updated an issue Jenkins / JENKINS-61602 Passing script parameters with "|" works on Linux but fails Windows Change By: Dirk Heinrichs Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205301.158471799.10250.1584718020333%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title Lakshmi Prasanna Damineni commented on JENKINS-61586 Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 can you please tell the reason why the ansible tower plugin version 0.10 and 0.12 is not able to pass machine type of credentials to ansible tower, recently we upgraded ansible tower version after this we are facing this issue ,previously it is working with this plugin versions Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205283.1584626324000.10269.1584718620113%40Atlassian.JIRA.
[JIRA] (JENKINS-61216) NPE in git plugin building environment variables for node
Title: Message Title Mark Waite commented on JENKINS-61216 Re: NPE in git plugin building environment variables for node Harry Papaxenopoulos any further hints you can offer? I can't duplicate the problem. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204770.1582622477000.10280.1584720660165%40Atlassian.JIRA.
[JIRA] (JENKINS-61509) Release Notes field is not interpolating values from Variable
Title: Message Title Jose Salgado commented on JENKINS-61509 Re: Release Notes field is not interpolating values from Variable Just as you did Mez Pahlan the value is being pass in a shell script executed before Appcenter Step. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205204.1584544055000.10305.1584722640192%40Atlassian.JIRA.
[JIRA] (JENKINS-60899) Job DSL runs brefore Gitea servers are loaded
Title: Message Title Bryan Burke commented on JENKINS-60899 Re: Job DSL runs brefore Gitea servers are loaded This problem seems to affect other SCM providers as well, the Atlassian Bitbucket Server Integration plugin in my case. I documented a dirty workaround to inject the clone and browser URLs into the XML via the DSL configure block. See: JENKINS-61210 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204289.1580254872000.10342.1584727140290%40Atlassian.JIRA.
[JIRA] (JENKINS-60899) Job DSL runs brefore Gitea servers are loaded
Title: Message Title Bryan Burke edited a comment on JENKINS-60899 Re: Job DSL runs brefore Gitea servers are loaded This problem seems to affect other SCM providers as well, the Atlassian Bitbucket Server Integration plugin in my case. I documented a dirty workaround to inject the clone and browser URLs into the XML via the DSL configure block. See: JENKINS-61210 *Edit*: I'm not certain if the same workaround would work for multibranch pipelines. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204289.1580254872000.10346.1584727200239%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Jesse Glick updated JENKINS-61409 Jenkins / JENKINS-61409 Websocket connections crash if message size is greater than 64Kb Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205063.1583801943000.10358.1584728400698%40Atlassian.JIRA.
[JIRA] (JENKINS-61603) Handle Spot Instance Interruption
Title: Message Title Joe Hansche created an issue Jenkins / JENKINS-61603 Handle Spot Instance Interruption Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-03-20 18:28 Labels: feature-request Priority: Minor Reporter: Joe Hansche According to the Spot Instance documentation, the instance will be notified (best effort) approximately 2 minutes before terminating a spot instance. Currently when the spot instance is being terminated, it will simply interrupt any executing builds, leading to a build failure, and then we have to restart the build. Additionally, the slave's executors remain online during the 2-minute-warning period, so they are available to take new builds, even though it will be terminated imminently. By monitoring the instance-action metadata (or CloudWatch events), we can receive notice that AWS is about to terminate a spot instance, and let the master react by taking the remaining executors offline (i.e., similar to the "Mark this node temporarily offline" button in the node status screen). That will do two things: Give visual notice in the Jenkins UI, that a slave is intentionally going offline Prevents any additional jobs being scheduled on that slave, allowing the built-in scheduling to route it to another online host, or possibly bring up a new instance to take its place We can then add configuration options to the SlaveTemplate to forcefully abort (setting status=Result.ABORTED) an executing job when we get notified that the slave will be terminated, so that the build status can ref
[JIRA] (JENKINS-61604) Pipeline deadlock caused by fix for JENKINS-59083
Title: Message Title Devin Nusbaum created an issue Jenkins / JENKINS-61604 Pipeline deadlock caused by fix for JENKINS-59083 Issue Type: Bug Assignee: Devin Nusbaum Components: workflow-job-plugin Created: 2020-03-20 19:06 Labels: pipeline Priority: Minor Reporter: Devin Nusbaum The fix for JENKINS-59038 has been observed to cause deadlock in some cases. Here is one example. Thread one: "SupportPlugin periodic bundle generator: writing " id=967 (0x3c7) state=BLOCKED cpu=94% - waiting to lock <0x71879181> (a java.lang.Object) owned by "Jenkins initialization thread" id=36 (0x24) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getListener(WorkflowRun.java:217) at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$300(WorkflowRun.java:133) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.getListener(WorkflowRun.java:970) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$2.onSuccess(CpsFlowExecution.java:789) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$2.onSuccess(CpsFlowExecution.java:776) at org.jenkinsci.plugins.workflow.support.concurrent.Futures$1.run(Futures.java:150) at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253) at com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(ExecutionList.java:149) at com.google.common.util.concurrent.ExecutionList.add(ExecutionList.java:105) at com.google.common.util.concurrent.AbstractFuture.addListener(AbstractFuture.java:155) at org.jenkinsci.plugins.workflow.support.concurrent.Futures.a
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title
John Westcott commented on JENKINS-61586
Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
In Tower 3.5 they changed how credentials are passed through he API. The commit that tried to compensate for that was release as part of 0.14.0. https://github.com/jenkinsci/ansible-tower-plugin/commit/4f2dc4055519fc2c247897209af1a135bfe02864 So we want to be using the latest version of the plugin to get those changes. The NPE exception you sent me is related to this line of code: `this.towerVersion.is_greater_or_equal("3.5.0") ||` Which is telling me that the module was unsuccessful at getting the details about your version of Tower. Can you log into Tower as the same user that the Jenkins plugin is using and then navigate to /api/v2/ping and paste the results into this ticket? I do see an issue where the plugin does not "complain" if its unable to get a version from Tower. But the ping page should be open to all users of Tower so that really shouldn't happen.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205283.1584626324000.10367.1584731820227%40Atlassian.JIRA.
[JIRA] (JENKINS-61605) Files with SpotBugs warnings are copied to the build folder but files with FindBugs warnings are not found
Title: Message Title Basil Crow created an issue Jenkins / JENKINS-61605 Files with SpotBugs warnings are copied to the build folder but files with FindBugs warnings are not found Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-03-20 19:36 Environment: warnings-ng 8.1.0 analysis-core 1.96 analysis-model-api 8.0.1 Priority: Minor Reporter: Basil Crow Overview When using Gradle and the Warnings Next Generation Plugin, files with SpotBugs warnings are copied to the build folder but files with FindBugs warnings are not found. Steps to Reproduce I have created a minimal reproducible example (MRE) at basil/warnings-ng-reproducer. Run the Jenkinsfile there to reproduce the issue. Expected Results This is a bare-bones Gradle build with two subprojects: findbugs and spotbugs. Each subproject has a single Java file with warnings. The findbugs subproject has the Gradle FindBugs plugin enabled, while the spotbugs subproject has the Gradle SpotBugs plugin enabled. Gradle detects the same warnings in both subprojects. The expected results are for the Warnings Next Generation Plugin to copy the files with issues in both subprojects to the build folder. Actual Results When recording issues with the Warnings Next Generation Plugin, the following occurs: […] [FindBugs] Copying affected files to Jenkins' build folder '/var/jenkins_home/jobs/test/builds/1/files-with-issues' [FindBugs] -> 0 copied, 0 not in workspace, 3 not-found, 0 with I/O error […] [SpotBugs] Copying affected files to Jenkins' build folder '/var/jenkins_home/jobs/test/builds/1/files-with-issues' [Spot
[JIRA] (JENKINS-61605) Files with SpotBugs warnings are copied to the build folder but files with FindBugs warnings are not found
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-61605 Files with SpotBugs warnings are copied to the build folder but files with FindBugs warnings are not found Change By: Basil Crow Attachment: findbugs-spotbugs.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205305.158473299.10371.1584733200127%40Atlassian.JIRA.
[JIRA] (JENKINS-28010) Use Google Apps group for Authorization
Title: Message Title Jon Tancer commented on JENKINS-28010 Re: Use Google Apps group for Authorization Any updates on this ticket? It appears that someone opened a PR adding this functionality to the plugin back in January. https://github.com/jenkinsci/google-login-plugin/pull/18 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162209.142951271.10374.1584733320599%40Atlassian.JIRA.
[JIRA] (JENKINS-61606) Gracefully handle missing Jenkins root URL
Title: Message Title
Bryan Burke created an issue
Jenkins / JENKINS-61606
Gracefully handle missing Jenkins root URL
Issue Type:
Improvement
Assignee:
Kristy Hughes
Attachments:
stack-trace.txt
Components:
atlassian-bitbucket-server-integration-plugin, job-dsl-plugin
Created:
2020-03-20 19:50
Environment:
atlassian-bitbucket-server-integration Plugin Version: 1.1.0 job-dsl Plugin version: 1.77
Priority:
Minor
Reporter:
Bryan Burke
When testing out the new multibranch pipeline support in version 1.1.0 of the plugin, I discovered that creation of a multibranch pipeline job via Job DSL fails when the Jenkins root URL is not set. It seems that the plugin tries to register the webhook but does not catch the exception thrown when the Jenkins root URL is unset. Full stack trace: stack-trace.txt Here is the Job DSL for the multibranch pipeline:
multibranchPipelineJob('test') {
branchSources {
branchSource {
source {
BbS {
credentialsId('Build-User')
id('test')
mirrorName(null)
projectName('TEST')
repositoryName('test')
serverId('Bitbucket')
traits {
cleanBeforeCheckoutTrait {
extension {
deleteUntrackedNestedRepositories(true)
[JIRA] (JENKINS-61604) Pipeline deadlock caused by fix for JENKINS-59083
Title: Message Title Devin Nusbaum updated JENKINS-61604 Jenkins / JENKINS-61604 Pipeline deadlock caused by fix for JENKINS-59083 Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205304.1584731204000.10435.1584735060453%40Atlassian.JIRA.
[JIRA] (JENKINS-61605) Files with SpotBugs warnings are copied to the build folder but files with FindBugs warnings are not found
Title: Message Title Ulli Hafner edited a comment on JENKINS-61605 Re: Files with SpotBugs warnings are copied to the build folder but files with FindBugs warnings are not found Can you make create a diff of the two different XML files. I doubt that this is a problem in my plugin, as the same parser is used for both warnings. BTW: why are you using using both tools? FIndBugs is end-of-life and has been replaced by SpotBugs. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205305.158473299.10431.1584735060386%40Atlassian.JIRA.
[JIRA] (JENKINS-61605) Files with SpotBugs warnings are copied to the build folder but files with FindBugs warnings are not found
Title: Message Title Ulli Hafner edited a comment on JENKINS-61605 Re: Files with SpotBugs warnings are copied to the build folder but files with FindBugs warnings are not found Can you create a diff of the two different XML files . ? I doubt that this is a problem in my plugin, as the same parser is used for both warnings. BTW: why are you using using both tools? FIndBugs is end-of-life and has been replaced by SpotBugs. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205305.158473299.10433.1584735060413%40Atlassian.JIRA.
[JIRA] (JENKINS-61604) Pipeline deadlock caused by fix for JENKINS-59083
Title: Message Title Devin Nusbaum started work on JENKINS-61604 Change By: Devin Nusbaum Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205304.1584731204000.10434.1584735060435%40Atlassian.JIRA.
[JIRA] (JENKINS-61605) Files with SpotBugs warnings are copied to the build folder but files with FindBugs warnings are not found
Title: Message Title Ulli Hafner commented on JENKINS-61605 Re: Files with SpotBugs warnings are copied to the build folder but files with FindBugs warnings are not found Can you make a diff of the two different XML files. I doubt that this is a problem in my plugin, as the same parser is used for both warnings. BTW: why are you using using both tools? FIndBugs is end-of-life and has been replaced by SpotBugs. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205305.158473299.10429.1584735060360%40Atlassian.JIRA.
[JIRA] (JENKINS-61605) Files with SpotBugs warnings are copied to the build folder but files with FindBugs warnings are not found
Title: Message Title Basil Crow commented on JENKINS-61605 Re: Files with SpotBugs warnings are copied to the build folder but files with FindBugs warnings are not found Thank you for the quick reply! Can you create a diff of the two different XML files? Sorry, I don't have the time to investigate this further at present. But you should be able to easily reproduce the problem following the instructions I listed under "Steps to Reproduce", after which you should be able to compare the two different XML files. Let me know if I can provide any additional context. BTW: why are you using using both tools? FIndBugs is end-of-life and has been replaced by SpotBugs. Yes, I am aware that FindBugs is EOL. I used both tools in the example merely to illustrate that the problem is only reproducible when using FindBugs. I am maintaining a Jenkins setup that runs an application build that I don't maintain, and that build still uses FindBugs, so unfortunately I still need to be able to use Jenkins with FindBugs. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.
[JIRA] (JENKINS-61478) "Apply" (and similar) banners look really bad with larger header bar
Title: Message Title Félix Queiruga Balado updated an issue Jenkins / JENKINS-61478 "Apply" (and similar) banners look really bad with larger header bar Change By: Félix Queiruga Balado Attachment: Captura de pantalla 2020-03-20 a las 21.51.16.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205161.1584140786000.10440.1584737940222%40Atlassian.JIRA.
[JIRA] (JENKINS-61478) "Apply" (and similar) banners look really bad with larger header bar
Title: Message Title Félix Queiruga Balado commented on JENKINS-61478 Re: "Apply" (and similar) banners look really bad with larger header bar I found one more banner that should be updated as well: Go to the /user/admin/configure page Generate an API token Click the button to copy the API token to the clipboard Screenshot: Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205161.1584140786000.10443.1584738000218%40Atlassian.JIRA.
[JIRA] (JENKINS-61509) Release Notes field is not interpolating values from Variable
Title: Message Title Mez Pahlan updated an issue Jenkins / JENKINS-61509 Release Notes field is not interpolating values from Variable Change By: Mez Pahlan Attachment: test-configuration.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205204.1584544055000.10447.1584739560426%40Atlassian.JIRA.
[JIRA] (JENKINS-61509) Release Notes field is not interpolating values from Variable
Title: Message Title Mez Pahlan updated an issue Jenkins / JENKINS-61509 Release Notes field is not interpolating values from Variable Change By: Mez Pahlan Attachment: test-output.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205204.1584544055000.10449.1584739560452%40Atlassian.JIRA.
[JIRA] (JENKINS-61509) Release Notes field is not interpolating values from Variable
Title: Message Title Mez Pahlan commented on JENKINS-61509 Re: Release Notes field is not interpolating values from Variable OK well in that case you can't do that. Each shell script executes in its own environment. You can test this quickly like this to confirm: Given this configuration: This is the output: Notice that the first shell is able to read the environment variable but the second one is not. I suggest you migrate your job to a pipeline job which has built in support for passing environment variables or use the Stackoverflow link above for more help. Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205204.1584544055000.10453.1584739980567%40Atlassian.JIRA.
[JIRA] (JENKINS-61509) Release Notes field is not interpolating values from Variable
Title: Message Title Mez Pahlan closed an issue as Not A Defect Jenkins / JENKINS-61509 Release Notes field is not interpolating values from Variable Change By: Mez Pahlan Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205204.1584544055000.10455.1584739980595%40Atlassian.JIRA.
[JIRA] (JENKINS-60802) JCasC EC2 Plugin private key not working
Title: Message Title
Richard Pula commented on JENKINS-60802
Re: JCasC EC2 Plugin private key not working
I faced the same problem and it was because the remoteFS attribute was missing in my jenkins.yaml. Here an example:
- amazonEC2:
cloudName: "Slaves EC2"
privateKey: "${KEY}"
region: "eu-central-1"
templates:
- ami: "ami-0269d640534cbf7ea"
amiType:
unixData:
sshPort: "22"
remoteFS: ""
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204131.1579199521000.10459.1584740820223%40Atlassian.JIRA.
[JIRA] (JENKINS-7139) HtmlPublisher should be able to handle wildcard paths to find multiple html files
Title: Message Title siva krishna jampani commented on JENKINS-7139 Re: HtmlPublisher should be able to handle wildcard paths to find multiple html files How to pass report path dynamically? ex: target/reports//index.html How can I ignore currentdate in reports path while publishing in Jenkins? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.137236.1280999333000.10463.1584741060656%40Atlassian.JIRA.
[JIRA] (JENKINS-45916) Path is not getting set correctly in pipeline when there is a variable present
Title: Message Title
Ilguiz Latypov commented on JENKINS-45916
Re: Path is not getting set correctly in pipeline when there is a variable present
The environment clause appears to be ignored by plugins executing code such as the following,
EnvVars vars = build.getEnvironment(listener);
My current work-around is to define hard-coded default values for the pipeline "parameters", even for the agent "master" which runs on the same machine with the server...
agent {
label 'master'
}
parameters {
string(name: 'FORTIFY_HOME', defaultValue: "/MYTOOLDIR/fortify",
description: 'A work-around to the plugin using FORTIFY_HOME of the Jenkins server instead of that of the agent')
string(name: 'PATH', defaultValue:
"/MYTOOLDIR/fortify/bin:/usr/local/FOO/bin:/usr/local/openjdk-8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
description: 'A work-around to the plugin using PATH of the Jenkins server instead of that of the agent')
}
I wish Jenkins in general its plugins in particular gave precendence to the agent's environment. I did not try to find the exact API to fetch that in the context of the plugin running on the server but aiming the given "agent".
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61607) Make number of context lines in FullTextFingerprint configurable
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-61607 Make number of context lines in FullTextFingerprint configurable Issue Type: Improvement Assignee: Ulli Hafner Components: analysis-model, warnings-ng-plugin Created: 2020-03-20 22:00 Priority: Minor Reporter: Ulli Hafner Currently, fingerprinting of files in order to detect new warnings (see FullTextFingerprint) uses a constant of 3 lines above and below a warning (see FullTextFingerprint). It would be helpful to make this property configurable. Add Comment
[JIRA] (JENKINS-61607) Make number of context lines in FullTextFingerprint configurable
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-61607 Make number of context lines in FullTextFingerprint configurable Change By: Ulli Hafner Labels: help-wanted newbie-friendly Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205308.1584741649000.10499.1584741840056%40Atlassian.JIRA.
[JIRA] (JENKINS-61383) Current new messages detection mechanism is not working for simple line insertion in case of many similar adjacent warning
Title: Message Title Ulli Hafner commented on JENKINS-61383 Re: Current new messages detection mechanism is not working for simple line insertion in case of many similar adjacent warning I created JENKINS-61607 to track the improvement. 3) I did not understood your comment about diff. There are many diff tools. We currently use a python lib for diff, but as you mentioned git diff is very strong tool for diff and can be used as command line even if the source repository is not git, see https://stackoverflow.com/a/17194704 for example. Ah now I understand your idea. This is not possible since there is no previous code available! All we have is the source code of the current build (and the fingerprint hashes of the warnings before). Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205036.1583663669000.10501.1584742020109%40Atlassian.JIRA.
[JIRA] (JENKINS-45916) Path is not getting set correctly in pipeline when there is a variable present
Title: Message Title
Ilguiz Latypov edited a comment on JENKINS-45916
Re: Path is not getting set correctly in pipeline when there is a variable present
The environment clause appears to be ignored by plugins executing code such as the following,{code:groovy}EnvVars vars = build.getEnvironment(listener); {code}My current work-around is to define hard-coded default values for the pipeline "parameters", even for the agent "master" which runs on the same machine with the server. However, this breaks Jenkins server's own checkout of the project using Git from PATH . . {code:groovy}agent {label 'master'}parameters {string(name: 'FORTIFY_HOME', defaultValue: "/MYTOOLDIR/fortify", description: 'A work-around to the plugin using FORTIFY_HOME of the Jenkins server instead of that of the agent')string(name: 'PATH', defaultValue: "/MYTOOLDIR/fortify/bin:/usr/local/FOO/bin:/usr/local/openjdk-8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", description: 'A work-around to the plugin using PATH of the Jenkins server instead of that of the agent')}{code}I wish Jenkins in general its plugins in particular gave precendence to the agent's environment. I did not try to find the exact API to fetch that in the context of the plugin running on the server but aiming the given "agent".
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+u
[JIRA] (JENKINS-45916) Path is not getting set correctly in pipeline when there is a variable present
Title: Message Title
Ilguiz Latypov edited a comment on JENKINS-45916
Re: Path is not getting set correctly in pipeline when there is a variable present
The environment clause appears to be ignored by plugins executing code such as the following,{code:groovy}EnvVars vars = build.getEnvironment(listener); {code}My current work-around is to define hard-coded default values for the pipeline "parameters", even for the agent "master" which runs on the same machine with the server. However, this breaks (If Jenkins server 's needs to run its own checkout of , say, a pipeline library, then it will fail to use Git on the project server using Git from the agent-targeting PATH ) .{code:groovy}agent {label 'master'}parameters {string(name: 'FORTIFY_HOME', defaultValue: "/MYTOOLDIR/fortify", description: 'A work-around to the plugin using FORTIFY_HOME of the Jenkins server instead of that of the agent')string(name: 'PATH', defaultValue: "/MYTOOLDIR/fortify/bin:/usr/local/FOO/bin:/usr/local/openjdk-8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", description: 'A work-around to the plugin using PATH of the Jenkins server instead of that of the agent')}{code}I wish Jenkins in general its plugins in particular gave precendence to the agent's environment. I did not try to find the exact API to fetch that in the context of the plugin running on the server but aiming the given "agent".
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-61608) Latest version throws IllegalArgumentException: Git repository URL 2 is an empty string
Title: Message Title
luc neulens created an issue
Jenkins / JENKINS-61608
Latest version throws IllegalArgumentException: Git repository URL 2 is an empty string
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2020-03-20 22:34
Environment:
Jenkins 2.204.2 git plugin 4.2.2 RedHat 7 Java 8
Labels:
git-plugin
Priority:
Major
Reporter:
luc neulens
After upgrading the Git plugin version 4.1.1 to the latest version 4.2.2, following exception is being thrown during a clone:
java.lang.IllegalArgumentException: Git repository URL 2 is an empty string in job definition. Checkout requires a valid repository URL
In earlier versions below git configuration was working fine:
checkout(scm: [$class: 'GitSCM', userRemoteConfigs: [[url: "${gitURL}"], [name: "origin"]], branches: [[name: "${gitTag}"]]])
Above snippet is taken from a Jenkins Shared Library groovy script. Rolling back to git version 4.1.1 works fine. Let me know if you need more information.
[JIRA] (JENKINS-60194) Separate injector for test resources
Title: Message Title Mez Pahlan updated an issue Jenkins / JENKINS-60194 Separate injector for test resources Change By: Mez Pahlan Labels: help-wanted Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203164.1574069472000.10520.1584744420064%40Atlassian.JIRA.
[JIRA] (JENKINS-61608) Latest version throws IllegalArgumentException: Git repository URL 2 is an empty string
Title: Message Title
Mark Waite resolved as Duplicate
You'll need to correct the checkout step you are using. The exception is telling you that your checkout syntax is incorrect. Your syntax is:
checkout(scm: [$class: 'GitSCM', userRemoteConfigs: [[url: "${gitURL}"], [name: "origin"]], branches: [[name: "${gitTag}"]]])
That syntax defines two userRemoteConfigs, one that has a url argument without a name and one that has a name argument without a url. You need syntax that defines one userRemoteConfig with both a url argument and a name (though the name is actually optional and will default to origin ):
checkout(scm: [$class: 'GitSCM', userRemoteConfigs: [[url: "${gitURL}", name: "origin"]], branches: [[name: "${gitTag}"]]])
It worked previously because you were not referencing other components which require that all userRemoteConfig entries must have non-empty URL's.
Jenkins / JENKINS-61608
Latest version throws IllegalArgumentException: Git repository URL 2 is an empty string
Change By:
Mark Waite
Status:
Open Resolved
Resolution:
Duplicate
Add Comment
[JIRA] (JENKINS-61608) Latest version throws IllegalArgumentException: Git repository URL 2 is an empty string
Title: Message Title Mark Waite closed an issue as Duplicate Jenkins / JENKINS-61608 Latest version throws IllegalArgumentException: Git repository URL 2 is an empty string Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205309.1584743665000.10524.1584744600145%40Atlassian.JIRA.
[JIRA] (JENKINS-59931) Print URL of uploaded resource
Title: Message Title
Mez Pahlan commented on JENKINS-59931
Re: Print URL of uploaded resource
Hi Valentin Chareyre sorry for the late reply. I've been looking through the API docs and there isn't an API that give you want you want unfortunately. After we have uploaded the resource and committed it we get back an object that contains a release url from this API. This unfortunately looks like: v0.1/apps/{owner_name}/{app_name}/releases/{release_id}. Notice this is only an endpoint and not the actual url - it is missing the schema and the host and the first part of it is wrong. I don't want to start guessing what this might be for various users so don't think it is appropriate to infer anything from this unless we can find an official API from Microsoft. Having said that, if you call that release url as a GET request you get a rather large object back that does contain a direct download url. It looks like it doesn't take you to the download page with the information about the build (release notes, hashes, etc) but will allow you to download the file from AppCenter directly. I can see about exposing that as some sort of build status badge or similar. Would you want me to look into that?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202733.1571990313000.10533.1584748980221%40Atlassian.JIRA.
