[JIRA] (JENKINS-57383) Exception thrown when testing proxy configuration
Title: Message Title Oleg Nenashev commented on JENKINS-57383 Re: Exception thrown when testing proxy configuration Hi Manet Maloo To unblock yourself, you can download an experimental war from https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.185-rc28456.53cd71780d2d/ > When fixed please add a test case to ensure that proxy connectivity is tested as part of CI. Fair point, please create a Jira ticket for 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199165.1557396422000.6190.1562736720350%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57383) Exception thrown when testing proxy configuration
Title: Message Title Manet Maloo edited a comment on JENKINS-57383 Re: Exception thrown when testing proxy configuration When fixed please add a test case to ensure that proxy connectivity is tested as part of CI. This issue is blocking the release of our project. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199165.1557396422000.6178.1562736300410%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58397) Error in Jenkins home screen as "java.lang.AssertionError: InstanceIdentity is missing its singleton"
Title: Message Title Subramanya Jagannath updated an issue Jenkins / JENKINS-58397 Error in Jenkins home screen as "java.lang.AssertionError: InstanceIdentity is missing its singleton" Change By: Subramanya Jagannath Priority: Critical Blocker 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200522.1562661058000.6175.1562732880102%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58353) New jenkins job doesn't get added to the Dashboard view using Python Jenkins
Title: Message Title Vineeth Karkad commented on JENKINS-58353 Re: New jenkins job doesn't get added to the Dashboard view using Python Jenkins Hi Jan, If you could spare some time; Would you mind having a look? Thanks in advance. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200468.1562310678000.6174.1562732460107%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58417) Include original build number when continuously restarting the build
Title: Message Title hhkkss updated an issue Jenkins / JENKINS-58417 Include original build number when continuously restarting the build Change By: hhkkss Labels: multi-branch pipeline stage-restart-improvements 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200544.1562731946000.6172.1562732040060%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58417) Include parent build number when continuously restarting the build
Title: Message Title hhkkss created an issue Jenkins / JENKINS-58417 Include parent build number when continuously restarting the build Issue Type: New Feature Assignee: Unassigned Components: pipeline Created: 2019-07-10 04:12 Priority: Major Reporter: hhkkss There is option to Restart from Stage in the multi branch pipeline where we can restart specific build number from specific stage. When restarting the build, in the logs its giving you the parent build number saying Restarted from build #[buildNO]. Assume I restarted a stage from build number 10, so the current build number become 11 and the logs says Restarted from build #10. but, there can be a situation I want to restart the build number 11 again. then the logs says Restarted from build #11. however there is no log or any other place that I can catch my original build number (10) because my original build started from 10. Is it possible to add a log or something like Original build NO where we can get actual build number (in my scenario build number 10) , so whenever we wanted to capture the original build number (Build number which was originally initiated)? Or is there any place that I can get this build number 10? Add Comment
[JIRA] (JENKINS-58417) Include original build number when continuously restarting the build
Title: Message Title hhkkss updated an issue Jenkins / JENKINS-58417 Include original build number when continuously restarting the build Change By: hhkkss Summary: Include parent original build number when continuously restarting the 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200544.1562731946000.6171.1562731980167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Title: Message Title
Basil Crow commented on JENKINS-53775
Re: FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Thinking about this some more, the fix might be even simpler. The Dynamic DSL already supports the new-style property. So all that we need to do in Job DSL is deprecated concurrentBuilds for Pipeline jobs and encourage users to migrate to the new property via the Dynamic DSL. In other words, users should convert this syntax …
concurrentBuild false
… to this syntax …
properties {
disableConcurrentBuilds()
}
I confirmed that this generates the new-style XML and that the "Do not allow concurrent builds" was checked when I viewed the generated job in the Jenkins UI.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194284.1537930113000.6169.1562729460245%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Title: Message Title Basil Crow commented on JENKINS-53775 Re: FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin I verified my understanding of the above by checking config.xml after Job DSL had generated the job with concurrentBuild false. It had the false attribute. I then checked how this had been deserialized in the Script Console: println job.@concurrentBuild println job.concurrentBuild This printed null and false, which was what I expected. The field had been set to null, and the getter was instead relying on the property. Next, I called job.save() from the Script Console and checked the contents of config.xml again. Now, false was gone. In its place, in the properties section was . Based on the above, I think the fix should be for Job DSL to generate the property rather than setting the deprecated concurrentBuild field. In other words, there seems to be a race in converting the deprecated field to the new-style property. If Job DSL simply used the new-style property in the first place, we would avoid the race and therefore we wouldn't put Pipeline in a pathological state that ultimate results in a FileNotFoundException. Daniel Spilker, do you have any concerns with this approach? If not, I will prepare a PR. 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. To view this discussion on the web visit
[JIRA] (JENKINS-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Title: Message Title
Basil Crow commented on JENKINS-53775
Re: FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Here is the behavior I have observed:
A WorkflowJob is created using Job DSL with concurrentBuilds false.
The job starts running.
Another build of the WorkflowJob is scheduled (due to an SCM commit) but remains in the queue, blocked on the first build.
A Job DSL job runs again and updates the above WorkflowJob's job definition.
At this point, what should be impossible happens: the second build starts running concurrently with the first build (even though concurrentBuilds is false in the DSL!). I can clearly see both running in the Jenkins classic UI.
The first build fails with the java.io.FileNotFoundException mentioned above (program.dat (No such file or directory)).
Here is some background information. When Job DSL creates a pipeline job with concurrentBuilds false, it emits the following XML in the flow definition:
false
Now, note that this field is deprecated in WorkflowJob:
/** @deprecated replaced by {@link DisableConcurrentBuildsJobProperty} */
private @CheckForNull Boolean concurrentBuild;
In fact, the getter and setter in WorkflowJob use this deprecated field just to set a DisableConcurrentBuildsJobProperty property on the job:
@Exported
@Override public boolean isConcurrentBuild() {
return getProperty(DisableConcurrentBuildsJobProperty.class) == null;
}
[...]
public void setConcurrentBuild(boolean b) throws IOException {
concurrentBuild = null;
boolean propertyExists = getProperty(DisableConcurrentBuildsJobProperty.class) != null;
// If the property exists, concurrent builds are disabled. So if the argument here is true and the
// property exists, we need to remove the property, while if the argument is false and the property
// does not exist, we need to add the property. Yay for flipping boolean values around!
if (propertyExists == b) {
BulkChange bc = new BulkChange(this);
try {
removeProperty(DisableConcurrentBuildsJobProperty.class);
if (!b) {
addProperty(new DisableConcurrentBuildsJobProperty());
}
bc.commit();
} finally {
bc.abort();
}
}
}
[JIRA] (JENKINS-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Title: Message Title Basil Crow commented on JENKINS-53775 Re: FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin Nikita Bochenko and Will Freeman, I made an interesting observation today. I've only seen this problem on jobs where Job DSL was setting concurrentBuild false. I've never seen the problem on jobs where concurrentBuild is set to true. Does this match your experience? It seems too uncanny to be a coincidence. And whenever I hit this bug, the two jobs seem to in fact be running concurrently, which "should" never happen because concurrentBuild is set to false. I wonder if this could actually be a Jenkins core issue, where two jobs are scheduled to run concurrently (even though they shouldn't be) and later trample on each other. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194284.1537930113000.6151.1562723220323%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57383) Exception thrown when testing proxy configuration
Title: Message Title Manet Maloo commented on JENKINS-57383 Re: Exception thrown when testing proxy configuration When fixed please add a test case to ensure that proxy connectivity is tested as part of CI. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199165.1557396422000.6136.1562722380334%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58416) Support sending deployment information to Jira
Title: Message Title Rafal Myslek created an issue Jenkins / JENKINS-58416 Support sending deployment information to Jira Issue Type: New Feature Assignee: Lenin Raj Rajasekaran Components: atlassian-jira-software-cloud-plugin Created: 2019-07-10 01:03 Priority: Minor Reporter: Rafal Myslek Support sending deployment information to Jira Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58088) trim the spaces in string parameter
Title: Message Title Aakash Kanvinde started work on JENKINS-58088 Change By: Aakash Kanvinde 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200129.156093211.6090.1562712000324%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58088) trim the spaces in string parameter
Title: Message Title Aakash Kanvinde stopped work on JENKINS-58088 Change By: Aakash Kanvinde Status: In Progress Open 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200129.156093211.6092.1562712000351%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43814) Password parameters should be hidden in pipeline logs by default
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-43814 Password parameters should be hidden in pipeline logs by default Change By: Jesse Glick Component/s: credentials-binding-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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181331.1493108836000.6075.1562710440237%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57717) showRawYaml doesn't work inside podTemplate
Title: Message Title Jesse Glick edited a comment on JENKINS-57717 Re: showRawYaml doesn't work inside podTemplate bq. When passing this parameter as env variable to the pod: name and value (taken from the password parameter)There is no supported way to do this currently: JENKINS- 36007 43814 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199660.1559055292000.6070.1562710380458%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57717) showRawYaml doesn't work inside podTemplate
Title: Message Title Jesse Glick resolved as Won't Do Jenkins / JENKINS-57717 showRawYaml doesn't work inside podTemplate Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199660.1559055292000.6073.1562710380554%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43814) Password parameters should be hidden in pipeline logs by default
Title: Message Title Jesse Glick commented on JENKINS-43814 Re: Password parameters should be hidden in pipeline logs by default proposed a mechanism by which it could be implemented This is actually possible now via TaskListenerDecorator, I think. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181331.1493108836000.6063.1562710320160%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57717) showRawYaml doesn't work inside podTemplate
Title: Message Title Jesse Glick commented on JENKINS-57717 Re: showRawYaml doesn't work inside podTemplate When passing this parameter as env variable to the pod: name and value (taken from the password parameter) There is no supported way to do this currently: JENKINS-36007 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199660.1559055292000.6061.1562710260150%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57830) Better default for PodTemplateStep.label
Title: Message Title Jesse Glick updated JENKINS-57830 Jenkins / JENKINS-57830 Better default for PodTemplateStep.label 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199786.155961517.6055.1562709720088%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36776) Support Windows Server Containers
Title: Message Title Guillaume Egles commented on JENKINS-36776 Re: Support Windows Server Containers Any update? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172815.1468881746000.5994.1562709421420%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58415) Google Play Android Publisher Plugin - folder level credential setup not working
Title: Message Title Lu Shen created an issue Jenkins / JENKINS-58415 Google Play Android Publisher Plugin - folder level credential setup not working Issue Type: Bug Assignee: Christopher Orr Attachments: image-2019-07-09-16-05-29-520.png Components: credentials-plugin, google-play-android-publisher-plugin Created: 2019-07-09 21:09 Environment: Jenkins 2.121.2 Google Play Android Publisher Plugin 1.8 Credentials Plugin 1.18 Folders Plugin 6.5.1 Priority: Critical Reporter: Lu Shen A google play service account has been set up. In Jenkins added a folder level credential of kind “Google Service Account from private key” but the project within that folder cannot find the credentials. See the attachment for the error - a folder credential was created at this point. If the credential of kind “Google Service Account from private key” is set up at global level it is visible for the job. We need to use folder level credentials to restrict the access to upload builds to Google play.
[JIRA] (JENKINS-55145) anonymous class org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1
Title: Message Title Nikolas Falco commented on JENKINS-55145 Re: anonymous class org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1 No, i suppose they still have to fix. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196212.1544612846000.5946.1562705520104%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55145) anonymous class org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1
Title: Message Title Nikolas Falco commented on JENKINS-55145 Re: anonymous class org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1 No, i suppose they still have to fix. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196212.1544612846000.5944.1562705470168%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55145) anonymous class org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1
Title: Message Title M Fadin edited a comment on JENKINS-55145 Re: anonymous class org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1 on version [Jenkins ver. 2.176.1|https://jenkins.io/] and still keep getting this issue in the logs. [~nfalco] have you found a fix for this 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196212.1544612846000.5942.1562704800084%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55145) anonymous class org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1
Title: Message Title M Fadin commented on JENKINS-55145 Re: anonymous class org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1 on version Jenkins ver. 2.176.1 and still keep getting this issue in the logs. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196212.1544612846000.5940.1562704740099%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58414) Property of object, which extends Map, couldn't be accessed
Title: Message Title
Dicom J created an issue
Jenkins / JENKINS-58414
Property of object, which extends Map, couldn't be accessed
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2019-07-09 20:34
Priority:
Blocker
Reporter:
Dicom J
Code (also used within library):
class MyMap extends java.util.LinkedHashMap {
public final String foobar
MyMap(Map map) {
super(map)
this.foobar = 'foobar'
}
def myFooBar() {
return this.foobar
}
}
node {
def m = new MyMap([foo: 'bar', bar: 'foo'])
print "bar=${m.bar}"
print "foo=${m.foo}"
print "foobar=${m.foobar}"
print "foobar=${m.myFooBar()}"
}
Result:
[Pipeline] node
Running on Jenkins in /build/workspace
[Pipeline] {
[Pipeline] echo
bar=foo
[Pipeline] echo
foo=bar
[Pipeline] echo
foobar=null
[Pipeline] echo
foobar=null
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS
Expected: 'foobar' value printed Conceptually and most likely overloaded getProperty(name) method has a bug...
[JIRA] (JENKINS-58193) EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-58193 Re: EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version the fix for windows will be in 1.44.2, can you test the build from master ? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200248.1561491352000.5932.1562703840274%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57717) showRawYaml doesn't work inside podTemplate
Title: Message Title Oliver Nocon commented on JENKINS-57717 Re: showRawYaml doesn't work inside podTemplate PR addressed the issue that showRawYaml: false did not take effect inside a Jenkinsfile. It has been merged, thus the issue can be closed. Issue was in a job with a password parameter. When passing this parameter as env variable to the pod: name and value (taken from the password parameter) were printed to the log. Now, using showRawYaml: false this can be prevented. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199660.1559055292000.5936.1562703840395%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58404) Avoid cropping of build numbers in diagramms at high build numbers
Title: Message Title Ulli Hafner commented on JENKINS-58404 Re: Avoid cropping of build numbers in diagramms at high build numbers A similar problem is visible in JENKINS-56264. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200529.1562677006000.5929.1562703780115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Jeff Thompson commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins Inspired by Pavel Roskin's patch, I submitted a PR about this issue: https://github.com/jenkinsci/jenkins/pull/4107 If anyone affected by this issue would like to review, comment, or especially test that proposal, please do. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.5908.1562703720467%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58403) Issue marked as new when the issue did exist in a previous build but on a different line
Title: Message Title Ulli Hafner commented on JENKINS-58403 Re: Issue marked as new when the issue did exist in a previous build but on a different line The comparison is using a two pass algorithm: in the first pass the properties of the warning are compared. If one property differs (e.g., line number) then this warning is moved to a second pass. In the second pass, the actual code is compared. This is currently done by checking the context above and below the warning (5 lines). Did the content (or whitespace) in the surrounding lines change? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200528.1562672143000.5906.1562703480199%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58413) Job for running UFT tests that located inside folder - inject to Octane run wrong UFT report link
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-58413 Job for running UFT tests that located inside folder - inject to Octane run wrong UFT report link Issue Type: Bug Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2019-07-09 20:14 Priority: Minor Reporter: 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. To view this discussion on the web visit
[JIRA] (JENKINS-57830) Better default for PodTemplateStep.label
Title: Message Title Jesse Glick started work on JENKINS-57830 Change By: Jesse Glick 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199786.155961517.5894.1562702958395%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57830) Better default for PodTemplateStep.label
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-57830 Better default for PodTemplateStep.label Change By: Jesse Glick Assignee: Carlos Sanchez 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199786.155961517.5893.1562702950167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58388) `report` link in monitoring plugin description doesn't work
Title: Message Title evernat updated JENKINS-58388 Reproduced in the Available and Updated tabs of plugin manager. This link works in the Installed tab after install, but it is currently escaped and broken when it comes from the update center (http://updates.jenkins-ci.org/update-center.json). Fixed by https://github.com/jenkinsci/monitoring-plugin/commit/d6187c616b4d1eefcbacde9b580e4c0bfff1d0c3 Jenkins / JENKINS-58388 `report` link in monitoring plugin description doesn't work Change By: evernat Status: Open 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. To view this discussion on the web visit
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Devin Nusbaum commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head I have also seen this occasionally on ci.jenkins.io, but have no idea about root cause. Does anyone have a minimal Jenkinsfile that can consistently reproduce the issue? If no one has that, then the next best thing would be a build folder for a build that failed with such an error. The relevant information to look for would be whether the flow node mentioned in the exception really was missing or if it is present on disk but could not be found or loaded for some other reason. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196374.1545361815000.5873.1562702580407%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58408) Jenkins configuration lost after safeRestart | Restart
Title: Message Title Omar Velazquez edited a comment on JENKINS-58408 Re: Jenkins configuration lost after safeRestart | Restart Root cause located at initialization scripts, thanks Just clarify:From Dockerfile:COPY x_y.groovy /usr/share/jenkins/ref/init.groovy.d/x_y.groovy[https://wiki.jenkins.io/display/JENKINS/Configuring+Jenkins+upon+start+up][https://wiki.jenkins.io/display/JENKINS/Post-initialization+script] 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200535.1562697339000.5871.1562702280047%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58408) Jenkins configuration lost after safeRestart | Restart
Title: Message Title Omar Velazquez closed an issue as Fixed Root cause located at initialization scripts, thanks Jenkins / JENKINS-58408 Jenkins configuration lost after safeRestart | Restart Change By: Omar Velazquez Status: Open Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200535.1562697339000.5870.1562701620093%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58412) Job connot be aborted
Title: Message Title Thomas Reinicke created an issue Jenkins / JENKINS-58412 Job connot be aborted Issue Type: Bug Assignee: Thomas Reinicke Components: exam-plugin Created: 2019-07-09 19:39 Priority: Minor Reporter: Thomas Reinicke When Jenkins is waiting to connect to EXAM, the job cannot be aborted. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58411) make connection timeout configurable
Title: Message Title Thomas Reinicke created an issue Jenkins / JENKINS-58411 make connection timeout configurable Issue Type: Improvement Assignee: Thomas Reinicke Components: exam-plugin Created: 2019-07-09 19:38 Priority: Minor Reporter: Thomas Reinicke Make connection timeout configurable on ManageJenkins site. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57099) Configuration of EXAM Installation not loaded
Title: Message Title Thomas Reinicke closed an issue as Fixed Jenkins / JENKINS-57099 Configuration of EXAM Installation not loaded Change By: Thomas Reinicke Status: Resolved 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198844.170946000.5867.1562700840399%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57100) Improve Communication with REST-API
Title: Message Title Thomas Reinicke closed an issue as Fixed Jenkins / JENKINS-57100 Improve Communication with REST-API Change By: Thomas Reinicke Status: Resolved 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198845.171351000.5865.1562700840373%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51707) Failure - java.net.SocketException: Connection reset
Title: Message Title Ty Connell commented on JENKINS-51707 Re: Failure - java.net.SocketException: Connection reset Okay, this is a bit of a thread necro, but this seemed like the most appropriate place to post. I also was getting the "java.net.SocketException: Connection reset" error, but it was not due to a proxy error as suggested here. The error was caused by our router, a Meraki, and something called "Advanced Malware Protection (AMP)" in combination with plugins downloaded from http (vs. http*s*) mirrors. The truly annoying part is that it silently crushes your download after it's started, making it look like the mirror is somehow at fault. The issue is discussed [over at the Meraki site.|https://community.meraki.com/t5/Security-SD-WAN/AMP-IDS-seems-to-block-file-download-without-logging-to-security/td-p/10222] 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191149.1528201981000.5861.1562700600235%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58410) Plot plugin csv file not getting created in project root directory
Title: Message Title
Jatin Mehta updated an issue
Jenkins / JENKINS-58410
Plot plugin csv file not getting created in project root directory
Change By:
Jatin Mehta
From the [plugin wiki|https://wiki.jenkins.io/display/JENKINS/Plot+Plugin]: {{csvFileName (string, default: "$ROOT_DIR/plot-.csv") The name of the CSV file that persists the plots data. The CSV file is stored in the projects root directory. This is different from the source CSVle that can be used as a source for the plot.}} However, I don't see the {{csvFileName}} in root directory or anywhere in the workspace. I do see the {{CSVle}} file in the root of the workspace directory.Here is the Jenkins snippet:{code:java}plot csvFileName: '$WORKSPACE/xxx.csv',group: ' HAThroughput_Plots yyy_Plots ', keepRecords: true, //latest data point propertiesSeries: [[file: 'yyyReport.properties', label: '']], style: 'line', title: 'yyy_Plot', yaxis: 'abc', yaxisMaximum: '20', yaxisMinimum: '0'{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.
To view this discussion on the web visit
[JIRA] (JENKINS-58410) Plot plugin csv file not getting created in project root directory
Title: Message Title Jatin Mehta updated an issue Jenkins / JENKINS-58410 Plot plugin csv file not getting created in project root directory Change By: Jatin Mehta Priority: Minor Major 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200537.156269842.5846.1562698500351%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58410) Plot plugin csv file not getting created in project root directory
Title: Message Title Jatin Mehta created an issue Jenkins / JENKINS-58410 Plot plugin csv file not getting created in project root directory Issue Type: Bug Assignee: Veaceslav Gaidarji Components: plot-plugin Created: 2019-07-09 18:53 Environment: Jenkins 2.176.1, Linux version 2.6.32-696.18.7.el6.x86_64 (mockbu...@c1bl.rdu2.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-18) (GCC) ), plot plugin 2.1.1 Labels: pipeline user-experience configuration csvFileName plot Priority: Minor Reporter: Jatin Mehta From the plugin wiki: csvFileName (string, default: "$ROOT_DIR/plot-.csv") The name of the CSV file that persists the plots data. The CSV file is stored in the projects root directory. This is different from the source CSVle that can be used as a source for the plot. However, I don't see the csvFileName in root directory or anywhere in the workspace. I do see the CSVle file in the root of the workspace directory. Here is the Jenkins snippet: plot csvFileName: '$WORKSPACE/xxx.csv',group: 'HAThroughput_Plots', keepRecords: true, //latest data point propertiesSeries: [[file: 'yyyReport.properties', label: '']], style: 'line', title: 'yyy_Plot', yaxis: 'abc', yaxisMaximum: '20', yaxisMinimum: '0'
[JIRA] (JENKINS-58409) java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name
Title: Message Title
Tobias Herrmann Hinz updated an issue
Jenkins / JENKINS-58409
java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name
Change By:
Tobias Herrmann Hinz
hi, first of all: i'm so sorry to open this (and another ticket). really appreciate your hard work and totally love it. i hope the following is not a n00b-misconfiguration-error-and-a-again-duplicate-ticket of someone who did not read the manual. but i'm out of ideas and this is blocking me (and around 400 developers) to go one step further and push our CICD to a more self managed platform. here is the issue: when running multiple concurrent builds of specific job (with declarative definition of the build pods jenkins seem to freak out and deny the connection from build slaves to the master: (from the jnlp container): {code:java}client name: brandhub-container-builder-834z6-3bmbk at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: brandhub-container-builder-834z6-3bmbk at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748) Suppressed: java.nio.channels.ClosedChannelException ... 7 more{code}when running only one build "it works". the multiple concurrent builds may get finished after some time. one need to be patient and on the lucky side. i searched the internet (and this jira) already and for quite some time. could not find help yet. ACHTUNG: when putting some other pod templates inline/declarative i get the same error. but if i define them in the configuration ui part in jenkins the builds are more stable and i got more reliable and satisfying results. tried it also with this builds but that trick did not help. ... here are some logs and content of related files,
[JIRA] (JENKINS-51248) Check for Invalid Names/Labels During Template Creation
Title: Message Title Jesse Glick commented on JENKINS-51248 Re: Check for Invalid Names/Labels During Template Creation This validation introduced the constraint that PodTemplateStepExecution.label contain only a single value, rather than a label set. In this context (as opposed to KubernetesCloud configuration) that is probably fine, though it means that the GUI label Labels was misleading. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190573.1525973235000.5836.1562698264642%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58296) Projects are triggered twice when using File Parameter and Firefox 67
Title: Message Title Josh Nutzman commented on JENKINS-58296 Re: Projects are triggered twice when using File Parameter and Firefox 67 I've also had this issue on Firefox/Mac 68.0 Jenkins 2.176.1 Chrome 75.0.3770.100 worked correctly. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200361.1562053852000.5831.1562697780271%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58409) java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name
Title: Message Title Tobias Herrmann Hinz updated an issue Jenkins / JENKINS-58409 java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name Change By: Tobias Herrmann Hinz Priority: Minor Critical 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200536.1562697471000.5833.1562697780298%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58409) java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name
Title: Message Title
Tobias Herrmann Hinz updated an issue
Jenkins / JENKINS-58409
java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name
Change By:
Tobias Herrmann Hinz
hi, when running multiple concurrent builds of specific job (with declarative definition of the build pods jenkins seem to freak out and deny the connection from build slaves to the master: (from the jnlp container): {code:java}client name: brandhub-container-builder-834z6-3bmbk at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: brandhub-container-builder-834z6-3bmbk at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748) Suppressed: java.nio.channels.ClosedChannelException ... 7 more{code}when running only one build "it works". the multiple concurrent builds may get finished after some time. one need to be patient and on the lucky side. i searched the internet (and this jira) already and for quite some time. could not find help yet. ACHTUNG: when putting some other pod templates inline/declarative i get the same error. but if i define them in the configuration ui part in jenkins the builds are more stable and i got more reliable and satisfying results. tried it also with this builds but that trick did not help. ... here are some logs and content of related files, also some version: - k8s: 1.11.x - jenkins: jenkins/jenkins:2.84 (10Gi Memory, 2000m cpu) - slave: jenkins/jnlp-slave:3.29-1 (3Gi and 200m cpu)- plugin version - kubernetes:1.16.4 THE JENKINSFILE: {code:java}pipeline { agent {kubernetes { label 'brandhub-container-builder' yamlFile 'api/.build.yaml'} } stages {stage('build and push container') { steps {
[JIRA] (JENKINS-58409) java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name
Title: Message Title
Tobias Herrmann Hinz updated an issue
Jenkins / JENKINS-58409
java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name
Change By:
Tobias Herrmann Hinz
hi, when running multiple concurrent builds of specific job (with declarative definition of the build pods jenkins seem to freak out and deny the connection from build slaves to the master: (from the jnlp container): {code:java}client name: brandhub-container-builder-834z6-3bmbk at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: brandhub-container-builder-834z6-3bmbk at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748) Suppressed: java.nio.channels.ClosedChannelException ... 7 more{code}when running only one build "it works". the multiple concurrent builds may get finished after some time. one need to be patient and on the lucky side. i searched the internet (and this jira) already and for quite some time. could not find help yet. ACHTUNG: when putting some other pod templates inline/declarative i get the same error. but if i define them in the configuration ui part in jenkins the builds are more stable and i got more reliable and satisfying results. tried it also with this builds but that trick did not help. ... here are some logs and content of related files, also some version: k8s: 1.11.x jenkins: jenkins/jenkins:2.84 (10Gi Memory, 2000m cpu)kubernetes:1.16.4 THE JENKINSFILE: {code:java}pipeline { agent {kubernetes { label 'brandhub-container-builder' yamlFile 'api/.build.yaml'} } stages {stage('build and push container') { steps { container(name: 'kaniko', shell: '/busybox/sh') {
[JIRA] (JENKINS-58409) java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name
Title: Message Title Tobias Herrmann Hinz created an issue Jenkins / JENKINS-58409 java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-07-09 18:37 Priority: Minor Reporter: Tobias Herrmann Hinz hi, when running multiple concurrent builds of specific job (with declarative definition of the build pods jenkins seem to freak out and deny the connection from build slaves to the master: (from the jnlp container): client name: brandhub-container-builder-834z6-3bmbk at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474) Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: brandhub-container-builder-834z6-3bmbk at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at
[JIRA] (JENKINS-58408) Jenkins configuration lost after safeRestart | Restart
Title: Message Title
Omar Velazquez updated an issue
Jenkins / JENKINS-58408
Jenkins configuration lost after safeRestart | Restart
Change By:
Omar Velazquez
Jenkins configuration is lost after safeRestart or Restart, is happening in all our Jenkins instancesConfiguration that is lost: * Global security -> Matrix-based security : users and groups are missing, just 'original' configuration remains, I mean, all those users and groups generated at first time when Jenkins instance is provisioned. * Master executor changed from 1 to 0From script console: "ls -lrt /var/jenkins_home/".execute().text*Before restart:*{color:#de350b}drwxr-xr-x 4 root root 4096 Jul 9 12:20 backups{color} {color:#de350b}drwxr-xr-x 154 root root 28672 Jul 9 12:42 plugins{color} {color:#de350b}drwxr-xr-x 4 root root 4096 Jul 9 12:45 users{color} {color:#de350b}drwxr-xr-x 4 root root 4096 Jul 9 12:45 jobs{color} {color:#de350b}-rw-r--r-- 1 root root 131 Jul 9 12:45 queue.xml.bak{color} {color:#ff}-rw-r--r-- 1 root root 16343 *Jul 9 12:45* *config.xml*{color} -rw-r--r-- 1 root root 7 Jul 9 12:45 jenkins.install.InstallUtil.lastExecVersion -rw-r--r-- 1 root root 0 Jul 9 13:03 ThinBackup Worker Thread.log*After rertart restart :*{color:#de350b}drwxr-xr-x 4 root root 4096 Jul 9 12:20 backups{color} {color:#de350b}drwxr-xr-x 154 root root 28672 Jul 9 12:42 plugins{color} {color:#de350b}drwxr-xr-x 4 root root 4096 Jul 9 12:45 users{color} {color:#de350b}drwxr-xr-x 4 root root 4096 Jul 9 12:45 jobs{color} {color:#de350b}-rw-r--r-- 1 root root 131 Jul 9 13:06 queue.xml.bak{color} -rw-r--r-- 1 root root 156 Jul 9 13:06 hudson.model.UpdateCenter.xml -rw-r--r-- 1 root root 907 Jul 9 13:06 nodeMonitors.xml -rw-r--r-- 1 root root 121 Jul 9 13:06 de.theit.jenkins.crowd.CrowdSecurityRealm.xml -rw-r--r-- 1 root root 7 Jul 9 13:06 jenkins.install.InstallUtil.lastExecVersion -rw-r--r-- 1 root root 0 Jul 9 13:06 ThinBackup Worker Thread.log -rw-r--r-- 1 root root 262 Jul 9 13:06 jenkins.model.JenkinsLocationConfiguration.xml -rw-r--r-- 1 root root 271 Jul 9 13:06 hudson.tasks.Mailer.xml -rw-r--r-- 1 root root 1401 Jul 9 13:06 hudson.plugins.emailext.ExtendedEmailPublisher.xml -rw-r--r-- 1 root root 747 Jul 9 13:06 com.cloudbees.jenkins.plugins.bitbucket.endpoints.BitbucketEndpointConfiguration.xml -rw-r--r-- 1 root root 932 Jul 9 13:06 hudson.plugins.sonar.SonarGlobalConfiguration.xml -rw-r--r-- 1 root root 686 Jul 9 13:06 hudson.plugins.sonar.SonarRunnerInstallation.xml -rw-r--r-- 1 root root 228 Jul 9 13:06 javaposse.jobdsl.plugin.GlobalJobDslSecurityConfiguration.xml {color:#de350b}-rw-r--r-- 1 root root 16426 *Jul 9 13:06* *config.xml*{color} Thanks in advance
[JIRA] (JENKINS-58408) Jenkins configuration lost after safeRestart | Restart
Title: Message Title
Omar Velazquez updated an issue
Jenkins / JENKINS-58408
Jenkins configuration lost after safeRestart | Restart
Change By:
Omar Velazquez
Jenkins configuration is lost after safeRestart or Restart, is happening in all our Jenkins instancesConfiguration that is lost: * Global security -> Matrix-based security : users and groups are missing, just 'original' configuration remains, I mean, all those users and groups generated at first time when Jenkins instance is provisioned. * Master executor changed from 1 to 0From script console: "ls -lrt /var/jenkins_home/".execute().text ### * Before restart: * {color:#de350b}drwxr-xr-x 4 root root 4096 Jul 9 12:20 backups{color}{color:#de350b}drwxr-xr-x 154 root root 28672 Jul 9 12:42 plugins{color}{color:#de350b}drwxr-xr-x 4 root root 4096 Jul 9 12:45 users{color}{color:#de350b}drwxr-xr-x 4 root root 4096 Jul 9 12:45 jobs{color}{color:#de350b}-rw-r--r-- 1 root root 131 Jul 9 12:45 queue.xml.bak{color}{color:# FF ff }-rw-r--r-- 1 root root 16343 *Jul 9 12:45* *config.xml*{color}-rw-r--r-- 1 root root 7 Jul 9 12:45 jenkins.install.InstallUtil.lastExecVersion-rw-r--r-- 1 root root 0 Jul 9 13:03 ThinBackup Worker Thread.log ### * After restart rertart : * {color:#de350b}drwxr-xr-x 4 root root 4096 Jul 9 12:20 backups{color}{color:#de350b}drwxr-xr-x 154 root root 28672 Jul 9 12:42 plugins{color}{color:#de350b}drwxr-xr-x 4 root root 4096 Jul 9 12:45 users{color}{color:#de350b}drwxr-xr-x 4 root root 4096 Jul 9 12:45 jobs{color}{color:#de350b}-rw-r--r-- 1 root root 131 Jul 9 13:06 queue.xml.bak{color}-rw-r--r-- 1 root root 156 Jul 9 13:06 hudson.model.UpdateCenter.xml-rw-r--r-- 1 root root 907 Jul 9 13:06 nodeMonitors.xml-rw-r--r-- 1 root root 121 Jul 9 13:06 de.theit.jenkins.crowd.CrowdSecurityRealm.xml-rw-r--r-- 1 root root 7 Jul 9 13:06 jenkins.install.InstallUtil.lastExecVersion-rw-r--r-- 1 root root 0 Jul 9 13:06 ThinBackup Worker Thread.log-rw-r--r-- 1 root root 262 Jul 9 13:06 jenkins.model.JenkinsLocationConfiguration.xml-rw-r--r-- 1 root root 271 Jul 9 13:06 hudson.tasks.Mailer.xml-rw-r--r-- 1 root root 1401 Jul 9 13:06 hudson.plugins.emailext.ExtendedEmailPublisher.xml-rw-r--r-- 1 root root 747 Jul 9 13:06 com.cloudbees.jenkins.plugins.bitbucket.endpoints.BitbucketEndpointConfiguration.xml-rw-r--r-- 1 root root 932 Jul 9 13:06 hudson.plugins.sonar.SonarGlobalConfiguration.xml-rw-r--r-- 1 root root 686 Jul 9 13:06 hudson.plugins.sonar.SonarRunnerInstallation.xml-rw-r--r-- 1 root root 228 Jul 9 13:06 javaposse.jobdsl.plugin.GlobalJobDslSecurityConfiguration.xml{color:#de350b}-rw-r--r-- 1 root root 16426 *Jul 9 13:06* *config.xml*{color} Thanks in advance
[JIRA] (JENKINS-58408) Jenkins configuration lost after safeRestart | Restart
Title: Message Title Omar Velazquez created an issue Jenkins / JENKINS-58408 Jenkins configuration lost after safeRestart | Restart Issue Type: Improvement Assignee: Unassigned Components: core, safe-restart Created: 2019-07-09 18:35 Environment: Linux 3a2b97dce7c1 4.9.0-5-amd64 #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) x86_64 GNU/Linux Open JDK v1.8.0_212-b04 Jenkins ver. 2.176.1 Plugin saferestart ver. 0.3 Jenkins Master is running on Docker container Docker image jenkins/jenkins:lts Happening in Master Node Browser: Chrome Version 75.0.3770.100 (Official Build) (64-bit) Labels: jenkins config.xml configuration Priority: Major Reporter: Omar Velazquez Jenkins configuration is lost after safeRestart or Restart, is happening in all our Jenkins instances Configuration that is lost: Global security -> Matrix-based security : users and groups are missing, just 'original' configuration remains, I mean, all those users and groups generated at first time when Jenkins instance is provisioned. Master executor changed from 1 to 0 From script console: "ls -lrt /var/jenkins_home/".execute().text
[JIRA] (JENKINS-57241) Copy Artifact copying files when shouldn't and parameter filter errors
Title: Message Title Kim Abbott updated JENKINS-57241 Jenkins / JENKINS-57241 Copy Artifact copying files when shouldn't and parameter filter errors Change By: Kim Abbott Status: Fixed but Unreleased Closed Released As: n/a 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199004.1556612983000.5818.1562695817814%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57241) Copy Artifact copying files when shouldn't and parameter filter errors
Title: Message Title Kim Abbott commented on JENKINS-57241 Re: Copy Artifact copying files when shouldn't and parameter filter errors I think you are absolutely correct. Thank you for the comment and sorry it has taken me so long to send you 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199004.1556612983000.5815.1562695740210%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26724) "Delete build" and "Delete project" actions are confusingly similar
Title: Message Title Edward Sutton commented on JENKINS-26724 Re: "Delete build" and "Delete project" actions are confusingly similar I am paranoid that when deleting a workspace, I may accidentally delete the job. The Delete Project menu on the left should be harder to access. Perhaps buried in the job's Configure settings might be less risky. Make user type in the job name before deletion is allowed. Both dialogs are basically identical: 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160399.1422786306000.5809.1562695080164%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26724) "Delete build" and "Delete project" actions are confusingly similar
Title: Message Title Edward Sutton updated an issue Jenkins / JENKINS-26724 "Delete build" and "Delete project" actions are confusingly similar Change By: Edward Sutton Attachment: delete-project-vs-workspace.png 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160399.1422786306000.5804.1562694720224%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title
Dicom J updated an issue
Jenkins / JENKINS-58407
Fail to call a Closure stored as a class attribute/field
Change By:
Dicom J
simple groovy code, like this{code:java}class SomeStruct {def aPointerToClosure}node {def st = new SomeStruct()st.aPointerToClosure = { println 'foobar' }st.aPointerToClosure()} {code}and even within groovy library, started yelling the following exception:{code:java}java.lang.IllegalStateException: expected to call SomeStruct.aPointerToClosure but wound up catching org.jenkinsci.plugins.workflow.cps.CpsClosure2.call; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/ at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService.handleMismatch(CpsVmExecutorService.java:117) at {code}The issue's appears as of 2.71 (05 Jul 2019), with 2.70 works properly.[ [ Changelog ](https://plugins.jenkins.io/workflow-cps) | [ https://plugins.jenkins.io/workflow-cps] ] , among other things, states the following:Improvement: Print detailed warnings to the build log when CPS-transformed code is called in a non-CPS context where possible. The warnings link to [https://jenkins.io/redirect/pipeline-cps-method-mismatches/] which gives additional context and some examples of how to fix common issues. (JENKINS-31314) Most likely, this is that "nice improvement"...Whole Stack Trace:{code:java} 11.906 [id=48] WARNING o.j.p.w.cps.CpsVmExecutorService#reportProblem: Unexpected exception in CPS VM thread: CpsFlowExecution[Owner[job/1:job #1]] 11.906 [id=48] WARNING o.j.p.w.cps.CpsVmExecutorService#reportProblem: Unexpected exception in CPS VM thread: CpsFlowExecution[Owner[job/1:job #1]]java.lang.IllegalStateException: expected to call SomeStruct.aPointerToClosure but wound up catching org.jenkinsci.plugins.workflow.cps.CpsClosure2.call; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/ at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService.handleMismatch(CpsVmExecutorService.java:117) at com.cloudbees.groovy.cps.impl.CpsCallableInvocation.checkMismatch(CpsCallableInvocation.java:63) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:94) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:113) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixName(FunctionCallBlock.java:78) 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 com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:83) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163) at
[JIRA] (JENKINS-47498) Select compatible plugin versions using a BOM
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-47498 Select compatible plugin versions using a BOM Change By: Jesse Glick Component/s: bom Component/s: plugin-pom 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185954.1508330794000.5784.1562691720727%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48578) Create BOM for components included into the Core
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-48578 Create BOM for components included into the Core Change By: Jesse Glick Component/s: bom Component/s: core 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187218.151334614.5788.1562691720783%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title
Dicom J created an issue
Jenkins / JENKINS-58407
Fail to call a Closure stored as a class attribute/field
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2019-07-09 16:59
Priority:
Blocker
Reporter:
Dicom J
simple groovy code, like this
class SomeStruct {
def aPointerToClosure
}
node {
def st = new SomeStruct()
st.aPointerToClosure = { println 'foobar' }
st.aPointerToClosure()
}
and even within groovy library, started yelling the following exception:
java.lang.IllegalStateException: expected to call SomeStruct.aPointerToClosure but wound up catching org.jenkinsci.plugins.workflow.cps.CpsClosure2.call; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/ at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService.handleMismatch(CpsVmExecutorService.java:117) at
The issue's appears as of 2.71 (05 Jul 2019), with 2.70 works properly. [Changelog|https://plugins.jenkins.io/workflow-cps], among other things, states the following: Improvement: Print detailed warnings to the build log when CPS-transformed code is called in a non-CPS context where possible. The warnings link to https://jenkins.io/redirect/pipeline-cps-method-mismatches/ which gives additional context and some examples of how to fix common issues. (JENKINS-31314) Most likely, this is that "nice improvement"... Whole Stack Trace:
[JIRA] (JENKINS-30231) Build creates second workspace@2 for non-concurrent build configuration
Title: Message Title Jatin Mehta commented on JENKINS-30231 Re: Build creates second workspace@2 for non-concurrent build configuration Hi Kamil Szuster. I tried that too. With every new build, my Jenkinsfile removes the previous build's workspace. Now, even if I remove the original workspace by hand, in the next build, it still goes on to create the workspace with an @2 suffix. Not sure if Jenkins caches the data (that a workspace xyz was present once upon a time on this node) using which it creates the new workspace (xyz@2) 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164818.1441065243000.5696.1562688611044%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58406) A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.
Title: Message Title
zhu xiaoyang updated an issue
Jenkins / JENKINS-58406
A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.
Change By:
zhu xiaoyang
A pipeline is pending, I just want to continue without any parameters, so I use pipeline API to check process, but it will be returned an error: "parameters is required".Now the request body like :{"id":"2", "parameters":[]} it works well, but the field "parameters" is not used.I guess If we remove "parameters" like \{"id":"2"} , The function can also work well.Perhaps support both different struct is more restful a better choice .
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200531.1562686643000.5651.1562687820061%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58406) A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.
Title: Message Title
zhu xiaoyang updated an issue
Jenkins / JENKINS-58406
A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.
Change By:
zhu xiaoyang
A pipeline is pending, I just want to continue without any parameters, so I use pipeline API to check proceed process , but it will be returned an error: "parameters is required"Now the request body like :{"id":"2", "parameters":[]}it works well, but the field "parameters" is not used.I guess remove "parameters" like \{"id":"2"} is more restful.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200531.1562686643000.5649.1562686980098%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58406) A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.
Title: Message Title
zhu xiaoyang updated an issue
Jenkins / JENKINS-58406
A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.
Change By:
zhu xiaoyang
A pipeline is pending, I just want to continue without any parameters, so I use pipeline API to check process, but it will be returned an error: "parameters is required" . Now the request body like :{"id":"2", "parameters":[]}it works well, but the field "parameters" is not used.I guess remove "parameters" like \{"id":"2"} is more restful.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200531.1562686643000.5650.1562686980140%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58406) A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.
Title: Message Title zhu xiaoyang started work on JENKINS-58406 Change By: zhu xiaoyang 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200531.1562686643000.5648.1562686800088%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58406) A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.
Title: Message Title
zhu xiaoyang created an issue
Jenkins / JENKINS-58406
A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.
Issue Type:
Improvement
Assignee:
zhu xiaoyang
Components:
blueocean-plugin
Created:
2019-07-09 15:37
Labels:
blueocean improvement
Priority:
Minor
Reporter:
zhu xiaoyang
A pipeline is pending, I just want to continue without any parameters, so I use pipeline API to check proceed, but it will be returned an error: "parameters is required" Now the request body like : {"id":"2", "parameters":[]} it works well, but the field "parameters" is not used. I guess remove "parameters" like {"id":"2"} is more restful.
Add Comment
[JIRA] (JENKINS-58048) P4 error - No open file stream in ClientSystemFileCommands.writeFile()
Title: Message Title Andrew Barnish edited a comment on JENKINS-58048 Re: P4 error - No open file stream in ClientSystemFileCommands.writeFile() I'm seeing the following error in linux since plugin version 1.10. 1 0 . Is it the same issue? ERROR: P4: Task Exception: com.perforce.p4java.exception.ConnectionException: No open file stream in ClientSystemFileCommands.writeFile() 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200069.1560779623000.5641.1562686560328%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53053) Add support for readCSV / writeCSV pipeline steps
Title: Message Title Stuart Rowe updated JENKINS-53053 Released as pipeline-utility-steps-plugin 2.3.0 Jenkins / JENKINS-53053 Add support for readCSV / writeCSV pipeline steps Change By: Stuart Rowe Status: Fixed but Unreleased Resolved 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193044.153435115.5635.1562685780115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57299) Add staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods drop/take variants to generic-whitelist
Title: Message Title Stuart Rowe updated JENKINS-57299 Released as release script-security-1.59 Jenkins / JENKINS-57299 Add staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods drop/take variants to generic-whitelist Change By: Stuart Rowe Status: Fixed but Unreleased Resolved 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199065.1556748218000.5633.1562685540582%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57299) Add staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods drop/take variants to generic-whitelist
Title: Message Title Stuart Rowe updated JENKINS-57299 Jenkins / JENKINS-57299 Add staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods drop/take variants to generic-whitelist Change By: Stuart Rowe 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199065.1556748218000.5627.1562685420526%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58405) Backward compatibility of the yaml field merge
Title: Message Title Vincent Latombe updated JENKINS-58405 Jenkins / JENKINS-58405 Backward compatibility of the yaml field merge Change By: Vincent Latombe 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200530.1562684455000.5622.1562684760709%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58405) Backward compatibility of the yaml field merge
Title: Message Title Vincent Latombe started work on JENKINS-58405 Change By: Vincent Latombe 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200530.1562684455000.5617.1562684760550%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58405) Backward compatibility of the yaml field merge
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-58405 Backward compatibility of the yaml field merge Change By: Vincent Latombe Assignee: Carlos Sanchez Vincent Latombe 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200530.1562684455000.5620.1562684760650%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58405) Backward compatibility of the yaml field merge
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-58405 Backward compatibility of the yaml field merge Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-07-09 15:00 Priority: Minor Reporter: Vincent Latombe In 1.15, a feature to Merge pod templates definitions from yaml has been added. This is a change from the previous behaviour, where the yaml definition from the last pod template in the hierarchy was shadowing any inherited pod template. In some case, this could cause some surprises when upgrading. The intent here is to make this feature backward compatible by providing users with the choice to merge or override yaml fragment from parent when defining a pod template. The default behaviour would be to override, to achieve backward compatibility with previous versions. Add Comment
[JIRA] (JENKINS-54714) Allow downloading raw CSV data for external processing
Title: Message Title Niklas Lingenauber commented on JENKINS-54714 Re: Allow downloading raw CSV data for external processing On the Jenkins Master Node I was able to find the CSV file in the job's directory. On the used Jenkins slave I also couldn't find it in the workspace (or elsewhere). It would be helpful if the CSV file could also be found in the workspace of the Jenkins slave, because the CSV file provides more possibilities to further process the data. This would also make it possible to archive the file and make it available to the various users of the Jenkins job. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195515.1542700725000.5610.1562684340432%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58318) Fix GitLabSCMNavigator
Title: Message Title Parichay Barpanda commented on JENKINS-58318 Re: Fix GitLabSCMNavigator One of the important bugs that wasn't caught earlier was when the apiBuilder method of GitLabHelper. The static getCredentials method had a flaw and it never retrieved the Personal Access Token for GitLab Server. I added a member getCredentials method to `GitLabServer` and it now works perfectly. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200426.1562153455000.5606.1562684040043%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58340) docker-plugin-1.1.6 docker cloud does not work with >=ssh-slaves-plugin-1.30.0
Title: Message Title Stephan Watermeyer commented on JENKINS-58340 Re: docker-plugin-1.1.6 docker cloud does not work with >=ssh-slaves-plugin-1.30.0 Hey Nicolas De Loof, just for your information. Peter and myself have discussed the issue on Github and Peter has already a good idea where it problem is. By chance you want to have a look at our discussion? https://github.com/jenkinsci/docker-plugin/issues/740 Maybe this is a quick fix for you. Otherwise... 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200453.1562229896000.5604.1562683260241%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58221) Swarm cannot connect to Jenkins Master provided port:50000 is not reachable
Title: Message Title Joey Khashab closed an issue as Not A Defect Jenkins / JENKINS-58221 Swarm cannot connect to Jenkins Master provided port:5 is not reachable Change By: Joey Khashab Status: Open Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200281.1561577565000.5600.1562683140336%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58221) Swarm cannot connect to Jenkins Master provided port:50000 is not reachable
Title: Message Title Joey Khashab commented on JENKINS-58221 Re: Swarm cannot connect to Jenkins Master provided port:5 is not reachable Basil Crow thanks for your reply, after trying several things, I realized I was passing in `-Dhudson.TcpSlaveAgentListener.hostName=master_ip` into my Jenkins as part of my Chef provisioning for Jenkins master, after putting in the correct IP address for master it seems to be working. Cancelling this 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200281.1561577565000.5599.1562683140305%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58188) Remoting-Kafka-K8s-Coding-Phase-2
Title: Message Title Andrey Falko updated an issue Jenkins / JENKINS-58188 Remoting-Kafka-K8s-Coding-Phase-2 Change By: Andrey Falko Labels: gsoc-2019 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200242.1561472627000.5597.1562682420155%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58193) EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title tapvir virk reopened an issue Hi Raihaan, I just observed, same exception is thrown on WIndows slave. Linux slaves are working fine. Can you please check and provide the fix? Thanks Tapvir Jenkins / JENKINS-58193 EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version Change By: tapvir virk Resolution: Duplicate Status: Closed Reopened 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200248.1561491352000.5595.1562682240487%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30231) Build creates second workspace@2 for non-concurrent build configuration
Title: Message Title Jatin Mehta edited a comment on JENKINS-30231 Re: Build creates second workspace@2 for non-concurrent build configuration [~dnusbaum], thank you for the reply. Makes sense, will do that. However, it will take some time since this problem occurs in a Jenkins environment of which I am not an admin and would need to replicate it locally. Meanwhile, if I could get any pointers, that would be great. EDIT: It doesn't get reproduced right away. It starts occurring only after several builds and hence is kinda hard to reproduce. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164818.1441065243000.5577.1562680740455%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58282) Heath metrics produces serious performance issues
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-58282 Heath metrics produces serious performance issues Change By: Allan BURDAJEWICZ Assignee: Francisco Fernández Allan BURDAJEWICZ 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200346.156197904.5573.1562680620728%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58282) Heath metrics produces serious performance issues
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-58282 Change By: Allan BURDAJEWICZ 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200346.156197904.5570.1562680560332%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58282) Heath metrics produces serious performance issues
Title: Message Title Allan BURDAJEWICZ edited a comment on JENKINS-58282 Re: Heath metrics produces serious performance issues We could have the weather columns Folder health metrics disabled by default when creating new folders or add a system property that could be used to disable it when creating new folders. We could also add a global configuration of Folder metrics so that any new folder that is created follow the global configuration. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200346.156197904.5565.1562679900201%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30231) Build creates second workspace@2 for non-concurrent build configuration
Title: Message Title Jatin Mehta commented on JENKINS-30231 Re: Build creates second workspace@2 for non-concurrent build configuration Devin Nusbaum, thank you for the reply. Makes sense, will do that. However, it will take some time since this problem occurs in a Jenkins environment of which I am not an admin and would need to replicate it locally. Meanwhile, if I could get any pointers, that would be great. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164818.1441065243000.5544.1562678521040%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30231) Build creates second workspace@2 for non-concurrent build configuration
Title: Message Title Devin Nusbaum commented on JENKINS-30231 Re: Build creates second workspace@2 for non-concurrent build configuration Jatin Mehta if you have a consistent way to reproduce the problem from scratch, please file a new issue with full reproduction steps (i.e. download Jenkins 2.176.1, start it up, install plugins X version Y and Z version W, create a Pipeline with the following (ideally minimal) script, etc.). 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164818.1441065243000.5530.1562678280621%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58404) Avoid cropping of build numbers in diagramms at high build numbers
Title: Message Title Niklas Lingenauber updated an issue Jenkins / JENKINS-58404 Avoid cropping of build numbers in diagramms at high build numbers Change By: Niklas Lingenauber Summary: High number Avoid cropping of builds are cropped build numbers in diagramms at high build numbers 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200529.1562677006000.5528.1562677140123%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58404) High number of builds are cropped in diagramms
Title: Message Title Niklas Lingenauber created an issue Jenkins / JENKINS-58404 High number of builds are cropped in diagramms Issue Type: Improvement Assignee: Ulli Hafner Attachments: image-2019-06-27-14-02-06-433.png, image-2019-07-02-08-22-00-000.png Components: warnings-ng-plugin Created: 2019-07-09 12:56 Environment: Warnings Next Generation Plugin - V4.0.0 Warnings Plug-in - V5.0.1 CloudBees Jenkins Enterprise 2.164.3.2 Priority: Minor Reporter: Niklas Lingenauber With a high number of builds, the last build number in the diagrams is cropped or completely removed (see attachments). This cutting should be avoided. Alternatively a possibility to rotate the label would be helpful in this case. Add Comment
[JIRA] (JENKINS-57967) vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher
Title: Message Title Nick Jones resolved as Fixed Fixed in version 2.20 Jenkins / JENKINS-57967 vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher Change By: Nick Jones Status: Open Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/vsphere-cloud-plugin/releases/tag/vsphere-cloud-2.20 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. To view this discussion on the web visit
[JIRA] (JENKINS-58234) LRR report not opening using the .tmp template mentioned in Jenkins job
Title: Message Title Govind Sureka commented on JENKINS-58234 Re: LRR report not opening using the .tmp template mentioned in Jenkins job Hello Rolando, I executed one more job and try to open the .LRA file but its giving error "Failed to open session. Cannot update. Database or Object is read only". Please advise. Thanks, Govind 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200295.1561627063000.5518.1562674980183%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58403) Issue marked as new when the issue did exist in a previous build but on a different line
Title: Message Title Julie Shamji created an issue Jenkins / JENKINS-58403 Issue marked as new when the issue did exist in a previous build but on a different line Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-07-09 11:35 Priority: Minor Reporter: Julie Shamji We have an issue which existed for a while, which is logged as which shows the issue is 24 days old: RequestAccessMergeProcessor.java:432 com.unisys.holmes2.h2ng.workflow.business.requestaccess Metrics JavaNCSSCheck Normal 24 In the next build, a change has been made to this file which moved this method to a new line, but the method remained unchanged. It is now logged as: RequestAccessMergeProcessor.java:434
[JIRA] (JENKINS-30231) Build creates second workspace@2 for non-concurrent build configuration
Title: Message Title Jatin Mehta commented on JENKINS-30231 Re: Build creates second workspace@2 for non-concurrent build configuration This issue is also seen in Jenkins ver 2.176.1. Jenkins is appending "@2" at the end of the workspace name for one of my nodes. This is causing the tests being run by the pipeline to fail since they look for files in a configured workspace name without the suffix @2. Jenkins seems to do that to prevent mishaps during concurrent builds but this happens for me even when I check Do not allow concurrent builds in the pipeline configuration. Is this new behavior due to a Jenkins version upgrade? Do we have any workarounds? I changed the project name that prevented it from happening but it came up again today. Can't keep changing project name to new ones. Please help! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164818.1441065243000.5477.1562669520374%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58234) LRR report not opening using the .tmp template mentioned in Jenkins job
Title: Message Title Rolando-Mihai Vlad commented on JENKINS-58234 Re: LRR report not opening using the .tmp template mentioned in Jenkins job Hello, The .LRA file contains the results with applied template. You can also see the template in the performance report section in jenkins (you might have to unset the CSP header due to security reasons in order to be able to see the graphs). Regards, Rolando 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200295.1561627063000.5474.1562669400093%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
