[JIRA] (JENKINS-56874) Log4j2.xml file in the plugin causes unexpected errors
Title: Message Title Yuri Guller commented on JENKINS-56874 Re: Log4j2.xml file in the plugin causes unexpected errors Hi all here, The plugin is said to write the logs into the `userContent` folder under the Jenkins base folder, which in general should be a generally accessible folder for custom contents. Can you, please, check if indeed your `userContent` folder is not accessible to the user, the Jenkins process is running with? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56865) Password to access InfluxDB is stored unencrypted on disk
Title: Message Title Aleksi Simell updated an issue Jenkins / JENKINS-56865 Password to access InfluxDB is stored unencrypted on disk Change By: Aleksi Simell Issue Type: Task Improvement Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21647) In Vsphere Cloud I can not create a machine from a template
Title: Message Title Abhijeet Zope commented on JENKINS-21647 Re: In Vsphere Cloud I can not create a machine from a template Hi guys, My VMware is setup is like : VC - host1 >> datastores - host2 >> datastores As you can see, there is no cluster and resource pool. I want to deploy a template using vsphere-cloud plugin. Is this supported ? Any workaround? I dont want to create a cluster and resource pool just to use the plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56861) Send PMD, FB, Checkstyle metrics to influxDB
Title: Message Title Aleksi Simell commented on JENKINS-56861 Re: Send PMD, FB, Checkstyle metrics to influxDB These metrics are not yet available in this plugin. Is/are there some specific plugin/s you're using, which I could use to get this data? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56951) JIRA plugin config incorrectly mixed with properties section
Title: Message Title Björn Pedersen created an issue Jenkins / JENKINS-56951 JIRA plugin config incorrectly mixed with properties section Issue Type: Bug Assignee: Francisco Fernández Attachments: screenshot-forge.frm2.tum.de-2019.04.10-06-50-16.png, screenshot-forge.frm2.tum.de-2019.04.10-06-55-55.png Components: cloudbees-folder-plugin, core, jira-plugin Created: 2019-04-10 04:58 Priority: Minor Reporter: Björn Pedersen See screenshot, the Jira plugin config (here on Folder level and on multibranch projects) is intermixed with the folder properties section ( as can be seen by the "Enable ..-based security" item that is not related to jira) . In normal pipeline jobs, they are correctly separated. Add Comment
[JIRA] (JENKINS-56950) ATH container does not build because java 8 package ismissing
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-56950 ATH container does not build because java 8 package ismissing Issue Type: Task Assignee: Oliver Gondža Components: acceptance-test-harness Created: 2019-04-10 04:48 Priority: Major Reporter: Oliver Gondža It appears debian:buster does no longer distribute java 8 and the previous version does not have java 11. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56874) Log4j2.xml file in the plugin causes unexpected errors
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-56874 Log4j2.xml file in the plugin causes unexpected errors Change By: Daniel Gront Labels: octane Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56874) Log4j2.xml file in the plugin causes unexpected errors
Title: Message Title Daniel Gront assigned an issue to Radi Berkovich Jenkins / JENKINS-56874 Log4j2.xml file in the plugin causes unexpected errors Change By: Daniel Gront Assignee: Daniel Gront Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56874) Log4j2.xml file in the plugin causes unexpected errors
Title: Message Title Daniel Gront commented on JENKINS-56874 Re: Log4j2.xml file in the plugin causes unexpected errors Timothy Klopotoski, Thanks for letting me know. It is being checked. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19195) Add description field to Release JIRA version action
Title: Message Title Olivier Lamy updated JENKINS-19195 thanks! Jenkins / JENKINS-19195 Add description field to Release JIRA version action Change By: Olivier Lamy Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (TEST-112) Issue for testing purpose so do not mind
Title: Message Title Vivek Pandey commented on TEST-112 Re: Issue for testing purpose so do not mind pipeline step comment Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (TEST-112) Issue for testing purpose so do not mind
Title: Message Title Vivek Pandey commented on TEST-112 Re: Issue for testing purpose so do not mind SUCCESS: Integrated in Jenkins build fs2 #2 (See http://localhost:8080/job/fs2/2/) TEST-112: Test fix5 (vivek.pandey: https://github.com/vivek/pipeline-demo-test/commit/8e93a2742839c0907088849d68f704820c7b8dbb) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55319) Mercurial plugin cannot handle spaces in file names
Title: Message Title Jesse Glick updated JENKINS-55319 Jenkins / JENKINS-55319 Mercurial plugin cannot handle spaces in file names Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55319) Mercurial plugin cannot handle spaces in file names
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-55319 Mercurial plugin cannot handle spaces in file names Change By: Jesse Glick Labels: space Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56949) Support URLs for linking to an arbitrary log lines in a pipeline node / step
Title: Message Title Stuart Rowe created an issue Jenkins / JENKINS-56949 Support URLs for linking to an arbitrary log lines in a pipeline node / step Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2019-04-09 22:50 Priority: Minor Reporter: Stuart Rowe The following URL would bring users directly to the specified line of the specified step of the specified node of the pipline: https:///blue/organizations/jenkins//detail///pipeline/#step--log- Dependent on JENKINS-42866 getting fixed first. Add Comment
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
JD Friedrikson edited a comment on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
Just sharing my workaround for others:{code:groovy}pipeline { agent {docker { image 'debian'} } stages {stage('script') { steps {script { status = sh(returnStatus: true,script: '''#!/bin/bash exec > >(tee output.log) 2>&1 echo 'one: stdout' >&2 echo 'one: stderr' exit 1''' ) output = readFile('output.log').trim() echo output if (status != 0) {currentBuild.result = 'UNSTABLE' }} }} } post {cleanup { deleteDir()} }}{code} { panel code:text }[Pipeline] {[Pipeline] stage[Pipeline] { (script)[Pipeline] script[Pipeline] {[Pipeline] shone: stdoutone: stderr[Pipeline] readFile[Pipeline] echoone: stdoutone: stderr[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] deleteDir (show)[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withDockerContainer[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: UNSTABLE{ panel code }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
JD Friedrikson edited a comment on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
Just sharing my workaround for others:{code:groovy}pipeline { agent {docker { image 'debian'} } stages {stage('script') { steps {script { status = sh(returnStatus: true,script: '''#!/bin/bash exec > >(tee output.log) 2>&1 echo 'one: stdout' >&2 echo 'one: stderr' exit 1''' ) output = readFile('output.log').trim() echo output if (status != 0) {currentBuild.result = 'UNSTABLE' }} }} } post {cleanup { deleteDir()} }}{code}{code :text }[Pipeline] {[Pipeline] stage[Pipeline] { (script)[Pipeline] script[Pipeline] {[Pipeline] shone: stdoutone: stderr[Pipeline] readFile[Pipeline] echoone: stdoutone: stderr[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] deleteDir (show)[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withDockerContainer[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: UNSTABLE{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
JD Friedrikson commented on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
Just sharing my workaround for others:
pipeline {
agent {
docker {
image 'debian'
}
}
stages {
stage('script') {
steps {
script {
status = sh(
returnStatus: true,
script: '''#!/bin/bash
exec > >(tee output.log) 2>&1
echo 'one: stdout'
>&2 echo 'one: stderr'
exit 1
'''
)
output = readFile('output.log').trim()
echo output
if (status != 0) {
currentBuild.result = 'UNSTABLE'
}
}
}
}
}
post {
cleanup {
deleteDir()
}
}
}
[Pipeline] { [Pipeline] stage [Pipeline] { (script) [Pipeline] script [Pipeline]
Unknown macro: { [Pipeline] sh one}
[Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline]
Unknown macro: { (Declarative}
[Pipeline] // stage [Pipeline] } [Pipeline] // withDockerContainer [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: UNSTABLE
Add Comment
[JIRA] (JENKINS-46882) Scripts not permitted to use new java.lang.Exception java.lang.String
Title: Message Title Antoine Tran commented on JENKINS-46882 Re: Scripts not permitted to use new java.lang.Exception java.lang.String Using script-security 1.53, this is not reproducible anymore. I can throw new Exception(String) without preapproval. Should be closed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56948) Whitelist Enum.valueOf()
Title: Message Title Antoine Tran created an issue Jenkins / JENKINS-56948 Whitelist Enum.valueOf() Issue Type: Improvement Assignee: Andrew Bayer Components: script-security-plugin Created: 2019-04-09 22:01 Environment: script-security-plugin 1.56 (latest as of now) Priority: Minor Reporter: Antoine Tran Using valueOf from known classes (Boolean.valueOf , etc.) are allowed (see source generic-whitelist). But for custom Enum, we have to approve. Now because we cannot override valueOf, this method is very secure. Because we can't authorize all valueOf from all existing Enum in the world, we could just allow Enum.valueOf(Class enumType, String name). Add Comment
[JIRA] (JENKINS-56938) Impossible to use system nodejs from a container image
Title: Message Title
Nikolas Falco edited a comment on JENKINS-56938
Re: Impossible to use system nodejs from a container image
Use the configFileProvider is clear way for what you want archieve. {noformat}configFileProvider([configFile(fileId: 'mynpmrc', variable: 'npm_config_userconfig')]) {// some block}{noformat}that is what the build wrapper does. You can use jenkins credential for private repository.Or if you use authentication variable in the config file you don't even need to install nodejs plugin.{noformat}configFileProvider([configFile(fileId: 'mynpmrc', targetLocation: '$WORKSPACE\root_of_the_project')]) {// some block}{noformat}NodeJS is specialized to provide an automatic installation regardless of operating system. If you do not use the plugin for this scope.If you want You can also define a tool specific for that docker image than in Jenkins->Manage Jenkins->Global Tool COnfiguration Configuration -> define a new Add NodeJS , installation and than disable "Install automatically" and put checkbox. Put there the home folder of the NodeJS. At runtime it verify that verifies if node executable file exists in the ${PATH}/bin/node ( depends on depending by the version and operative system). If you do that , it works (I had try locally on my computer) . It's a bit useless since the defined tool works only on that docker image and loose the global package install feature.If you had test with a valid (for sure not /usr/local/bin or /usr/local) NodeJS home path (I had try on my computer) and does not work than I will spend time for futher investigation on other O.S. different than mine otherwise I will close the issue as "Not a Defect"I do not want make tool as optional parameter or define a "System Default" tool because I can not gaurantee nodejs is really installed and this cause confusion (and issue opening) when the same pipeline work on a node but not on other.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this
[JIRA] (JENKINS-56938) Impossible to use system nodejs from a container image
Title: Message Title
Nikolas Falco commented on JENKINS-56938
Re: Impossible to use system nodejs from a container image
Use the configFileProvider is clear way for what you want archieve.
configFileProvider([configFile(fileId: 'mynpmrc', variable: 'npm_config_userconfig')]) {
// some block
}
that is what the build wrapper does. You can use jenkins credential for private repository. Or if you use authentication variable in the config file you don't even need to install nodejs plugin.
configFileProvider([configFile(fileId: 'mynpmrc', targetLocation: '$WORKSPACE\root_of_the_project')]) {
// some block
}
NodeJS is specialized to provide an automatic installation regardless of operating system. If you do not use the plugin for this scope. If you want define a tool specific for docker image than in Jenkins->Manage Jenkins->Global Tool COnfiguration->define a new NodeJS, disable "Install automatically" and put the home folder of the NodeJS. At runtime it verify that node executable file exists in the ${PATH}/bin/node (depends on the version and operative system). If you do that it works. It's a bit useless since the defined tool works only on that docker image and loose the global package install feature. If you had test with a valid (for sure not /usr/local/bin or /usr/local) NodeJS home path (I had try on my computer) and does not work than I will spend time for futher investigation on other O.S. different than mine otherwise I will close the issue as "Not a Defect" I do not want make tool as optional parameter or define a "System Default" tool because I can not gaurantee nodejs is really installed and this cause confusion (and issue opening) when the same pipeline work on a node but not on other.
Add Comment
[JIRA] (JENKINS-56938) Impossible to use system nodejs from a container image
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-56938 Impossible to use system nodejs from a container image Change By: Nikolas Falco Priority: Major Trivial Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55319) Mercurial plugin cannot handle spaces in file names
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-55319 Mercurial plugin cannot handle spaces in file names Change By: Jesse Glick Assignee: Mitchell Bagot Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56698) Use LookaheadParser for NagFortranParser
Title: Message Title Colin Kaschel assigned an issue to Colin Kaschel Jenkins / JENKINS-56698 Use LookaheadParser for NagFortranParser Change By: Colin Kaschel Assignee: Colin Kaschel Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56725) Add unit tests for AggregatedTrendAction
Title: Message Title Colin Kaschel assigned an issue to Ulli Hafner Jenkins / JENKINS-56725 Add unit tests for AggregatedTrendAction Change By: Colin Kaschel Assignee: Colin Kaschel Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56725) Add unit tests for AggregatedTrendAction
Title: Message Title Colin Kaschel assigned an issue to Unassigned Jenkins / JENKINS-56725 Add unit tests for AggregatedTrendAction Change By: Colin Kaschel Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54604) checkUpdatesServer fails to use SSL
Title: Message Title Josh Soref commented on JENKINS-54604 Re: checkUpdatesServer fails to use SSL We thought this was the right bug: https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1800792 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912333 https://issues.apache.org/jira/browse/SUREFIRE-1588 However, we just upgraded to 8u191-b12-2ubuntu0.18.04.1 and still hit what feels like this error. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56947) File handle leak in EnvActionImpl when accessing environment of completed builds
Title: Message Title Michael Wong created an issue Jenkins / JENKINS-56947 File handle leak in EnvActionImpl when accessing environment of completed builds Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2019-04-09 19:04 Environment: Jenkins 2.150.1 workflow-job 2.32 workflow-cps 2.64 Labels: jenkins pipeline workflow-cps-plugin workflow-job-plugin Priority: Minor Reporter: Michael Wong We recently upgraded workflow-job-plugin from 2.24 => 2.32 and started seeing file handle leaks in our builds. We installed the file handle leak plugin and saw a lot of file handles being locked by other builds. This only seemed to happen when we were accessing the previous build's environment information. We narrowed it down to it using the EnvActionImpl to access environment variables. To workaround the issue, we called getEnvironment(TaskListener.NULL) to access the environment before accessing the variables. I'm wondering if this change is intentional. I believe the cause of this issue is that the EnvActionImpl getListener() uses the job's FlowExecution getListener(). This listener is set to always initialize whenever it is null. Whenever, a WorkFlowRun finished (calls finish()), the listener is set to null, so whenever something else accesses the build environment, the listener is re-initialized. Function causing file leak: @NonCPS private static def
[JIRA] (JENKINS-56725) Add unit tests for AggregatedTrendAction
Title: Message Title Colin Kaschel assigned an issue to Colin Kaschel Jenkins / JENKINS-56725 Add unit tests for AggregatedTrendAction Change By: Colin Kaschel Assignee: Colin Kaschel Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56874) Log4j2.xml file in the plugin causes unexpected errors
Title: Message Title
Timothy Klopotoski edited a comment on JENKINS-56874
Re: Log4j2.xml file in the plugin causes unexpected errors
[~gront], I am also experiencing this problem. I see the above log snipped on Jenkins startup (as opposed to a specific step) , right after the line which says {quote} INFO: Listed all plugins{quote} I have version 5.7 of the {{hp-application-automation-tools-plugin}} plugin installed.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56703) Add unit test for LinesDataSet#add that throws Exception
Title: Message Title Lorenz Munsch started work on JENKINS-56703 Change By: Lorenz Munsch Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56858) unable to load plugins
Title: Message Title Yufen Kuo commented on JENKINS-56858 Re: unable to load plugins If I specify the exploded directory with the -w option, it works. But if I just specify the -v option (without -w option), I get the same error message. Running pipeline on jenkins 2.164.1 1.405 [id=50] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: Step API v2.19 (workflow-step-api) java.io.IOException: Pipeline: Step API v2.19 failed to load. You must update Jenkins from v2.89 to v2.121.1 or later to run this plugin. at Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56764) Pipeline fails on some AMI images / node types because of Broken Pipe
Title: Message Title Alex Nederlof commented on JENKINS-56764 Re: Pipeline fails on some AMI images / node types because of Broken Pipe I have it on EKS K8S 1.11, so I don't think that is related. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45164) In jenkins pipeline a "checkout scm" now adds "--no-tags" instead of "--tags" for git projects
Title: Message Title rupert je thurner commented on JENKINS-45164 Re: In jenkins pipeline a "checkout scm" now adds "--no-tags" instead of "--tags" for git projects the main challenge is that there are 3 possibilities "git fetch" fetches a branch with tags reachable, the ideal default - and jenkins cannot do it at all "git fetch --no-tags" fetches a branch without tags "git fetch --tags" fetches tags not reachable from the branch, i.e. other branches also Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56517) fetch has 3 options: nothing, --no-tags, --tags, jenkins only 2
Title: Message Title rupert je thurner commented on JENKINS-56517 Re: fetch has 3 options: nothing, --no-tags, --tags, jenkins only 2 duplicate of JENKINS-45164 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45164) In jenkins pipeline a "checkout scm" now adds "--no-tags" instead of "--tags" for git projects
Title: Message Title
rupert je thurner edited a comment on JENKINS-45164
Re: In jenkins pipeline a "checkout scm" now adds "--no-tags" instead of "--tags" for git projects
currently we use the following workaround to deal with "push -f" to branches, and it still does not work in 100% of the cases. which i find a phantastic pain :( {code:java}// code placeholder checkout([$class: 'GitSCM',branches: [[name: 'refs/heads/'+env.BRANCH_NAME]],extensions: [[$class: 'CloneOption', noTags: false, shallow: false, depth: 0, reference: '']],userRemoteConfigs: scm.userRemoteConfigs, ]) sh "git checkout ${env.BRANCH_NAME}" sh "git reset --hard origin/${env.BRANCH_NAME}" {code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45164) In jenkins pipeline a "checkout scm" now adds "--no-tags" instead of "--tags" for git projects
Title: Message Title
rupert je thurner commented on JENKINS-45164
Re: In jenkins pipeline a "checkout scm" now adds "--no-tags" instead of "--tags" for git projects
currently we use the following workaround to deal with "push -f" to branches, and it still does not work in 100% of the cases. which i find a phantastic pain
// code placeholder
checkout([
$class: 'GitSCM',
branches: [[name: 'refs/heads/'+env.BRANCH_NAME]],
extensions: [[$class: 'CloneOption', noTags: false, shallow: false, depth: 0, reference: '']],
userRemoteConfigs: scm.userRemoteConfigs,
])
sh "git checkout ${env.BRANCH_NAME}"
sh "git reset --hard origin/${env.BRANCH_NAME}"
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37396) java.io.NotSerializableException: groovy.sql.GroovyRowResult
Title: Message Title Jean KST updated an issue Jenkins / JENKINS-37396 java.io.NotSerializableException: groovy.sql.GroovyRowResult Change By: Jean KST Comment: Had a similar issue and upgrading to Groovy plugin 2.2 fixed it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56517) fetch has 3 options: nothing, --no-tags, --tags, jenkins only 2
Title: Message Title
rupert je thurner updated an issue
Jenkins / JENKINS-56517
fetch has 3 options: nothing, --no-tags, --tags, jenkins only 2
Change By:
rupert je thurner
git fetch has three options to fetch tags: * "git fetch" fetches a branch with tags reachable, the ideal default * "git fetch --no-tags" fetches a branch without tags * "git fetch --tags" fetches tags not reachable from the branch, i.e. other branches alsoin jenkins variant 1, fetching tags reachable cannot be configured any more (with ease), while it reasonably should be the default? also the branch name is not there in the git repo fetched. all of these operatins add labels to existing commits so do not increase the clone size.this should be for multibranch pipeline, not sure what the correct component is. the current workaround is:{code:java}// code placeholder{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44376) Ability to set variables shared between stages
Title: Message Title
Jesse Glick commented on JENKINS-44376
Re: Ability to set variables shared between stages
read a config file in one stage
Trivial in Scripted. This is antithetical to the notion of “Declarative”. Anyway I think this is asking the wrong question. The right way to write a Pipeline which reads and then uses a config file is
pipeline {
agent any
stages {
stage('All') {
steps {
sh 'do-it-all'
}
}
}
}
where the script in question is written in Ruby or whatever you find most convenient for such things. If you just want Blue Ocean to display a stage boundary between parts of a single sh step, that is another matter, and better done by creating a Pipeline analogue to Collapsing Console Sections.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44376) Ability to set variables shared between stages
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-44376
Ability to set variables shared between stages
Change By:
Jesse Glick
It would be extremely useful to be able to share variables between stages ; currently, environment variables are overriden per-stage only, given the following example : { {stages \{ code } } stages { { stage('Setup profile') \ { }} {{ environment \ { }} {{ MVNARGS = "-P$ \ {params.profile}" }} {{ } }} {{ when \ { }} {{ _expression_ \ { }} {{ params.profile != ''} } {{ } }} {{ }}}{{ steps \ { }} {{ echo "deploying as args:$ \ {env.MVNARGS} - env:$ \ {MVNARGS} - pprofile:$ \ {params.profile} - ..." }} {{ } }} {{ } }} {{ stage('Build') \ { }} {{ steps \ { }} {{ sh "mvn $ \ {env.MVNARGS} xxx" } } } { { code } }}} In Build, MVNARGS is null because the override from the Setup profile is stage scoped.I did not find a workaround for this, I've tried to share using the params Map but it's an unmodifiable read-only map. Any ideas ? Thanks
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] (JENKINS-26354) First time build does not show changelog
Title: Message Title
Oleg Stepura commented on JENKINS-26354
Re: First time build does not show changelog
Hi! Thanks for quick reply and sorry I did not react as fast. I discussed internally if this is acceptable to do what you suggested and it was not, but another option to workaround the limitations here was found: JENKINS-54285 I tried using commands from that ticket, it works if we use big enough shallow clone depth (I set it to 100). the only issue I faced was being unable to use sh in a function. It looks buggy. Seems like I cannot simply define a function like this:
def getLastCommitHash() {
return sh(
returnStdout: true,
script: "git show -s --no-abbrev-commit --pretty=format:%P%n%H%n HEAD"
).trim().split("\n").last().trim()
}
and the use it:
def otherFunction() {
def lastCommit = getLastCommitHash()
// do something else with it expecting lastCommit has one-line string
return [a, b, c]
}
In the example above otherFunction() will return exact unprocessed output of sh command from getLastCommitHash() function. This is weird. I was able to workaround this creating simple functions which only run sh commands and do no post-processing (just return sh output) and other functions that only work with strings and not do anything with sh. Then all those functions are used together inside our main node {} context.
def getHeads() {
return sh(
returnStdout: true,
script: "git show -s --no-abbrev-commit --pretty=format:%P%n%H%n HEAD"
)
}
def getLastCommitHash(headsOutput) {
return headsOutput.trim().split("\n").last().trim()
}
then use this in Jenkinsfile:
node("xxx") {
def headsOutput = getHeads()
def lastCommitHash = getLastCommitHash(headsOutput)
// ...
}
[JIRA] (JENKINS-43758) Parameters disappear from pipeline job after running the job
Title: Message Title
Alexander Komarov edited a comment on JENKINS-43758
Re: Parameters disappear from pipeline job after running the job
[~aarondmarasco_vsi], to my knowledge there is no way to get current job properties in the format suitable for *properties{}*. The only way I can see of doing this would be to access the individual getters on *currentBuild.rawBuild.parent* (an instance of [WorkflowRun|https://javadoc.jenkins.io/plugin/workflow-job/org/jenkinsci/plugins/workflow/job/WorkflowRun.html] ) and then transform their current values into arguments to *properties{}.* This would certainly be brittle, and if you use Script Security, this will require approval.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43758) Parameters disappear from pipeline job after running the job
Title: Message Title
Alexander Komarov edited a comment on JENKINS-43758
Re: Parameters disappear from pipeline job after running the job
[~aarondmarasco_vsi], to my knowledge there is no way to get job properties in the format suitable for *properties{}*. The only way I can see of doing this would be to access the individual getters on *currentBuild.rawBuild.parent* (an instance of [WorkflowRun| [ https://javadoc.jenkins.io/plugin/workflow-job/org/jenkinsci/plugins/workflow/job/WorkflowRun.html] ] ) and then transform their current values into arguments to *properties{}.* This would certainly be brittle, and if you use Script Security, this will require approval.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43758) Parameters disappear from pipeline job after running the job
Title: Message Title
Alexander Komarov edited a comment on JENKINS-43758
Re: Parameters disappear from pipeline job after running the job
[~aarondmarasco_vsi], to my knowledge there is no way to get job properties in the format suitable for *properties{}*. The only way I can see of doing this would be to access the individual getters on *currentBuild.rawBuild.parent* (an instance of [WorkflowRun|[https://javadoc.jenkins.io/plugin/workflow-job/org/jenkinsci/plugins/workflow/job/WorkflowRun.html]]) and then transform their current values into arguments to *properties{}.* This would certainly be brittle, and if you use Script Security, this will require approval.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43758) Parameters disappear from pipeline job after running the job
Title: Message Title
Alexander Komarov edited a comment on JENKINS-43758
Re: Parameters disappear from pipeline job after running the job
[~aarondmarasco_vsi], to my knowledge there is no way to get job properties in the format suitable for *properties{}*. The only way I can see of doing this would be to access the individual getters on *currentBuild.rawBuild.parent* (an instance of [WorkflowRun|[https://javadoc.jenkins.io/plugin/workflow-job/org/jenkinsci/plugins/workflow/job/WorkflowRun.html]] ) and then transform their current values into arguments to *properties{}.* This would certainly be brittle, and if you use Script Security, this will require approval.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43758) Parameters disappear from pipeline job after running the job
Title: Message Title
Alexander Komarov commented on JENKINS-43758
Re: Parameters disappear from pipeline job after running the job
Aaron Marasco, to my knowledge there is no way to get job properties in the format suitable for properties{}. The only way I can see of doing this would be to access the individual getters on currentBuild.rawBuild.parent (an instance of [WorkflowRun|https://javadoc.jenkins.io/plugin/workflow-job/org/jenkinsci/plugins/workflow/job/WorkflowRun.html]) and then transform their current values into arguments to properties{}. This would certainly be brittle, and if you use Script Security, this will require approval.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43758) Parameters disappear from pipeline job after running the job
Title: Message Title Aaron Marasco commented on JENKINS-43758 Re: Parameters disappear from pipeline job after running the job Just stumbled on this bug as well, wondering why I lose my JobDSL parameters after a run. Alexander Komarov has a great workaround above, but I really need what Michal Rysanek is asking for - a way to get the current properties so I can add to them. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53045) Plugin trips FARGATE rate limit.
Title: Message Title Mike Kozell assigned an issue to Philipp Garbe Jenkins / JENKINS-53045 Plugin trips FARGATE rate limit. Change By: Mike Kozell Assignee: Jan Roehrich Philipp Garbe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51038) Re-defining existing job loses environment variables
Title: Message Title Aaron Marasco commented on JENKINS-51038 Re: Re-defining existing job loses environment variables I just stumbled on JENKINS-43758 and am 99% sure this is what was biting me in this bug report! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56874) Log4j2.xml file in the plugin causes unexpected errors
Title: Message Title Timothy Klopotoski commented on JENKINS-56874 Re: Log4j2.xml file in the plugin causes unexpected errors Daniel Gront, I am also experiencing this problem. I see the above log snipped on Jenkins startup, right after the line which says INFO: Listed all plugins I have version 5.7 of the hp-application-automation-tools-plugin plugin installed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51638) No Enum Constant Found - Default PreBuildMerge Failure
Title: Message Title Jesse Glick updated JENKINS-51638 Jenkins / JENKINS-51638 No Enum Constant Found - Default PreBuildMerge Failure Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44892) Ability to override reflective metadata in DescribableModel
Title: Message Title Jesse Glick commented on JENKINS-44892 Re: Ability to override reflective metadata in DescribableModel Daniel Spilker I have proposed an API and would like feedback on whether you think it makes sense for Job DSL. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44892) Ability to override reflective metadata in DescribableModel
Title: Message Title Jesse Glick updated JENKINS-44892 Jenkins / JENKINS-44892 Ability to override reflective metadata in DescribableModel Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
Title: Message Title Konrad Mosoń commented on JENKINS-54929 Re: Some final output is missing in Jenkins Pipeline when using the Ansible Plugin I've experienced this problem too ;( Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48552) Please add possibility to get token from gitlab API token
Title: Message Title
Alexei Moussatov commented on JENKINS-48552
Re: Please add possibility to get token from gitlab API token
workarround
import com.cloudbees.plugins.credentials.CredentialsProviderdef credsList = com.cloudbees.plugins.credentials.CredentialsProvider.lookupCredentials(
com.cloudbees.plugins.credentials.Credentials.class,Jenkins.instance,null,null);
def creds = credsList.findResult { it.id == "" ? it : null }
println("apiToken: ${creds.apiToken}")
where - creds id in Jenkins
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37396) java.io.NotSerializableException: groovy.sql.GroovyRowResult
Title: Message Title Jean KST commented on JENKINS-37396 Re: java.io.NotSerializableException: groovy.sql.GroovyRowResult Had a similar issue and upgrading to Groovy plugin 2.2 fixed it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title
Christopher Smith edited a comment on JENKINS-55836
Re: Unable to delete workspace due to locked git .pack file
***It turned out that we had used a different user than the user account the Jenkins slave service was using when troubleshooting/working with the Jenkins workspace directory. Despite both accounts being members of the Administrators group it seems everything needed to be owned/created/modified using the same account*** Recently ran into issues with plugins and we did a update of all plugins. As soon as that was done this problem started occurring for us. Tried a bunch of workarounds so far and none of it seems to work. Adding the workaround Aaron suggested. Even manually deleting the contents of workspace myself doesn't seem to fix the issue either as the next time a job runs and goes to pull down a branch it fails due to permissions. My C:\Jenkins\workspace folder on the Slave node where these files should be being cleaned up is basically wide open right now with Everyone having full permission. I assume this is still related to some kind of lock?Note: The below should says {code:java}*/.git/** {code} but the second asterisk isn't coming through.{panel}**/.git/** exclude and Apply pattern also on directories set in the Workspace Cleanup config in the job* [WS-CLEANUP] Deleting project workspace... ERROR: [WS-CLEANUP] Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. ERROR: Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. sent [C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\hpc_install20190320.log] to splunk in 1 events Finished: FAILURE{panel}{panel}**/.git/** exclude, Apply pattern also on directories, and Disable deferred wipeout set in the Workspace Cleanup config in the job* [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... ERROR: [WS-CLEANUP] Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. ERROR: Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. sent [C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\hpc_install20190320.log] to splunk in 1 events Finished: FAILURE{panel}
Add Comment
[JIRA] (JENKINS-54500) Charset not respected in parallel sync
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-54500 Charset not respected in parallel sync Change By: Karl Wirth Labels: P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55737) "No polling baseline - Changes found" causing runaway polling
Title: Message Title Karl Wirth commented on JENKINS-55737 Re: "No polling baseline - Changes found" causing runaway polling Fixes have been submitted in mainline (not released yet): https://swarm.workshop.perforce.com/changes/25439 https://swarm.workshop.perforce.com/changes/25437 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56295) multibranch jobs triggering repeatedly
Title: Message Title Karl Wirth commented on JENKINS-56295 Re: multibranch jobs triggering repeatedly Fixes have been submitted in mainline (not released yet): https://swarm.workshop.perforce.com/changes/25439 https://swarm.workshop.perforce.com/changes/25437 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56946) P4 Plugin does not sync Mac resource forks on Mac
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-56946 P4 Plugin does not sync Mac resource forks on Mac Change By: Karl Wirth Labels: P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56946) P4 Plugin does not sync Mac resource forks on Mac
Title: Message Title Karl Wirth commented on JENKINS-56946 Re: P4 Plugin does not sync Mac resource forks on Mac Hi Peter DB. Thanks for highlighting this. I cannot see any known bugs in P4Java so I will try this out and get back to you with my findings. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56946) P4 Plugin does not sync Mac resource forks on Mac
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-56946 P4 Plugin does not sync Mac resource forks on Mac Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56029) Kubernetes Plugin: Concurrent builds do not have their own unique workspaces
Title: Message Title Martin Sjölund commented on JENKINS-56029 Re: Kubernetes Plugin: Concurrent builds do not have their own unique workspaces I have similar issues where two parallel jobs in a pipeline each execute on a different pod on the same machine. They both try to do git pull at the same time, causing conflicts in the index.lock files, etc. I would be perfectly happy with something like #47591 or simply having the possibility to not use persistent storage at all for my pod (slower, but at least would not break things and is probably easy to implement). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56579) .mvn/extensions.xml not recognized
Title: Message Title Benjamin Büscher commented on JENKINS-56579 Re: .mvn/extensions.xml not recognized It's a little ugly: jenkins -> ant -> cmd -> maven: Jenkins calls an ant build via ant plugin. Inside of the ant build an exec target is used to call cmd launching the maven build. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56579) .mvn/extensions.xml not recognized
Title: Message Title
Benjamin Brummer updated an issue
Jenkins / JENKINS-56579
.mvn/extensions.xml not recognized
Change By:
Benjamin Brummer
We wanted to setup a tycho-pomless build on jenkins, with maven 3.6.0. Running the build without Jenkins works fine.The pom.xml is in a subfolder next to the .mvn/extensions.xmlThis job only works when the pom.xml is in the workspace root and maven 3.3.9 is used. Useing dir() in a pipeline when calling maven 3.3.9 is working to too . We could reproduce this issue with the tycho-example form here too [https://github.com/vogellacompany/tycho-example]h1. 3.3.9 + code in "sub"{code:java}[Vogella] $ cmd.exe /C "c:\jenkins\tools\hudson.tasks.Maven_MavenInstallation\3.3.9\bin\mvn.cmd clean verify -V -B --file sub/pom.xml && exit %%ERRORLEVEL%%"Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)Maven home: c:\jenkins\tools\hudson.tasks.Maven_MavenInstallation\3.3.9Java version: 1.8.0_202, vendor: Oracle CorporationJava home: c:\jenkins\tools\hudson.model.JDK\8\jreDefault locale: en_US, platform encoding: Cp1252OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"[INFO] Scanning for projects...[ERROR] [ERROR] Some problems were encountered while processing the POMs:[ERROR] Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.logging.config\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist @ [ERROR] Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.tycho.plugin1\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist @ [ERROR] Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.tycho.rcp\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist @ [ERROR] Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.tycho.p2.ui\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist @ [ERROR] Child module C:\jenkins\workspace\Vogella\sub\features\com.vogella.tycho.feature\pom.xml of C:\jenkins\workspace\Vogella\sub\features\pom.xml does not exist @ [ERROR] Child module C:\jenkins\workspace\Vogella\sub\tests\com.vogella.tycho.plugin1.tests\pom.xml of C:\jenkins\workspace\Vogella\sub\tests\pom.xml does not exist @ [ERROR] Child module C:\jenkins\workspace\Vogella\sub\tests\com.vogella.tycho.rcp.tests\pom.xml of C:\jenkins\workspace\Vogella\sub\tests\pom.xml does not exist @ @ [ERROR] The build could not read 3 projects -> [Help 1][ERROR] [ERROR] The project com.vogella.tycho:com.vogella.tycho.bundles:1.0.0-SNAPSHOT (C:\jenkins\workspace\Vogella\sub\bundles\pom.xml) has 4 errors[ERROR] Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.logging.config\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist[ERROR] Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.tycho.plugin1\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist[ERROR] Child module
[JIRA] (JENKINS-32215) jenkins will not delete /tmp/upload_*.tmp files,after use File parameter upload file for build
Title: Message Title Baptiste Mathus resolved as Duplicate Marking as a duplicate of JENKINS-12699, please correct me if I'm wrong. AFAICT, both are really about using File Parameters and the uploaded file never gets deleted. Jenkins / JENKINS-32215 jenkins will not delete /tmp/upload_*.tmp files,after use File parameter upload file for build Change By: Baptiste Mathus Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12699) Temp upload files from file param not removed after transferred to slave
Title: Message Title Baptiste Mathus updated JENKINS-12699 Jenkins / JENKINS-12699 Temp upload files from file param not removed after transferred to slave Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12699) Temp upload files from file param not removed after transferred to slave
Title: Message Title Baptiste Mathus assigned an issue to Brian Hinz Jenkins / JENKINS-12699 Temp upload files from file param not removed after transferred to slave Change By: Baptiste Mathus Assignee: Brian Hinz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12699) Temp upload files from file param not removed after transferred to slave
Title: Message Title Baptiste Mathus started work on JENKINS-12699 Change By: Baptiste Mathus Status: Reopened In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56579) .mvn/extensions.xml not recognized
Title: Message Title Benjamin Brummer commented on JENKINS-56579 Re: .mvn/extensions.xml not recognized "I call maven via CMD, not the jenkins maven plugin" => Without jenkins involved at all? Without jenkins it works here with 3.6.0. Useing a Jenkins agent => No matter how we call mvn, it fails. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56579) .mvn/extensions.xml not recognized
Title: Message Title Benjamin Büscher commented on JENKINS-56579 Re: .mvn/extensions.xml not recognized I think I ran into the same issue but from a slightly different direction. I also have a pomless tycho build running on Windows slaves. I call maven via CMD, not the jenkins maven plugin. (-> I dont think its a jenkins issue) This build fails on maven 3.6.0 with similar looking log and works on maven 3.3.9, just as described here. I've set up a local jenkins on my dev machine (win10) - this build works fine using maven 3.6.0! My guess is that this is a maven issue on win server, probably related to how plugins like tycho are loaded. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56946) P4 Plugin does not sync Mac resource forks on Mac
Title: Message Title Peter DB created an issue Jenkins / JENKINS-56946 P4 Plugin does not sync Mac resource forks on Mac Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-04-09 12:22 Environment: P4 Plugin version: 1.9.6 Jenkins version: 2.150.2 Java version: 1.8.0_192 macOS version: 10.13.6 Perforce server version: P4D/NTX64/2014.2/1014956 (2015/02/26) Priority: Major Reporter: Peter DB When submitting a file with a resource fork from Mac with P4 or P4V, it is put in the depot as file type "apple". However, when syncing such an "apple" file back to Mac with the P4 Plugin, it is synced as two separate files "myfile" and "%myfile", instead of the original single file with a resource fork. Upon further inspection, these two separate files are the "AppleDouble" format: "myfile" contains the original data fork and "%myfile" contains the original resource fork. AppleDouble is normally used for syncing "apple" files by non-MacOS clients, as described in Perforce Platform Notes - Apple Macintosh. But in this case it's happening for a MacOS client too. That is unexpected. The latest P4 and P4V for MacOS all sync "apple" files back to Mac as genuine Apple files. It seems logical to expect the same result from P4 Plugin as from P4 and P4V, when syncing. Also, it seems logical to expect getting the same file back as was submitted, if submitting and syncing happen on the same platform and possibly even on the same machine. I guess this is related to change #546744 in P4Java as mentioned on Release Notes for P4Java. Our setup is a Freestyle project, with P4 Workspace behaviour set to "Static (static view, master only)".
[JIRA] (JENKINS-19403) Unable to Open Report Created by HTML Publisher Plugin
Title: Message Title Richard Bywater commented on JENKINS-19403 Re: Unable to Open Report Created by HTML Publisher Plugin Hi Randell Maree - are you able to please raise a new issue and provide any relevant screenshots/job configuration/pipeline code/etc. to show exactly what issue you are seeing? Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56939) pipeline gets stuck: root cause unclear
Title: Message Title
Jan Heylen updated an issue
Jenkins / JENKINS-56939
pipeline gets stuck: root cause unclear
Change By:
Jan Heylen
I'm running following pipeline in 10 build at the same time (so 10 *30 = 300 "stages"){code:java}def label = "v5-$USER"def batchList = "batchList"def batchListArray = []timestamps {podTemplate(label: label,serviceAccount: "jenkins",idleMinutes: 0,podRetention: never(),containers: [containerTemplate(name: 'kubectl',image: 'lachlanevenson/k8s-kubectl:v1.10.7',ttyEnabled: true,command: 'cat'),containerTemplate(name: 'helm',image: 'lachlanevenson/k8s-helm:v2.9.1',ttyEnabled: true,command: 'cat')]){node(label) {stage('Setup') {stage('Get list batches') {container("kubectl") {sh """echo 1 > $batchListecho 2 >> $batchListecho 3 >> $batchListecho 4 >> $batchListecho 5 >> $batchListecho 6 >> $batchListecho 7 >> $batchListecho 8 >> $batchListecho 9 >> $batchListecho 10 >> $batchListecho 11 >> $batchListecho 12 >> $batchListecho 13 >> $batchListecho 14 >> $batchListecho 15 >> $batchListecho 16 >> $batchListecho 17 >> $batchListecho 18 >> $batchListecho 19 >> $batchListecho 20 >> $batchListecho 21 >> $batchListecho 22 >> $batchListecho 23 >> $batchListecho 24 >> $batchListecho 25 >> $batchListecho 26 >> $batchListecho 27 >> $batchListecho 28 >> $batchListecho 29 >> $batchListecho 30 >> $batchList"""}batchListFile = readFile "$batchList"lines = batchListFile.readLines()for (batch in lines) {batchListArray.add(batch)}}}stage ('Parallel') {def parallelData = [:]batchListArray.each { batch ->parallelData[batch] = {stage("Deploy - $batch") {container("helm") { sh """ sleep 5 """}}stage("Queue - $batch") {container("kubectl") { sh """ sleep 600 """}}}}parallel parallelData}stage('Clean up') {container("helm") {sh """sleep 10
[JIRA] (JENKINS-56939) pipeline gets stuck: root cause unclear
Title: Message Title
Jan Heylen commented on JENKINS-56939
Re: pipeline gets stuck: root cause unclear
After further investigation it looks like the container statements are the ones causing the performance issue. container("some container") { Once you run the same pipeline, but without the 'container' statements (so everything just on the jnlp container?), the scaling performance issue is no longer seen.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19403) Unable to Open Report Created by HTML Publisher Plugin
Title: Message Title Randell Maree commented on JENKINS-19403 Re: Unable to Open Report Created by HTML Publisher Plugin Hi, I'm also still experiencing the same issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56938) Impossible to use system nodejs from a container image
Title: Message Title
Vladimir Kulev edited a comment on JENKINS-56938
Re: Impossible to use system nodejs from a container image
I mean .npmrc file, the way I meant to use it is : {noformat}nodejs(configId: 'npm-proxy-config') { sh 'npm install'}{noformat}I eventually managed to achieve the same with configFileProvider([configFile(...)]), but having it like above would be a much cleaner way.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56938) Impossible to use system nodejs from a container image
Title: Message Title
Vladimir Kulev commented on JENKINS-56938
Re: Impossible to use system nodejs from a container image
I mean .npmrc file, the way a meant to use it is:
nodejs(configId: 'npm-proxy-config') {
sh 'npm install'
}
I eventually managed to achieve the same with configFileProvider([configFile(...)]), but having it like above would be a much cleaner way.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56938) Impossible to use system nodejs from a container image
Title: Message Title
Vladimir Kulev edited a comment on JENKINS-56938
Re: Impossible to use system nodejs from a container image
I mean .npmrc file, the way a I meant to use it is: {noformat}nodejs(configId: 'npm-proxy-config') { sh 'npm install'}{noformat}I eventually managed to achieve the same with configFileProvider([configFile(...)]), but having it like above would be a much cleaner way.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55618) When using spot instances, requests 3-4 nodes when one is needed
Title: Message Title Harry McLaughlin commented on JENKINS-55618 Re: When using spot instances, requests 3-4 nodes when one is needed Also facing the same issue; this is quite a problem as the entire benefit of spot instances is reduced user cost. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56625) Too many open file descriptors from embedded build status usage
Title: Message Title Thomas Döring updated JENKINS-56625 Thanks to Adam BH and Oleg Nenashev Jenkins / JENKINS-56625 Too many open file descriptors from embedded build status usage Change By: Thomas Döring Status: Fixed but Unreleased Resolved Released As: v2.0.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35371) Please add option to deploy ova file using vSphere Cloud Plugin
Title: Message Title Abhijeet Zope commented on JENKINS-35371 Re: Please add option to deploy ova file using vSphere Cloud Plugin Seem very old issue. any ETA on this ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56625) Too many open file descriptors from embedded build status usage
Title: Message Title Thomas Döring updated JENKINS-56625 Jenkins / JENKINS-56625 Too many open file descriptors from embedded build status usage Change By: Thomas Döring Status: Open Fixed but Unreleased Assignee: Antonio Muñiz Thomas Döring Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56625) Too many open file descriptors from embedded build status usage
Title: Message Title Thomas Döring commented on JENKINS-56625 Re: Too many open file descriptors from embedded build status usage Adam BH Thank you. I just merged your pull request. A v2.0.1 bugfix release will be released any time soon. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56625) Too many open file descriptors from embedded build status usage
Title: Message Title Thomas Döring updated an issue Jenkins / JENKINS-56625 Too many open file descriptors from embedded build status usage Change By: Thomas Döring Labels: embeddable-build-status plugin v2.0.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56796) JCASC and ParameterizedRemoteTrigger: Not able to set auth for remote Jenkins
Title: Message Title Ralf Loesche updated JENKINS-56796 Jenkins / JENKINS-56796 JCASC and ParameterizedRemoteTrigger: Not able to set auth for remote Jenkins Change By: Ralf Loesche Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56796) JCASC and ParameterizedRemoteTrigger: Not able to set auth for remote Jenkins
Title: Message Title Ralf Loesche updated JENKINS-56796 Defining credentials for remote jenkins is deprecated - so it does not make sense to configure this Jenkins / JENKINS-56796 JCASC and ParameterizedRemoteTrigger: Not able to set auth for remote Jenkins Change By: Ralf Loesche Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51734) sessionTimeout isn't be honoured
Title: Message Title Alejandro Ruiz commented on JENKINS-51734 Re: sessionTimeout isn't be honoured Hi! Is there any update on this? Is it possible to workaround this using Groovy init scripts? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56945) Pipeline suddenly terminated when running in parallel: java.io.NotSerializableException: groovy.util.slurpersupport.NodeChild
Title: Message Title Cong Ha Minh updated an issue Jenkins / JENKINS-56945 Pipeline suddenly terminated when running in parallel: java.io.NotSerializableException: groovy.util.slurpersupport.NodeChild Change By: Cong Ha Minh Summary: Pipeline suddenly terminated when running in parallel: java.io.NotSerializableException: groovy.util.slurpersupport.NodeChild Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56945) Pipeline terminated when running java.io.NotSerializableException: groovy.util.slurpersupport.NodeChild
Title: Message Title
Cong Ha Minh created an issue
Jenkins / JENKINS-56945
Pipeline terminated when running java.io.NotSerializableException: groovy.util.slurpersupport.NodeChild
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
exception.png, log.txt
Components:
pipeline
Created:
2019-04-09 08:23
Environment:
jenkins 2.164.1 Pipeline 2.6 Pipeline: API 2.33 Pipeline: Job 2.32
Labels:
plugin pipeline
Priority:
Major
Reporter:
Cong Ha Minh
I have a pipline job written by scripted pipeline, in my pipline, i used parallel stage as below
// groovy
def unitTestCodeCoverageAndSonarQubeScan(buildType) {
stage("Unit Test & Code Coverage Test") {
try {
echo "code coverage started"
sh './build.sh coverage'
echo "code coverage done"
publishHTML([
allowMissing : false,
alwaysLinkToLastBuild: false,
keepAll : true,
reportDir: 'cicd/target/jacoco-aggregate-report/',
reportFiles : 'index.html',
reportName : 'Code-Coverage-Report',
reportTitles :
[JIRA] (JENKINS-56944) Sort tags in git-parameter plugin
Title: Message Title Flemming Steffensen created an issue Jenkins / JENKINS-56944 Sort tags in git-parameter plugin Issue Type: Bug Assignee: Boguslaw Klimas Components: git-parameter-plugin Created: 2019-04-09 08:06 Environment: Jenkins 2.170 Git Parameter Plug-in 0.9.10 Priority: Minor Reporter: Flemming Steffensen Sort the tags for the git parameter plugin. For projects with many tags the current UI makes finding the right tag very difficult. Currently, no matter what sort mode I select, of the available five sort modes: None, Assending Smart, Descending Smart, Assenting or Descending I get the same semi-ordered list of tags: 0.1.3-7 0.1.3-8 0.0.0-0 0.1.3-8_Test_Build 0.1.3-7_Test_Build Interestingly, if I add a tag similar to 0.1.3-8_Test_Build, it will sink to the bottom, and if I add one similar to 0.1.3-8, it will rise to the top - but both top and bottom sections are not sorted. It does not seem like the order is related to the tag creation order, but just in case it's interesting, the tags were added to the (Bitbucket) repository in the following order, to commits in the repository that progress naturally in time: 0.0.0-0 0.1.3-7_Test_Build 0.1.3-7
[JIRA] (JENKINS-56938) Impossible to use system nodejs from a container image
Title: Message Title Nikolas Falco commented on JENKINS-56938 Re: Impossible to use system nodejs from a container image What di you mean for "node configuration management"? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56922) FolderConfigFileAction.doShow NullPointerException
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-56922 FolderConfigFileAction.doShow NullPointerException Change By: Dominik Bartholdi Priority: Major Trivial Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56023) JobConfigHistory plugin does not display Folder configs correctly
Title: Message Title Jochen A. Fürbacher resolved as Fixed Fixed in 2.20. Jenkins / JENKINS-56023 JobConfigHistory plugin does not display Folder configs correctly Change By: Jochen A. Fürbacher Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49301) The Move action does not move job config history also
Title: Message Title Jochen A. Fürbacher resolved as Fixed Fixed in 2.20. Jenkins / JENKINS-49301 The Move action does not move job config history also Change By: Jochen A. Fürbacher Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45821) JobConfigHistory is flooded by pipeline steps
Title: Message Title Jochen A. Fürbacher resolved as Fixed Fixed in 2.20. Jenkins / JENKINS-45821 JobConfigHistory is flooded by pipeline steps Change By: Jochen A. Fürbacher Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
