[JIRA] (JENKINS-12548) Read-only system configuration browsing
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-12548 Read-only system configuration browsing Change By: Tim Jacomb Labels: jcasc-compatibility multibranch Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.142914.1327605395000.18750.1588057260662%40Atlassian.JIRA.
[JIRA] (JENKINS-61204) Read-only system - Global tool configuration
Title: Message Title Tim Jacomb updated JENKINS-61204 Jenkins / JENKINS-61204 Read-only system - Global tool configuration Change By: Tim Jacomb Status: In Review Resolved Resolution: Fixed Released As: 2.233 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204754.1582562737000.18751.1588057440107%40Atlassian.JIRA.
[JIRA] (JENKINS-61201) Read-only system - About jenkins
Title: Message Title Tim Jacomb updated JENKINS-61201 Jenkins / JENKINS-61201 Read-only system - About jenkins Change By: Tim Jacomb Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204750.1582559353000.18752.1588057500188%40Atlassian.JIRA.
[JIRA] (JENKINS-56109) Change jenkins configuration ui from tables to divs
Title: Message Title Félix Queiruga Balado commented on JENKINS-56109 Re: Change jenkins configuration ui from tables to divs I'm gonna go ahead and put the checklist of TODO items here: Style for hierarchies of nested elements. This includes hetero lists and repeatable elements. Indentation problems caused by the .container class and the 15px padding it sets. Maybe we should create a new class for forms instead of reusing .container. This would also work to remove the width changes on this class. Checkbox fixes for the Git plugin & similar (I have a JS based solution for this but it needs a bit more work). refactor: move the helper text to inside the form entry element. refactor: move the validation errors to inside the form entry element - not the easiest due to the _javascript_. Verify that form submission (buildFormTree) still works properly. Too much spacing on the API key list on the user configuration (easy). Broken scroll-aware headers on the job configuration (this one is medium at best, difficult if we need to do lots of fixing for the JS tests). ⚠️ Broken drag & drop of repetable elements Pending: Forms are IMO too wide. I'd suggest adding a max-width for inputs but maybe it is out of scope for this. Fix offset of .validation-error-area Add Comment
[JIRA] (JENKINS-56109) Change jenkins configuration ui from tables to divs
Title: Message Title
Félix Queiruga Balado edited a comment on JENKINS-56109
Re: Change jenkins configuration ui from tables to divs
I'm gonna go ahead and put the checklist of TODO items here: * -Style for hierarchies of nested elements. This includes _hetero lists_ and repeatable elements.- * -Indentation problems caused by the {{.container}} class and the 15px padding it sets. Maybe we should create a new class for forms instead of reusing {{.container}}. This would also work to remove the width changes on this class.- * -Checkbox fixes for the Git plugin & similar (I have a JS based solution for this but it needs a bit more work).- * -{{}} refactor: move the helper text to inside the form entry element.- * -{{}} refactor: move the validation errors to inside the form entry element - not the easiest due to the _javascript_.- * -Verify that form submission (_buildFormTree_) still works properly.- * -Too much spacing on the API key list on the user configuration (easy).- * -Broken scroll-aware headers on the job configuration (this one is medium at best, difficult if we need to do lots of fixing for the JS tests).- * -⚠️ Broken drag & drop of repetable elements-Pending: * Forms are IMO too wide. I'd suggest adding a max-width for inputs but maybe it is out of scope for this. * Fix offset Tune styling of _ nesting indicator * Provide backwards compatibility for {{findFollowingTR(e, "validation-error-area")}} . Used directly in many plugins ([https://github.com/search?q=org%3Ajenkinsci+ validation-error- area_ area&type=Code])
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message b
[JIRA] (JENKINS-61744) Remote file plugin should allow to use folders or wildcards as marker files
Title: Message Title Andrey Hura commented on JENKINS-61744 Re: Remote file plugin should allow to use folders or wildcards as marker files Thank you for adding this functionality. The folder marker works as requested. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205573.158558355.18764.1588061220454%40Atlassian.JIRA.
[JIRA] (JENKINS-61744) Remote file plugin should allow to use folders or wildcards as marker files
Title: Message Title Andrey Hura updated JENKINS-61744 Jenkins / JENKINS-61744 Remote file plugin should allow to use folders or wildcards as marker files Change By: Andrey Hura Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205573.158558355.18766.1588061220716%40Atlassian.JIRA.
[JIRA] (JENKINS-62077) findFiles fails when executed in empty workspace
Title: Message Title
Christopher Fenner created an issue
Jenkins / JENKINS-62077
findFiles fails when executed in empty workspace
Issue Type:
Bug
Assignee:
rsandell
Components:
pipeline-utility-steps-plugin
Created:
2020-04-28 08:31
Environment:
Jenkins: 2.204.2 pipeline-utility-steps-plugin: 2.5.0
Priority:
Minor
Reporter:
Christopher Fenner
When executing `findFiles` with a glob pattern on an empty workspace, a `java.io.IOException` is raised stating that the workspace is not found. Pipeline script to reproduce
node{
deleteDir()
findFiles(glob: 'test')
}
Exception:
java.io.IOException: /var/jenkins_home/workspace/Test/FindFiles does not exist.
at hudson.FilePath.glob(FilePath.java:1932)
at hudson.FilePath.access$3200(FilePath.java:211)
at hudson.FilePath$ListGlob.invoke(FilePath.java:1906)
at hudson.FilePath$ListGlob.invoke(FilePath.java:1894)
at hudson.FilePath.act(FilePath.java:1075)
at hudson.FilePath.act(FilePath.java:1058)
at hudson.FilePath.list(FilePath.java:1892)
at hudson.FilePath.list(FilePath.java:1876)
at org.jenkinsci.plugins.pipeline.utility.steps.fs.FindFilesStepExecution.run(FindFilesStepExecution.java:63)
at org.jenkinsci.plugins.pipeline.utility.steps.fs.FindFilesStepExecution.run(FindFilesStepExecution.java:44)
at org.jenkinsci.plugins.workflow
[JIRA] (JENKINS-62040) pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan
Title: Message Title Anthony Guo commented on JENKINS-62040 Re: pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan any update? any clue? Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205931.1587715343000.18772.1588063020105%40Atlassian.JIRA.
[JIRA] (JENKINS-34217) add option to disable historical statistics gathering for test results
Title: Message Title Xavier Raynaud commented on JENKINS-34217 Re: add option to disable historical statistics gathering for test results Another patch tentative (based on Jim Carrothers one) is available here: https://github.com/jenkinsci/junit-plugin/pull/133 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169751.1460592535000.18774.1588063380242%40Atlassian.JIRA.
[JIRA] (JENKINS-62078) Jenkins sometimes is not able to index branches
Title: Message Title
Danny Heinrich updated an issue
Jenkins / JENKINS-62078
Jenkins sometimes is not able to index branches
Change By:
Danny Heinrich
Hey there,unfortunalty we've the following issues with a fresh Bitbucket AND fresh Jenkins installation # Jenkins got stuck on some branches when running "**branch indexing**" ## !Screenshot from 2020-04-28 12-03-35.png! # Jenkins got stuck when "**Running as **" (i cut the username from the picture) ## !Screenshot from 2020-04-28 11-59-57.png!I was unable to find log entries regarding to this issue.We just usually see the following:{code:java}Added a missed class for missing class telemetry. Class: javax.annotation.NonnullAdded a missed class for missing class telemetry. Class: javax.annotation.Nonnulljava.lang.ClassNotFoundException: javax.annotation.Nonnull at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1387) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1342) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1089) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522) at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.Class.forName(Class.java:398) at java.base/sun.reflect.generics.factory.CoreReflectionFactory.makeNamedType(CoreReflectionFactory.java:114) at java.base/sun.reflect.generics.visitor.Reifier.visitClassTypeSignature(Reifier.java:125) at java.base/sun.reflect.generics.tree.ClassTypeSignature.accept(ClassTypeSignature.java:49) at java.base/sun.reflect.annotation.AnnotationParser.parseSig(AnnotationParser.java:440) at java.base/sun.reflect.annotation.AnnotationParser.parseAnnotation2(AnnotationParser.java:242) at java.base/sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:121) at java.base/sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:73) at java.base/java.lang.reflect.Executable.declaredAnnotations(Executable.java:604) at java.base/java.lang.reflect.Executable.declaredAnnotations(Executable.java:602) at java.base/java.lang.reflect.Executable.getAnnotation(Executable.java:572) at java.base/java.lang.reflect.Method.getAnnotation(Method.java:695) at org.kohsuke.stapler.ClassDescriptor$1.compare(ClassDescriptor.java:153) at org.kohsuke.stapler.ClassDescriptor$1.compare(ClassDescriptor.java:150) at java.base/java.util.TimSort.countRunAndMakeAscending(TimSort.java:360) at java.base/java.util.TimSort.sort(TimSort.java:220) at java.base/java.util.Arrays.sort(Arrays.java:1441) at org.kohsuke.stapler.ClassDescriptor.findMethods(ClassDescriptor.java:150) at org.kohsuke.stapler.ClassDescriptor.(ClassDescriptor.java:85) at org.kohsuke.stapler.lang.KlassNavigator$1.getFunctions(KlassNavigator.java:216) at org.kohsuke.stapler.lang.KlassNavigator$1.getFunctions(KlassNavigator.java:141) at org.kohsuke.stapler.lang.Klass.getFunctions(Klass.java:98) at org.kohsuke.stapler.KlassDescriptor.(KlassDescriptor.java:27) at org.kohsuke.stapler.MetaClass.buildDispatchers(MetaClass.java:109) at org.kohsuke.s
[JIRA] (JENKINS-62078) Jenkins sometimes is not able to index branches
Title: Message Title Danny Heinrich created an issue Jenkins / JENKINS-62078 Jenkins sometimes is not able to index branches Issue Type: Bug Assignee: Mark Waite Attachments: Screenshot from 2020-04-28 11-59-57.png, Screenshot from 2020-04-28 12-03-35.png Components: bitbucket-plugin, git-plugin Created: 2020-04-28 10:07 Environment: Infrastructure * Atlassian Bitbucket v6.8.0 * nginx as reverse Proxy ** https to port jenkins:8080 * Jenkins 2.234 SCM: * Git plugin - 4.2.2 * Bitbucket Plugin - 1.1.11 Labels: Jenkins git-plugin bitbucket-plugin bitbucket-server Priority: Blocker Reporter: Danny Heinrich Hey there, unfortunalty we've the following issues with a fresh Bitbucket AND fresh Jenkins installation Jenkins got stuck on some branches when running "*branch indexing*" Jenkins got stuck when "*Running as *"
[JIRA] (JENKINS-62078) Jenkins sometimes is not able to index branches
Title: Message Title Danny Heinrich updated an issue Jenkins / JENKINS-62078 Jenkins sometimes is not able to index branches Change By: Danny Heinrich Environment: Infrastructure : * Atlassian Bitbucket v6.8.0* nginx as reverse Proxy* * https to port jenkins:8080* Jenkins 2.234SCM:* Git plugin - 4.2.2 * Bitbucket Plugin - 1.1.11 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205981.1588068429000.18826.1588068600237%40Atlassian.JIRA.
[JIRA] (JENKINS-62077) findFiles fails when executed in empty workspace
Title: Message Title
Christopher Fenner updated an issue
Jenkins / JENKINS-62077
findFiles fails when executed in empty workspace
Change By:
Christopher Fenner
When executing `findFiles` with a glob pattern on an empty workspace, a `java.io.IOException` is raised stating that the workspace is not found. Pipeline script to reproduce {code:java}node{ deleteDir() findFiles(glob: 'test')}{code} Exception: Exception: {code:java}java.io.IOException: /var/jenkins_home/workspace/Test/FindFiles does not exist. at hudson.FilePath.glob(FilePath.java:1932) at hudson.FilePath.access$3200(FilePath.java:211) at hudson.FilePath$ListGlob.invoke(FilePath.java:1906) at hudson.FilePath$ListGlob.invoke(FilePath.java:1894) at hudson.FilePath.act(FilePath.java:1075) at hudson.FilePath.act(FilePath.java:1058) at hudson.FilePath.list(FilePath.java:1892) at hudson.FilePath.list(FilePath.java:1876) at org.jenkinsci.plugins.pipeline.utility.steps.fs.FindFilesStepExecution.run(FindFilesStepExecution.java:63) at org.jenkinsci.plugins.pipeline.utility.steps.fs.FindFilesStepExecution.run(FindFilesStepExecution.java:44) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) 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){code}
Add Comment
[JIRA] (JENKINS-61995) P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long
Title: Message Title Karl Wirth commented on JENKINS-61995 Re: P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long Hi ling fu - Sorry I'm going to need more the information I requested above. Note that if you are an exsiting Perforce customer you may already have a NDA in place with us. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205886.1587487073000.18830.1588072920160%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning
Title: Message Title James Nord commented on JENKINS-59016 Re: GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning this causes lots of confusion when the credential works for an organisation folder (scanning all of github) and then the scan of the actual repo does not and falls back to anonymous. eg. [Thu Mar 19 11:12:10 UTC 2020] Updating actions... Looking up details of myghorg... Organization URL: CloudBees [Thu Mar 19 11:12:10 UTC 2020] Consulting GitHub Organization 11:12:10 Connecting to https://api.github.com using my-credential/** (PAT token for GitHub) 11:12:10 Looking up repositories of organization myghorg Ignoring wibble Ignoring bar Ignoring foo ... ignoring silly-name Proposing some-repo 11:13:21 GitHub API Usage: Current quota has 59 remaining (5 under budget). Next quota of 60 in 1 hr 0 min 11:13:22 Connecting to https://api.github.com with no credentials, anonymous access ERROR: [Thu Mar 19 11:13:22 UTC 2020] Could not fetch sources from navigator org.jenkinsci.plugins.github_branch_source.GitHubSCMNavigator@7cf2c1ef I beleive the scanning is done by the same plugin - which is why this is just confusing. > Credential domains usually only control user interface visibility of the credential, not job internal visibility of the credential that should never be the case, where it is it is a security issue in the plugins that do that - please file them if you know of this. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title Dmitrii Lapin commented on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time Same problem on SVN. Is there any provider which can send email to "developer, who created branch"? Sometimes branches can be copied from unstable trunk and developer shoud see results of all builds. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.157265.1410250514000.18860.1588077120357%40Atlassian.JIRA.
[JIRA] (JENKINS-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title Dmitrii Lapin commented on JENKINS-51218 Re: EMail-Ext does not send email, because or empty recipients Same older ticket: https://issues.jenkins-ci.org/browse/JENKINS-24638 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190538.1525867922000.18876.1588078200275%40Atlassian.JIRA.
[JIRA] (JENKINS-61670) Attribute like e.g. class gets lost from HTML code in description fields
Title: Message Title Alexander Komarov commented on JENKINS-61670 Re: Attribute like e.g. class gets lost from HTML code in description fields Likewise affected. Now, to style my descriptions I need to use the Simple Theme plugin, but since I can't add class to a div anymore, I need to use selectors like div#description>div>div:nth-child(2) to style them. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205403.1585077195000.18887.1588079100165%40Atlassian.JIRA.
[JIRA] (JENKINS-61992) Adding Veracode Scan to Veracode Jenkins Open source project
Title: Message Title Shihaaz Buhary started work on JENKINS-61992 Change By: Shihaaz Buhary Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205883.1587480871000.18893.158808137%40Atlassian.JIRA.
[JIRA] (JENKINS-62040) pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan
Title: Message Title Marky Jackson commented on JENKINS-62040 Re: pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan My apologies for the delayed reply. I tried reproducing this and could not. In looking at your Jenkinsfile, I see that you are using a library, that could be suspect. Can you provide the logs from Managed Jenkins>System Logs Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205931.1587715343000.18896.1588081020216%40Atlassian.JIRA.
[JIRA] (JENKINS-62061) Kubernetes plugins show Warning message WatchConnectionManager$1#onFailure
Title: Message Title Mayur Kumar updated an issue Jenkins / JENKINS-62061 Kubernetes plugins show Warning message WatchConnectionManager$1#onFailure Change By: Mayur Kumar Environment: Jenkins v2.222.1kubernetes v1.25.3kubernetes-client-api v4.9.1-1kubernetes-credentials v0.6.2Kubernetes cluster : v1.16.3 and v1.17.4 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205960.1587980742000.18897.1588081320138%40Atlassian.JIRA.
[JIRA] (JENKINS-55088) Jenkins Home config.xml reset upon restart
Title: Message Title Ian M commented on JENKINS-55088 Re: Jenkins Home config.xml reset upon restart I also have this problem with the config file getting overwritten. I'm using an AWS EC2 instance with a separate EBS volume for JENKINS_HOME that is mounted at startup. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196141.1544218094000.18907.1588081440650%40Atlassian.JIRA.
[JIRA] (JENKINS-62043) EC2 nodes broken
Title: Message Title Jason Antman commented on JENKINS-62043 Re: EC2 nodes broken This issue is affecting us as well. Jenkins starts, but builds queue indefinitely as it is not able to assign builds to a node: Apr 28 13:40:20 ree-bento docker-jenkins-master[9759]: 2020-04-28 13:40:20.408+ [id=998]WARNINGh.ExpressionFactory2$JexlExpression#evaluate: Caught exception evaluating: !c.acceptingTasks in /. Reason: java.lang.reflect.InvocationTargetException Apr 28 13:40:20 ree-bento docker-jenkins-master[9759]: java.lang.NullPointerException Apr 28 13:40:20 ree-bento docker-jenkins-master[9759]: at hudson.plugins.ec2.EC2AbstractSlave.isAcceptingTasks(EC2AbstractSlave.java:471) This is happening for builds of any type (EC2 nodes, builds with a label of "master", or builds for Docker nodes). It essentially stops Jenkins from running any builds at all. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205934.1587719449000.18900.1588081440541%40Atlassian.JIRA.
[JIRA] (JENKINS-61670) Attribute like e.g. class gets lost from HTML code in description fields
Title: Message Title Alexander Komarov edited a comment on JENKINS-61670 Re: Attribute like e.g. class gets lost from HTML code in description fields Likewise affected. Now, to style my job descriptions I need to use the Simple Theme plugin, but since I can't add *class* to a *div* anymore, I need to use selectors like *div#description>div>div:nth-child(2)*to style them. Or, I suppose, I can switch to using *style=""* since all my job descriptions are generated with Job DSL anyway. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205403.1585077195000.18920.1588081680113%40Atlassian.JIRA.
[JIRA] (JENKINS-62043) EC2 nodes broken
Title: Message Title Mark Waite commented on JENKINS-62043 Re: EC2 nodes broken Same issue affected ci.jenkins.io on the upgrade from 1.49.1 to 1.50. Special thanks to Gunter Grodotzki for immediately pointing me to this issue. Much appreciated! We rolled back to 1.49.1 on ci.jenkins.io so that we could return it to production as quickly as possible. We'll plan to remove all EC2 agents at some future time and then upgrade to 1.50 or a newer release. Null pointer exception stack trace was: Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: java.lang.NullPointerException Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.plugins.ec2.EC2AbstractSlave.isAcceptingTasks(EC2AbstractSlave.java:471) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.model.Node.canTake(Node.java:421) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.model.Queue$JobOffer.getCauseOfBlockage(Queue.java:277) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.model.Queue.maintain(Queue.java:1634) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.model.Queue$MaintainTask.doRun(Queue.java:2905) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:91) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.lang.Thread.run(Thread.java:834) Add Comment
[JIRA] (JENKINS-62043) EC2 nodes broken
Title: Message Title
Mark Waite edited a comment on JENKINS-62043
Re: EC2 nodes broken
Same issue affected ci.jenkins.io on the upgrade from 1.49.1 to 1.50. Special thanks to [~lifeofguenter] for immediately pointing me to this issue. Much appreciated! We rolled back to 1.49.1 on ci.jenkins.io so that we could return it to production as quickly as possible. We'll plan to remove all EC2 agents at some future time and then upgrade to 1.50 or a newer release.Null pointer exception stack trace was:{noformat}Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: java.lang.NullPointerExceptionApr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.plugins.ec2.EC2AbstractSlave.isAcceptingTasks(EC2AbstractSlave.java:471)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.model.Node.canTake(Node.java:421)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.model.Queue$JobOffer.getCauseOfBlockage(Queue.java:277)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.model.Queue.maintain(Queue.java:1634)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.model.Queue$MaintainTask.doRun(Queue.java:2905)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:91)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.lang.Thread.run(Thread.java:834){noformat}
Add Comment
[JIRA] (JENKINS-60726) Print two lines to each line if use Timestamper and Color Ansi Console Output
Title: Message Title Cesar Jorge Martínez commented on JENKINS-60726 Re: Print two lines to each line if use Timestamper and Color Ansi Console Output Yes, I now use all latest plugins with LTS jenkins version 2.222.3. Revising a bit, I use http://afonsof.com/jenkins-material-theme/. Maybe interfering this? Add resource to manage exclusion Add timestamps to the Console Output (Checked) Ant/Ivy-Artifactory Integration Color ANSI Console Output (Checked using xterm) ANSI color map Example output: 15:49:44 Started by user user 15:49:44 Running as SYSTEM 15:49:44 [EnvInject] - Loading node environment variables. 15:49:44 Building in workspace /var/lib/jenkins/jobs/job1/workspace 15:49:44 [WS-CLEANUP] Deleting project workspace... 15:49:44 ...
[JIRA] (JENKINS-62079) No way to email just a PR's owner
Title: Message Title Brian J Murrell created an issue Jenkins / JENKINS-62079 No way to email just a PR's owner Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 2020-04-28 14:42 Priority: Major Reporter: Brian J Murrell I can't seem to figure out any recipientProviders that contact just a (GitHub) PR's owner/author, in all cases. In simple cases, where somebody creates a PR and pushes a few patches, developers seems like the right target. But as soon as the PR owner merges with master, that becomes every patch owner in the merge also, correct? Is there an option I am missing here to achieve what I am looking for? Add Comment
[JIRA] (JENKINS-62080) PR owner information in Pipeline?
Title: Message Title Brian J Murrell created an issue Jenkins / JENKINS-62080 PR owner information in Pipeline? Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2020-04-28 14:50 Priority: Minor Reporter: Brian J Murrell Is GitHub PR information available in an object/variable/etc. in a Pipeline job? I'd like to be able to send an e-mail to a PR's owner/author for example. But just the PR owner/author, not any of the authors of any other patches that may be merged into the PR, so I don't think any of email-ext's current recipientProviders can do this. So instead I'd like to get the PR owner from this plugin and use it as the recipient in an email-ext call. Add Comment
[JIRA] (JENKINS-62074) Send build failure email to approver of pull request
Title: Message Title Alex Earl commented on JENKINS-62074 Re: Send build failure email to approver of pull request I don't believe I have access to anyone but the authors of commits via the API's available to me. So, I don't know how I would get that information. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205977.1588044661000.18964.1588085880205%40Atlassian.JIRA.
[JIRA] (JENKINS-62081) Git tags are not sorted in natural order in multibranch pipeline view
Title: Message Title manuel boillod created an issue Jenkins / JENKINS-62081 Git tags are not sorted in natural order in multibranch pipeline view Issue Type: Improvement Assignee: Mark Waite Attachments: tag sort.png Components: git-plugin, pipeline-multibranch-defaults-plugin Created: 2020-04-28 15:22 Environment: Jenkins version: Jenkins ver. 2.204.1 (I do not have access to plugin versions) Priority: Minor Reporter: manuel boillod Hi, I'm using multibranch pipeline project and have enabled git behaviour "Discover tags". In the project view, the tags are not sorted in natural order in the tags tab (see attachment), so it's difficult to find the latest tag. Best regards Add Comment
[JIRA] (JENKINS-62081) Git tags are not sorted in natural order in multibranch pipeline view
Title: Message Title manuel boillod commented on JENKINS-62081 Re: Git tags are not sorted in natural order in multibranch pipeline view Note the tag name being prefixed by "v" is the default behavior of "npm version" Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205987.1588087337000.18968.1588087440120%40Atlassian.JIRA.
[JIRA] (JENKINS-62043) EC2 plugin stops builds on ALL nodes
Title: Message Title Jason Antman updated an issue Jenkins / JENKINS-62043 EC2 plugin stops builds on ALL nodes Change By: Jason Antman Summary: EC2 plugin stops builds on ALL nodes broken Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205934.1587719449000.18971.1588087560381%40Atlassian.JIRA.
[JIRA] (JENKINS-61103) LinkageError on agent following RemotingSystemException(InterruptedException)
Title: Message Title Thomas de Grenier de Latour updated an issue Jenkins / JENKINS-61103 LinkageError on agent following RemotingSystemException(InterruptedException) Change By: Thomas de Grenier de Latour URL: https://github.com/jenkinsci/remoting/pull/ 372 379 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204615.1581800768000.18979.1588089180223%40Atlassian.JIRA.
[JIRA] (JENKINS-62082) Multibranch pipeline: checkout to subdirectory or exclude some paths from cleanup
Title: Message Title Piotr Krukowiecki created an issue Jenkins / JENKINS-62082 Multibranch pipeline: checkout to subdirectory or exclude some paths from cleanup Issue Type: New Feature Assignee: Unassigned Components: pipeline Created: 2020-04-28 15:54 Labels: multibranch Priority: Minor Reporter: Piotr Krukowiecki My use case: I want to have clean checkout (no artefacts from previous build, no modified files etc) I want to keep some additional files/folders (not in repository) The additional files are files which are downloaded during build (let's say data files). Once they are downloaded, there's no need to re-download them again. The problem: multi-branch pipeline clones and checkouts directly in workspace there is no way to exclude some files/folders in "Clean before/after checkout" additional behaviour in multi-branch pipeline If multi-branch could clone/checkout into a subfolder, I could keep the extra files next to the repository, and use "Clean..." on the repository - it would not affect my extra files. If mult-branch could exclude some files/folders in "Clean...", I could download the extrac files to some folder inside my repo, use "Clean..." but exclude this folder. Is there another way?
[JIRA] (JENKINS-62082) Multibranch pipeline: checkout to subdirectory or exclude some paths from cleanup
Title: Message Title Piotr Krukowiecki updated an issue Jenkins / JENKINS-62082 Multibranch pipeline: checkout to subdirectory or exclude some paths from cleanup Change By: Piotr Krukowiecki My use case: * I want to have clean checkout (no artefacts from previous build, no modified files etc) * I want to keep some additional files/folders which are not in repositoryThe additional files are files which are downloaded during build (let's say data files). Once they are downloaded, there's no need to re-download them again.The problem: * multi-branch pipeline clones and checkouts directly in workspace * there is no way to exclude some files/folders in "Clean before/after checkout" additional behaviour in multi-branch pipelineIf multi-branch could clone/checkout into a subfolder, I could keep the extra files next to the repository, and use "Clean..." on the repository - it would not affect my extra files.If mult-branch could exclude some files/folders in "Clean...", I could download the extrac extra files to some folder inside my repo, use "Clean..." but exclude this folder.Is there another way? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62082) Multibranch pipeline: checkout to subdirectory or exclude some paths from cleanup
Title: Message Title Piotr Krukowiecki updated an issue Jenkins / JENKINS-62082 Multibranch pipeline: checkout to subdirectory or exclude some paths from cleanup Change By: Piotr Krukowiecki My use case: * I want to have clean checkout (no artefacts from previous build, no modified files etc) * I want to keep some additional files/folders ( which are not in repository ) The additional files are files which are downloaded during build (let's say data files). Once they are downloaded, there's no need to re-download them again.The problem: * multi-branch pipeline clones and checkouts directly in workspace * there is no way to exclude some files/folders in "Clean before/after checkout" additional behaviour in multi-branch pipelineIf multi-branch could clone/checkout into a subfolder, I could keep the extra files next to the repository, and use "Clean..." on the repository - it would not affect my extra files.If mult-branch could exclude some files/folders in "Clean...", I could download the extrac files to some folder inside my repo, use "Clean..." but exclude this folder.Is there another way? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62083) The plugin does not use the standard release process
Title: Message Title Pierre Beitz created an issue Jenkins / JENKINS-62083 The plugin does not use the standard release process Issue Type: Bug Assignee: Assaf hefetz Components: snyk-security-plugin Created: 2020-04-28 15:57 Environment: Any version of the plugin in version 2.x Priority: Major Reporter: Pierre Beitz It appears that the snyk-security plugin does not follow the standard release process (as explained in https://www.jenkins.io/doc/developer/publishing/releasing/. As a consequence, the pom.xml inside the artifact is not properly formed. Especially the version field is not properly populated. See for instance the latest release 2.10.4 pom: https://github.com/jenkinsci/snyk-security-scanner-plugin/blob/a42a97bc8d2f47738bc4695d6b5934e4d131ae8f/pom.xml#L12. This does not seem to impact the Open Source Update Center, but it impacts other Update Centers. Would you mind reviewing the release process? Add Comment
[JIRA] (JENKINS-62082) Multibranch pipeline: checkout to subdirectory or exclude some paths from cleanup
Title: Message Title Piotr Krukowiecki updated an issue Jenkins / JENKINS-62082 Multibranch pipeline: checkout to subdirectory or exclude some paths from cleanup Change By: Piotr Krukowiecki My use case: * I want to have clean checkout (no artefacts from previous build, no modified files etc) * I want to keep some additional files/folders which are not in repositoryThe additional files are files which are downloaded during build (let's say data files) . Once they are downloaded, there's no need to re-download them again. (To be more specific, I have a job which builds a vscode extension and runs tests. vscode tests automatically download vscode executable if it does not exists in specific subfolder. Becauses git cleanup is enabled it deletes the downloaded vscode and it's re-downloaded with each build). The problem: * multi-branch pipeline clones and checkouts directly in workspace * there is no way to exclude some files/folders in "Clean before/after checkout" additional behaviour in multi-branch pipelineIf multi-branch could clone/checkout into a subfolder, I could keep the extra files next to the repository, and use "Clean..." on the repository - it would not affect my extra files.If mult-branch could exclude some files/folders in "Clean...", I could download the extra files to some folder inside my repo, use "Clean..." but exclude this folder.Is there another way? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62043) EC2 plugin stops builds on ALL nodes
Title: Message Title Ryan Slobojan commented on JENKINS-62043 Re: EC2 plugin stops builds on ALL nodes There is a PR with a fix for this on Github which has been approved and is awaiting merging: https://github.com/jenkinsci/ec2-plugin/pull/452 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205934.1587719449000.18990.1588090860317%40Atlassian.JIRA.
[JIRA] (JENKINS-62043) EC2 plugin stops builds on ALL nodes
Title: Message Title Ryan Slobojan started work on JENKINS-62043 Change By: Ryan Slobojan Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205934.1587719449000.19000.1588091401492%40Atlassian.JIRA.
[JIRA] (JENKINS-62043) EC2 plugin stops builds on ALL nodes
Title: Message Title Ryan Slobojan updated JENKINS-62043 Jenkins / JENKINS-62043 EC2 plugin stops builds on ALL nodes Change By: Ryan Slobojan Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205934.1587719449000.19010.1588091403403%40Atlassian.JIRA.
[JIRA] (JENKINS-60762) pipeline used to wait to schedule task now stops immediately
Title: Message Title Roman Pickl updated JENKINS-60762 Jenkins / JENKINS-60762 pipeline used to wait to schedule task now stops immediately Change By: Roman Pickl Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204023.1579003891000.19019.1588091460278%40Atlassian.JIRA.
[JIRA] (JENKINS-60762) pipeline used to wait to schedule task now stops immediately
Title: Message Title Roman Pickl updated JENKINS-60762 we cannot reproduce this after some updates. Jenkins / JENKINS-60762 pipeline used to wait to schedule task now stops immediately Change By: Roman Pickl Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion o
[JIRA] (JENKINS-62062) EC2 Plugin Null Pointer Exception IsAcceptingTask
Title: Message Title Ryan Slobojan commented on JENKINS-62062 Re: EC2 Plugin Null Pointer Exception IsAcceptingTask See JENKINS-62043 - a PR is in progress on Github which fixes this issue, it is approved and awaiting merge: https://github.com/jenkinsci/ec2-plugin/pull/452 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205961.1587980992000.19025.1588091641836%40Atlassian.JIRA.
[JIRA] (JENKINS-62062) EC2 Plugin Null Pointer Exception IsAcceptingTask
Title: Message Title Ryan Slobojan started work on JENKINS-62062 Change By: Ryan Slobojan Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205961.1587980992000.19028.1588091642084%40Atlassian.JIRA.
[JIRA] (JENKINS-62062) EC2 Plugin Null Pointer Exception IsAcceptingTask
Title: Message Title Ryan Slobojan updated JENKINS-62062 Jenkins / JENKINS-62062 EC2 Plugin Null Pointer Exception IsAcceptingTask Change By: Ryan Slobojan Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205961.1587980992000.19034.1588091642460%40Atlassian.JIRA.
[JIRA] (JENKINS-62084) Adding Veracode Jenkins Open Source Plugin to newRelic
Title: Message Title Dennis Gu created an issue Jenkins / JENKINS-62084 Adding Veracode Jenkins Open Source Plugin to newRelic Issue Type: Story Assignee: Dennis Gu Components: veracode-scan-plugin Created: 2020-04-28 16:45 Priority: Minor Reporter: Dennis Gu We need to track the usage of our Veracode Jenkins Open Source plugin after it is released, it has used different package name and we need to create new entry in newRelic. This data will give us better idea the adoption of our new open source plugin, and we can make a better plan when to stop support old Veracode Jenkins plugin. Add Comment
[JIRA] (JENKINS-54868) Display Organization/Project and Repository name(s) on the job details page
Title: Message Title Didier Crest commented on JENKINS-54868 Re: Display Organization/Project and Repository name(s) on the job details page Nice Kezhi Xiong, your trying seems great. Instead the repository name which seems difficult to get. Why do not write the URL of git remote? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195866.1543263718000.19041.1588093020315%40Atlassian.JIRA.
[JIRA] (JENKINS-62085) Enable sequential matrix execution
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-62085 Enable sequential matrix execution Issue Type: Improvement Assignee: Liam Newman Components: pipeline-model-definition-plugin Created: 2020-04-28 17:00 Priority: Major Reporter: Liam Newman This SO question describes the desired behavior: https://stackoverflow.com/questions/60654533/jenkins-declarative-pipeline-sequential-execution-of-an-axis-of-a-matrix-build Add Comment This message was sent by Atlassian Jira (v7.13.
[JIRA] (JENKINS-62085) Add option for sequential execution of matrix in pipeline
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-62085 Add option for sequential execution of matrix in pipeline Change By: Liam Newman Summary: Enable Add option for sequential matrix execution of matrix in pipeline Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205991.1588093249000.19047.1588093320066%40Atlassian.JIRA.
[JIRA] (JENKINS-60726) Print two lines to each line if use Timestamper and Color Ansi Console Output
Title: Message Title Basil Crow commented on JENKINS-60726 Re: Print two lines to each line if use Timestamper and Color Ansi Console Output Hi Cesar Jorge Martínez, I set up a Jenkins master with Timestamper 1.11.3, AnsiColor 0.6.3, Simple Theme Plugin 0.6, and the Material Theme. Then I created a Freestyle job with "Add timestamps to the Console Output" and "Color ANSI Console Output" checked. When I ran the job I could not reproduce the issue. Can you please provide me with steps to reproduce the issue from scratch? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203975.1578651011000.19049.1588093440246%40Atlassian.JIRA.
[JIRA] (JENKINS-62081) Git tags are not sorted in natural order in multibranch pipeline view
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-62081 Git tags are not sorted in natural order in multibranch pipeline view Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205987.1588087337000.19052.1588095300174%40Atlassian.JIRA.
[JIRA] (JENKINS-62081) Git tags are not sorted in natural order in multibranch pipeline view
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-62081 Git tags are not sorted in natural order in multibranch pipeline view Change By: Mark Waite Hi,I'm using multibranch pipeline project and have enabled git behaviour "Discover tags".In the project view, the tags are not sorted in natural order in the tags tab (see attachment), so it's difficult to find the latest tag.Best regards !tag sort.png|thumbnail! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205987.1588087337000.19054.1588095360311%40Atlassian.JIRA.
[JIRA] (JENKINS-61347) Checkout problem on a branch
Title: Message Title Mark Waite closed an issue as Not A Defect Please don' t use the Jenkins issue tracker as a question and answer site. The Jenkins.io site provides links to mailing lists and chat channels that can answer your questions. In this specific case, if you're using Git as the SCM, then refer to https://plugins.jenkins.io/git/#checkout-to-specific-local-branch as one way of handling your request. Jenkins / JENKINS-61347 Checkout problem on a branch Change By: Mark Waite Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61881) Jenkins build failing due to failure of creation of docker container(ppwershell failure)
Title: Message Title Mark Waite closed an issue as Cannot Reproduce After almost two weeks without a reply to the request for more information, closing as "Cannot reproduce" Jenkins / JENKINS-61881 Jenkins build failing due to failure of creation of docker container(ppwershell failure) Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, sen
[JIRA] (JENKINS-62055) best
Title: Message Title Mark Waite closed an issue as Not A Defect The Jenkins Jira site is not a location for posting test bugs or links to unrelated domains. Jenkins / JENKINS-62055 best Change By: Mark Waite Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit htt
[JIRA] (JENKINS-59016) GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning
Title: Message Title Liam Newman commented on JENKINS-59016 Re: GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning James Nord > Credential domains usually only control user interface visibility of the credential, not job internal visibility of the credential that should never be the case, where it is it is a security issue in the plugins that do that - please file them if you know of this. Not according to the documentation: The use-case for credentials domains is to provide a way for the user to provide information about the services with which the credentials are expected to work. Credential domains are intended to help select correct credentials for each services. Credential domains are not intended to prevent credentials from being used against the wrong services. In some cases, the domain requirements of a credential cannot be determined, such as when using a credentials parameter or when using a plugin that has not fully implemented the recommendations of the consumer guide. In order to ensure that users can actually select the required credentials in these cases, the Credentials API needs to return credentials from all domains, which is why we use Excluding credentials from domains that do not match. Because of the above: Credential domains are not intended to restrict access to credentials. https://github.com/jenkinsci/credentials-plugin/blob/master/docs/user.adoc Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62078) Jenkins sometimes is not able to index branches
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-62078 Jenkins sometimes is not able to index branches Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205981.1588068429000.19065.1588098360145%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning
Title: Message Title James Nord commented on JENKINS-59016 Re: GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning > In some cases, the domain requirements of a credential cannot be determined, such as when using a credentials parameter or when using a plugin that has not fully implemented the recommendations of the consumer guide. Yes - and not implementing the consumer guide correctly is a bug, credentials being security sensitive makes it a security bug. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201369.1566328715000.19067.1588098480197%40Atlassian.JIRA.
[JIRA] (JENKINS-62078) Jenkins sometimes is not able to index branches
Title: Message Title Mark Waite commented on JENKINS-62078 Re: Jenkins sometimes is not able to index branches That Nonnull message is an expected message that is a result of the transition from the deprecated javax annotations to the spotbugs annotations. Should be unrelated to the issue you are describing. I don't know how to duplicate the problem you're describing. You might check authentication logs on the Bitbucket server or you might enable finer logging for the git plugin and git client plugin and Bitbucket plugin. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205981.1588068429000.19070.1588098840117%40Atlassian.JIRA.
[JIRA] (JENKINS-61431) Atomatically Scan Bitbucket Server Project for Repositories
Title: Message Title Padraig Lennon commented on JENKINS-61431 Re: Atomatically Scan Bitbucket Server Project for Repositories +1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205109.1583933438000.19072.1588099800258%40Atlassian.JIRA.
[JIRA] (JENKINS-33126) unstash fails to overwrite read-only files
Title: Message Title Alan Czajkowski commented on JENKINS-33126 Re: unstash fails to overwrite read-only files running into the same problem, being able to unstash the .git/ directory is very important for certain tools and needs to be allowed when moving the workspace around Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168493.1456315471000.19080.1588104360634%40Atlassian.JIRA.
[JIRA] (JENKINS-33126) unstash fails to overwrite read-only files
Title: Message Title
Alan Czajkowski edited a comment on JENKINS-33126
Re: unstash fails to overwrite read-only files
running into the same problem, being able to unstash the {{.git/}} directory is very important for certain tools and needs to be allowed when moving the workspace around {{Jenkinsfile}}:{code}... stash name: WORKSPACE_NAME, useDefaultExcludes: false... unstash name: WORKSPACE_NAME...{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168493.1456315471000.19103.1588104660558%40Atlassian.JIRA.
[JIRA] (JENKINS-33126) unstash fails to overwrite read-only files
Title: Message Title
Alan Czajkowski edited a comment on JENKINS-33126
Re: unstash fails to overwrite read-only files
running into the same problem, being able to unstash the {{.git/}} directory is very important for certain tools and needs to be allowed when moving the workspace around{{Jenkinsfile}}:{code}... stash name: WORKSPACE_NAME, useDefaultExcludes: false... unstash name: WORKSPACE_NAME...{code} references:- https://www.jenkins.io/doc/pipeline/steps/workflow-basic-steps/#stash-stash-some-files-to-be-used-later-in-the-build{quote}*useDefaultExcludes* (optional)If selected, use the default excludes from Ant - see [here|http://ant.apache.org/manual/dirtasks.html#defaultexcludes] for the list.Type: boolean{quote}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168493.1456315471000.19126.1588104960535%40Atlassian.JIRA.
[JIRA] (JENKINS-62034) Matrix stages reported skipped instead of actual status.
Title: Message Title Liam Newman commented on JENKINS-62034 Re: Matrix stages reported skipped instead of actual status. John Malmberg What does this look like in the non-Blue Ocean view? What doest the full log show for your sample Jenkinsfile show? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205925.1587662025000.19148.1588106220139%40Atlassian.JIRA.
[JIRA] (JENKINS-61951) build.bat' is not recognized as an internal or external command, operable program or batch file.
Title: Message Title Liam Newman commented on JENKINS-61951 Re: build.bat' is not recognized as an internal or external command, operable program or batch file. Narayanasamy Ramaiah Please include the log file from the pipeline in question. Also, it looks like the above is trying to run "d2unitybuild.bat" not "build.bat". Unclear what you're pointing to. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205832.158714518.19151.1588106400149%40Atlassian.JIRA.
[JIRA] (JENKINS-61707) githubTagDiscovery trait still not configurable via job-dsl
Title: Message Title Liam Newman commented on JENKINS-61707 Re: githubTagDiscovery trait still not configurable via job-dsl Groovy and Java are case-sensitive. The name of the symbol is "gitHubTagDiscovery" (capital H). https://github.com/jenkinsci/github-branch-source-plugin/blob/aa83a7713c28b4a0a144f84081501f4c93e4c236/src/main/java/org/jenkinsci/plugins/github_branch_source/TagDiscoveryTrait.java#L77 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205532.1585299414000.19154.1588106760419%40Atlassian.JIRA.
[JIRA] (JENKINS-61707) githubTagDiscovery trait still not configurable via job-dsl
Title: Message Title Liam Newman closed an issue as Not A Defect Jenkins / JENKINS-61707 githubTagDiscovery trait still not configurable via job-dsl Change By: Liam Newman Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205532.1585299414000.19157.1588106820370%40Atlassian.JIRA.
[JIRA] (JENKINS-61828) Failing with java.lang.IndexOutOfBoundsException while using environment block
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-61828
Failing with java.lang.IndexOutOfBoundsException while using environment block
Change By:
Liam Newman
I am using DSL for the Jenkins pipeline as code. This particular piece of code runs fine .{code:groovy}pipeline {agent{label 'master'}stages {stage('test script') {steps {script {env.Environment_Name = input(id: 'Env', message: 'Select Environment',parameters: [[$class: 'ChoiceParameterDefinition', choices: 'test-1\ntest-2\ntest-3', description: '', name: '']]) println " $Environment_Name"def allCreds = sh(returnStdout: true,script: "cat $JENKINS_HOME/jobs/$Environment_Name/config.xml | grep \"\" | cut -d'>' -f2 | cut -d'<' -f1").trim().split('\n').join('\n')println "- $allCreds"env.Cred_Name = input(id: 'Cred', message: 'Select Credential to Update',parameters: [[$class: 'ChoiceParameterDefinition', choices: allCreds, description: '', name: '']])println "- $Cred_Name"env.User_Name = input(id: 'User_Name', message: 'Enter Username',parameters: [[$class: 'TextParameterDefinition', description: 'Username', name: 'User_Name']])}}}stage('print the variables') {steps {echo "${Environment_Name}"echo "${User_Name}"}}}} {code} But when I add environment block to this code it fails with the following *exception java.lang.IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)* pipeline { agent { label 'master' } *environment{* *JENKINS_CREDS = credentials('JENKINS_CREDS')* *}* stages { stage('test script') { steps { script { env.Environment_Name = input( id: 'Env', message: 'Select Environment', parameters: [ [$class: 'ChoiceParameterDefinition', choices: 'test-1\ntest-2\ntest-3', description: '', name: ''] ]) println " $Environment_Name" def allCreds = sh(returnStdout: true, script: "cat $JENKINS_HOME/jobs/$Environment_Name/config.xml | grep \"\" | cut -d'>' -f2 | cut -d'<' -f1").trim().split('\n').join('\n') println "- $allCreds" env.Cred_Name = input( id: 'Cred', message: 'Select Credential to Update', parameters: [ [$class: 'ChoiceParameterDefinition', choices: allCreds, description: '', name: ''] ]) println "- $Cred_Name" env.User_Name = input(id: 'User_Name', message: 'Enter Username',parameters: [ [$class: 'TextParameterDefinition', description: 'Username', name: 'User_Name'] ]) } } } stage('print the variables'){ steps{ echo "${Environment_Name}" echo "${User_Name}" *echo "${JENKINS_CREDS_USR}"* } } } }I have tested this code against the Jenkins version [ *2.222.1* and it runs without an error but fails when running in the version 2.204.5.|https://jenkins.io/]
[JIRA] (JENKINS-61828) Failing with java.lang.IndexOutOfBoundsException while using environment block
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-61828
Failing with java.lang.IndexOutOfBoundsException while using environment block
Change By:
Liam Newman
I am using DSL for the Jenkins pipeline as code. This particular piece of code runs fine . {code:groovy} pipeline { agent { label 'master' } stages { stage('test script') { steps { script { env.Environment_Name = input( id: 'Env', message: 'Select Environment', parameters: [ [$class: 'ChoiceParameterDefinition', choices: 'test-1\ntest-2\ntest-3', description: '', name: ''] ]) println " $Environment_Name"def allCreds = sh(returnStdout: true, script: "cat $JENKINS_HOME/jobs/$Environment_Name/config.xml | grep \"\" | cut -d'>' -f2 | cut -d'<' -f1").trim().split('\n').join('\n') println "- $allCreds"env.Cred_Name = input( id: 'Cred', message: 'Select Credential to Update', parameters: [ [$class: 'ChoiceParameterDefinition', choices: allCreds, description: '', name: ''] ]) println "- $Cred_Name"env.User_Name = input(id: 'User_Name', message: 'Enter Username',parameters: [ [$class: 'TextParameterDefinition', description: 'Username', name: 'User_Name'] ]) } } } stage('print the variables'){ steps{ echo "${Environment_Name}" echo "${User_Name}" } } } } {code} But when I add environment block to this code it fails with the following *exception java.lang.IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)* pipeline { agent { label 'master' } *environment{* *JENKINS_CREDS = credentials('JENKINS_CREDS')* *}* stages { stage('test script') { steps { script { env.Environment_Name = input( id: 'Env', message: 'Select Environment', parameters: [ [$class: 'ChoiceParameterDefinition', choices: 'test-1\ntest-2\ntest-3', description: '', name: ''] ]) println " $Environment_Name" def allCreds = sh(returnStdout: true, script: "cat $JENKINS_HOME/jobs/$Environment_Name/config.xml | grep \"\" | cut -d'>' -f2 | cut -d'<' -f1").trim().split('\n').join('\n') println "- $allCreds" env.Cred_Name = input( id: 'Cred', message: 'Select Credential to Update', parameters: [ [$class: 'ChoiceParameterDefinition', choices: allCreds, description: '', name: ''] ]) println "- $Cred_Name" env.User_Name = input(id: 'User_Name', message: 'Enter Username',parameters: [ [$class: 'TextParameterDefinition', description: 'Username', name: 'User_Name'] ]) } } } stage('print the variables'){ steps{ echo "${Environment_Name}" echo "${User_Name}" *echo "${JENKINS_CREDS_USR}"* } } } }I have tested this code against the Jenkins version [ *2.222.1* and it runs without an error but fails when running in the version 2.204.5.|https://jenkins.io/]
[JIRA] (JENKINS-61828) Failing with java.lang.IndexOutOfBoundsException while using environment block
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-61828
Failing with java.lang.IndexOutOfBoundsException while using environment block
Change By:
Liam Newman
I am using DSL for the Jenkins pipeline as code. This particular piece of code runs fine .{code:groovy}pipeline {agent {label 'master'}stages {stage('test script') {steps {script {env.Environment_Name = input(id: 'Env', message: 'Select Environment', parameters: [[$class: 'ChoiceParameterDefinition', choices: 'test-1\ntest-2\ntest-3', description: '', name: '']]) println " $Environment_Name"def allCreds = sh(returnStdout: true, script: "cat $JENKINS_HOME/jobs/$Environment_Name/config.xml | grep \"\" | cut -d'>' -f2 | cut -d'<' -f1").trim().split('\n').join('\n')println "- $allCreds"env.Cred_Name = input(id: 'Cred', message: 'Select Credential to Update', parameters: [[$class: 'ChoiceParameterDefinition', choices: allCreds, description: '', name: '']])println "- $Cred_Name"env.User_Name = input(id: 'User_Name', message: 'Enter Username', parameters: [[$class: 'TextParameterDefinition', description: 'Username', name: 'User_Name']])}}}stage('print the variables') {steps {echo "${Environment_Name}"echo "${User_Name}"}}}} {code} But when I add environment block to this code it fails with the following *exception java.lang.IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)* {code:groovy} pipeline { agent { label 'master' } * environment{ * * JENKINS_CREDS = credentials('JENKINS_CREDS') * * } *stages { stage('test script') { steps { script { env.Environment_Name = input( id: 'Env', message: 'Select Environment',parameters: [ [$class: 'ChoiceParameterDefinition', choices: 'test-1\ntest-2\ntest-3', description: '', name: ''] ]) println " $Environment_Name"def allCreds = sh(returnStdout: true,script: "cat $JENKINS_HOME/jobs/$Environment_Name/config.xml | grep \"\" | cut -d'>' -f2 | cut -d'<' -f1").trim().split('\n').join('\n') println "- $allCreds"env.Cred_Name = input( id: 'Cred', message: 'Select Credential to Update',parameters: [ [$class: 'ChoiceParameterDefinition', choices: allCreds, description: '', name: ''] ]) println "- $Cred_Name"env.User_Name = input(id: 'User_Name', message: 'Enter Username', parameters: [ [$class: 'TextParameterDefinition', description: 'Username', name: 'User_Name'] ]) } } } stage('print the variables'){ steps{ echo "${Environment_Name}" echo "${User_Name}" * echo "${JENKINS_CREDS_USR}" * } } } } {code} I have tested this code against the Jenkins version [ *2.222.1* and it runs without an error but fails
[JIRA] (JENKINS-61828) Failing with java.lang.IndexOutOfBoundsException while using environment block
Title: Message Title Liam Newman commented on JENKINS-61828 Re: Failing with java.lang.IndexOutOfBoundsException while using environment block Updated the formatting of your examples. What is the full stacktrace you're seeing? Is the id of your credential JENKINS_CREDS ? Have you tried changing the env variable name? Have your tried using a different credential id? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205681.1586251731000.19165.1588107480208%40Atlassian.JIRA.
[JIRA] (JENKINS-61828) Failing with java.lang.IndexOutOfBoundsException while using environment block
Title: Message Title Liam Newman edited a comment on JENKINS-61828 Re: Failing with java.lang.IndexOutOfBoundsException while using environment block Updated the formatting of your examples. What is the full stacktrace you're seeing? Is the id of your credential JENKINS_CREDS ?Have you tried changing the env variable name? Have your tried using a different credential id? What is the log output (in text form please not screenshot)? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205681.1586251731000.19167.1588107540107%40Atlassian.JIRA.
[JIRA] (JENKINS-61828) Failing with java.lang.IndexOutOfBoundsException while using environment block
Title: Message Title Liam Newman edited a comment on JENKINS-61828 Re: Failing with java.lang.IndexOutOfBoundsException while using environment block Updated the formatting of your examples. What is the full stacktrace you're seeing (in text form, rather than screenshot) ? Is the id of your credential JENKINS_CREDS ? Have you tried changing the env variable name?Have your tried using a different credential id? What is the log output (in text form please not screenshot)? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205681.1586251731000.19169.1588107600134%40Atlassian.JIRA.
[JIRA] (JENKINS-57441) Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830
Title: Message Title Mez Pahlan commented on JENKINS-57441 Re: Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830 Hi Oleg Nenashev can I double check something please. I'm running the demos from https://github.com/jenkinsci/jenkinsfile-runner/tree/master/demo and after building the vanilla docker image I get the errors in this issue. The sample pipeline runs fine but there's a lot of log noise at the start. The change in https://github.com/jenkinsci/jenkinsfile-runner/pull/177 seems to have reverted the workaround you've mentioned in https://github.com/jenkinsci/jenkinsfile-runner/pull/125. Was that to be expected? Great project btw, I'm really looking forward to using it in our production. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199254.1557791602000.19171.1588108140192%40Atlassian.JIRA.
[JIRA] (JENKINS-62034) Matrix stages reported skipped instead of actual status.
Title: Message Title John Malmberg updated an issue Jenkins / JENKINS-62034 Matrix stages reported skipped instead of actual status. Change By: John Malmberg Attachment: Jenkins_matrix_skip_bug2.PNG Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205925.1587662025000.19174.1588109040363%40Atlassian.JIRA.
[JIRA] (JENKINS-62086) Getting java.lang.ClassNotFoundException exception javax.xml.bind.JAXBException checkmarx plaugin with agent using open jdk 11
Title: Message Title Bharat Bhatia created an issue Jenkins / JENKINS-62086 Getting java.lang.ClassNotFoundException exception javax.xml.bind.JAXBException checkmarx plaugin with agent using open jdk 11 Issue Type: Bug Assignee: Sergey Kadaner Components: checkmarx-plugin Created: 2020-04-28 21:34 Environment: Checkmrx plugin version 8.90.4 Jenkins 2.234 Priority: Minor Reporter: Bharat Bhatia I am getting exception Getting java.lang.ClassNotFoundException exception javax.xml.bind.JAXBException checkmarx plaugin with agent using open jdk 11 Stack trace java.lang.ClassNotFoundException: Bootstrap pseudo-classloader disabled: javax.xml.bind.JAXBException via null at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch4(RemoteClassLoader.java:858) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch3(RemoteClassLoader.java:893) at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:931) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at org.jenkinsci.remoting.CallableDecorator.call(CallableDecorator.java:18) at hudson.remoting.CallableDecoratorList$1.call(CallableDecoratorList.java:21) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.co
[JIRA] (JENKINS-62034) Matrix stages reported skipped instead of actual status.
Title: Message Title John Malmberg updated an issue Jenkins / JENKINS-62034 Matrix stages reported skipped instead of actual status. Change By: John Malmberg Attachment: Jenkins-62304_1_consoleText.txt Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205925.1587662025000.19178.1588109760197%40Atlassian.JIRA.
[JIRA] (JENKINS-62034) Matrix stages reported skipped instead of actual status.
Title: Message Title John Malmberg commented on JENKINS-62034 Re: Matrix stages reported skipped instead of actual status. Jenkins_matrix_skip_bug2.PNG shows the matrix output where the no status is rendered for Matrix entry of COLOR='red' and 'SHAPE'='none' which failed in the build. Jenkins-62304_1_consoleText.txt shows that the job had an execution error for that cell. And stages that were skipped are showing up as taking 2 seconds in the traditional UI. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205925.1587662025000.19180.1588110900156%40Atlassian.JIRA.
[JIRA] (JENKINS-62034) Matrix stages reported skipped instead of actual status.
Title: Message Title John Malmberg updated an issue Jenkins / JENKINS-62034 Matrix stages reported skipped instead of actual status. Change By: John Malmberg Attachment: Jenkins_matrix_skip_bug3.PNG Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205925.1587662025000.19182.1588110960226%40Atlassian.JIRA.
[JIRA] (JENKINS-62034) Matrix stages reported skipped instead of actual status.
Title: Message Title John Malmberg edited a comment on JENKINS-62034 Re: Matrix stages reported skipped instead of actual status. Jenkins_matrix_skip_bug2.PNG shows the matrix output where the no status is rendered for Matrix entry of COLOR='red' and 'SHAPE'='none' which failed in the build.Jenkins-62304_1_consoleText.txt shows that the job had an execution error for that cell.And stages that were skipped are showing up as taking 2 seconds in the traditional UI in Jenkins_matrix_skip_bug3 . PNG Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205925.1587662025000.19184.1588110960257%40Atlassian.JIRA.
[JIRA] (JENKINS-61326) Replace 24-column Bootstrap 3 grid with 12-column Bootstrap 4 version
Title: Message Title Ulli Hafner commented on JENKINS-61326 Re: Replace 24-column Bootstrap 3 grid with 12-column Bootstrap 4 version I created https://github.com/jenkinsci/jenkins/pull/4693 as a workaround for plugins until a fix is available. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204915.1583330952000.19188.1588111320445%40Atlassian.JIRA.
[JIRA] (JENKINS-62079) No way to email just a PR's owner
Title: Message Title Alex Earl commented on JENKINS-62079 Re: No way to email just a PR's owner I don't think I have access to that information. The GitHub plugin (if that is being used) might have that info and could implement their own RecipientProvider which could then be used in email-ext. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205984.1588084934000.19190.1588112340141%40Atlassian.JIRA.
[JIRA] (JENKINS-62087) Detect Gradle module names
Title: Message Title Joe Hansche created an issue Jenkins / JENKINS-62087 Detect Gradle module names Issue Type: New Feature Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-04-28 23:28 Priority: Major Reporter: Joe Hansche Currently ModuleDetector[1] is capable of detecting module names from pom.xml files, build.xml files, and MANIFEST.MF files. But I would also like to look for Gradle module names. Typically in a multi-module Gradle project, the module name would match the subdirectory that the module is in, but it can also be overridden by settings.gradle[2]. The easy way would be to find the build.gradle file the same way it looks for the other files, and take that file's parent directory name: ./ |-- settings.gradle |-- build.gradle |-- moduleA/ |-- build.gradle |-- build/ (contains for example **/checkstyle-result.xml) |-- moduleB/ |-- build.gradle |-- build/ So as an example, when we find ./moduleA/build/reports/checkstyle/checkstyle-result.xml, that belongs to the ":moduleA" gradle module. [1] https://github.com/jenkinsci/analysis-model/blob/master/src/main/java/edu/hm/hafner/analysis/ModuleDetector.java [2] https://docs.gradle.org/current/userguide/organizing_gradle_projects.html
[JIRA] (JENKINS-62043) EC2 plugin stops builds on ALL nodes
Title: Message Title Raihaan Shouhell commented on JENKINS-62043 Re: EC2 plugin stops builds on ALL nodes We just merged the PR fix and made a bugfix release 1.50.1. Thanks to all contributors and users for their patience on this bug. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205934.1587719449000.19197.1588133280514%40Atlassian.JIRA.
[JIRA] (JENKINS-62078) Jenkins sometimes is not able to index branches
Title: Message Title Danny Heinrich updated an issue Jenkins / JENKINS-62078 Jenkins sometimes is not able to index branches Change By: Danny Heinrich Attachment: Screenshot from 2020-04-29 06-35-44.png Attachment: Screenshot from 2020-04-29 06-35-21.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205981.1588068429000.19207.1588135020275%40Atlassian.JIRA.
[JIRA] (JENKINS-62078) Jenkins sometimes is not able to index branches
Title: Message Title Danny Heinrich updated an issue Jenkins / JENKINS-62078 Jenkins sometimes is not able to index branches Change By: Danny Heinrich Attachment: Screenshot from 2020-04-29 06-35-21.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205981.1588068429000.19210.1588135080326%40Atlassian.JIRA.
[JIRA] (JENKINS-62078) Jenkins sometimes is not able to index branches
Title: Message Title Danny Heinrich updated an issue Jenkins / JENKINS-62078 Jenkins sometimes is not able to index branches Change By: Danny Heinrich Attachment: Screenshot from 2020-04-29 06-35-21.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205981.1588068429000.19212.1588135080366%40Atlassian.JIRA.
[JIRA] (JENKINS-62078) Jenkins sometimes is not able to index branches
Title: Message Title Danny Heinrich updated an issue Jenkins / JENKINS-62078 Jenkins sometimes is not able to index branches Change By: Danny Heinrich Attachment: Screenshot from 2020-04-29 06-35-44.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205981.1588068429000.19209.1588135080302%40Atlassian.JIRA.
[JIRA] (JENKINS-62078) Jenkins sometimes is not able to index branches
Title: Message Title Danny Heinrich updated an issue Jenkins / JENKINS-62078 Jenkins sometimes is not able to index branches Change By: Danny Heinrich Attachment: Screenshot from 2020-04-29 06-35-21.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205981.1588068429000.19215.1588135140217%40Atlassian.JIRA.
[JIRA] (JENKINS-62078) Jenkins sometimes is not able to index branches
Title: Message Title Danny Heinrich commented on JENKINS-62078 Re: Jenkins sometimes is not able to index branches Mark Waite Thats what I thought too, thtat this was unrelated. Bitbucket does not show any error. Both System have a fair usage of CPU + RAM. I already did but it remains empty. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205981.1588068429000.19217.1588135200118%40Atlassian.JIRA.
[JIRA] (JENKINS-62078) Jenkins sometimes is not able to index branches
Title: Message Title Danny Heinrich edited a comment on JENKINS-62078 Re: Jenkins sometimes is not able to index branches [~markewaite] Thats what I thought too, thtat this was unrelated.Bitbucket does not show any error.Both System have a fair usage of CPU + RAM. I already did but it remains empty. !Screenshot from 2020-04-29 06-35-21.png|thumbnail! !Screenshot from 2020-04-29 06-35-44.png|thumbnail! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205981.1588068429000.19222.1588135260316%40Atlassian.JIRA.
[JIRA] (JENKINS-62078) Jenkins sometimes is not able to index branches
Title: Message Title Danny Heinrich edited a comment on JENKINS-62078 Re: Jenkins sometimes is not able to index branches [~markewaite] Thats what I thought too, thtat this was unrelated.Bitbucket does not show any error.Both System have a fair usage of CPU + RAM. I already did but it remains empty. !Screenshot from 2020-04-29 06-35-21.png! !Screenshot from 2020-04-29 06-35-44.png! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205981.1588068429000.19219.1588135260244%40Atlassian.JIRA.
[JIRA] (JENKINS-62078) Jenkins sometimes is not able to index branches
Title: Message Title Danny Heinrich updated an issue Jenkins / JENKINS-62078 Jenkins sometimes is not able to index branches Change By: Danny Heinrich Attachment: Screenshot from 2020-04-29 06-35-44.png Attachment: Screenshot from 2020-04-29 06-35-21.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205981.1588068429000.19220.1588135260258%40Atlassian.JIRA.
[JIRA] (JENKINS-57441) Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830
Title: Message Title Oleg Nenashev commented on JENKINS-57441 Re: Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830 Strange. New version worked for me on smoke tests. Will try it more and revert the version again if needed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199254.1557791602000.19226.1588135800303%40Atlassian.JIRA.
[JIRA] (JENKINS-62041) PrioritySorter doesn't work as expected. High Prio jobs last in queue
Title: Message Title Tomasz Koźlak commented on JENKINS-62041 Re: PrioritySorter doesn't work as expected. High Prio jobs last in queue I solved the problem by downgrading Pipepilne plugin from 2.6 to 2.5. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205932.1587715678000.19227.1588141260108%40Atlassian.JIRA.
[JIRA] (JENKINS-61992) Adding Veracode Scan to Veracode Jenkins Open source project
Title: Message Title Shihaaz Buhary updated an issue Jenkins / JENKINS-61992 Adding Veracode Scan to Veracode Jenkins Open source project Change By: Shihaaz Buhary It is better to scan our Veracode Jenkins open source plugin in platform before we are releasing into Jenkins Marketplace.The best option is adding Veracode scan into GitHub Jenkins build pipeline, but not sure it is feasible or not.The other options is to adding script to do it by download binary from Jenkins Artifcatory, or scan it manually before releasing it. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205883.1587480871000.19228.1588141440159%40Atlassian.JIRA.
[JIRA] (JENKINS-61992) Adding Veracode Scan to Veracode Jenkins Open source project
Title: Message Title Shihaaz Buhary commented on JENKINS-61992 Re: Adding Veracode Scan to Veracode Jenkins Open source project I have added a GitHub workflow to our Jenkins open-source code-base and included the Veracode Scan by adding a stage. This worked successfully for pushes and pull requests. Please find these changes in the below PR. PR: https://github.com/jenkinsci/veracode-scan-plugin/pull/12 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205883.1587480871000.19229.1588141500051%40Atlassian.JIRA.
