[JIRA] (JENKINS-53592) Build Pipeline Plugin GUI showing only last build# of child job if called multiple times and only once if from Post Build Action
Title: Message Title Arun Sangal created an issue Jenkins / JENKINS-53592 Build Pipeline Plugin GUI showing only last build# of child job if called multiple times and only once if from Post Build Action Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 2018-09-15 00:41 Labels: build-pipeline-plugin jenkins-plugin jenkins parent-child upstream-downstream job Priority: Major Reporter: Arun Sangal https://stackoverflow.com/questions/52340580/build-pipeline-plugin-jenkins-showing-last-build-number-of-child-job-called Same Child job called multiple times from Build and Post build action Shows same build # for the last run Only shows one box for multiple calls (from Post-Build Action) Add Comment
[JIRA] (JENKINS-53591) x-error header should be provided for ALL API error responses
Title: Message Title
Harvey Chapman updated an issue
Jenkins / JENKINS-53591
x-error header should be provided for ALL API error responses
Change By:
Harvey Chapman
While developing/extending a Hubot plugin which uses the Jenkins remote api, I noticed the 'x-error' header on responses for telling users what went wrong. It isn't always returned, though. It would be really handy to remote API users to always have an x-error header available. I don't think this should be too hard since the API is already returning the error string inside the middle of a large chunk of HTML.Here's an example:{code:java}POST 403 /job/skynet/job/the-job-name/config.xmlresponse headers:{ connection: 'close', date: 'Sat, 15 Sep 2018 00:17:31 GMT', 'x-content-type-options': 'nosniff', 'x-you-are-authenticated-as': 'hv-core', 'x-you-are-in-group-disabled': 'JENKINS-39402: use -Dhudson.security.AccessDeniedException2.REPORT_GROUP_HEADERS=true or use /whoAmI to diagnose', 'x-required-permission': 'hudson.model.Item.Configure', 'x-permission-implied-by': 'hudson.security.Permission.GenericConfigure, hudson.security.Permission.GenericUpdate, hudson.security.Permission.GenericWrite, hudson.model.Hudson.Administer', expires: 'Thu, 01 Jan 1970 00:00:00 GMT', 'cache-control': 'no-cache,no-store,must-revalidate', 'x-hudson-theme': 'default', 'content-type': 'text/html;charset=utf-8', 'set-cookie': [ 'JSESSIONID.4fc412a5=node0plyw4mi19q2wpexcmdu21pb321.node0;Path=/;HttpOnly' ], 'x-hudson': '1.395', 'x-jenkins': '2.121.1', 'x-jenkins-session': '21d95bc9', 'x-hudson-cli-port': '54901', 'x-jenkins-cli-port': '54901', 'x-jenkins-cli2-port': '54901', 'x-frame-options': 'sameorigin', 'x-instance-identity': 'MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAjzhBNV8jwC2dTf4HoRdG01MV94FjDykB57hQxWNQtNMoj8+/hz+yFhrtuh3fI7f8fKnQlqFH9Gyoe5D7rrBqtneHxBuLd8ALI0xLxnK24Fed3Wv1Fr78ETik/QKNTvuiJx8GGYKbyLSyh6gea2i9lkCICI8uKkcKNhqo1lKY+iUh6tUtR5dcpnF5IoqTDLuM8Q7lYP+nO/oWujuT+Ph5WNuHtBNpibdc5yha63ornzx8UmtQrT12v2n4xgxZ2p6ePifecTbd+JlCI74MmBWVL7FXryT3T/2XIB7LAGI/2QX0PMNVQHRgRc0fYruYKEXfMwkHCrdwo1K+ZkU7+o58mQIDAQAB', 'content-length': '6670', server: 'Jetty(9.4.z-SNAPSHOT)' } Snippet from the returned HTML body:Access Deniedhv-core is missing the Job/Configure permission {code}
Add Comment
[JIRA] (JENKINS-53591) x-error header should be provided for ALL API error responses
Title: Message Title
Harvey Chapman created an issue
Jenkins / JENKINS-53591
x-error header should be provided for ALL API error responses
Issue Type:
Improvement
Assignee:
Unassigned
Components:
core
Created:
2018-09-15 00:33
Environment:
Jenkins ver. 2.121.1
Priority:
Minor
Reporter:
Harvey Chapman
While developing/extending a Hubot plugin which uses the Jenkins remote api, I noticed the 'x-error' header on responses for telling users what went wrong. It isn't always returned, though. It would be really handy to remote API users to always have an x-error header available. I don't think this should be too hard since the API is already returning the error string inside the middle of a large chunk of HTML. Here's an example:
POST 403 /job/skynet/job/the-job-name/config.xml
response headers:
{ connection: 'close',
date: 'Sat, 15 Sep 2018 00:17:31 GMT',
'x-content-type-options': 'nosniff',
'x-you-are-authenticated-as': 'hv-core',
'x-you-are-in-group-disabled':
'JENKINS-39402: use -Dhudson.security.AccessDeniedException2.REPORT_GROUP_HEADERS=true or use /whoAmI to diagnose',
'x-required-permission': 'hudson.model.Item.Configure',
'x-permission-implied-by':
'hudson.security.Permission.GenericConfigure, hudson.security.Permission.GenericUpdate, hudson.security.Permission.GenericWrite, hudson.model.Hudson.Administer',
expires: 'Thu, 01 Jan 1970 00:00:00 GMT',
'cache-control': 'no-cache,no-store,must-revalidate',
'x-hudson-theme': 'default',
'content-type': 'text/html;charset=utf-8',
'set-cookie':
[ 'JSESSIONID.4fc412a5=node0plyw4mi19q2wpexcmdu21pb321.node0;Path=/;HttpOnly'
[JIRA] (JENKINS-53590) Increase user when use curl to visit Jenkins
Title: Message Title suren pi created an issue Jenkins / JENKINS-53590 Increase user when use curl to visit Jenkins Issue Type: Bug Assignee: suren pi Components: core Created: 2018-09-15 00:12 Priority: Major Reporter: suren pi When I use cmd `curl -u tom:password "http://localhost:8080/jenkins"` to visit Jenkins, then a user called 'tom' will be created. So if I create a shell to use lots of random users to visit Jenkins, then there are too many used users information in it. Discovered from https://groups.google.com/forum/#!topic/jenkinsci-zh/jKE-9cIyUWQ Add Comment
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Daniel Beck commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox I suspect it'll be one button, but it's reused a lot as the f:submit form control. Just needs someone to figure out where JS takes a wrong turn to address this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45419) 'Use Repository' setting does not find other remote urls if multiple repos are added to job
Title: Message Title Shawn Fox commented on JENKINS-45419 Re: 'Use Repository' setting does not find other remote urls if multiple repos are added to job Could someone explain how it is supposed to work? I think I am having the same issue with the latest plugin. It seems to get all of the branches from one of the repositories each time or gives the no git repository configured error. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49276) Support for Copy Artifact input parameter type
Title: Message Title Stuart Rowe edited a comment on JENKINS-49276 Re: Support for Copy Artifact input parameter type [~jamesdumay] [Copy Artifact| https://plugins.jenkins.io/copyartifact ] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49276) Support for Copy Artifact input parameter type
Title: Message Title Stuart Rowe commented on JENKINS-49276 Re: Support for Copy Artifact input parameter type https://plugins.jenkins.io/copyartifact Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53569) Remoting deadlock observed after upgrading to 3.26
Title: Message Title Jeff Thompson commented on JENKINS-53569 Re: Remoting deadlock observed after upgrading to 3.26 I haven't had a chance to examine your report any further, but I ran across something somewhere else and wondered if it might be similar to yours. From what I've read, this issue JENKINS-42187 can possibly appear to cause hangs relating to Docker and swarms. It sounds like your environment might be similar so I thought I pass this along to see if it provided any help to you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53588) [P4 Plugin] Shelve fails with 'tampered with after resolve' for utf8 files
Title: Message Title Stuart Rowe assigned an issue to Paul Allen Jenkins / JENKINS-53588 [P4 Plugin] Shelve fails with 'tampered with after resolve' for utf8 files Change By: Stuart Rowe Assignee: Paul Allen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53589) Evergreen client deletes should also remove the associated exploded plugin directories
Title: Message Title
Baptiste Mathus created an issue
Jenkins / JENKINS-53589
Evergreen client deletes should also remove the associated exploded plugin directories
Issue Type:
Improvement
Assignee:
R. Tyler Croy
Components:
evergreen
Created:
2018-09-14 21:56
Labels:
evergreen
Priority:
Major
Reporter:
Baptiste Mathus
Problem statement Though I think removing the .hpi only should work, I think this is safer to also delete the corresponding exploded plugin directory under ${JENKINS_VAR}.
ls -1Fd /evergreen/jenkins/*/*/docker-plugin*
/evergreen/jenkins/home/plugins/docker-plugin.hpi
/evergreen/jenkins/var/plugins/docker-plugin/ # this one should better be removed too
Expected behavior For a plugin P, both the:
P.hpi file under $JENKINS_HOME/plugins/
and the P directory under $JENKINS_VAR/plugins
Should be removed. So that we avoid any weird behaviour with Jenkins still picking up the exploded directory even if the hpi has been removed.
[JIRA] (JENKINS-53569) Remoting deadlock observed after upgrading to 3.26
Title: Message Title Jeff Thompson commented on JENKINS-53569 Re: Remoting deadlock observed after upgrading to 3.26 Basil Crow it is unlikely that any of the recent changes would have caused the behavior you are seeing. The one you reference shouldn't have caused this as it was a re-factoring or rearrangement to allow the remoting-kafka plugin access to some pieces. I don't have any insight into what might be going on in your system. I'm not familiar with any other reports like this. I'll try to take a little deeper look at your report when I get the chance. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title
Devin Nusbaum commented on JENKINS-46507
Re: Parallel Pipeline random java.lang.InterruptedException
I finally had a chance to take a look at this. Alexey Grigorov: You are using println inside of an @NonCPS method. It might seem like this should be ok, but behind the scenes println ends up calling the echo step, which means that you are executing Pipeline Steps inside of an @NonCPS method, which should not be done even though it may appear to work correctly in some cases. Toby Broyles If you have a minimal pipeline that can reproduce the issue, or a scenario in which you can reproduce the problem consistently it would be very helpful if you could post the Pipeline script and the build folder of one of the builds that failed with the exception here. Otherwise, it would be great to see your actual pipeline that is hitting the error so we can check for any similarities with Alexey's or Rick's Pipelines that might give us an idea of what is happening. The only way I have been able to reproduce anything remotely similar to the exceptions seen here has been to create @NonCPS methods that take more than 5 minutes to complete, which causes CpsThread#runNextChunk to interrupt the thread. AIUI that may very well be the code that is interrupting pp.get here, but even so, I am not sure why the CpsFlowExecution's program promise would be taking so long to load. My only theory is that in CpsThread#getThreadGroupSynchronously the local variable pp is set to the nonnull value of flowExecution.programPromise, but then maybe something else changes the value of flowExecution.programPromise, but we are still waiting on the stale program promise pp which does not complete for whatever reason and eventually it times out. If that is the issue, we might be able to fix this issue with a patch like the following to CpsThread#getThreadGroupSynchronously:
diff --git a/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsStepContext.java b/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsStepContext.java
index 2b90bec1..6f0a45cb 100644
--- a/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsStepContext.java
+++ b/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsStepContext.java
@@ -63,6 +63,8 @@ import java.util.concurrent.Callable;
import java.util.concurrent.ExecutionException;
import java.util.concurrent.ExecutorService;
import java.util.concurrent.Executors;
+import java.util.concurrent.TimeUnit;
+import java.util.concurrent.TimeoutException;
import java.util.logging.Level;
import java.util.logging.Logger;
import jenkins.model.CauseOfInterruption;
@@ -241,14 +243,19 @@ public class CpsStepContext extends DefaultStepContext { // TODO add XStream cla
if (threadGroup == null) {
ListenableFuture pp;
CpsFlowExecution flowExecution = getFlowExecution();
+while (true) {
while ((pp = flowExecution.programPromise) == null) {
Thread.sleep(100); // TODO does JENKINS-33005 remove the need for this?
}
try {
-threadGroup = pp.get();
+// Wait in 30-second intervals in case the local variable pp becomes stale.
+threadGroup = pp.get(30, TimeUnit.SECONDS);
+} catch (TimeoutException e) {
+// Update reference to flowExecution.programPromise and attempt to load it again.
} catch (ExecutionException e) {
throw new IOException(e);
}
+
[JIRA] (JENKINS-53529) Evergreen client should be able to automatically update itself
Title: Message Title R. Tyler Croy started work on JENKINS-53529 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53588) [P4 Plugin] Shelve fails with 'tampered with after resolve' for utf8 files
Title: Message Title
Stuart Rowe created an issue
Jenkins / JENKINS-53588
[P4 Plugin] Shelve fails with 'tampered with after resolve' for utf8 files
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-09-14 20:29
Environment:
Jenkins LTS 2.121.1 on CentOS Linux release 7.3.1611 (Core) p4-plugin 1.8.15 P4 Server version: P4D/LINUX26X86_64/2017.2/1622831 (2018/02/20) P4 Client on Windows 10
Labels:
p4-plugin
Priority:
Major
Reporter:
Stuart Rowe
Steps to reproduce:
Create a new file with type
Branch that file
Edit and submit changes to the original file
Run a Jenkins pipeline job with steps similar to below:
// helper method for creating a changelist
def createChangelist(p4) {
def changelistId = -1
def changeForm = p4.fetch("change", "")
changeForm.put("Description", "Integrate")
def changeMsg = p4.save("change", changeForm)
def changeOutput = changeMsg[0].get("change")
if (changeOutput) {
def match = changeOutput =~ /Change (\d+)/
changelistId = match[0][1]
}
return changelistId
}
node {
//
[JIRA] (JENKINS-53587) Sequential parallel stages show green while still running
Title: Message Title Ilya Lederman updated an issue Jenkins / JENKINS-53587 Sequential parallel stages show green while still running Change By: Ilya Lederman Summary: Sequential parallel stages show as green while still running Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53587) Sequential parallel stages show as still running
Title: Message Title Ilya Lederman created an issue Jenkins / JENKINS-53587 Sequential parallel stages show as still running Issue Type: Bug Assignee: Unassigned Attachments: image-2018-09-14-13-20-29-471.png Components: blueocean-plugin Created: 2018-09-14 20:24 Environment: org.jenkins-ci.main:jenkins-war:2.121.1 org.jenkins-ci:crypto-util:1.1 commons-httpclient:commons-httpclient:3.1-jenkins-1 aopalliance:aopalliance:1.0 org.jenkins-ci.main:jenkins-core:2.121.1 org.kohsuke.stapler:stapler-jelly:1.254 com.google.inject:guice:4.0 org.jenkins-ci.modules:slave-installer:1.6 org.springframework:spring-dao:1.2.9 org.jenkins-ci.modules:instance-identity:2.1 org.jenkins-ci:constant-pool-scanner:1.2 org.connectbot.jbcrypt:jbcrypt:1.0.0 org.jenkins-ci.modules:ssh-cli-auth:1.4 org.ow2.asm:asm-commons:5.0.3 org.jenkins-ci:symbol-annotation:1.1 com.github.jnr:jnr-constants:0.9.8 org.jenkins-ci.modules:windows-slave-installer:1.9.2 commons-digester:commons-digester:2.1 commons-io:commons-io:2.4 org.kohsuke:trilead-putty-extension:1.2 commons-codec:commons-codec:1.9 net.sf.kxml:kxml2:2.3.0 org.kohsuke:libzfs:0.8 org.jenkins-ci.ui:jquery-detached:1.2 org.kohsuke.stapler:json-lib:2.4-jenkins-2 org.jvnet.robust-http-client:robust-http-client:1.2 org.ow2.asm:asm:5.0.3 net.java.sezpoz:sezpoz:1.12 org.kohsuke.stapler:stapler-adjunct-timeline:1.5 org.slf4j:log4j-over-slf4j:1.7.25 org.jenkins-ci:version-number:1.4 org.codehaus.groovy:groovy-all:2.4.11 org.jvnet.hudson:commons-jelly-tags-define:1.0.1-hudson-20071021 org.jenkins-ci:jmdns:3.4.0-jenkins-3 commons-lang:commons-lang:2.6 org.springframework:spring-jdbc:1.2.9 org.codehaus.woodstox:wstx-asl:3.2.9 org.springframework:spring-core:2.5.6.SEC03 org.springframework:spring-aop:2.5.6.SEC03 org.samba.jcifs:jcifs:1.3.17-kohsuke-1 org.jenkins-ci:bytecode-compatibility-transformer:1.8 org.apache.ant:ant:1.9.2 com.sun.solaris:embedded_su4j:1.1 javax.inject:javax.inject:1 org.jenkins-ci.modules:upstart-slave-installer:1.1 org.apache.commons:commons-compress:1.10 commons-beanutils:commons-beanutils:1.8.3 org.jvnet.localizer:localizer:1.24 org.fusesource.jansi:jansi:1.11 org.jenkins-ci.modules:sshd:2.4 org.springframework:spring-beans:2.5.6.SEC03 javax.xml.stream:stax-api:1.0-2 org.slf4j:slf4j-jdk14:1.7.25 org.jvnet.hudson:activation:1.1.1-hudson-1 org.jenkins-ci.main:cli:2.121.1 commons-jelly:commons-jelly-tags-fmt:1.0
[JIRA] (JENKINS-24998) Introduce 'Make me an owner' button
Title: Message Title Supun Wanniarachchi updated an issue Jenkins / JENKINS-24998 Introduce 'Make me an owner' button Change By: Supun Wanniarachchi Labels: google-code-in newbie-friendly user-experience Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48375) Jenkins RSS feeds are actually Atom feeds
Title: Message Title Supun Wanniarachchi updated an issue Jenkins / JENKINS-48375 Jenkins RSS feeds are actually Atom feeds Change By: Supun Wanniarachchi Labels: google-code-in newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17116) gracefull job termination
Title: Message Title Antoine Musso commented on JENKINS-17116 Re: gracefull job termination The merge https://github.com/jenkinsci/jenkins/commit/d8eac92ee9a1c19bf145763589f1c152607bf3ed is in tag jenkins-2.141 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52093) Exploratory testing of K8s plugin with Java 10/11
Title: Message Title Supun Wanniarachchi updated an issue Jenkins / JENKINS-52093 Exploratory testing of K8s plugin with Java 10/11 Change By: Supun Wanniarachchi Labels: google-code-in java10_hackathon newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50684) declarative pipeline P4_CHANGELIST + P4_CLIENT uses Jenkinsfile value, not workspace mapping in the Jenkinsfile script
Title: Message Title
Daniel Hsueh updated an issue
Jenkins / JENKINS-50684
declarative pipeline P4_CHANGELIST + P4_CLIENT uses Jenkinsfile value, not workspace mapping in the Jenkinsfile script
Change By:
Daniel Hsueh
The P4_CHANGELIST and P4_CLIENT values seen in the environment end up with values from the Jenkinsfile checkout, and not from the workspace mapping in the script.I have checked against ---JENKINS-42411--- and ---JENKINS-38401--- and attempted the workarounds. I usually name the workspace for For both lightweight and regular Jenkinsfile checkout from SCM with a '{{\-jenkinsfile}}' suffix, and it automagically changes to "{{jenkinsTemp-(uuid)}}" at some point in time without my intervention, but in all cases the console output shows a uuid workspace or a workspace name different from my in-script '{{jenkins\-$\{NODE_NAME\}\-$\{JOB_NAME\}}}' or '{{jenkins\-$\{JOB_NAME\}}}' value. resulting The environment P4_CHANGELIST and P4_CLIENT values reflect the script checkout, not the checkout invoked in the script.(The results of the checkout invoked in the script seem to have the correct perforce retrieval though. The console output show the correct in-script workspace name used in p4 client/changes/reconcile/sync commands.)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down ok, this one looks better if agents work correctly for a while and then start to fail randomly, in that case, the issue could be related to JENKINS-49235 . There is a workaround https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/doc/TROUBLESHOOTING.md#threads-stuck-at-credentialsprovidertrackall, in any case, I will test it on EC2 to see if I can replicate it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-53468 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down config_linux.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila updated an issue Jenkins / JENKINS-53468 Since 1.27 update Channel is closing or has closed down Change By: John Zila Attachment: config_linux.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down Oops I gave you the config for one of our Windows agents. Let me attach the config for one of our linux agents. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down you have configured 'c:\Jenkins' as working dir (remoteFS and fsRoot) in the agents, probably this path does not exist on a linux agent, I think that is your problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51424) Prototype integration between Code Coverage API and Cobertura plugin
Title: Message Title Jeff Pearce updated JENKINS-51424 Released in version 1.13 Jenkins / JENKINS-51424 Prototype integration between Code Coverage API and Cobertura plugin Change By: Jeff Pearce Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53586) Launcher.ProcStarter.readStderr() has no effect
Title: Message Title Yuxiang Zhu created an issue Jenkins / JENKINS-53586 Launcher.ProcStarter.readStderr() has no effect Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: core Created: 2018-09-14 17:40 Priority: Major Reporter: Yuxiang Zhu Hi, I found Launcher.ProcStarter.readStderr() has no effect when developing a Jenkins plugin. After calling `readStderr`, the stderr of the remote process is still merged to `stdout` while `Proc.getStderr()` will always get a stream with empty content. I currently don't have time to look at the code carefully or fix it, but I guess it is caused by the following reason: What readStderr() does is just setting `reverseStderr` to true, resulting in the err parameter passed to LocalProc is set to LocalProc.SELFPUMP_OUTPUT ( https://github.com/jenkinsci/jenkins/blob/stable-2.138/core/src/main/java/hudson/Launcher.java#L934), otherwise err parameter will be set to null. But the construct of LocalProc will set the redirectError parameter of ProcessBuilder to true in both cases (https://github.com/jenkinsci/jenkins/blob/stable-2.138/core/src/main/java/hudson/Proc.java#L219). If my understanding is correct, the `redirectError` parameter should be set to true only when `err == null`. Add
[JIRA] (JENKINS-53539) org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-53539 org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53585) ppublishHTML support for mutliple reports
Title: Message Title Mark Huijgen created an issue Jenkins / JENKINS-53585 ppublishHTML support for mutliple reports Issue Type: Improvement Assignee: Richard Bywater Components: htmlpublisher-plugin Created: 2018-09-14 17:02 Priority: Minor Reporter: Mark Huijgen It would be nice if the pipeline workflow publishHTML would support setting multiple targets like the plugin already does for standard jenkins jobs where multiple reports can be added. Currently if publisHTML is called twice in a pipeline only the report of the last call is saved in the project and the first is lost. And the call also does not support setting an array of targets. Add Comment
[JIRA] (JENKINS-53556) Fix invalid proxy settings and validation
Title: Message Title Naresh Rayapati commented on JENKINS-53556 Re: Fix invalid proxy settings and validation Released this with 1.1.1, should be available in the update center soon. Thank you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53556) Fix invalid proxy settings and validation
Title: Message Title Naresh Rayapati closed an issue as Fixed Jenkins / JENKINS-53556 Fix invalid proxy settings and validation Change By: Naresh Rayapati Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53556) Fix invalid proxy settings and validation
Title: Message Title Naresh Rayapati updated JENKINS-53556 Jenkins / JENKINS-53556 Fix invalid proxy settings and validation Change By: Naresh Rayapati Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52525) Investigate switchinig evergreen-client to use strictly socket.io messaging
Title: Message Title R. Tyler Croy updated JENKINS-52525 Jenkins / JENKINS-52525 Investigate switchinig evergreen-client to use strictly socket.io messaging Change By: R. Tyler Croy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53541) Provide an API for a client to record a tainted update level
Title: Message Title R. Tyler Croy updated JENKINS-53541 Jenkins / JENKINS-53541 Provide an API for a client to record a tainted update level Change By: R. Tyler Croy Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53581) Folders- provide info, groovy, how to get permissions
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-53581
Re: Folders- provide info, groovy, how to get permissions
Hi, it is better to use the jenkins jenkinsci - ci users mailing list for a question like this instead of opening a bug on the bug tracker: [ https://jenkins.io/mailing-lists/ ] .As the error message states, your error is from this line: {code :java }AbstractProject proj = Hudson.instance.getItem(it.fullName){code} Folders are not a subtype of AbstractProject, so this fails. You should use AbstractFolder as the type on the left hand side, and if you are using {{it.fullName}} you should use {{Jenkins.instance.getItemByFullName}}.If that doesn't fix the issue for you, please send an email to the mailing list explaining what you are trying to accomplish (i.e. why are you trying to get folder permissions in the groovy console), and we can help you work through any other issues there.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53543) evergreen-client should re-authenticate when the jwt has expired.
Title: Message Title R. Tyler Croy updated JENKINS-53543 Jenkins / JENKINS-53543 evergreen-client should re-authenticate when the jwt has expired. Change By: R. Tyler Croy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53581) Folders- provide info, groovy, how to get permissions
Title: Message Title Devin Nusbaum closed an issue as Not A Defect Jenkins / JENKINS-53581 Folders- provide info, groovy, how to get permissions Change By: Devin Nusbaum Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51304) All evergreen-client calls should retry on connection failures.
Title: Message Title R. Tyler Croy updated JENKINS-51304 Jenkins / JENKINS-51304 All evergreen-client calls should retry on connection failures. Change By: R. Tyler Croy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53581) Folders- provide info, groovy, how to get permissions
Title: Message Title Devin Nusbaum commented on JENKINS-53581 Re: Folders- provide info, groovy, how to get permissions Hi, it is better to use the jenkins-ci mailing list for a question like this instead of opening a bug on the bug tracker: https://jenkins.io/mailing-lists/. As the error message states, your error is from this line: AbstractProject proj = Hudson.instance.getItem(it.fullName) Folders are not a subtype of AbstractProject, so this fails. You should use AbstractFolder as the type on the left hand side, and if you are using it.fullName you should use Jenkins.instance.getItemByFullName. If that doesn't fix the issue for you, please send an email to the mailing list explaining what you are trying to accomplish (i.e. why are you trying to get folder permissions in the groovy console), and we can help you work through any other issues there. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22172) "Copy this job" menu item in context menu of each job in any job view
Title: Message Title Sven Schoenung commented on JENKINS-22172 Re: "Copy this job" menu item in context menu of each job in any job view Not related to the view-job-filters-plugin as far as I can see. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22172) "Copy this job" menu item in context menu of each job in any job view
Title: Message Title Sven Schoenung updated an issue Jenkins / JENKINS-22172 "Copy this job" menu item in context menu of each job in any job view Change By: Sven Schoenung Component/s: core Component/s: view-job-filters-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22438) View Job Filters - Need to hide views
Title: Message Title Sven Schoenung resolved as Won't Do Jenkins / JENKINS-22438 View Job Filters - Need to hide views Change By: Sven Schoenung Status: Open Resolved Assignee: Jacob Robertson Sven Schoenung Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22438) View Job Filters - Need to hide views
Title: Message Title Sven Schoenung commented on JENKINS-22438 Re: View Job Filters - Need to hide views If this means excluding jobs that are in another view, there's already the Other Views Filter for that. If this means actually hiding a view in the Jenkins UI then that's out of scope for this plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46809) Allow sequential stages inside parallel in Declarative syntax
Title: Message Title Oliver Santschi commented on JENKINS-46809 Re: Allow sequential stages inside parallel in Declarative syntax Does this example works for anyone? Do I need a special version for a special plugin? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46822) Document license for view-job-filters-plugin
Title: Message Title Sven Schoenung resolved as Fixed Jenkins / JENKINS-46822 Document license for view-job-filters-plugin Change By: Sven Schoenung Status: Open Resolved Assignee: Jacob Robertson Sven Schoenung Resolution: Fixed Released As: https://github.com/jenkinsci/view-job-filters-plugin/releases/tag/view-job-filters-2.0.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46822) Document license for view-job-filters-plugin
Title: Message Title Sven Schoenung commented on JENKINS-46822 Re: Document license for view-job-filters-plugin License was clarified and included with the 2.0.0 release. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44070) Single emoji not an acceptable view name
Title: Message Title Sven Schoenung updated an issue Jenkins / JENKINS-44070 Single emoji not an acceptable view name Change By: Sven Schoenung Component/s: core Component/s: view-job-filters-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44070) Single emoji not an acceptable view name
Title: Message Title Sven Schoenung commented on JENKINS-44070 Re: Single emoji not an acceptable view name Not sure what this has to do with the view-job-filters-plugin. The 'newView' page is part of Jenkins core, not this plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53584) Replayed build message is "replayed # $2"
Title: Message Title Jeff Allen created an issue Jenkins / JENKINS-53584 Replayed build message is "replayed # $2" Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2018-09-14 15:46 Priority: Minor Reporter: Jeff Allen On version 1.8.2 · Core 2.138.1, when I click replay on a build, the message on the new build is "Replay # $2". I bet that the $2 is supposed to be interpolated to something real. Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Jesse Glick commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should I do not see any reason to think that this issue is specific to Declarative vs. Scripted. Nor do I think it is necessarily a “huge amount of work”. There is already an API to indicate that a step failed: ErrorAction. This is added implicitly when StepContext.onFailure is called. The overall build status is set to failed (or some other statuses, acc. to FlowInterruptedException) if the FlowEndNode is marked this way, typically because the error was not caught and handled. To set a less severe result, there is a StepContext.setResult API. Unfortunately the implementation in CpsStepContext simply sets an overall build status, which is not useful, and anyway JUnitResultsStepExecution does not call it. There could perhaps be a new action type retroactively implemented by ErrorAction, or somehow related to it, which would be added to a FlowNode when setResult is called and which just defines a getResult method. This would allow JUnitResultsStepExecution to set a per-step UNSTABLE status instead of a build result, at least optionally. (I think this would need to be opt-in for compatibility reasons, unless you declare that setting a step result also makes the build result at least as bad, which may be unwanted.) Then FlowNode.getIconColor would honor the new action, causing Pipeline Steps in the classic UI to show yellow balls where appropriate, and Blue Ocean would need to be patched to do the same. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41929) Offer "Build with Parameters" on first build when declarative Jenkinsfile found
Title: Message Title
Falko Modler commented on JENKINS-41929
Re: Offer "Build with Parameters" on first build when declarative Jenkinsfile found
I am also affected by this:
Jenkinsfile from SCM
string parameter with defaultValue
value is accessed via ${params.[...]}
changed defaultValue is only picked up in the second build, not right away
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45041) Shared library pluging - can't use getResource to load a resource?
Title: Message Title Jesse Glick commented on JENKINS-45041 Re: Shared library pluging - can't use getResource to load a resource? Ilguiz Latypov’s comment is unrelated to the reported issue, but at any rate: perhaps you are selecting distinct names for the “same” library, which is not wise since it would result in both versions of the library being loaded in one build. Please use the users’ list for advice. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16352) Add ability to specify parameters in the crontab
Title: Message Title Bassam Khouri commented on JENKINS-16352 Re: Add ability to specify parameters in the crontab "Parameterized Scheduler" plugin's helpdoc has the following Clicking on "this Jenkins issue" points to this ticket. Clearly, the original author the "Parameterized Scheduler" plugin has idea to integrate the plugin into the core. This ticket should be reopened, or the help test from the "Parameterized Schedule" plugin should be updated. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Ernst de Haan commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Fully agree with Brian J Murrell. But then should we split this ticket in two? Then… …one of them (declarative) could be picked up and resolved, …while the other one (scripted) could potentially be implemented on a different schedule. An additional benefit could be that when we've got the solution in place for the declarative pipeline, the challenge for implementing the fix for scripted could be reduced, because we already have a guiding implementation in place (the one for declarative). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16352) Add ability to specify parameters in the crontab
Title: Message Title Bassam Khouri updated an issue Jenkins / JENKINS-16352 Add ability to specify parameters in the crontab Change By: Bassam Khouri Attachment: Screen Shot 2018-09-14 at 11.07.22 AM.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26148) Incorrect implementation of RetryStepExecution.stop
Title: Message Title Jesse Glick commented on JENKINS-26148 Re: Incorrect implementation of RetryStepExecution.stop Looks that way. Thanks for noticing! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Brian J Murrell commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should While I can appreciate the desire for a single solution to address both Pipeline styles, if a solution for one of the styles is relatively easy while the other quite complex, let's not let the perfect be the enemy of the good here. Please. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53561) ApiTokenStore.HashedToken is not serializable
Title: Message Title James Nord resolved as Fixed Jenkins / JENKINS-53561 ApiTokenStore.HashedToken is not serializable Change By: James Nord Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Sam Van Oort commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines Mike Kozell That specific case sounds a lot like a gremlin we've been chasing on and off for quite a while. I'm assigning this to Jose Blas Camacho Taboada to investigate. I think what you report may be independent of what was discussed here though which is probably the root cause of the issue: https://issues.jenkins-ci.org/browse/JENKINS-34256?focusedCommentId=336282=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-336282 through https://issues.jenkins-ci.org/browse/JENKINS-34256?focusedCommentId=332080=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-332080 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26148) Incorrect implementation of RetryStepExecution.stop
Title: Message Title Sam Van Oort updated JENKINS-26148 Jesse Glick I think we got all the parts released here, right? Jenkins / JENKINS-26148 Incorrect implementation of RetryStepExecution.stop Change By: Sam Van Oort Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Sam Van Oort assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-46507 Parallel Pipeline random java.lang.InterruptedException Change By: Sam Van Oort Assignee: Sam Van Oort Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Sam Van Oort assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-34256 Preparing Jenkins For Shutdown Hangs Running Pipelines Change By: Sam Van Oort Assignee: Sam Van Oort Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46067) Pipeline task scheduled on uninitialized node
Title: Message Title Sam Van Oort assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-46067 Pipeline task scheduled on uninitialized node Change By: Sam Van Oort Assignee: Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40839) pipeline timeout doesn't kill the job
Title: Message Title Sam Van Oort assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-40839 pipeline timeout doesn't kill the job Change By: Sam Van Oort Assignee: Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48556) timestamps() randomly not recognized as a valid option
Title: Message Title Bart Van Haute commented on JENKINS-48556 Re: timestamps() randomly not recognized as a valid option got the same problem today. the same build worked before , without having been rebooted , or updates of the jenkins or plugins jenkins 2.1.141 Pipeline:Declarative : 1.3.2 timestamper 1.8.10 error : org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 7: Invalid option type "timestamps". Valid option types: [authorizationMatrix, buildDiscarder, catchError, checkoutToSubdirectory, disableConcurrentBuilds, disableResume, durabilityHint, gitLabConnection, gitlabBuilds, newContainerPerStage, overrideIndexTriggers, preserveStashes, quietPeriod, retry, script, skipDefaultCheckout, skipStagesAfterUnstable, timeout, withCredentials, ws] @ line 7, column 9. timestamps() ^ 1 error at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:131) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:125) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:560) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:521) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:330) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-53583) Error when executing UFT test with the Micro Focus plugin
Title: Message Title Pere Felices edited a comment on JENKINS-53583 Re: Error when executing UFT test with the Micro Focus plugin The job that is showing the error is configured just with 2 steps:*Build section:* "Execute functional tests from Micro Focus ALM" (with a proper user and a proper path to the Test Set)*Post-build Actions:* "Publish Micro Focus test Result" (Always archive test reports)This configuration job was working fine in the agents with my the previous configuration version of the plugin .I have tried executing the script manually from the agent (opening ALM and executing the script from there), and works fine. So, it seems that the error is with the plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53246) Regression in pipeline job features.
Title: Message Title Sam Van Oort commented on JENKINS-53246 Re: Regression in pipeline job features. I've marked this one as "cannot reproduce" because it sounds like the issue is not reproducible, but we can re-open it if you can provide the information to reproduce it and confirm that Jose's information did not resolve it for you. Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53583) Error when executing UFT test with the Micro Focus plugin
Title: Message Title Pere Felices commented on JENKINS-53583 Re: Error when executing UFT test with the Micro Focus plugin The job that is showing the error is configured just with 2 steps: Build section: "Execute functional tests from Micro Focus ALM" (with a proper user and a proper path to the Test Set) Post-build Actions: "Publish Micro Focus test Result" (Always archive test reports) This configuration fine in the agents with my previous configuration. I have tried executing the script manually from the agent (opening ALM and executing the script from there), and works fine. So, it seems that the error is with the plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53246) Regression in pipeline job features.
Title: Message Title Sam Van Oort closed an issue as Cannot Reproduce Jenkins / JENKINS-53246 Regression in pipeline job features. Change By: Sam Van Oort Status: In Progress Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Brian Villanueva commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Georg Henzler - Thanks for the suggestion on using IllegalStateException to turn single stage red. Does this work for the Blue Ocean UI as well? Michael Neale - Are you suggesting that the scope of this issue be narrowed to declarative syntax? I would imagine that many of the voters and watchers of this issue are using scripted pipelines. I know we are, as there are many advanced scenarios that simply are not feasible using declarative syntax. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53583) Error when executing UFT test with the Micro Focus plugin
Title: Message Title Pere Felices created an issue Jenkins / JENKINS-53583 Error when executing UFT test with the Micro Focus plugin Issue Type: Bug Assignee: Kevin Lee Components: microfocus-da-plugin Created: 2018-09-14 13:36 Environment: Micro Focus Application Automation Tools v.5.5 JIRA: 2.138.1 ALM: 12.20 UFT: 14.50 Labels: plugin MicroFocus uft-integration Priority: Critical Reporter: Pere Felices After upgrading to the new "Micro Focus Application Automation Tools" plugin (v.5.5), from the version 5.4, I have experienced errors in the executions and the jobs are no longer working. The error shown is: Test: [1]X, Status: Error, Message: Unified Functional Testing error: Unable to connect the testing tool to the requested ALM/QC server. Error from Unified Functional Testing: Failure in Spider Module Process. Error: This type of installation requires that UAC be disabled. Disable UAC or run the program with administrator privileges \nLink: td://YY:8080/qcbin/TestLabModule-3649890581?EntityType=IRun=6948\n Previously, the jobs were working fine with this configuration: Micro Focus Application Automation Tools v.5.4 JIRA: 2.138.1 ALM: 12.20 UFT: 14.50
[JIRA] (JENKINS-53127) Parallel sequential stages should display stage label
Title: Message Title Hokwang Lee commented on JENKINS-53127 Re: Parallel sequential stages should display stage label By the way, did you try failFast true option? there is bug also. If one stage failed, all other stage running same time shows fail mark. So I can not find easily which one is really failed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53127) Parallel sequential stages should display stage label
Title: Message Title Hokwang Lee commented on JENKINS-53127 Re: Parallel sequential stages should display stage label The reason why I mentioned "Building and ..." , stages name, is they choose stages name for showing rather than stage name. I think they consider and have to make a dicision for showing which one at implementing this feature step. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53509) Job created inside a view inside a folder does not give the option to add the job to the view
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-53509 Job created inside a view inside a folder does not give the option to add the job to the view Change By: Devin Nusbaum Component/s: core Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53509) Job created inside a view inside a folder does not give the option to add the job to the view
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-53509
Re: Job created inside a view inside a folder does not give the option to add the job to the view
[~wbagdon] Thanks for opening the issue! This seems reasonable at a glance, although I am a little concerned about whether there may be any compatibility issues if the URL were changed. I think as long as it still used the current URL when the {{All}} view was selected then there would probably be no issue. That said, I don't have any plans to fix this. Maybe [~fcojfernandez] who was recently added as a maintainer would be interested in taking a look.If you wanted to take a look at fixing it yourself, I think based on [sidepanel.jelly|https://github.com/jenkinsci/cloudbees-folder-plugin/blob/master/src/main/resources/com/cloudbees/hudson/plugins/folder/AbstractFolder/sidepanel.jelly] in cloudbees-folder, the {{view}} variable should be defined and available to use when creating the New Item link in [tasks-create.jelly| https://github.com/jenkinsci/cloudbees-folder-plugin/blob/fbc2799b46d5a8bf33c4e8f63df7c2b6e1b179e3/src/main/resources/com/cloudbees/hudson/plugins/folder/Folder/tasks-create.jelly#L27], so I'd see if you can use {{view}} in tasks-create.jelly to create a better link in some cases. I'm not sure if that's the right approach, but it's what I'd do look at first .
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53509) Job created inside a view inside a folder does not give the option to add the job to the view
Title: Message Title Devin Nusbaum commented on JENKINS-53509 Re: Job created inside a view inside a folder does not give the option to add the job to the view Bill Bagdon Thanks for opening the issue! This seems reasonable at a glance, although I am a little concerned about whether there may be any compatibility issues if the URL were changed. I think as long as it still used the current URL when the All view was selected then there would probably be no issue. That said, I don't have any plans to fix this. Maybe Francisco Fernández who was recently added as a maintainer would be interested in taking a look. If you wanted to take a look at fixing it yourself, I think based on sidepanel.jelly in cloudbees-folder, the view variable should be defined and available to use when creating the New Item link in tasks-create.jelly, so I'd see if you can use view in tasks-create.jelly to create a better link in some cases. I'm not sure if that's the right approach, but it's what I'd do. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53509) Job created inside a view inside a folder does not give the option to add the job to the view
Title: Message Title Devin Nusbaum assigned an issue to Unassigned Jenkins / JENKINS-53509 Job created inside a view inside a folder does not give the option to add the job to the view Change By: Devin Nusbaum Assignee: Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53545) Error while saving System Configuration in Jenkins
Title: Message Title Vivek Shukla assigned an issue to Sysdig Inc Jenkins / JENKINS-53545 Error while saving System Configuration in Jenkins Change By: Vivek Shukla Assignee: Sysdig Inc Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52939) Need to lint pipeline from UI, and also parse parameters
Title: Message Title Keith Zantow commented on JENKINS-52939 Re: Need to lint pipeline from UI, and also parse parameters I'd suggest to add a different ticket for Updating Input Parameters. It's currently a limitation of pipeline itself, nothing to do with blue ocean or jenkins ui per se. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53545) Error while saving System Configuration in Jenkins
Title: Message Title Vivek Shukla assigned an issue to Sysdig Inc Jenkins / JENKINS-53545 Error while saving System Configuration in Jenkins Change By: Vivek Shukla Component/s: sysdig-secure-plugin Component/s: core Assignee: Sysdig Inc Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53545) Error while saving System Configuration in Jenkins
Title: Message Title Vivek Shukla assigned an issue to Unassigned Jenkins / JENKINS-53545 Error while saving System Configuration in Jenkins Change By: Vivek Shukla Component/s: core Component/s: sysdig-secure-plugin Assignee: Sysdig Inc Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53545) Error while saving System Configuration in Jenkins
Title: Message Title Vivek Shukla updated an issue Jenkins / JENKINS-53545 Error while saving System Configuration in Jenkins Change By: Vivek Shukla Component/s: core Component/s: systemloadaverage-monitor-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52939) Need to lint pipeline from UI, and also parse parameters
Title: Message Title Keith Zantow updated an issue Jenkins / JENKINS-52939 Need to lint pipeline from UI, and also parse parameters Change By: Keith Zantow Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52939) Need to lint pipeline from UI, and also parse parameters
Title: Message Title Keith Zantow commented on JENKINS-52939 Re: Need to lint pipeline from UI, and also parse parameters Craig Rodrigues yes, I mentioned there is a validation function already. If you load the editor, you can simply copy/paste a declarative pipeline - E.g. go to http:///blue/organizations/jenkins/pipeline-editor/ then press Ctrl-S / Cmd-S on windows/osx to get a text area to paste the pipeline into. It doesn't validate every bit of the pipeline, though, but does a good job of linting it: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53582) Success rate percentages are not calculated per-template
Title: Message Title Nick Jones created an issue Jenkins / JENKINS-53582 Success rate percentages are not calculated per-template Issue Type: Bug Assignee: Oliver Gondža Attachments: image-2018-09-14-09-06-45-111.png Components: cloud-stats-plugin Created: 2018-09-14 13:07 Environment: Cloud Statistics plugin 0.18 Priority: Minor Reporter: Nick Jones The "Overall success rate" and "Current success rate" displayed on the /cloud-stats/ page is simply the cloud-level rate repeated per row:This should be calculated per template (e.g., in my case, for vs2015, vs2017, and vs2013). Add Comment
[JIRA] (JENKINS-50921) Team Foundation Sercer plugin error: workspace is already mapped
Title: Message Title Serban Constantin commented on JENKINS-50921 Re: Team Foundation Sercer plugin error: workspace is already mapped Same problem here on Jenkins 2.121.3 using Team Foundation Server Plug-in version 5.139.2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52939) Need to lint pipeline from UI, and also parse parameters
Title: Message Title Keith Zantow updated an issue Jenkins / JENKINS-52939 Need to lint pipeline from UI, and also parse parameters Change By: Keith Zantow Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46940) Build pipeline plugin duplicates static linked jobs in view
Title: Message Title Oleg Vlasenko updated an issue Jenkins / JENKINS-46940 Build pipeline plugin duplicates static linked jobs in view Change By: Oleg Vlasenko Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53550) SSC - Octane integration - inject SSC vulnerabilities to Octane -us #587042 : Fortify OnPrem E2E
Title: Message Title Daniel Gront assigned an issue to Michael Seldin Jenkins / JENKINS-53550 SSC - Octane integration - inject SSC vulnerabilities to Octane -us #587042 : Fortify OnPrem E2E Change By: Daniel Gront Assignee: Daniel Gront Michael Seldin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41704) Clicking On `Cppcheck Results` From A Multi-Branch Pipeline Build Results In javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException
Title: Message Title Philip Pemberton commented on JENKINS-41704 Re: Clicking On `Cppcheck Results` From A Multi-Branch Pipeline Build Results In javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException I'm seeing this in Jenkins 2.141 too, with plugin 1.24. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53581) Folders- provide info, groovy, how to get permissions
Title: Message Title
Pavel Novak updated an issue
Jenkins / JENKINS-53581
Folders- provide info, groovy, how to get permissions
Change By:
Pavel Novak
Hi, just a question (I did not found another place where to ask)Is there any possibility how to obtain permissions for the folder job?I need something like permitted user (with permission level in ideal case) for the folder in jenkinsI tried this: {code:java}import com.cloudbees.hudson.plugins.folder.*import groovyjarjarasm.asm.Itemimport jenkins.model.Jenkinsimport hudson.security.*import hudson.model.*//AbstractProject proj = Hudson.instance.getItem("YourJob")//AuthorizationMatrixProperty authProperty = proj.getProperty(AuthorizationMatrixProperty.class) def items=Jenkins.instance.getAllItems();//load all items in jenkins items.each{ //get folders only if(it instanceof Folder){ // println it //print for debug AbstractProject proj = Hudson.instance.getItem(it.fullName) AuthorizationMatrixProperty authProperty = proj.getProperties(AuthorizationMatrixProperty.class) } }{code}But I cannot understand it fully, and this script returns {code:java}org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object 'com.cloudbees.hudson.plugins.folder.Folder@4c019d3f[foldername]' with class 'com.cloudbees.hudson.plugins.folder.Folder' to class 'hudson.model.AbstractProject'{code} I am using following, but it should not matters|[Matrix Authorization Strategy Plugin|http://wiki.jenkins-ci.org/display/JENKINS/Matrix+Authorization+Strategy+Plugin] |Can you advise how to get it, or where to put my question? Thanks in advance note * if I am correct, javadoc for cloudbee's folder class is https://javadoc.jenkins.io/plugin/cloudbees-folder/com/cloudbees/hudson/plugins/folder/Folder.html
Add Comment
[JIRA] (JENKINS-53581) Folders- provide info, groovy, how to get permissions
Title: Message Title
Pavel Novak updated an issue
Jenkins / JENKINS-53581
Folders- provide info, groovy, how to get permissions
Change By:
Pavel Novak
Hi, just a question (I did not found another place where to ask)Is there any possibility how to obtain permissions for the folder job?I need something like permitted user (with permission level in ideal case) for the folder in jenkinsI tried this: {code:java}import com.cloudbees.hudson.plugins.folder.*import groovyjarjarasm.asm.Itemimport jenkins.model.Jenkinsimport hudson.security.*import hudson.model.*//AbstractProject proj = Hudson.instance.getItem("YourJob")//AuthorizationMatrixProperty authProperty = proj.getProperty(AuthorizationMatrixProperty.class) def items=Jenkins.instance.getAllItems();//load all items in jenkins items.each{ //get folders only if(it instanceof Folder){ // println it //print for debug AbstractProject proj = Hudson.instance.getItem(it.fullName) AuthorizationMatrixProperty authProperty = proj.getProperties(AuthorizationMatrixProperty.class) } }{code}But I cannot understand it fully, and this script returns {code:java}org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object 'com.cloudbees.hudson.plugins.folder.Folder@4c019d3f[foldername]' with class 'com.cloudbees.hudson.plugins.folder.Folder' to class 'hudson.model.AbstractProject'{code} I am using following, but it should not matters|[Matrix Authorization Strategy Plugin|http://wiki.jenkins-ci.org/display/JENKINS/Matrix+Authorization+Strategy+Plugin] |Can you advise how to get it, or where to put my question? Thanks in advance
Add Comment
[JIRA] (JENKINS-53581) Folders- provide info, groovy, how to get permissions
Title: Message Title Pavel Novak updated an issue Jenkins / JENKINS-53581 Folders- provide info, groovy, how to get permissions Change By: Pavel Novak Environment: Jenkins ver. 2.121.2 + Folders plugin 6.5.1 + Matrix Authorization Strategy 2.3 Jenkins ver. 2.107.3 + Folders plugin 6.4 + Matrix Authorization Strategy 2.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Thales Pereira edited a comment on JENKINS-37324 Re: We would like a more meaningful description of a step Hi [~cliffmeyers], this was implemented ? or Or there's any alternative for this suggestion available for usage? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53581) Folders- provide info, groovy, how to get permissions
Title: Message Title
Pavel Novak created an issue
Jenkins / JENKINS-53581
Folders- provide info, groovy, how to get permissions
Issue Type:
Task
Assignee:
Devin Nusbaum
Components:
cloudbees-folder-plugin, matrix-auth-plugin
Created:
2018-09-14 11:12
Environment:
Jenkins ver. 2.121.2 Jenkins ver. 2.107.3
Labels:
groovy-script script groovy permission permissions folders
Priority:
Minor
Reporter:
Pavel Novak
Hi, just a question (I did not found another place where to ask) Is there any possibility how to obtain permissions for the folder job? I need something like permitted user (with permission level in ideal case) for the folder in jenkins I tried this:
import com.cloudbees.hudson.plugins.folder.*
import groovyjarjarasm.asm.Item
import jenkins.model.Jenkins
import hudson.security.*
import hudson.model.*
//AbstractProject proj = Hudson.instance.getItem("YourJob")
//AuthorizationMatrixProperty authProperty = proj.getProperty(AuthorizationMatrixProperty.class)
def items=Jenkins.instance.getAllItems();
//load all items in jenkins
items.each{
//get folders only
if(it instanceof Folder){
// println it
AbstractProject proj = Hudson.instance.getItem(it.fullName)
AuthorizationMatrixProperty authProperty = proj.getProperties(AuthorizationMatrixProperty.class)
}
}
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Thales Pereira commented on JENKINS-37324 Re: We would like a more meaningful description of a step Hi Cliff Meyers, this was implemented ? or there's any alternative for this suggestion available for usage? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53579) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-53579
Asynchronous cleanup not removing renamed workspace directories on slaves
Change By:
Jakub Bochenski
After upgrading to ws-cleanup 0.24 in order to get the asynchronous cleanup function we We noticed the workspaces on our slaves getting renamed to the form of ${WORKSPACE}_ws-cleanup_${TIMESTAMP}. (ie, job1 would become job1_ws-cleanup_1411197183394). The expected behavior under ws-cleanup 0.24 is that these were temporary to support asynchronous processing and would be deleted. However, these directories never get removed from the slave. Over time, the slave hard drives filled up resulting in build failures.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
