[JIRA] (JENKINS-26535) DescribableHelper does not handle wildcards well
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26535 Re: DescribableHelper does not handle wildcards well Code changed in jenkins User: Daniel Spilker Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java src/test/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigatorTraitsTest.java http://jenkins-ci.org/commit/github-branch-source-plugin/745dfbfe4f8002b085386e8da8a9416a964472d2 Log: added a workaround for JENKINS-26535 [FIXES JENKINS-45860] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46494) Certain conditions might lock more resources than required quantity
Title: Message Title Reinhold Füreder commented on JENKINS-46494 Re: Certain conditions might lock more resources than required quantity Antonio Muñiz Since the github activities of Marcus Antonsson seem to indicate that he is unfortunately no longer active, could you (as one of the plugin owners) maybe take over this bug – in the hope that it is a low hanging fruit and the linked pull request actually makes really sense... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Andrew Bayer started work on JENKINS-50833 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41858) Label + Quantity is sometimes not honored
Title: Message Title Joe Carlyon commented on JENKINS-41858 Re: Label + Quantity is sometimes not honored Yep - that's the same problem. FWIW, I haven't seen this come up in the better half of a year. I'm using version 2.0 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50847) Unable to Update or Install Plugin.
Title: Message Title Jothi Vignesh C created an issue Jenkins / JENKINS-50847 Unable to Update or Install Plugin. Issue Type: Bug Assignee: Unassigned Components: plugin-usage-plugin Created: 2018-04-17 14:26 Environment: JDK - 1.8.0_162 Priority: Blocker Reporter: Jothi Vignesh C I installed Jenkins and Launched First time, it is throwing the below error clicking on Check-now button on Plugin. A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:141) at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126) at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280) at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:392) Caused: sun.security.validator.ValidatorException: PKIX path building failed at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:397) at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:302) at sun.security.validator.Validator.validate(Validator.java:260) at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324) at
[JIRA] (JENKINS-50848) Define the client<->server update lifecycle
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-50848 Define the client<->server update lifecycle Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-04-17 14:32 Priority: Minor Reporter: R. Tyler Croy How are updates computed and indicated to the client? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50137) Trend report ID field cannot be parametrized
Title: Message Title Daniel Danan resolved as Fixed trend report ID can be parametrized after code fix Jenkins / JENKINS-50137 Trend report ID field cannot be parametrized Change By: Daniel Danan Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49989) Rebranding "HPE" to "Micro Focus" for expressions used in UI
Title: Message Title Daniel Danan resolved as Fixed rebranding done Jenkins / JENKINS-49989 Rebranding "HPE" to "Micro Focus" for expressions used in UI Change By: Daniel Danan Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50849) Define the versions manifest schema
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-50849 Define the versions manifest schema Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-04-17 14:32 Priority: Minor Reporter: R. Tyler Croy Need to codify ow the versions are actually supposed to be defined for POSTing to the versions service Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50760) JEP-200 issue with plugin Kubernetes Continuous Deploy Plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50760 Re: JEP-200 issue with plugin Kubernetes Continuous Deploy Plugin Code changed in jenkins User: Menghua Xiao Path: src/main/java/com/microsoft/jenkins/kubernetes/command/DeploymentCommand.java src/test/java/com/microsoft/jenkins/kubernetes/command/DeploymentCommandTest.java http://jenkins-ci.org/commit/kubernetes-cd-plugin/d1314ceb390b135a38773ff37275b208b4a50b7d Log: Transfrom slave exceptions to whitelist exceptions (JENKINS-50760) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23123) NPE from MavenSiteArchiver.getModulePath
Title: Message Title
Michael Grafl commented on JENKINS-23123
Re: NPE from MavenSiteArchiver.getModulePath
This often happens if the master project (aka. root project) is not the parent project. For example:
master.pom (has parent.pom as its parent)
`-- parent.pom
`-- module1.pom (has parent.pom as its parent)
The MavenSiteArchiver goes up the pom hierarchy until it finds the root project:
MavenProject currentLevel = pom;
// build the path to the module by ascending to the parent pom until the root project
while (!rootArtifactId.equals(currentLevel.getArtifactId())) {
path = currentLevel.getArtifactId() + File.separator + path;
currentLevel = currentLevel.getParent();
}
So, eventually, currentLevel.getParent() will return null.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code exetute this command to see the version of sshd you use sshd --foo Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50635) NUnit plugin does not fail build on test-runner error
Title: Message Title Kai Bublitz commented on JENKINS-50635 Re: NUnit plugin does not fail build on test-runner error We could do this if you can tell me how. This might look like a stupid questions but I have no idea how to enable keeping JUnit files. There is no option for this, so what should I do? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49509) Refactoring PC plugin due to new dependency to "com.microfocus.adm.performancecenter"
Title: Message Title Daniel Danan resolved as Fixed refactoring done. Jenkins / JENKINS-49509 Refactoring PC plugin due to new dependency to "com.microfocus.adm.performancecenter" Change By: Daniel Danan Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-50635) NUnit plugin does not fail build on test-runner error
Title: Message Title Kai Bublitz commented on JENKINS-50635 Re: NUnit plugin does not fail build on test-runner error I looked through all the "Manage Jenkins" but I couldn't find anything related to nunit settings. There is no "Global Configuration" in "Manage Jenkins" on our server. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45860) Support traits for ScmNavigators
Title: Message Title SCM/JIRA link daemon commented on JENKINS-45860 Re: Support traits for ScmNavigators Code changed in jenkins User: Robert Sandell Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java src/test/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigatorTraitsTest.java http://jenkins-ci.org/commit/github-branch-source-plugin/2aaa13771c05c784bfff060856ed6c4d055bf6f1 Log: Merge pull request #174 from daspilker/JENKINS-45860 JENKINS-45860 added a workaround for JENKINS-26535 Compare: https://github.com/jenkinsci/github-branch-source-plugin/compare/66373c2859f1...2aaa13771c05 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45860) Support traits for ScmNavigators
Title: Message Title SCM/JIRA link daemon commented on JENKINS-45860 Re: Support traits for ScmNavigators Code changed in jenkins User: Daniel Spilker Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java src/test/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigatorTraitsTest.java http://jenkins-ci.org/commit/github-branch-source-plugin/745dfbfe4f8002b085386e8da8a9416a964472d2 Log: added a workaround for JENKINS-26535 [FIXES JENKINS-45860] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50716) Include scm/tag in flattened POM
Title: Message Title
Jesse Glick commented on JENKINS-50716
Re: Include scm/tag in flattened POM
Patched git-changelist-maven-extension in 1.0-alpha-2 to set an scmTag parameter, and using that as
${scmTag}
Confirmed that .flattened-pom.xml contains
no tag when from a snapshot
an actual tag when in a MRP artifact
a commit hash when in Incrementals mode
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46494) Certain conditions might lock more resources than required quantity
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-46494
Re: Certain conditions might lock more resources than required quantity
I think I just stumbled over this issue as well and the change in linked pull request https://github.com/jenkinsci/lockable-resources-plugin/pull/66 actually looks reasonable/applicable at a quick naive glance...So here is my situation:# Started playing around with lock based on 'label' (2 lockable resources with same label), but forgot to specify 'quantity' => so it reserved all available 2 resources (with this label)# Fixing the problem by specifying 'quantity: 1'# Triggering a new pipeline build with the fix, WHILE an old pipeline build WITHOUT THE FIX was still running AND was STILL LOCKING ALL 2 RESOURCES although logs claim something else :#* The old build (#793, 20180417-133734-revUNKNOWN) WITHOUT the fix:{noformat}13:38:43 Trying to acquire lock on [Label: PhpStorm]13:38:43 Found 0 available resource(s). Waiting for correct amount: 2.13:38:43 [Label: PhpStorm] is locked, waiting...13:41:36 Lock acquired on [Label: PhpStorm]...13:46:29 Lock released on resource [Label: PhpStorm]{noformat}#* The new build (#794, 20180417-134149-revUNKNOWN) WITH the fix and right (lying logs) and wrong behaviour:{noformat}13:45:36 Trying to acquire lock on [Label: PhpStorm, Quantity: 1]13:45:36 Found 0 available resource(s). Waiting for correct amount: 1.13:45:36 [Label: PhpStorm, Quantity: 1] is locked, waiting...13:46:29 Lock acquired on [Label: PhpStorm, Quantity: 1]...{noformat}# So the new pipeline build had to correctly wait for the releasing of the lock, but it then incorrectly locked again for all 2 resources instead of just 1:#* Lockable Resources view: !screenshot-1.png|thumbnail! # Subsequent builds -- after a coincidental pause/break that seemingly allowed to release all locks and give them completely back, instead of re-using them for queued/waiting builds -- seemed to behave correctly then (and just lock 1 resource)
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73
[JIRA] (JENKINS-50680) CLONE - Can not edit Pipeline script - text not visible on Configure Page
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-50680 CLONE - Can not edit Pipeline script - text not visible on Configure Page Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46494) Certain conditions might lock more resources than required quantity
Title: Message Title Reinhold Füreder commented on JENKINS-46494 Re: Certain conditions might lock more resources than required quantity Marcus Antonsson Sorry for my harsh words and thanks for the clarification... and of course thanks for the pull request... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Andrew Bayer updated JENKINS-50833 Jenkins / JENKINS-50833 NoSuchMethodError causing Pipeline editor to not see agent settings Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Andrew Bayer commented on JENKINS-50833 Re: NoSuchMethodError causing Pipeline editor to not see agent settings PR up that should fix this at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/263 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46882) Scripts not permitted to use new java.lang.Exception java.lang.String
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-46882
Re: Scripts not permitted to use new java.lang.Exception java.lang.String
Code changed in jenkins User: James Hogarth Path: src/main/resources/org/jenkinsci/plugins/scriptsecurity/sandbox/whitelists/generic-whitelist http://jenkins-ci.org/commit/script-security-plugin/b4584131f5580fd7bc8dfe63e11fea8a9ea6cbff Log: JENKINS-46882 allow new Exceptions to be thrown new Execption("foo") is currently not permitted, but is very useful to do and is a standard/safe thing in a Jenkinsfile
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46882) Scripts not permitted to use new java.lang.Exception java.lang.String
Title: Message Title SCM/JIRA link daemon commented on JENKINS-46882 Re: Scripts not permitted to use new java.lang.Exception java.lang.String Code changed in jenkins User: Andrew Bayer Path: src/main/resources/org/jenkinsci/plugins/scriptsecurity/sandbox/whitelists/generic-whitelist http://jenkins-ci.org/commit/script-security-plugin/d0ef83d271d3c93176562146345dc042d4eefcbb Log: Merge pull request #198 from hogarthj/JENKINS-46882 JENKINS-46882 allow new Exceptions to be thrown Compare: https://github.com/jenkinsci/script-security-plugin/compare/9d642ae73c88...d0ef83d271d3 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46882) Scripts not permitted to use new java.lang.Exception java.lang.String
Title: Message Title Andrew Bayer resolved as Fixed Merged, will be in script-security 1.44. Jenkins / JENKINS-46882 Scripts not permitted to use new java.lang.Exception java.lang.String Change By: Andrew Bayer Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-48939) PRQA Plugin is affected by JEP-200 in Jenkins 2.102+
Title: Message Title Marcos Bento commented on JENKINS-48939 Re: PRQA Plugin is affected by JEP-200 in Jenkins 2.102+ The source code has been pushed. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Ryan Campbell commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Patrick Rose, which pull request? I don't see it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50746) statistics-gatherer-plugin should be able to feed data into mongodb
Title: Message Title lucamilanesio assigned an issue to lucamilanesio Jenkins / JENKINS-50746 statistics-gatherer-plugin should be able to feed data into mongodb Change By: lucamilanesio Assignee: Maxime Charron lucamilanesio Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45719) Description for a pipeline run is not compatible and cannot be disabled
Title: Message Title Krasimir Popov reopened an issue We need way to display links in build description for both UI's Jenkins / JENKINS-45719 Description for a pipeline run is not compatible and cannot be disabled Change By: Krasimir Popov Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-50834) Getting stack trace errors when click on create new job
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50834 Getting stack trace errors when click on create new job Change By: Oleg Nenashev Component/s: _unsorted Component/s: component Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50834) Getting stack trace errors when click on create new job
Title: Message Title Oleg Nenashev resolved as Incomplete Please follow the guidelines in https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue and reopen the issue once you can provide the diagnostics info Jenkins / JENKINS-50834 Getting stack trace errors when click on create new job Change By: Oleg Nenashev Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from
[JIRA] (JENKINS-50746) statistics-gatherer-plugin should be able to feed data into mongodb
Title: Message Title lucamilanesio started work on JENKINS-50746 Change By: lucamilanesio Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43440) Support for pipeline jobs?
Title: Message Title lucamilanesio started work on JENKINS-43440 Change By: lucamilanesio Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50477) Subversion Plugin 2.10.5 Login to SVN Server broken.
Title: Message Title Ivan Fernandez Calvo closed an issue as Fixed Jenkins / JENKINS-50477 Subversion Plugin 2.10.5 Login to SVN Server broken. Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Andrew Bayer updated JENKINS-50833 Merged, releasing in Declarative 1.2.9 later today. Jenkins / JENKINS-50833 NoSuchMethodError causing Pipeline editor to not see agent settings Change By: Andrew Bayer Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50833 Re: NoSuchMethodError causing Pipeline editor to not see agent settings Code changed in jenkins User: Andrew Bayer Path: pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/generator/AgentDirective.java pipeline-model-extensions/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/agent/DeclarativeAgentDescriptor.java http://jenkins-ci.org/commit/pipeline-model-definition-plugin/6b0e8f283437061169ae87dab25d44175e0afad0 Log: [FIXED JENKINS-50833] Revert DeclarativeAgentDescriptor.all() signature Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49474) Hash the Perforce ticket when saving it in the Credentials.xml
Title: Message Title Paul Allen started work on JENKINS-49474 Change By: Paul Allen Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49474) Hash the Perforce ticket when saving it in the Credentials.xml
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49474 Re: Hash the Perforce ticket when saving it in the Credentials.xml Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/credentials/TicketModeImpl.java http://jenkins-ci.org/commit/p4-plugin/31e3ecfcca54a8517e38decc9abc878de1549a7b Log: Store Perforce Ticket as a Secret, but support old clear text ticket credentials. JENKINS-49474 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37008) Jenkins vSphere cloud plugin does not expose guest info to pipeline
Title: Message Title
vassil marjunits commented on JENKINS-37008
Re: Jenkins vSphere cloud plugin does not expose guest info to pipeline
Same problem with vSphere PoweOn/Resume class. exposing vSphere variables to jenkins environmental variable not working in pipeline. Jenkins ver. 2.107.2, vSphere Plugin 2.17 Im using vSphere PoweOn/Resume to get IP aadress. #!/usr/bin/env groovy def vmDomainName = 'vm-test.ci.kit' node() { stage ('Build'){ vSphere buildStep: [$class: 'PowerOn', timeoutInSeconds: 180, vm: vmDomainName], serverName: 'testvcs' def vm_ip = env.VSPHERE_IP def build_id = env.BUILD_ID echo "VM IP: ${vm_ip}" echo "Build_id: ${build_id}" } } Console Output: Started by user someuser Running in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on Jenkins in /var/lib/jenkins/workspace/PowerOnVmPipeline[Pipeline] {[Pipeline] stage[Pipeline] { (Build)[Pipeline] vSphere[vSphere] [vSphere] Performing vSphere build step: "Power-On/Resume VM" [vSphere] Attempting to use server configuration: "testvcs" [vSphere] Successfully retrieved IP for "vm-test.ci.kit" : 10.0.24.55 [vSphere] Exposing 10.0.24.55 as environment variable VSPHERE_IP[Pipeline] echoVM IP: null[Pipeline] echoBuild_id: 14[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS Custom log record: Apr 17, 2018 6:14:17 PM FINE org.jenkinsci.plugins.workflow.job.WorkflowRun PowerOnVmPipeline #13 in /var/lib/jenkins/jobs/PowerOnVmPipeline/builds/13: result is set to SUCCESS java.lang.Exception at org.jenkinsci.plugins.workflow.job.WorkflowRun.setResult(WorkflowRun.java:738) at org.jenkinsci.plugins.workflow.job.WorkflowRun.finish(WorkflowRun.java:747) at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$1100(WorkflowRun.java:142) at org.jenkinsci.plugins.workflow.job.WorkflowRun$GraphL.onNewHead(WorkflowRun.java:1094) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.notifyListeners(CpsFlowExecution.java:1413) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.run(CpsThreadGroup.java:412) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:35) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Apr 17, 2018 6:14:17 PM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finish PowerOnVmPipeline #13 completed: SUCCESS
Add Comment
[JIRA] (JENKINS-50652) Aborting a sh or bat step fires both aborted and failure post conditions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50652 Re: Aborting a sh or bat step fires both aborted and failure post conditions Code changed in jenkins User: Andrew Bayer Path: pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Failure.groovy pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/BuildConditionResponderTest.java http://jenkins-ci.org/commit/pipeline-model-definition-plugin/70d2af8039aa06db05fb0bb1dcc2d370940387ac Log: [FIXED JENKINS-50652] Don't fire post failure for aborted durable task It appears that an aborted durable task like sh results in `CpsFlowExecution#result` being `ABORTED`, but `WorkflowRun#result` being `FAILURE`, until the whole build actually finishes and the run gets updated accordingly. So the `failure` `post` condition shouldn't fire if `CpsFlowExecution#result` is `ABORTED`. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42568) The selected option from Active Choice Parameter groovy script is not used when building a job periodically (using cron)
Title: Message Title Pavel Chadima updated an issue Jenkins / JENKINS-42568 The selected option from Active Choice Parameter groovy script is not used when building a job periodically (using cron) Change By: Pavel Chadima Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41885) Build log is scrolled down unconditionally on update
Title: Message Title Krasimir Popov commented on JENKINS-41885 Re: Build log is scrolled down unconditionally on update +1 for improving the the autoscroll in blue ocean, we would like to have a similar experience to the normal UI Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50839) Repository depth 'as-it-is' is broken in 2.10.5, it works as depth 'files'
Title: Message Title Ivan Fernandez Calvo closed an issue as Duplicate Jenkins / JENKINS-50839 Repository depth 'as-it-is' is broken in 2.10.5, it works as depth 'files' Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48939) PRQA Plugin is affected by JEP-200 in Jenkins 2.102+
Title: Message Title Oleg Nenashev commented on JENKINS-48939 Re: PRQA Plugin is affected by JEP-200 in Jenkins 2.102+ Marcos Bento there is no source code in https://github.com/jenkinsci/prqa-plugin . Could you please push it? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48551) Cannot select CIFS publish in project configuration
Title: Message Title Kevin Waite updated an issue Jenkins / JENKINS-48551 Cannot select CIFS publish in project configuration Change By: Kevin Waite Attachment: image-2018-04-17-11-25-26-554.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48551) Cannot select CIFS publish in project configuration
Title: Message Title Kevin Waite commented on JENKINS-48551 Re: Cannot select CIFS publish in project configuration I am having the same problem as those above. The share configuration list is empty, but is set up in the global config, see 2nd image at the bottom. Promotion does not finish with SUCCESS, no gold star, etc. Jenkins ver. 2.113 Publish Over CIFS 0.9 Drop down is wrongly empty, the plugin's checkboxes are not labeled. Promotion results in this error: ERROR: Failed to find configuration named [] check the global configuration build CifsPromotionPublisherPlugin[delegate=CifsPublisherPlugin[consolePrefix=CIFS: ,delegate=BPInstanceConfig[publishers=[CifsPublisher[configName=,verbose=true,transfers=[CifsTransfer[sourceFiles=**,excludes=,removePrefix=,remoteDirectory=$JOB_NAME/$BUILD_NUMBER,remoteDirectorySDF=false,flatten=true,cleanRemote=false,noDefaultExcludes=false,makeEmptyDirs=false,patternSeparator=]],useWorkspaceInPromotion=false,usePromotionTimestamp=false,retry=CifsRetry[retries=0,retryDelay=0],label=CifsPublisherLabel[label=],credentials=]],continueOnError=false,failOnError=false,masterNodeName=,alwaysPublishFromMaster=false,paramPublish=CifsParamPublish[parameterName= Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code $ sshd --foo sshd: unknown option -- - OpenSSH_7.3p1, OpenSSL 1.0.2j 26 Sep 2016 usage: sshd [-46DdeiqTt] [-b bits] [-C connection_spec] [-c host_cert_file] [-E log_file] [-f config_file] [-g login_grace_time] [-h host_key_file] [-k key_gen_time] [-o option] [-p port] [-u len] There are no other files in the folder: D:\CI\jenkins-ssh, except the "slave.jar" When I try to download: http://jenkins/computer/windows-ssh/config.xml I get the attached XML. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder updated an issue Jenkins / JENKINS-50638 windows agent via SSH - Slave JVM has terminated. Exit code Change By: Zack Snyder Attachment: config.zip Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48494) Pass Additional attributes from Jenkins to HP Performance Center 12.53
Title: Message Title Daniel Danan assigned an issue to Daniel Danan Jenkins / JENKINS-48494 Pass Additional attributes from Jenkins to HP Performance Center 12.53 Change By: Daniel Danan Assignee: Oren Pelzman Daniel Danan Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50846) Cannot start build runner due to Trend error even if no Trend option is selected
Title: Message Title Daniel Danan updated an issue Jenkins / JENKINS-50846 Cannot start build runner due to Trend error even if no Trend option is selected Change By: Daniel Danan Labels: PerformanceCenter Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48933) Unstoppable Multibranch Pipeline Scan
Title: Message Title Kevin Lannen commented on JENKINS-48933 Re: Unstoppable Multibranch Pipeline Scan This seems similar to this issue: https://issues.jenkins-ci.org/browse/JENKINS-32767 We are using Bitbucket for our source control. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50716) Include scm/tag in flattened POM
Title: Message Title Jesse Glick resolved as Fixed Jenkins / JENKINS-50716 Include scm/tag in flattened POM Change By: Jesse Glick Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48551) Cannot select CIFS publish in project configuration
Title: Message Title Kevin Waite updated an issue Jenkins / JENKINS-48551 Cannot select CIFS publish in project configuration Change By: Kevin Waite Attachment: image-2018-04-17-11-26-30-313.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title
Zack Snyder edited a comment on JENKINS-50638
Re: windows agent via SSH - Slave JVM has terminated. Exit code
{noformat}$ sshd --foosshd: unknown option -- -OpenSSH_7.3p1, OpenSSL 1.0.2j 26 Sep 2016usage: sshd [-46DdeiqTt] [-b bits] [-C connection_spec] [-c host_cert_file][-E log_file] [-f config_file] [-g login_grace_time][-h host_key_file] [-k key_gen_time] [-o option] [-p port][-u len]{noformat} There are no other files in the folder: D:\CI\jenkins-ssh, except the "slave.jar"When I try to download: [ http://jenkins/computer/windows-ssh/config.xml ] I get the attached XML (config . zip)
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42568) The selected option from Active Choice Parameter groovy script is not used when building a job periodically (using cron)
Title: Message Title Pavel Chadima commented on JENKINS-42568 Re: The selected option from Active Choice Parameter groovy script is not used when building a job periodically (using cron) I have the same problem and it is important issue for me since my configured pipelines are scheduled for automatically executed nightly builds which is now useless. The only solution now is to execute some nightly builds when I leave work in the evening. I would really apreciate fixing this! Thanks. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50746) statistics-gatherer-plugin should be able to feed data into mongodb
Title: Message Title lucamilanesio commented on JENKINS-50746 Re: statistics-gatherer-plugin should be able to feed data into mongodb I have implemented a LOGBack appender support in this plugin that would allow to log events to MongoDB. So, as soon as I'll manage to get that merged (see [1]) you just need to: Enable LOGBack notification Specify a logback.xml that uses a MongoDb appender (see [2]) [1] https://github.com/jenkinsci/statistics-gatherer-plugin/pull/5 [2] https://github.com/qos-ch/logback-contrib/wiki/MongoDB Maxime Charron are you still looking after this plugin? Can you please have a look at my PRs? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43440) Support for pipeline jobs?
Title: Message Title lucamilanesio assigned an issue to lucamilanesio Jenkins / JENKINS-43440 Support for pipeline jobs? Change By: lucamilanesio Assignee: Maxime Charron lucamilanesio Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code When using cygwin as bash, I get also the environment variables printed: [04/17/18 17:58:59] [SSH] Opening SSH connection to windows-build-server:22. [04/17/18 17:58:59] [SSH] SSH host key matches key seen previously for this host. Connection will be allowed. [04/17/18 17:58:59] [SSH] Authentication successful. [04/17/18 17:58:59] [SSH] The remote user's environment is: ALLUSERSPROFILE='C:\ProgramData' APPDATA='C:\Users\BuildUser\AppData\Roaming' BASH=/usr/bin/bash BASHOPTS=cmdhist:complete_fullquote:extquote:force_fignore:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath BASH_ALIASES=() BASH_ARGC=() BASH_ARGV=() BASH_CMDS=() BASH_EXECUTION_STRING=set BASH_LINENO=() BASH_SOURCE=() BASH_VERSINFO=([0]="4" [1]="4" [2]="12" [3]="3" [4]="release" [5]="x86_64-unknown-cygwin") BASH_VERSION='4.4.12(3)-release' COMMONPROGRAMFILES='C:\Program Files\Common Files' COMPUTERNAME=W10X64-BUILDSRV COMSPEC='C:\WINDOWS\system32\cmd.exe' CYG_SYS_BASHRC=1 CommonProgramW6432='C:\Program Files\Common Files' DIRSTACK=() DXSDK_DIR='C:\Program Files (x86)\Microsoft DirectX SDK (June 2010)\' EUID=197611 GROUPS=() HOME=/home/BuildUser HOMEDRIVE=C: HOMEPATH='\Users\BuildUser' HOSTNAME=W10x64-BuildSrv HOSTTYPE=x86_64 IFS=$' \t\n' LOCALAPPDATA='C:\Users\BuildUser\AppData\Local' MACHTYPE=x86_64-unknown-cygwin NUMBER_OF_PROCESSORS=4 OPTERR=1 OPTIND=1 OS=Windows_NT OSTYPE=cygwin _OneDrive_='C:\Users\BuildUser\OneDrive' PATH='/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/WINDOWS/System32/WindowsPowerShell/v1.0:/cygdrive/c/Program Files (x86)/Windows Kits/8.1/Windows Performance Toolkit:/cygdrive/c/Program Files/Microsoft SQL Server/110/Tools/Binn:/cygdrive/c/Program Files (x86)/Microsoft SDKs/TypeScript/1.0:/cygdrive/c/Program Files/Microsoft SQL Server/120/Tools/Binn:/cygdrive/c/Program Files/Git/cmd:/cygdrive/c/Program Files/SafeNet/Authentication/SAC/x64:/cygdrive/c/Program Files/SafeNet/Authentication/SAC/x32:/cygdrive/c/WINDOWS/SysWOW64/WindowsPowerShell/v1.0/Modules/TShell/TShell:/cygdrive/c/WINDOWS/system32/config/systemprofile/AppData/Local/Microsoft/WindowsApps:/cygdrive/c/Users/BuildUser/AppData/Local/Microsoft/WindowsApps' PATHEXT='.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC' PIPESTATUS=([0]="0") PPID=1 PROCESSOR_ARCHITECTURE=AMD64 PROCESSOR_IDENTIFIER='Intel64 Family 6 Model 60 Stepping 3, GenuineIntel' PROCESSOR_LEVEL=6 PROCESSOR_REVISION=3c03 PROGRAMFILES='C:\Program Files' PROMPT='builduser@W10X64-BUILDSRV $P$G' PS4='+ ' PSModulePath='C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules' PUBLIC='C:\Users\Public' PWD=/cygdrive/c/Users/BuildUser ProgramData='C:\ProgramData' ProgramW6432='C:\Program Files' SHELL=/bin/bash SHELLOPTS=braceexpand:hashall:interactive-comments SHLVL=1 SSH_CLIENT='192.168.115.188 59638 22' SSH_CONNECTION='192.168.115.188 59638 192.168.120.187 22' SYSTEMDRIVE=C: SYSTEMROOT='C:\WINDOWS' TEMP=/cygdrive/c/Users/BuildUser/AppData/Local/Temp TERM=cygwin TMP=/cygdrive/c/Users/BuildUser/AppData/Local/Temp UID=197611 USERDOMAIN=WORKGROUP USERNAME=builduser USERPROFILE='C:\Users\BuildUser' VS110COMNTOOLS='C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools\' VS120COMNTOOLS='C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\'
[JIRA] (JENKINS-50746) statistics-gatherer-plugin should be able to feed data into mongodb
Title: Message Title lucamilanesio commented on JENKINS-50746 Re: statistics-gatherer-plugin should be able to feed data into mongodb I've reassigned the issue to me because I am currently working on it Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43440) Support for pipeline jobs?
Title: Message Title lucamilanesio commented on JENKINS-43440 Re: Support for pipeline jobs? I've reassigned the issue to me because I am currently working on it Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Patrick Rose commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Ryan Campbell - this one, there's a compilation error I need to look into but I've not had the chance to yet. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45719) Description for a pipeline run is not compatible and cannot be disabled
Title: Message Title Krasimir Popov commented on JENKINS-45719 Re: Description for a pipeline run is not compatible and cannot be disabled I am also experiencing the same issue but I do not want to disable it I want to display links there via Markdown or HTML it does not matter. But I need a way to have my build description to look nice and to contain links in both UI's. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45719) Description for a pipeline run is not compatible and cannot be disabled
Title: Message Title Krasimir Popov edited a comment on JENKINS-45719 Re: Description for a pipeline run is not compatible and cannot be disabled I am also experiencing the same issue but I do not want to disable it build description. I want to display links there via Markdown or HTML it does not matter.But I need a way to have my build description to look nice and to contain links in both UI's. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code Create a file named D:\CI\jenkins-ssh\logging.properties and add this property to the JVM options *-Djava.util.logging.config.file=/cygdrive/d/CI/jenkins-ssh/logging.properties* also set the *root fs* to /cygdrive/d/CI/jenkins-ssh/ in the Agent configuration # -Djava.util.logging.config.file=logging.properties .level = ALL handlers= java.util.logging.FileHandler java.util.logging.FileHandler.level = ALL java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter java.util.logging.FileHandler.pattern=jenkins-ssh-agent-%u.log java.util.logging.FileHandler.limit = 1000 java.util.logging.FileHandler.count = 10 javax.jms.connection.level = INFO hudson.level = INFO hudson.remoting.Channel.level = FINE hudson.remoting.FileSystemJarCache.level = INFO hudson.remoting.jnlp.level = FINE hudson.remoting.RemoteClassLoader.level = INFO jenkins.slaves.level = FINE hudson.slaves.level = FINE org.jenkinsci.remoting.engine.level = FINE jenkins.AgentProtocol.level = FINE The config file attached is not completed, it is a copy and paste of an parse error in your browser, please download the file and attach it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this
[JIRA] (JENKINS-37008) Jenkins vSphere cloud plugin does not expose guest info to pipeline
Title: Message Title
vassil marjunits edited a comment on JENKINS-37008
Re: Jenkins vSphere cloud plugin does not expose guest info to pipeline
Same problem with vSphere PoweOn/Resume class.exposing vSphere variables to jenkins environmental variable not working in pipeline. Jenkins ver. 2.107.2, vSphere Plugin 2.17Im using vSphere PoweOn/Resume to get IP aadress.#!/usr/bin/env groovydef vmDomainName = 'vm-test.ci.kit'node() \{ stage ('Build')\{ vSphere buildStep: [$class: 'PowerOn', timeoutInSeconds: 180, vm: vmDomainName], serverName: 'testvcs' def vm_ip = env.VSPHERE_IP def build_id = env.BUILD_ID echo "VM IP: $\{vm_ip}" echo "Build_id: $\{build_id}" } }Console Output:Started by user someuserRunning in Durability level: MAX_SURVIVABILITY{color:#9a}[Pipeline] node{color}Running on [Jenkins |https://jenkins-dev.ci.kit/computer/(master)/]in /var/lib/jenkins/workspace/PowerOnVmPipeline{color:#9a}[Pipeline] \{{color}{color:#9a}[Pipeline] stage{color}{color:#9a}[Pipeline] \{ (Build){color}{color:#9a}[Pipeline] vSphere{color}[vSphere] [vSphere] Performing vSphere build step: "Power-On/Resume VM"[vSphere] Attempting to use server configuration: "testvcs"[vSphere] Successfully retrieved IP for "vm-test.ci.kit" : 10.0.24.55[vSphere] Exposing 10.0.24.55 as environment variable VSPHERE_IP {color:#9a}[Pipeline] echo{color}VM IP: null {color:#9a}[Pipeline] echo{color}Build_id: 14 {color:#9a}[Pipeline] }{color}{color:#9a}[Pipeline] // stage{color}{color:#9a}[Pipeline] }{color}{color:#9a}[Pipeline] // node{color}{color:#9a}[Pipeline] End of Pipeline{color}Finished: SUCCESS Custom log record:Apr 17, 2018 6:14:17 PM FINE org.jenkinsci.plugins.workflow.job.WorkflowRunPowerOnVmPipeline #13 in /var/lib/jenkins/jobs/PowerOnVmPipeline/builds/13: result is set to SUCCESS java.lang.Exception at org.jenkinsci.plugins.workflow.job.WorkflowRun.setResult(WorkflowRun.java:738) at org.jenkinsci.plugins.workflow.job.WorkflowRun.finish(WorkflowRun.java:747) at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$1100(WorkflowRun.java:142) at org.jenkinsci.plugins.workflow.job.WorkflowRun$GraphL.onNewHead(WorkflowRun.java:1094) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.notifyListeners(CpsFlowExecution.java:1413) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.run(CpsThreadGroup.java:412) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:35) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Apr 17, 2018 6:14:17 PM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finishPowerOnVmPipeline #13 completed: SUCCESS
[JIRA] (JENKINS-41239) Error during always block skips execution of remaining steps
Title: Message Title Andrew Bayer updated JENKINS-41239 Merged, releasing later today in Declarative 1.2.9 Jenkins / JENKINS-41239 Error during always block skips execution of remaining steps Change By: Andrew Bayer Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-41239) Error during always block skips execution of remaining steps
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41239 Re: Error during always block skips execution of remaining steps Code changed in jenkins User: Andrew Bayer Path: pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Cleanup.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Messages.properties pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/BuildConditionResponderTest.java pipeline-model-definition/src/test/resources/postChecksAllConditions.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/83abd0ec35960c1f2a37b6a66b2d26385b2962e2 Log: [FIXED JENKINS-41239] Add new cleanup post condition The new `cleanup` condition will always run regardless of build status, like `always`, but runs after all other `post` conditions have been evaluated, rather than before. I wanted to call this `finally` but that actually breaks Groovy parsing because `finally` is a reserved word. Dang. So for now, I'm calling it `cleanup`, but am open to suggestions. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50652) Aborting a sh or bat step fires both aborted and failure post conditions
Title: Message Title Andrew Bayer updated JENKINS-50652 Will be released in Declarative 1.2.9 later today. Jenkins / JENKINS-50652 Aborting a sh or bat step fires both aborted and failure post conditions Change By: Andrew Bayer Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-43440) Support for pipeline jobs?
Title: Message Title lucamilanesio commented on JENKINS-43440 Re: Support for pipeline jobs? Have the same problem here I am going to implement the Pipeline support and issue a PR on the project. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49774) NPE in Autofavorite plugin
Title: Message Title
Alex Gray commented on JENKINS-49774
Re: NPE in Autofavorite plugin
I just go this same error (rebuilding fixes it): {noformat} GitHub has been notified of this commit’s build result java.lang.NullPointerException at io.jenkins.blueocean.autofavorite.FavoritingScmListener.onCheckout(FavoritingScmListener.java:109) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:127) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) {noformat} This is using 1.2.2 of the Autofavorite for Blue Ocean Plugin. This is using Jenkins ver. 2.107.2
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-50007) cannot be cast to hudson.scm.SVNRevisionState
Title: Message Title Ivan Fernandez Calvo closed an issue as Incomplete https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue Jenkins / JENKINS-50007 cannot be cast to hudson.scm.SVNRevisionState Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-48939) PRQA Plugin is affected by JEP-200 in Jenkins 2.102+
Title: Message Title Oleg Nenashev commented on JENKINS-48939 Re: PRQA Plugin is affected by JEP-200 in Jenkins 2.102+ thanks! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48933) Unstoppable Multibranch Pipeline Scan
Title: Message Title Kevin Lannen commented on JENKINS-48933 Re: Unstoppable Multibranch Pipeline Scan We are running into this same issue, This is a major issue for us since restarting Jenkins is not a valid workaround during the workday. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48933) Unstoppable Multibranch Pipeline Scan
Title: Message Title Kevin Lannen updated an issue Jenkins / JENKINS-48933 Unstoppable Multibranch Pipeline Scan Change By: Kevin Lannen Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38840) log parser plugin fails on slave node
Title: Message Title Ragu Raman S commented on JENKINS-38840 Re: log parser plugin fails on slave node I also have the same issue and looks like Log parser rules are referred only from Master(this plugin doesn't support to configure parser rules in slave machines) - any workaround/solution? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40839) pipeline timeout doesn't kill the job
Title: Message Title
Maxfield Stewart commented on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Here's my minimal repro for this: ``` node ('somelabel) { timeout (30) { timetstamps { withEnv(someEnvArray) { sleep 15 } } } } ``` While the sleep is running, put Jenkins in shutdown. Then cancel shutdown. The job will trigger the timeout, eventually say it's killing with extreme prejudice and need to be hard aborted otherwise it will be stuck forever. This mainly manifests as a problem when doing maintenance/restarts where some jobs might properly resume but end up stuck for other reasons and never cleanup.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Laurent DEVOS commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API I'm using version 2.5 of the plugin. The problem was resolved after upgrading to 2.107.2 and updating all of my other plugins that had a new version. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40839) pipeline timeout doesn't kill the job
Title: Message Title
Maxfield Stewart edited a comment on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Here's my minimal repro for this: {code:java}node ('somelabel) { timeout (30) { timetstamps { withEnv(someEnvArray) { sleep 15 } } }}{code} While the sleep is running, put Jenkins in shutdown. Then cancel shutdown. The job will trigger the timeout, eventually say it's killing with extreme prejudice and need to be hard aborted otherwise it will be stuck forever.This mainly manifests as a problem when doing maintenance/restarts where some jobs might properly resume but end up stuck for other reasons and never cleanup. When I forcibly terminate at the text prompt it's still stuck inside "withEnv"
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40839) pipeline timeout doesn't kill the job
Title: Message Title
Maxfield Stewart edited a comment on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Here's my minimal repro for this: ``` {code:java} node ('somelabel) \ { timeout (30) \ { timetstamps \ { withEnv(someEnvArray) \ { sleep 15 } } } } {code } ``` While the sleep is running, put Jenkins in shutdown. Then cancel shutdown. The job will trigger the timeout, eventually say it's killing with extreme prejudice and need to be hard aborted otherwise it will be stuck forever.This mainly manifests as a problem when doing maintenance/restarts where some jobs might properly resume but end up stuck for other reasons and never cleanup.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40839) pipeline timeout doesn't kill the job
Title: Message Title
Maxfield Stewart edited a comment on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Here's my minimal repro for this: {code:java}node ('somelabel) { timeout (30) { timetstamps timestamps { withEnv(someEnvArray) { sleep 15 } } }}{code} While the sleep is running, put Jenkins in shutdown. Then cancel shutdown. The job will trigger the timeout, eventually say it's killing with extreme prejudice and need to be hard aborted otherwise it will be stuck forever.This mainly manifests as a problem when doing maintenance/restarts where some jobs might properly resume but end up stuck for other reasons and never cleanup. When I forcibly terminate at the text prompt it's still stuck inside "withEnv" I've also tested this by removing the "withEnv" and just using "timestamps" and the same problem occurs. As well as doing it without "timestamps" at each interval the nested section it's stuck in is inner one. So this seems to be a problem with the timeout handler.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41858) Label + Quantity is sometimes not honored
Title: Message Title Reinhold Füreder commented on JENKINS-41858 Re: Label + Quantity is sometimes not honored Maybe also related to JENKINS-46494? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Zangdaarr Mortpartout commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline We are using custom workspace but this is causing trouble with third party tools which do not know that custom workspaces exists. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50716) Include scm/tag in flattened POM
Title: Message Title Jesse Glick started work on JENKINS-50716 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code Is there a support folder in D:\CI\jenkins-ssh? Are there log files in D:\CI\jenkins-ssh? Are there hs_err_* files in D:\CI\jenkins-ssh? Is java in the path of the user that you use when you enter with ssh? Could you attach the config.xml of the agent? JENKINS_URL/computer/AGENT_NAME/config.xml How much memory this Agent has? Could you attach the D:/CI/jenkins-ssh/log.txt file? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35324) Support restoring secrets
Title: Message Title Chetan Sharma commented on JENKINS-35324 Re: Support restoring secrets This regex works form me - (.\.xml)|(secrets|.\.key|.\.KEY|.\.Secret|.\.secret|.\.mac|.\.MAC|.\.seed|.\.crumbSalt|.\.consoleAnnotator|.\.serverCookie|.-switch|whitelisted-callables\.d|.\.conf|filepath-filters\.d|.\.conf)$ Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50693) Script to interoperate with maven-release-plugin
Title: Message Title
Jesse Glick commented on JENKINS-50693
Re: Script to interoperate with maven-release-plugin
mvn help:evaluate -Dexpression=project.version -Doutput=version && mvn versions:set -Ddollar='$' -DnewVersion='${dollar}{revision}${dollar}{changelist}' -DgenerateBackupPoms=false && mvn versions:set-property -Dproperty=revision -DnewVersion=`sed -e 's/-SNAPSHOT$//' < version` -DgenerateBackupPoms=false && rm version
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50693) Script to interoperate with maven-release-plugin
Title: Message Title Jesse Glick started work on JENKINS-50693 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48939) PRQA Plugin is affected by JEP-200 in Jenkins 2.102+
Title: Message Title Marcos Bento updated JENKINS-48939 Jenkins / JENKINS-48939 PRQA Plugin is affected by JEP-200 in Jenkins 2.102+ Change By: Marcos Bento Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48939) PRQA Plugin is affected by JEP-200 in Jenkins 2.102+
Title: Message Title Marcos Bento updated JENKINS-48939 Jenkins / JENKINS-48939 PRQA Plugin is affected by JEP-200 in Jenkins 2.102+ Change By: Marcos Bento Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48939) PRQA Plugin is affected by JEP-200 in Jenkins 2.102+
Title: Message Title Marcos Bento commented on JENKINS-48939 Re: PRQA Plugin is affected by JEP-200 in Jenkins 2.102+ This issue is fixed in PRQA Jenkins plugin 3.0.1. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50769) Deploying EAR to WAS 7 Issue with JDK
Title: Message Title
Andrew Closs updated an issue
Jenkins / JENKINS-50769
Deploying EAR to WAS 7 Issue with JDK
Change By:
Andrew Closs
Hello, I'm having an issue deploying an EAR file to WebSphere and I think it's related to the JDK. Running the Jenkins service under the IBM JDK 6 results in a StackOverflowError and crashing of the Jenkins service:{quote}... BUILD SUCCESSFUL Total time: 1 minute 2 seconds HeadlessWorkspaceSettings: RESTORED autoBuild=true maxFile=1048576 Connecting to IBM WebSphere Application Server... FATAL: null java.lang.StackOverflowError at java.lang.ClassLoader.loadClass(ClassLoader.java:668) ...{quote}Running the Jenkins service under Oracle JDK 1.8 results in it getting slightly farther, acknowledging the EAR file to deploy : {quote}... BUILD SUCCESSFUL Total time: 1 minute 38 seconds HeadlessWorkspaceSettings: RESTORED autoBuild=true maxFile=1048576 Connecting to IBM WebSphere Application Server... The following artifacts will be deployed in this order... --- ProjectEAR_201804121146AM.ear --- Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: ...{quote}These are excerpts from the Jenkins GUI log. I've attached the console output of these two, they have a few more details. As a note I've changed the projects runtime JDK of both Jenkins to IBM JDK6 and 8, Oracle JDK 6, 7, and 8. It doesn't seem to make a difference. As I read in the troubleshooting guide Jenkins runs the plugin based off the services JDK, which is what it appears to be doing. However using the same JDK as my WebSphere doesn't work either. Any ideas where I can go from here? Thanks.
Add Comment
[JIRA] (JENKINS-50769) Deploying EAR to WAS 7 Issue with JDK
Title: Message Title
Andrew Closs updated an issue
Jenkins / JENKINS-50769
Deploying EAR to WAS 7 Issue with JDK
Change By:
Andrew Closs
Hello, I'm having an issue deploying an EAR file to WebSphere and I think it's related to the JDK. Running the Jenkins service under the IBM JDK 6 results in a StackOverflowError and crashing of the Jenkins service:{quote}... BUILD SUCCESSFUL Total time: 1 minute 2 seconds HeadlessWorkspaceSettings: RESTORED autoBuild=true maxFile=1048576 Connecting to IBM WebSphere Application Server... FATAL: null java.lang.StackOverflowError at java.lang.ClassLoader.loadClass(ClassLoader.java:668) ...{quote}Running the Jenkins service under Oracle and IBM JDK 1.8 results in it getting slightly farther, acknowledging the EAR file to deploy : {quote}... BUILD SUCCESSFUL Total time: 1 minute 38 seconds HeadlessWorkspaceSettings: RESTORED autoBuild=true maxFile=1048576 Connecting to IBM WebSphere Application Server... The following artifacts will be deployed in this order... --- ProjectEAR_201804121146AM.ear --- Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: ...{quote}These are excerpts from the Jenkins GUI log. I've attached the console output of these two, they have a few more details. As a note I've changed the projects runtime JDK of both Jenkins to IBM JDK6 and 8, Oracle JDK 6, 7, and 8. It doesn't seem to make a difference. As I read in the troubleshooting guide Jenkins runs the plugin based off the services JDK, which is what it appears to be doing. However using the same JDK as my WebSphere doesn't work either. Any ideas where I can go from here? Thanks.
Add Comment
[JIRA] (JENKINS-50769) Deploying EAR to WAS 7 Issue with JDK
Title: Message Title
Andrew Closs updated an issue
Jenkins / JENKINS-50769
Deploying EAR to WAS 7 Issue with JDK
Change By:
Andrew Closs
Hello, I'm having an issue deploying an EAR file to WebSphere and I think it's related to the JDK. Running the Jenkins service under the IBM JDK 6 results in a StackOverflowError and crashing of the Jenkins service:{quote}... BUILD SUCCESSFUL Total time: 1 minute 2 seconds HeadlessWorkspaceSettings: RESTORED autoBuild=true maxFile=1048576 Connecting to IBM WebSphere Application Server... FATAL: null java.lang.StackOverflowError at java.lang.ClassLoader.loadClass(ClassLoader.java:668) ...{quote}Running the Jenkins service under Oracle IBM JDK 1.8 results in it getting slightly farther, acknowledging the EAR file to deploy : {quote}... BUILD SUCCESSFUL Total time: 1 minute 38 seconds HeadlessWorkspaceSettings: RESTORED autoBuild=true maxFile=1048576 Connecting to IBM WebSphere Application Server... The following artifacts will be deployed in this order... --- ProjectEAR_201804121146AM.ear --- Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: ...{quote}These are excerpts from the Jenkins GUI log. I've attached the console output of these two, they have a few more details. As a note I've changed the projects runtime JDK of both Jenkins to IBM JDK6 and 8, Oracle JDK 6, 7, and 8. It doesn't seem to make a difference. As I read in the troubleshooting guide Jenkins runs the plugin based off the services JDK, which is what it appears to be doing. However using the same JDK as my WebSphere doesn't work either. Any ideas where I can go from here? Thanks.
Add Comment
[JIRA] (JENKINS-48524) Misc infrastructure errors are missing from step view. Blue ocean should default to showing a log tail at end of failed build.
Title: Message Title Vivek Pandey commented on JENKINS-48524 Re: Misc infrastructure errors are missing from step view. Blue ocean should default to showing a log tail at end of failed build. Michael Neale https://issues.jenkins-ci.org/browse/JENKINS-48074 fixes cases where pipeline script failed to start due to error (that is no step or stages got to run). Cases such as handling intermediate step failed due to infra error are not handled by JENKINS-48074. I think we should keep it open. Right fix should really come from upstream pipeline library where pipeline step contextual errors are made available thru FlowNode or executor so that in case of failure we can display it in context of failed step. cc: Sam Van Oort. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50773) Pipline script for vSphere ExposeGuestInfo generates . Pipeline DSL ExposeGuestInfo Build fails
Title: Message Title
vassil marjunits commented on JENKINS-50773
Re: Pipline script for vSphere ExposeGuestInfo generates . Pipeline DSL ExposeGuestInfo Build fails
thanx bro, I added waitForIp4 parameter. It seems to be common issue with exposing vSphere variables to the Jenkins environmental variables in a pipeline mode. Its disaster fo my CI automation. I dont have experiences with Java to fix vSphere plugin for Jenkins pipeline mode. #!/usr/bin/env groovy def vmDomainName = 'vassilm-test.ci.kit' node() { stage ('Build'){ vSphere buildStep: [$class: 'ExposeGuestInfo', envVariablePrefix: 'VSPHERE', vm: vmDomainName, waitForIp4: true], serverName: 'testvcs' vSphere buildStep: [$class: 'PowerOn', timeoutInSeconds: 180, vm: vmDomainName], serverName: 'testvcs' echo "This is env variable BUILD ID: ${BUILD_ID}" def IPfromGuestInfo = env.VSPHERE_IpAddress def IPfromPowerON = env.VSPHERE_IP echo "This is VSPHERE_IpAddress from ExposeGuestInfo instance: $IPfromGuestInfo" echo "This is VSPHERE_IP from PowerOn instance $IPfromPowerON" echo "For stack trace: ${VSPHERE_IpAddress}" } } Started by user someuser Running in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on Jenkins in /var/lib/jenkins/workspace/PowerOnVmPipeline[Pipeline] {[Pipeline] stage[Pipeline] { (Build)[Pipeline] vSphere[vSphere] Performing vSphere build step: "Expose Guest Info" [vSphere] Attempting to use server configuration: "testvcs" [vSphere] Exposing guest info for VM "vassilm-test.ci.kit" as environment variables [vSphere] Added environmental variable "VSPHERE_InteractiveGuestOperationsReady" with a value of "false" [vSphere] Added environmental variable "VSPHERE_GuestStateChangeSupported" with a value of "true" [vSphere] Skipped "GenerationInfo" as it is of type class [Lcom.vmware.vim25.GuestInfoNamespaceGenerationInfo; [vSphere] Added environmental variable "VSPHERE_ToolsStatus" with a value of "toolsOk" [vSphere] Added environmental variable "VSPHERE_ToolsVersionStatus" with a value of "guestToolsUnmanaged" [vSphere] Added environmental variable "VSPHERE_ToolsVersionStatus2" with a value of "guestToolsUnmanaged" [vSphere] Added environmental variable "VSPHERE_ToolsRunningStatus" with a value of "guestToolsRunning" [vSphere] Added environmental variable "VSPHERE_ToolsVersion" with a value of "2147483647" [vSphere] Added environmental variable "VSPHERE_GuestFamily" with a value of "linuxGuest" [vSphere] Added environmental variable "VSPHERE_GuestFullName" with a value of "Ubuntu Linux (64-bit)" [vSphere] Skipped "Net" as it is of type class [Lcom.vmware.vim25.GuestNicInfo; [vSphere] Skipped "IpStack" as it is of type class [Lcom.vmware.vim25.GuestStackInfo; [vSphere] Skipped "Disk" as it is of type class [Lcom.vmware.vim25.GuestDiskInfo; [vSphere] Skipped "Screen" as it is of type class com.vmware.vim25.GuestScreenInfo [vSphere] Added environmental variable "VSPHERE_GuestState" with a value of "running" [vSphere] Added environmental variable "VSPHERE_AppHeartbeatStatus" with a value of "appStatusGray" [vSphere] Skipped "GuestKernelCrashed" as it is a null value [vSphere] Added environmental variable "VSPHERE_AppState" with a value of "none" [vSphere] Added environmental variable "VSPHERE_GuestOperationsReady" with a value of "true" [vSphere] Added environmental variable "VSPHERE_GuestId" with a value of "ubuntu64Guest" [vSphere] Added environmental variable "VSPHERE_IpAddress" with a value of "10.0.24.55" [vSphere] Added environmental variable "VSPHERE_HostName" with a value of "vassilm-test" [vSphere] Successfully exposed guest info for VM
[JIRA] (JENKINS-50769) Deploying EAR to WAS 7 Issue with JDK
Title: Message Title
Andrew Closs updated an issue
Jenkins / JENKINS-50769
Deploying EAR to WAS 7 Issue with JDK
Change By:
Andrew Closs
Hello, I'm having an issue deploying an EAR file to WebSphere and I think it's related to the JDK. Running the Jenkins service under the IBM JDK 6 results in a StackOverflowError and crashing of the Jenkins service:{quote}... BUILD SUCCESSFUL Total time: 1 minute 2 seconds HeadlessWorkspaceSettings: RESTORED autoBuild=true maxFile=1048576 Connecting to IBM WebSphere Application Server... FATAL: null java.lang.StackOverflowError at java.lang.ClassLoader.loadClass(ClassLoader.java:668) ...{quote}Running the Jenkins service under:Oracle JDK 1.8, IBM JDK 1.8, and Oracle JDK 1.6results in it getting slightly farther, acknowledging the EAR file to deploy and not resulting in a StackOverFlowError: {quote}... BUILD SUCCESSFUL Total time: 1 minute 38 seconds HeadlessWorkspaceSettings: RESTORED autoBuild=true maxFile=1048576 Connecting to IBM WebSphere Application Server... The following artifacts will be deployed in this order... --- ProjectEAR_201804121146AM ProjectEar_201804171129AM .ear --- Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.getAppName(WebSphereDeploymentService.java:193) at org . jenkinsci . plugins . websphere.services.deployment.WebSphereDeploymentService.getAppName(WebSphereDeploymentService.java:169) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.getAppName(WebSphereDeployerPlugin.java:318) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.createArtifact(WebSphereDeployerPlugin.java:275) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.perform(WebSphereDeployerPlugin.java:197) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1783) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240)Caused by: com.ibm.websphere.management.application.client.AppDeploymentException: [Root exception is java.lang.IncompatibleClassChangeError: Implementing class]... {quote}These are excerpts are from the Jenkins GUI log. I've attached the console output of these, they have a few more details. As a note I've changed the projects runtime JDK of both Jenkins to IBM JDK6 and 8, Oracle JDK 6, 7, and 8. It doesn't seem to make a difference. As I read in the
[JIRA] (JENKINS-50851) Skipped count percentage is affected by integer rounding
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50851 Re: Skipped count percentage is affected by integer rounding Code changed in jenkins User: pauljohnston2009 Path: src/main/java/org/jenkinsci/plugins/xunit/threshold/SkippedThreshold.java http://jenkins-ci.org/commit/xunit-plugin/9bebef1f895a48439bfc7dcec635917743c6e1d7 Log: JENKINS-50851 Skipped count percentage is affected by integer rounding Integer division was causing percentSkipped to always be 0 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50825) Add editor ATH coverage for deleting steps and stages from a pipeline
Title: Message Title Karl Shultz started work on JENKINS-50825 Change By: Karl Shultz Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50805 Jenkins Blue Ocean won't show Agent when creating a Pipeline Change By: Karl Shultz Attachment: screenshot-3.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
