[JIRA] (JENKINS-61900) CredentialsProvider implementations are ignore by JCasC
Title: Message Title Antonio Muñiz assigned an issue to Antonio Muñiz Jenkins / JENKINS-61900 CredentialsProvider implementations are ignore by JCasC Change By: Antonio Muñiz Assignee: Antonio Muñiz 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.205772.1586881595000.11101.1586881620279%40Atlassian.JIRA.
[JIRA] (JENKINS-61900) CredentialsProvider implementations are ignore by JCasC
Title: Message Title Antonio Muñiz started work on JENKINS-61900 Change By: Antonio Muñiz 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.205772.1586881595000.11102.1586881620293%40Atlassian.JIRA.
[JIRA] (JENKINS-61900) CredentialsProvider implementations are ignore by JCasC
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-61900 CredentialsProvider implementations are ignore by JCasC Issue Type: Bug Assignee: Unassigned Components: credentials-plugin Created: 2020-04-14 16:26 Priority: Major Reporter: Antonio Muñiz The current implementation to support JCasC is handling credentials from the system provider (SystemCredentialsProvider) exclusively. Any extension of CredentialsProvider is ignored, so credentials coming from it are not handled by JCasC. Add Comment
[JIRA] (JENKINS-61880) `GlobalCredentialsConfiguration` JCasC compatibility
Title: Message Title Antonio Muñiz started work on JENKINS-61880 Change By: Antonio Muñiz 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.205750.1586780064000.9642.1586780220084%40Atlassian.JIRA.
[JIRA] (JENKINS-61880) `GlobalCredentialsConfiguration` JCasC compatibility
Title: Message Title Antonio Muñiz assigned an issue to Antonio Muñiz Jenkins / JENKINS-61880 `GlobalCredentialsConfiguration` JCasC compatibility Change By: Antonio Muñiz Assignee: Antonio Muñiz 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.205750.1586780064000.9641.1586780160893%40Atlassian.JIRA.
[JIRA] (JENKINS-61880) `GlobalCredentialsConfiguration` JCasC compatibility
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-61880 `GlobalCredentialsConfiguration` JCasC compatibility Issue Type: Bug Assignee: Unassigned Components: credentials-plugin Created: 2020-04-13 12:14 Priority: Major Reporter: Antonio Muñiz Extensions of `GlobalCredentialsConfiguration` are JCasC compatible out of the box, however the yaml for them is quite ugly. For example: ? '' : cyberArkGlobalConfiguration: The empty string node comes from the `GlobalCredentialsConfiguration` category, which does not have a proper Symbol. Add Comment
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Antonio Muñiz edited a comment on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script FTR: I'm hitting this with a "not-so-big" (and no matrix) pipeline, ~800 lines, it includes a few separated stages:* Build on Linux (and unit tests)* Build on Windows (and unit tests)* QA (spotbugs, checkstyle, etc)* Security analysis* Integration tests* Release 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.174127.1473169024000.2690.1585568581726%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Antonio Muñiz commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script FTR: I'm hitting this with "not so big" pipeline, ~800 lines, it includes a few separated stages: Build on Linux (and unit tests) Build on Windows (and unit tests) QA (spotbugs, checkstyle, etc) Security analysis Integration tests Release 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.174127.1473169024000.2602.1585568525127%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Antonio Muñiz edited a comment on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script FTR: I'm hitting this with a "not - so - big" pipeline, ~800 lines, it includes a few separated stages:* Build on Linux (and unit tests)* Build on Windows (and unit tests)* QA (spotbugs, checkstyle, etc)* Security analysis* Integration tests* Release 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.174127.1473169024000.2604.1585568525151%40Atlassian.JIRA.
[JIRA] (JENKINS-61455) Allow Jenkins.MANAGE user to access "About Jenkins"
Title: Message Title Antonio Muñiz updated JENKINS-61455 Jenkins / JENKINS-61455 Allow Jenkins.MANAGE user to access "About Jenkins" Change By: Antonio Muñiz 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.205134.1584015622000.6332.1584028980205%40Atlassian.JIRA.
[JIRA] (JENKINS-61455) Allow Jenkins.MANAGE user to access "About Jenkins"
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-61455 Allow Jenkins.MANAGE user to access "About Jenkins" Change By: Antonio Muñiz Users with Jenkins.MANAGE permission allows should be able to access "About Jenkins" management link. 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.205134.1584015622000.6330.1584028860185%40Atlassian.JIRA.
[JIRA] (JENKINS-61455) Allow Jenkins.MANAGE user to access "About Jenkins"
Title: Message Title Antonio Muñiz assigned an issue to Antonio Muñiz Jenkins / JENKINS-61455 Allow Jenkins.MANAGE user to access "About Jenkins" Change By: Antonio Muñiz Assignee: Antonio Muñiz 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.205134.1584015622000.6253.1584017520261%40Atlassian.JIRA.
[JIRA] (JENKINS-61455) Allow Jenkins.MANAGE user to access "About Jenkins"
Title: Message Title Antonio Muñiz started work on JENKINS-61455 Change By: Antonio Muñiz 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.205134.1584015622000.6255.1584017520306%40Atlassian.JIRA.
[JIRA] (JENKINS-59446) Write technical guidelines to write stable ATH
Title: Message Title Antonio Muñiz resolved as Fixed Jenkins / JENKINS-59446 Write technical guidelines to write stable ATH Change By: Antonio Muñiz Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202031.1568901233000.141.1570039320132%40Atlassian.JIRA.
[JIRA] (JENKINS-59446) Write technical guidelines to write stable ATH
Title: Message Title Antonio Muñiz started work on JENKINS-59446 Change By: Antonio Muñiz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202031.1568901233000.4016.1569318360082%40Atlassian.JIRA.
[JIRA] (JENKINS-59446) Write technical guidelines to write stable ATH
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-59446 Write technical guidelines to write stable ATH Change By: Antonio Muñiz There are a few tips to write stable non-flaky ATH. Put those in a readme and review if the other thousand md files in the repo still make sense . Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202031.1568901233000.3993.1569318120782%40Atlassian.JIRA.
[JIRA] (JENKINS-59446) Write technical guidelines to write stable ATH
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-59446 Write technical guidelines to write stable ATH Change By: Antonio Muñiz Summary: Write technical guideline guidelines to write stable ATH Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202031.1568901233000.3985.1569318060116%40Atlassian.JIRA.
[JIRA] (JENKINS-59446) Write technical guideline to write stable ATH
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-59446 Write technical guideline to write stable ATH Issue Type: Improvement Assignee: Antonio Muñiz Components: acceptance-test-harness Created: 2019-09-19 13:53 Priority: Major Reporter: Antonio Muñiz There are a few tips to write stable non-flaky ATH. Put those in a readme and review if the other thousand md files in the repo still make sense. Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-58488) Restart from stage does not work with timeout step
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-58488 Restart from stage does not work with timeout step Issue Type: Bug Assignee: Unassigned Components: workflow-basic-steps-plugin Created: 2019-07-15 08:23 Priority: Major Reporter: Antonio Muñiz If a stage contains a timeout step, then the "Restart from stage" feature does not work. Any attempt to restart the stage is just skipped by the timeout step. A quick look to the timeout step code shows that it stores the time limit (end) as an absolute timestamp. So if the restart stage happens after that fixed time limit has passed then this issue is visible. Add Comment
[JIRA] (JENKINS-57713) Remoting changing behaviour
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-57713 Remoting changing behaviour Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2019-05-28 12:29 Priority: Major Reporter: Antonio Muñiz This change https://github.com/jenkinsci/remoting/pull/193/commits/69f9ebe72c608e14745fb3fc5f8d9e4c65758d89 is modifying the behaviour of the agent connection cycle. Retrying the connection even when the agent is not yet created in the master was something a cloud implementation could rely on (one of our proprietary implementations does). IMHO this was a breaking change. There should be at least one way to keep the previous behaviour (with a new parameter, or maybe reusing the existent "noReconnect"). Add Comment
[JIRA] (JENKINS-55976) Missing error log
Title: Message Title Antonio Muñiz assigned an issue to Antonio Muñiz Jenkins / JENKINS-55976 Missing error log Change By: Antonio Muñiz Assignee: Jeff Thompson Antonio Muñiz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55976) Missing error log
Title: Message Title Antonio Muñiz started work on JENKINS-55976 Change By: Antonio Muñiz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55976) Missing error log
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-55976 Missing error log Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2019-02-05 14:02 Priority: Minor Reporter: Antonio Muñiz There is a missing log call here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received
[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents
Title: Message Title Antonio Muñiz commented on JENKINS-55257 Re: Timestamper break builds on Windows agents It's JRE-8u151 to launch the agent and then the build uses a regular tool installer for 1.8.0_192. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents
Title: Message Title
Antonio Muñiz created an issue
Jenkins / JENKINS-55257
Timestamper break builds on Windows agents
Issue Type:
Bug
Assignee:
Jeff Thompson
Components:
remoting, timestamper-plugin
Created:
2018-12-19 10:43
Priority:
Major
Reporter:
Antonio Muñiz
The following pipeline fails on Windows agents:
pipeline {
options {
timestamps()
skipDefaultCheckout()
}
agent {
label 'windows-astro'
}
stages {
stage("Stage 1") {
steps {
git 'g...@github.com:amuniz/maven-helloworld.git'
withMaven(jdk: 'jdk-8', maven: 'mvn-3.3.9', mavenLocalRepo: '.repository') {
bat 'mvn -version'
}
}
}
}
}
Error:
[Pipeline] node
Running on b314ca90e2fb in c:\build\e4909a8e\workspace\my-team\Tinkering\amuniz\test-p
[Pipeline] {
[Pipeline] timestamps
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Stage 1)
[Pipeline] git
Cloning the remote Git repository
ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: java.io.IOException: Remote call on JNLP4-connect connection from ip-172-18-51-14.ec2.internal/172.18.51.14:49670 failed
at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:169)
at sun.reflect.GeneratedMethodAccessor642.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
[JIRA] (JENKINS-54539) REST API to generate API tokens
Title: Message Title Antonio Muñiz updated JENKINS-54539 Jenkins / JENKINS-54539 REST API to generate API tokens Change By: Antonio Muñiz Status: In Review Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54539) REST API to generate API tokens
Title: Message Title Antonio Muñiz updated JENKINS-54539 Jenkins / JENKINS-54539 REST API to generate API tokens Change By: Antonio Muñiz Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54539) REST API to generate API tokens
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-54539 REST API to generate API tokens Issue Type: New Feature Assignee: Antonio Muñiz Components: core Created: 2018-11-08 11:07 Priority: Minor Reporter: Antonio Muñiz As part of the installation procedure, Jenkins X needs to be able to get the API token for the default (admin) Jenkins user. At the moment, this is only possible/easy via browser interaction by clicking on the "Add new token" button in /me/configure and so the Jenkins X installer has to resort to opening up a browser and attaching a driver to perform the interaction (which is not ideal for very obvious reasons). We need a programmatic way (ie, RESTish) to create-and-get a new API Token. Jenkins X (at the moment) just uses Jenkins' default security realm (basic auth). Add Comment
[JIRA] (JENKINS-54539) REST API to generate API tokens
Title: Message Title Antonio Muñiz started work on JENKINS-54539 Change By: Antonio Muñiz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52255) Add an option to the list-plugins CLI command to output XML
Title: Message Title Antonio Muñiz closed an issue as Won't Fix See PR comments for more information. Jenkins / JENKINS-52255 Add an option to the list-plugins CLI command to output XML Change By: Antonio Muñiz Status: In Progress Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53675) Exclusion annotation for access-modifier-checker
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-53675 Exclusion annotation for access-modifier-checker Issue Type: Task Assignee: Unassigned Components: plugin-pom Created: 2018-09-20 07:39 Priority: Major Reporter: Antonio Muñiz access-modifier should offer a way to selectively skip access checks on specific classes or methods, instead of the all or nothing offered currently. Using plugin-pom as component because there is no component for access-modifier. Add Comment
[JIRA] (JENKINS-53675) Exclusion annotation for access-modifier-checker
Title: Message Title Antonio Muñiz assigned an issue to Antonio Muñiz Jenkins / JENKINS-53675 Exclusion annotation for access-modifier-checker Change By: Antonio Muñiz Assignee: Antonio Muñiz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53505) Remove Restriction on DownloadSettings
Title: Message Title Antonio Muñiz started work on JENKINS-53505 Change By: Antonio Muñiz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53505) Remove Restriction on DownloadSettings
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-53505 Remove Restriction on DownloadSettings Issue Type: Task Assignee: Antonio Muñiz Components: core Created: 2018-09-11 08:46 Priority: Minor Reporter: Antonio Muñiz jenkins.model.DownloadSettings is Restricted, however: It is using the Symbol annotation which means it is used externally The information held by the extension is potentially useful for other extensions working with user data. In my use case, I need to read useBrowser to be able replicate that in another Jenkins instance. Add Comment
[JIRA] (JENKINS-52718) Jenkins#getInstallState should not be restricted
Title: Message Title Antonio Muñiz commented on JENKINS-52718 Re: Jenkins#getInstallState should not be restricted Yes, it's ok. However this is not really a breaking change in the API. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51495) descriptorRadioList does not honor DescriptorVisibilityFilter
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-51495 descriptorRadioList does not honor DescriptorVisibilityFilter Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-05-23 08:12 Priority: Major Reporter: Antonio Muñiz descriptorRadioList does not honor DescriptorVisibilityFilter extensions. The workaround for this has been to pass an already filtered list of descriptors to descriptorRadioList (ie here): f.descriptorRadioList([...], descriptors: h.filterDescriptors(app, MyExtensionPoint.all())) However this has a side effect as descriptorRadioList is using an index to match frontend selected descriptor with a backend instance, so when a descriptor is hidden (by the visibility filter) in the frontend then backend indexes do not match. So, I believe descriptorRadioList should be fixed to either a) Generate correct indexes when there a visibility filter or b) stop using indexes to match things (which seems quite awkward).
[JIRA] (JENKINS-50618) Provide information in the console about who owns a lock when waiting
Title: Message Title Antonio Muñiz edited a comment on JENKINS-50618 Re: Provide information in the console about who owns a lock when waiting This could cause a security issue: users would be aware of able to know about Job names which they could do not even have read/discover permission on. That's why current locks status is shown to admins only in a separated page. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49671) Can't configure jenkinsfile in subdirectory
Title: Message Title Antonio Muñiz closed an issue as Fixed Jenkins / JENKINS-49671 Can't configure jenkinsfile in subdirectory Change By: Antonio Muñiz Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47254) Support for building tags for Bitbucket Server/Cloud
Title: Message Title Antonio Muñiz closed an issue as Fixed Fixed by https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/120 Jenkins / JENKINS-47254 Support for building tags for Bitbucket Server/Cloud Change By: Antonio Muñiz Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-49709) Proxy Config broken in Bitbucket Branch Source Plugin
Title: Message Title Antonio Muñiz closed an issue as Fixed Fixed in https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/112 Jenkins / JENKINS-49709 Proxy Config broken in Bitbucket Branch Source Plugin Change By: Antonio Muñiz Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-45860) Support traits for ScmNavigators
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-45860 Support traits for ScmNavigators Change By: Antonio Muñiz Component/s: bitbucket-branch-source-plugin Component/s: github-branch-source-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45860) Support traits for ScmNavigators
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-45860 Support traits for ScmNavigators Change By: Antonio Muñiz Component/s: github-branch-source-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45860) Support traits for ScmNavigators
Title: Message Title Antonio Muñiz updated JENKINS-45860 Jenkins / JENKINS-45860 Support traits for ScmNavigators Change By: Antonio Muñiz Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50618) Provide information in the console about who owns a lock when waiting
Title: Message Title Antonio Muñiz commented on JENKINS-50618 Re: Provide information in the console about who owns a lock when waiting This could cause a security issue: users would be aware of Job names which they could not even have read/discover permission on. That's why current locks status is shown to admins only in a separated page. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48510) Pipeline Milestone step: Adding parameter for milestone classification
Title: Message Title Antonio Muñiz commented on JENKINS-48510 Re: Pipeline Milestone step: Adding parameter for milestone classification additional maintenance needed (DRY principle is not fulfilled) Not necessarily. Use a shared library loaded from a separated SCM, then create a really simple Jenkinsfile on each project (this is the approach of the Jenkins Plugins project, this is the Jenkinsfile for the milestone plugin for example). Maintenance would be mostly centralized in the shared library. higher dependency to Jenkins / more Jenkins centric view Can you elaborate? I see the same grade of dependency in both approaches. multi branch has limitations (e.g. try to handle Subversion and GIT in one job) You can use more than one call to `checkout` step to get Git and Subversion workspaces in the same pipeline. What's the limitation? I use it to define where data shall be processed but not how Pipelines are designed to define "how" the project is built (among other things), not sure what other use you could do of it. So in case of double builds Why would you have double builds? A commit in a specific repository should trigger a single build in the corresponding job. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-48510) Pipeline Milestone step: Adding parameter for milestone classification
Title: Message Title
Antonio Muñiz commented on JENKINS-48510
Re: Pipeline Milestone step: Adding parameter for milestone classification
The proposed ordinalGroup feature would be a workaround for a good practice: one branch, one job. Having 2 projects/branches been built by the same job is not desirable. Avoiding this is the whole point of multibranch projects. Each project should have its own multibranch job. If projects live in branches of the same repository, then use specific {{Jenkinsfile}}s in branches.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49740) readTrusted fails on Bitbucket PR branch
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-49740 readTrusted fails on Bitbucket PR branch Change By: Antonio Muñiz Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49623) Resource list stored in env variable empty when label is used in locking
Title: Message Title Antonio Muñiz commented on JENKINS-49623 Re: Resource list stored in env variable empty when label is used in locking 2.2 ships JENKINS-40997 which should cover your use case. Actually I don't know what variable are you talking about as the feature did not exist before. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40997) Add way to get locked resource name in pipeline
Title: Message Title Antonio Muñiz commented on JENKINS-40997 Re: Add way to get locked resource name in pipeline Released as 2.2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49734) Use PauseAction while acquiring lock
Title: Message Title Antonio Muñiz resolved as Fixed Released as 2.2 Jenkins / JENKINS-49734 Use PauseAction while acquiring lock Change By: Antonio Muñiz Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43574) Lockable resources plugin does not take effect
Title: Message Title Antonio Muñiz resolved as Fixed Released as 2.2 Jenkins / JENKINS-43574 Lockable resources plugin does not take effect Change By: Antonio Muñiz Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40062) Optionally include config.xml files for nodes
Title: Message Title Antonio Muñiz closed an issue as Fixed Jenkins / JENKINS-40062 Optionally include config.xml files for nodes Change By: Antonio Muñiz Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34021) NPE: Failed to abort CpsFlowExecutiontask.DurableTaskStep$Execution.stop(DurableTaskStep.java:140)
Title: Message Title
Antonio Muñiz edited a comment on JENKINS-34021
Re: NPE: Failed to abort CpsFlowExecutiontask.DurableTaskStep$Execution.stop(DurableTaskStep.java:140)
# Jenkins 2.32 (with all default plugins, which I think is latest versions)# {{workflow-basic-steps-plugin}} didn't have [the fix for retry|https://github.com/jenkinsci/workflow-basic-steps-plugin/pull/35] at that time (which makes the case easier to reproduce)# Create a pipeline with the script I posted before# Trigger a build# Click on the build stop button# {{retry}} swallow swallows the request and retry retries its body# The halt link is printed in the console log, click on it# The kill link is printed in the console log, click on it# The build is killed, but a warning is continuously printed in Jenkins global log[~jglick] I hope it helps.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40368) Locked resources are not always freed up on Pipeline hard kill when there are other pipelines waiting on the Resource
Title: Message Title Antonio Muñiz resolved as Fixed Jenkins / JENKINS-40368 Locked resources are not always freed up on Pipeline hard kill when there are other pipelines waiting on the Resource Change By: Antonio Muñiz Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34433) pipeline lock does not retry
Title: Message Title Antonio Muñiz commented on JENKINS-34433 Re: pipeline lock does not retry This may be fixed by https://github.com/jenkinsci/lockable-resources-plugin/pull/46 Needs checking. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38906) Remove lock resource name from global configuration when lock is released
Title: Message Title Antonio Muñiz assigned an issue to Antonio Muñiz Jenkins / JENKINS-38906 Remove lock resource name from global configuration when lock is released Change By: Antonio Muñiz Assignee: CloudBees Inc. Antonio Muñiz Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38906) Remove lock resource name from global configuration when lock is released
Title: Message Title Antonio Muñiz commented on JENKINS-38906 Re: Remove lock resource name from global configuration when lock is released Removing on release would not be safe. +1 for the transient parameter. There should be a periodic background task looping on defined resources and removing those marked as transient and not used after a specific amount of time. Also transient resources should not be displayed in the administration page as it does not make sense to configure them nor remove them. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34021) NPE: Failed to abort CpsFlowExecutiontask.DurableTaskStep$Execution.stop(DurableTaskStep.java:140)
Title: Message Title Antonio Muñiz commented on JENKINS-34021 Re: NPE: Failed to abort CpsFlowExecutiontask.DurableTaskStep$Execution.stop(DurableTaskStep.java:140) Jenkins 2.32 (with all default plugins, which I think is latest versions) workflow-basic-steps-plugin didn't have the fix for retry at that time (which makes the case easier to reproduce) Create a pipeline with the script I posted before Trigger a build Click on the build stop button retry swallow the request and retry its body The halt link is printed in the console log, click on it The kill link is printed in the console log, click on it The build is killed, but a warning is continuously printed in Jenkins global log Jesse Glick I hope it helps. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-34021) NPE: Failed to abort CpsFlowExecutiontask.DurableTaskStep$Execution.stop(DurableTaskStep.java:140)
Title: Message Title
Antonio Muñiz commented on JENKINS-34021
Re: NPE: Failed to abort CpsFlowExecutiontask.DurableTaskStep$Execution.stop(DurableTaskStep.java:140)
Reproducible by hard killing this:
retry (10) {
node {
sh 'sleep 30'
}
}
The I see the warning message in the logs indefinitely. Maybe this specific case is fixed by https://github.com/jenkinsci/workflow-basic-steps-plugin/pull/35, I don't know, didn't try.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40368) Locked resources are not always freed up on Pipeline hard kill when there are other pipelines waiting on the Resource
Title: Message Title Antonio Muñiz started work on JENKINS-40368 Change By: Antonio Muñiz Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40368) Locked resources are not always freed up on Pipeline hard kill when there are other pipelines waiting on the Resource
Title: Message Title Antonio Muñiz assigned an issue to Antonio Muñiz Jenkins / JENKINS-40368 Locked resources are not always freed up on Pipeline hard kill when there are other pipelines waiting on the Resource Change By: Antonio Muñiz Assignee: Antonio Muñiz Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40368) Locked resources are not always freed up on Pipeline hard kill when there are other pipelines waiting on the Resource
Title: Message Title Antonio Muñiz commented on JENKINS-40368 Re: Locked resources are not always freed up on Pipeline hard kill when there are other pipelines waiting on the Resource Reproduced locally. The problem is that LockableResourcesManager is supposing a queued context will always have a valid linked build (waiting for the lock), but that turns to be false under some circumstances (like the one described in this issue: a hard killed job which for some other reason does not call LockRunListener.onComplete - something to be investigated separately, as it can happen if Jenkins is stopped abruptly so there is no chance to call anything, thus a fix here is needed at any rate). This is the stack trace (where #20 is a hard killed job while it was holding a lock): java.io.IOException: test #20 did not yet start at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:724) at org.jenkinsci.plugins.workflow.cps.CpsStepContext.getFlowExecution(CpsStepContext.java:432) at org.jenkinsci.plugins.workflow.cps.CpsStepContext.getThreadGroupSynchronously(CpsStepContext.java:239) at org.jenkinsci.plugins.workflow.cps.CpsStepContext.getThreadSynchronously(CpsStepContext.java:233) at org.jenkinsci.plugins.workflow.cps.CpsStepContext.doGet(CpsStepContext.java:285) at org.jenkinsci.plugins.workflow.support.DefaultStepContext.get(DefaultStepContext.java:71) at org.jenkins.plugins.lockableresources.LockableResourcesManager.unlockNames(LockableResourcesManager.java:332) at org.jenkins.plugins.lockableresources.LockableResourcesManager.unlockNames(LockableResourcesManager.java:338) at org.jenkins.plugins.lockableresources.LockableResourcesManager.unlock(LockableResourcesManager.java:285) at org.jenkins.plugins.lockableresources.LockableResourcesManager.unlock(LockableResourcesManager.java:273) at org.jenkins.plugins.lockableresources.actions.LockableResourcesRootAction.doUnlock(LockableResourcesRootAction.java:103) Add Comment
[JIRA] (JENKINS-38266) Lock released, but waiting acquirers won't continue to work
Title: Message Title Antonio Muñiz commented on JENKINS-38266 Re: Lock released, but waiting acquirers won't continue to work Nicolas PENCREACH the issue you are describing looks like a valida bug but unrelated to this, can you file it separately please? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40879) Locked areas are executed multiple times in parallel
Title: Message Title Antonio Muñiz updated JENKINS-40879 Jenkins / JENKINS-40879 Locked areas are executed multiple times in parallel Change By: Antonio Muñiz Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40899) Transitive plugin dependencies not correctly checked when using snapshots
Title: Message Title
Antonio Muñiz edited a comment on JENKINS-40899
Re: Transitive plugin dependencies not correctly checked when using snapshots
[~jglick] yes, it is. {{mvn-hpi-plugin:1.121}} is setting {{Plugin-Dependencies}} versions in the plugin manifest to {{X.Y.Z-SNAPSHOT}} instead of the timestamped string for the snapshot, and it makes Jenkins core to behave as expected.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40899) Transitive plugin dependencies not correctly checked when using snapshots
Title: Message Title
Antonio Muñiz edited a comment on JENKINS-40899
Re: Transitive plugin dependencies not correctly checked when using snapshots
[~jglick] yes, it is. {{mvn-hpi-plugin:1.121}} is setting {{Plugin-Dependencies}} versions to {{X.Y.Z-SNAPSHOT}} instead of the timestamped string for the snapshot, and it makes Jenkins core to behave as expected.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40899) Transitive plugin dependencies not correctly checked when using snapshots
Title: Message Title Antonio Muñiz commented on JENKINS-40899 Re: Transitive plugin dependencies not correctly checked when using snapshots Jesse Glick yes, it is. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40899) Transitive plugin dependencies not correctly checked when using snapshots
Title: Message Title Antonio Muñiz edited a comment on JENKINS-40899 Re: Transitive plugin dependencies not correctly checked when using snapshots The issue is not in core but maven-hpi-plugin and it is fixed by in 1.121.It can be closed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40899) Transitive plugin dependencies not correctly checked when using snapshots
Title: Message Title Antonio Muñiz commented on JENKINS-40899 Re: Transitive plugin dependencies not correctly checked when using snapshots The issue is not in core but maven-hpi-plugin and it is fixed by in 1.121. It can be closed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41699) Add a timeout field
Title: Message Title
Antonio Muñiz created an issue
Jenkins / JENKINS-41699
Add a timeout field
Issue Type:
New Feature
Assignee:
Antonio Muñiz
Components:
lockable-resources-plugin
Created:
2017/Feb/03 10:49 AM
Priority:
Minor
Reporter:
Antonio Muñiz
It would be something like:
lock (resources: "my-res", timeout: 5) {
[real work here]
}
So it tries to lock the resource and give up after 5 seconds.
Add Comment
[JIRA] (JENKINS-38266) Lock released, but waiting acquirers won't continue to work
Title: Message Title Antonio Muñiz closed an issue as Duplicate Jenkins / JENKINS-38266 Lock released, but waiting acquirers won't continue to work Change By: Antonio Muñiz Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38510) Add a count to the locks to allow limited ressources
Title: Message Title Antonio Muñiz closed an issue as Won't Do Jenkins / JENKINS-38510 Add a count to the locks to allow limited ressources Change By: Antonio Muñiz Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38510) Add a count to the locks to allow limited ressources
Title: Message Title Antonio Muñiz commented on JENKINS-38510 Re: Add a count to the locks to allow limited ressources This is exactly what Throttle Concurrent Builds plugin is doing. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40368) Locked resources are not always freed up on Pipeline hard kill when there are other pipelines waiting on the Resource
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-40368 Locked resources are not always freed up on Pipeline hard kill when there are other pipelines waiting on the Resource Change By: Antonio Muñiz Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41313) On first index after upgrade to 2.0.0 all open PRs are rebuilt
Title: Message Title Antonio Muñiz resolved as Fixed https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/33 Jenkins / JENKINS-41313 On first index after upgrade to 2.0.0 all open PRs are rebuilt Change By: Antonio Muñiz Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-41311) NPE in CleanupJobsOnDelete
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-41311 NPE in CleanupJobsOnDelete Issue Type: Bug Assignee: Antonio Muñiz Components: pipeline-milestone-step-plugin Created: 2017/Jan/23 9:28 AM Priority: Major Reporter: Antonio Muñiz As noted here there is a NPE in the CleanupJobsOnDelete listener. The condition to apply the listener must be improved as the milestone state storage file is not granted to exists. Note that the NPE should not affect anything, it is a warning when trying to apply the listener when there is no status file to read so there is no jobs to clean in the file. Add Comment
[JIRA] (JENKINS-40879) Locked areas are executed multiple times in parallel
Title: Message Title Antonio Muñiz commented on JENKINS-40879 Re: Locked areas are executed multiple times in parallel Is this always happening, or is it only under certain conditions? if so, can you describe such conditions? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36874) Pull request not built when build status patch is applied
Title: Message Title Antonio Muñiz resolved as Fixed Jenkins / JENKINS-36874 Pull request not built when build status patch is applied Change By: Antonio Muñiz Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39267) Honor non-proxy hosts
Title: Message Title Antonio Muñiz resolved as Fixed Jenkins / JENKINS-39267 Honor non-proxy hosts Change By: Antonio Muñiz Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38165) Support lockable resource labels in the pipeline
Title: Message Title Antonio Muñiz closed an issue as Duplicate Jenkins / JENKINS-38165 Support lockable resource labels in the pipeline Change By: Antonio Muñiz Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34273) Extend quantity configuration to Pipeline lock step
Title: Message Title Antonio Muñiz resolved as Fixed Released as 1.11 Jenkins / JENKINS-34273 Extend quantity configuration to Pipeline lock step Change By: Antonio Muñiz Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title Antonio Muñiz resolved as Fixed Released as 1.11 Jenkins / JENKINS-34268 Lock multiple resources using the Pipeline lock step Change By: Antonio Muñiz Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title Antonio Muñiz assigned an issue to Antonio Muñiz Jenkins / JENKINS-34268 Lock multiple resources using the Pipeline lock step Change By: Antonio Muñiz Assignee: Antonio Muñiz Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title Antonio Muñiz started work on JENKINS-38641 Change By: Antonio Muñiz Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title Antonio Muñiz assigned an issue to Antonio Muñiz Jenkins / JENKINS-38641 Milestone step fails to pass due to deleted/future builds having passed Change By: Antonio Muñiz Assignee: CloudBees Inc. Antonio Muñiz Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title Antonio Muñiz updated JENKINS-38641 Jenkins / JENKINS-38641 Milestone step fails to pass due to deleted/future builds having passed Change By: Antonio Muñiz Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40094) Global config.xml only contains a exception
Title: Message Title Antonio Muñiz started work on JENKINS-40094 Change By: Antonio Muñiz Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40094) Global config.xml only contains a exception
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-40094 Global config.xml only contains a exception Issue Type: Bug Assignee: Antonio Muñiz Components: support-core-plugin Created: 2016/Nov/29 12:26 PM Priority: Major Reporter: Antonio Muñiz --- WARNING: Could not attach /home/support/hudson_home/support/patched100416060363402908.xml as it cannot currently be found --- java.io.FileNotFoundException: /home/support/hudson_home/support/patched100416060363402908.xml (No such file or directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.(FileInputStream.java:138) at hudson.util.IOUtils.copy(IOUtils.java:29) at com.cloudbees.jenkins.support.api.FileContent.writeTo(FileContent.java:63) The generated file is being removed before it is actually added to the bundle. Add Comment
[JIRA] (JENKINS-40062) Optionally include config.xml files for nodes
Title: Message Title
Antonio Muñiz updated an issue
Jenkins / JENKINS-40062
Optionally include config.xml files for nodes
Change By:
Antonio Muñiz
There is useful diagnosis information in the nodes' config file, like {{ { prefixStartSlaveCmd}} } for example.Having those files in the support bundle would be great.Secrets must be filtered out and the inclusion of this files in the bundle must be optional.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40062) Optionally include config.xml files for nodes
Title: Message Title
Antonio Muñiz created an issue
Jenkins / JENKINS-40062
Optionally include config.xml files for nodes
Issue Type:
Improvement
Assignee:
Antonio Muñiz
Components:
support-core-plugin
Created:
2016/Nov/28 9:42 AM
Priority:
Major
Reporter:
Antonio Muñiz
There is useful diagnosis information in the nodes' config file, like {{ {prefixStartSlaveCmd} }} for example. Having those files in the support bundle would be great. Secrets must be filtered out and the inclusion of this files in the bundle must be optional.
Add Comment
[JIRA] (JENKINS-40062) Optionally include config.xml files for nodes
Title: Message Title Antonio Muñiz started work on JENKINS-40062 Change By: Antonio Muñiz Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title Antonio Muñiz commented on JENKINS-38641 Re: Milestone step fails to pass due to deleted/future builds having passed Downgrading to major as remove/readd a job with the same name is not a frequent task in a production environment. BTW the workaround (ugly but a workaround) is to edit the file JENKINS_HOME/org.jenkinsci.plugins.pipeline.milestone.MilestoneStep.xml and remove the entry element about the removed job (the job name is in //entry/string). It will be regenerated automatically after the first run of the new job. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-38641 Milestone step fails to pass due to deleted/future builds having passed Change By: Antonio Muñiz Priority: Blocker Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title Antonio Muñiz commented on JENKINS-38641 Re: Milestone step fails to pass due to deleted/future builds having passed Ok. If this is happening when a job is deleted and recreated for some reason (intead of deleting builds), then looks like a valid bug. A JobListener has to be added to monitor job deletions so the internal status tracking file can be updated accordingly. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39267) Honor non-proxy hosts
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-39267 Honor non-proxy hosts Issue Type: Improvement Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Oct/26 1:30 PM Priority: Minor Reporter: Antonio Muñiz HTTP requests done to retrieve repository and PR information are not applying the non-proxy hosts configuration at Jenkins global level. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38891) Pull Requests page is confusing
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-38891 Pull Requests page is confusing Change By: Antonio Muñiz The current view for PRs is a bit confusing (for me at least).Is build 8 7 (in the screenshot) building all that commits? Why are there in different lines if it is the same build? Am I missing something?Screenshot taken from [jenkins on jenkins instance|https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/pr]. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38891) Pull Requests page is confusing
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-38891 Pull Requests page is confusing Issue Type: Improvement Assignee: Unassigned Attachments: bo-builds.png Components: blueocean-plugin Created: 2016/Oct/11 11:04 AM Priority: Minor Reporter: Antonio Muñiz The current view for PRs is a bit confusing (for me at least). Is build 8 (in the screenshot) building all that commits? Why are there in different lines if it is the same build? Am I missing something? Screenshot taken from jenkins on jenkins instance. Add Comment
[JIRA] (JENKINS-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title Antonio Muñiz commented on JENKINS-38641 Re: Milestone step fails to pass due to deleted/future builds having passed davidkarlsen if you are using a "Bitbucket Team/Project", then make sure you have installed branch-api plugin at 1.8 or above, so Orphaned Item Strategy is propagated to every repository discovered on folder computation. The workaround should work (and 1 day should be enough, unless your Bitbucket instance is down more than 24 hours). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38748) Bitbucket Server auto-register webhooks
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-38748 Bitbucket Server auto-register webhooks Issue Type: Improvement Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Oct/05 7:07 PM Priority: Minor Reporter: Antonio Muñiz Add for Bitbucket Server webhooks auto-registering (as it is for BB Cloud now). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title Antonio Muñiz edited a comment on JENKINS-38641 Re: Milestone step fails to pass due to deleted/future builds having passed So what you want to get fixed is JENKINS-36029, not this. I just posted a possible workaround - until it is fixed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
