[JIRA] (JENKINS-57672) Determine Dependencies between PluginManager.java on Jenkins Core
Title: Message Title Natasha Stopa closed an issue as Postponed Jenkins / JENKINS-57672 Determine Dependencies between PluginManager.java on Jenkins Core Change By: Natasha Stopa Status: In Progress Closed Resolution: Postponed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199605.1558721108000.25732.1560317761549%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57672) Determine Dependencies between PluginManager.java on Jenkins Core
Title: Message Title Natasha Stopa commented on JENKINS-57672 Re: Determine Dependencies between PluginManager.java on Jenkins Core So I'm going to close this Jira task since I think it was more or less completed and we've since decided to go a different direction to start. Perhaps a little later in the summer we can circle back to incorporating the high level API and Jenkins core. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199605.1558721108000.25727.1560317761430%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57672) Determine Dependencies between PluginManager.java on Jenkins Core
Title: Message Title Natasha Stopa updated JENKINS-57672 Jenkins / JENKINS-57672 Determine Dependencies between PluginManager.java on Jenkins Core Change By: Natasha Stopa Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199605.1558721108000.25728.1560317761454%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56305) Need some help with init scripts on this plugin
Title: Message Title
Dominik Bartholdi commented on JENKINS-56305
Re: Need some help with init scripts on this plugin
as described above, you should not do it this way and I can't guarantee this will always work! But for sure this words will not stop you from doing so, therefore I show you at least a better way to do it: (Please never interact with the *Provider classes at all):
def folder = Jenkins.instance.getItemByFullName('ios');
def action = ""
def store = action.getStore();
def config = new org.jenkinsci.plugins.configfiles.json.JsonConfig("_config", "Config for ", "Branch config ", "{A:B}");
// save the new config
store.save(config);
// get the new config
def jsonConfig = store.getById("_config");
// remove the config
store.remove("_config");
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197885.155124611.25722.1560317700310%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57713) Cloud agent provisioning errors due to Remoting behaviour change
Title: Message Title Oliver Gondža commented on JENKINS-57713 Re: Cloud agent provisioning errors due to Remoting behaviour change Jeff Thompson, I agree a switch to opt-in/out of the behavior is about the only thing to do as far as I can see. I do not think it is sane to rely on any asumptions with regards the sequence of actions on master/agent during cloud provisioning. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199655.1559046575000.25706.1560314040291%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57969) Add License to the Plugin Installation Manager tool
Title: Message Title Natasha Stopa started work on JENKINS-57969 Change By: Natasha Stopa Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199953.1560276626000.25702.1560313440148%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55624) Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set
Title: Message Title Peter Philipp commented on JENKINS-55624 Re: Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set Since Jenkins pushed the Build Authorization https://jenkins.io/doc/book/system-administration/security/build-authorization/ with the last update, we didn't want to dismiss this and added the plugin. And we also started experiencing the same issue as described in the summary. However, it seems like this is actually a git-plugin related issue because while the git plugin doesn't list the parent / global credentials, the docker plugin lists them properly. (I couldn't test if these credentials work yet or are just listed.) I've also tried to tune the user permissions but no matter if the specified user has full or just limited permissions the parent credentials wont show up. Checking the issue history of the git-plugin it seems like there has been quite a collection related issues e.g.: https://issues.jenkins-ci.org/browse/JENKINS-38126?focusedCommentId=289182=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-289182 https://issues.jenkins-ci.org/browse/JENKINS-44773 Following issue also links to some other related issues: https://issues.jenkins-ci.org/browse/JENKINS-44774 Given all that I wonder if the bug report should be filed / merged with one of the git-plugin related issues. As for now we switched back to using the SYSTEM user. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196797.1547654507000.25683.1560311100268%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57978) "Allow ECS to break build" is meaningless and the help is not helpful
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-57978 "Allow ECS to break build" is meaningless and the help is not helpful Issue Type: Task Assignee: Anatoliy Varanitsa Attachments: image-2019-06-11-22-00-08-354.png, image-2019-06-11-22-03-01-024.png, image-2019-06-11-22-03-13-410.png, image-2019-06-11-22-03-18-222.png Components: ecs-publisher-plugin Created: 2019-06-12 02:05 Priority: Minor Reporter: Josh Soref This is what the plugin provides: Allow ECS to break build Allow break build. (from ECS publisher) Manage Break Sensitivity Break on vulnerabilities
[JIRA] (JENKINS-54530) Upgrade maven embedder from 3.1.0 to at least 3.5.4
Title: Message Title Olivier Lamy started work on JENKINS-54530 Change By: Olivier Lamy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195301.1541643577000.25672.1560298920172%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55787) Switch labels from entry to checkbox
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-55787 Switch labels from entry to checkbox Change By: Josh Soref Component/s: analysis-core-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197176.1548453513000.25670.1560296940281%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57949) EC2 plugin not found by install-plugins.sh
Title: Message Title Pablo Gomes Ludermir closed an issue as Not A Defect Jenkins / JENKINS-57949 EC2 plugin not found by install-plugins.sh Change By: Pablo Gomes Ludermir Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199927.1560226595000.25668.1560296520230%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57949) EC2 plugin not found by install-plugins.sh
Title: Message Title Pablo Gomes Ludermir updated an issue Jenkins / JENKINS-57949 EC2 plugin not found by install-plugins.sh Change By: Pablo Gomes Ludermir Comment: Added the question on Stackoverflow: [https://stackoverflow.com/questions/56552829/jenkins-ec2-plugin-not-installing-via-the-install-plugins-sh] It seems that the plugin is available on the mirror sites, but it's not known to the main Jenkins update site. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199927.1560226595000.25666.1560295980125%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57949) EC2 plugin not found by install-plugins.sh
Title: Message Title Pablo Gomes Ludermir commented on JENKINS-57949 Re: EC2 plugin not found by install-plugins.sh Added the question on Stackoverflow: https://stackoverflow.com/questions/56552829/jenkins-ec2-plugin-not-installing-via-the-install-plugins-sh It seems that the plugin is available on the mirror sites, but it's not known to the main Jenkins update site. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199927.1560226595000.25664.1560295680086%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57831) Remoting susceptible to race between HTTP availability and JNLP availability during master initialization
Title: Message Title Basil Crow commented on JENKINS-57831 Re: Remoting susceptible to race between HTTP availability and JNLP availability during master initialization I just discovered jenkinsci/docker#805, which sounds similar to my scenario on the surface. There, Pedro Rodrigues found that the JNLP port number is first set to a random value and then a Groovy initialization script in the Docker image changes to it the desired value. This opens up a race where Jenkins is responding to the wrong JNLP port for a short amount of time during initialization. Pedro fixed this in the Docker image by using a Java system property rather than a Groovy initialization script to set the port. The Java system property is used when Jenkins first initializes JNLP, so this theoretically closes the race. I wonder if this phenomenon could explain my observations above, where Jenkins was replying to HTTP request but the JNLP port was not available. It seems like the following sequence of events is possible: Jenkins advertises the old JNLP port Swarm/Remoting picks this up Jenkins executes the Groovy initialization script to change the port Swarm/Remoting tries to connect to the old port I'll be deploying Pedro's changes to the Docker image next week. I don't know for sure they will fix this problem, but I am hopeful that they might. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on
[JIRA] (JENKINS-50886) Declarative pipeline with pollSCM triggers 2 builds
Title: Message Title Mark Waite commented on JENKINS-50886 Re: Declarative pipeline with pollSCM triggers 2 builds Priyatham Tadikonda no solution in progress and no solution proposed. We recommend that webhooks are better than polling (faster response, lighter load on the git server). See "polling must die" by Kohsuke Kawaguchi for more details. If polling is truly the only way to achieve your goal, then you might also consider setting the polling interval to be greater than the average build time. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190011.1524103101000.25611.1560292560172%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50886) Declarative pipeline with pollSCM triggers 2 builds
Title: Message Title Priyatham Tadikonda commented on JENKINS-50886 Re: Declarative pipeline with pollSCM triggers 2 builds I encounter this issue too. Do we have a solution for this yet? I'm using Multibranch Pipeline project and Github repostitory. We are polling every 5minutes but the build takes more than 30mins to complete.Duplicate Builds are being triggered with the same commit ID. Please help me. Thank you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190011.1524103101000.25605.1560292140222%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57831) Remoting susceptible to race between HTTP availability and JNLP availability during master initialization
Title: Message Title Jeff Thompson commented on JENKINS-57831 Re: Remoting susceptible to race between HTTP availability and JNLP availability during master initialization You've done some impressive diagnosis and reporting on this one. That will make it a lot easier to understand and see if we can come up with any solutions. I'll need to find time tomorrow or the next day to study this more thoroughly. I doubt your first suggestion is feasible. The Jenkins init sequence has some cool capabilities but it's pretty limited. Disrupting it can cause lots of problems. It's probably worth investigating, but I'm not hopeful, based on my last attempt to get it to do exactly what I needed. Your second suggestion has me worried, mostly because of recent events involving #JENKINS-46515. @witokondoria made an attempt to improve the connection sequence but it broke other scenarios, #57713. I'd really like to see us make improvements in this area, but there may be too many different implementations and scenarios relying on the existing sequence. We may have to pursue your third suggestion. I'll look it in more detail but I'm very interested in any further ideas or suggestions. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199788.1559625798000.25601.1560290220096%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57747) Add form validation for gitlab gold and ultimate server urls
Title: Message Title Parichay Barpanda commented on JENKINS-57747 Re: Add form validation for gitlab gold and ultimate server urls See https://github.com/gitlab4j/gitlab4j-api/issues/384 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199692.1559151818000.25584.1560289740143%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57747) Add form validation for gitlab gold and ultimate server urls
Title: Message Title Parichay Barpanda commented on JENKINS-57747 Re: Add form validation for gitlab gold and ultimate server urls No more performing form validation for gitlab server url. Only checking if it is a valid url. Not checking if it a valid gitlab server url. Since gitlab doesn't have a public endpoint to validate the server url. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199692.1559151818000.25583.1560289680044%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57747) Add form validation for gitlab gold and ultimate server urls
Title: Message Title Parichay Barpanda started work on JENKINS-57747 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199692.1559151818000.25581.1560289620119%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57747) Add form validation for gitlab gold and ultimate server urls
Title: Message Title Parichay Barpanda updated JENKINS-57747 Jenkins / JENKINS-57747 Add form validation for gitlab gold and ultimate server urls Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199692.1559151818000.25582.1560289620166%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57211) Jenkins won't start due to some User Migration Exception.
Title: Message Title Jeff Thompson closed an issue as Cannot Reproduce Since there has been a lack of response for quite a while on this, I'm going to close this issue. If you have additional information to help move this along, feel free to provide it and re-open as needed. Jenkins / JENKINS-57211 Jenkins won't start due to some User Migration Exception. Change By: Jeff Thompson Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198596.1554513891000.25578.1560289560366%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56560) Slave logs full of remoting error: "unable to read a command"
Title: Message Title Jeff Thompson closed an issue as Cannot Reproduce Since there has been a lack of response for quite a while on this, I'm going to close this issue. If you have additional information to help move this along, feel free to provide it and re-open as needed. Jenkins / JENKINS-56560 Slave logs full of remoting error: "unable to read a command" Change By: Jeff Thompson Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198175.1552567697000.25576.1560289500253%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57010) Build agent offline with "FATAL: java.nio.channels.ClosedChannelException"
Title: Message Title Jeff Thompson closed an issue as Cannot Reproduce Since there has been a lack of response for quite a while on this, I'm going to close this issue. If you have additional information to help move this along, feel free to provide it and re-open as needed. Jenkins / JENKINS-57010 Build agent offline with "FATAL: java.nio.channels.ClosedChannelException" Change By: Jeff Thompson Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198711.155532933.25574.1560289440386%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54476) JNLP Agent disconnected, having issues connecting to master.
Title: Message Title Jeff Thompson closed an issue as Cannot Reproduce Since there has been a lack of response for quite a while on this, I'm going to close this issue. If you have additional information to help move this along, feel free to provide it and re-open as needed. Jenkins / JENKINS-54476 JNLP Agent disconnected, having issues connecting to master. Change By: Jeff Thompson Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195242.1541459424000.25572.1560289440359%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56474) agent stuck in infinite loop at connect time on FreeBSD/arm with openjdk 8
Title: Message Title Jeff Thompson updated JENKINS-56474 Jenkins / JENKINS-56474 agent stuck in infinite loop at connect time on FreeBSD/arm with openjdk 8 Change By: Jeff Thompson Resolution: Cannot Reproduce Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198074.1552031841000.25568.1560289020324%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56474) agent stuck in infinite loop at connect time on FreeBSD/arm with openjdk 8
Title: Message Title Jeff Thompson closed an issue as Cannot Reproduce Jenkins / JENKINS-56474 agent stuck in infinite loop at connect time on FreeBSD/arm with openjdk 8 Change By: Jeff Thompson Status: Reopened Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198074.1552031841000.25570.1560289020348%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56474) agent stuck in infinite loop at connect time on FreeBSD/arm with openjdk 8
Title: Message Title Jeff Thompson updated JENKINS-56474 Since there has been a lack of response for quite a while on this, I'm going to close this issue. If you have additional information to help move this along, feel free to provide it and re-open as needed. Jenkins / JENKINS-56474 agent stuck in infinite loop at connect time on FreeBSD/arm with openjdk 8 Change By: Jeff Thompson Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198074.1552031841000.25566.1560288960180%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57889) Add HashTable or HashMap for GitLabServer faster access
Title: Message Title Parichay Barpanda updated JENKINS-57889 Jenkins / JENKINS-57889 Add HashTable or HashMap for GitLabServer faster access Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199853.1559837778000.25564.1560288840088%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57864) Test Converted Docker Plugin Bash Script
Title: Message Title Natasha Stopa started work on JENKINS-57864 Change By: Natasha Stopa Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199826.1559753122000.25563.156028885%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57977) Investigate Use of File Locks for Plugin Manager Tool
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-57977 Investigate Use of File Locks for Plugin Manager Tool Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-11 21:18 Priority: Minor Reporter: Natasha Stopa I'm generally confused about how the bash script used file locks. The goal of this task is to clarify if these are really needed for the plugin manager tool. Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-57767) Remote call failed
Title: Message Title Jeff Thompson commented on JENKINS-57767 Re: Remote call failed Unfortunately, there isn't enough information in this report to make it actionable. Random failures can be difficult to diagnose when you have access to the systems and can examine differences in status and behaviors. One of the first things to check is that you have compatible versions of both Java and the agent (slave) jar. Given the randomness, this seems unlikely but it is essential to validate it. Try to isolate anything you can about what is different between the successes and failures. Do the failures always occur with the same action? (In this case it is DeleteDirStep.) Can you observe any differences in the types of systems where it succeeds or fails? Are there differences in the job configurations? Are you up-to-date with Jenkins and plugin versions? Are your agents up-to-date? Many times unexplained failures result from some combination of plugins. Tracking them down may require running experiments with disabling one or more plugins. At a minimum, this issue report needs to include the version of Jenkins you are using, along with plugins and their versions. Perhaps others have seen some similar behavior and may be to provide ideas. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199714.1559241868000.25561.1560287760100%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57849) Move Plugin Management Repo to Jenkins
Title: Message Title Natasha Stopa commented on JENKINS-57849 Re: Move Plugin Management Repo to Jenkins The repository has now completely been moved to jenkinsci. The artifact id was updated to match the repository name. The original repository was deleted and I started my own fork from the repository: https://github.com/stopalopa/plugin-installation-manager-tool. A pull request was created for update permissions: https://github.com/jenkins-infra/repository-permissions-updater/pull/1171. Some error was thrown when trying to merge the PR: https://ci.jenkins.io/blue/organizations/jenkins/Infra%2Frepository-permissions-updater/detail/PR-1171/1/pipeline/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199807.1559678689000.25559.1560287460194%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57718) Cannot disable reduceLog setting
Title: Message Title Nikolas Falco updated JENKINS-57718 Jenkins / JENKINS-57718 Cannot disable reduceLog setting Change By: Nikolas Falco Status: Fixed but Unreleased Closed Released As: 2.3.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199661.1559056688000.25557.1560287040286%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57849) Move Plugin Management Repo to Jenkins
Title: Message Title Natasha Stopa updated JENKINS-57849 Jenkins / JENKINS-57849 Move Plugin Management Repo to Jenkins Change By: Natasha Stopa Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199807.1559678689000.2.1560286980299%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56271) xUnit produce an empty report for NUnit3 type
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-56271 xUnit produce an empty report for NUnit3 type Change By: Nikolas Falco Released As: 2.3. 2 3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197843.155110973.25553.1560286800377%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52125) jenkins master: Cannot contact : java.lang.InterruptedException without heavy load or obvious network issue
Title: Message Title Jeff Thompson commented on JENKINS-52125 Re: jenkins master: Cannot contact : java.lang.InterruptedException without heavy load or obvious network issue I've seen something like what Dennis Tran reports a few times associated with an OutOfMemoryError. It can take a bit of digging to actually see the errors in these cases. Because the channel or VM fails, the errors may not reach the logs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191724.1529617125000.25542.1560286320244%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57889) Add HashTable or HashMap for GitLabServer faster access
Title: Message Title Parichay Barpanda started work on JENKINS-57889 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199853.1559837778000.25540.1560286080088%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57976) Add JCasC configuration instructions to README
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57976 Add JCasC configuration instructions to README Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-06-11 20:44 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda 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
[JIRA] (JENKINS-54249) GitHub Commit Status Setter - Cannot retrieve Git metadata
Title: Message Title Baptiste Gaillard commented on JENKINS-54249 Re: GitHub Commit Status Setter - Cannot retrieve Git metadata Oleksandr Stovbenko thanks for the suggestions, I already tried this few months ago without success. Today I tried to update the https://github.com/jenkinsci/github-plugin to find the problem and fix it. It seems that the problem came from the fact that the https://github.com/jenkinsci/git-plugin replaced the BuildData class by the BuildDetails class (this is explained here https://github.com/jenkinsci/git-plugin/commit/07cfa5ddef698838b01d4214915f98d4e902c0f8#diff-6cb4dc50342af417dc66c68b45c48fb1). As a result when Jenkins run a job the Github plugin failed to get the last build (to then retrieve the revision SHA1). For now I just implemented VERY UGLY updates (i'll take the time to propose a clean PR later), the repo is here https://github.com/bgaillard/github-plugin. If you would like to test it compile it with mvn install -Dmaven.test.skip=true (I did not took time to fix the tests). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194891.1540467307000.25511.1560285300659%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57975) src/main/resources/hudson/plugins/parameterizedtrigger/BinaryFileParameterFactory/help-parameterName.html is empty
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-57975 src/main/resources/hudson/plugins/parameterizedtrigger/BinaryFileParameterFactory/help-parameterName.html is empty Issue Type: Task Assignee: Unassigned Components: parameterized-trigger-plugin Created: 2019-06-11 20:25 Priority: Minor Reporter: Josh Soref install the Jenkins Parameterized Trigger plugin (2.35.2) create a freestyle job click Add build step click Trigger/call builds on [sic] other projects click Add ParameterFactories [sic] click For every matching file, invoke one build click next to File Name In Child Projects See a blank help box. Expected results: there should be help. The relevant empty file is: https://github.com/jenkinsci/parameterized-trigger-plugin/blob/55f8d5b10f00164a090972f8af89794acddf870b/src/main/resources/hudson/plugins/parameterizedtrigger/matrix/MatrixSubsetBuildParameters/help-filter.html#L20 I'm not going to fix this right away. Filing it because I found it while reading the help for everything and I'm punting as I'm not quite sure about the fix.
[JIRA] (JENKINS-57974) If you do need to escape '$', use '$'.
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-57974 If you do need to escape '$', use '$'. Issue Type: Task Assignee: Unassigned Components: parameterized-trigger-plugin Created: 2019-06-11 20:18 Priority: Minor Reporter: Josh Soref install the Jenkins Parameterized Trigger plugin (2.35.2) create a freestyle job click Add build step click Trigger/call builds on [sic] other projects click Add Parameters click Restrict matrix execution to a subset click read the bottom of the help: However, Jenkins variable expansion leaves undefined variables as-is, so most of the time your Groovy string line _expression_ syntax will survive the expansion, get passed to Groovy as-is, and work as expected. If you do need to escape '$', use '$'. Expected results: the two things should presumably be different. The relevant code is: https://github.com/jenkinsci/parameterized-trigger-plugin/blob/55f8d5b10f00164a090972f8af89794acddf870b/src/main/resources/hudson/plugins/parameterizedtrigger/matrix/MatrixSubsetBuildParameters/help-filter.html#L20
[JIRA] (JENKINS-57968) Set the source root for Warnings-ng plugin
Title: Message Title Ulli Hafner closed an issue as Duplicate Jenkins / JENKINS-57968 Set the source root for Warnings-ng plugin Change By: Ulli Hafner Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199952.1560274992000.25506.1560284100161%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57968) Set the source root for Warnings-ng plugin
Title: Message Title Ulli Hafner resolved as Duplicate Jenkins / JENKINS-57968 Set the source root for Warnings-ng plugin Change By: Ulli Hafner Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199952.1560274992000.25504.1560284040240%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48930) Add new way to publish shared libraries
Title: Message Title Jesse Glick resolved as Won't Do Thanks! Jenkins / JENKINS-48930 Add new way to publish shared libraries Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187735.1515943372000.25501.1560283980330%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38257) Feature to define non-actual user
Title: Message Title Jesse Glick resolved as Duplicate a composite security realm Possibly, but see discussion in JENKINS-15063. Jenkins / JENKINS-38257 Feature to define non-actual user Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174420.1473972094000.25497.1560283800301%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15063) support for multiple security realms with failover
Title: Message Title Jesse Glick commented on JENKINS-15063 Re: support for multiple security realms with failover which I recall being the case Examples like this or this are not hard to find. So making the realm proxyable would at a minimum require some logic changes to various popular realm plugins, and perhaps require new core APIs to permit adequate context / state to be “threaded” through various interfaces rather than grabbing it from a global singleton. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.145783.1346946053000.25443.1560283741161%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47827) Support passing a user/uid into containerTemplate
Title: Message Title Cochise Ruhulessin updated JENKINS-47827 Jenkins / JENKINS-47827 Support passing a user/uid into containerTemplate Change By: Cochise Ruhulessin Resolution: Won't Do Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186329.1509818749000.25427.1560282241319%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47827) Support passing a user/uid into containerTemplate
Title: Message Title Cochise Ruhulessin updated JENKINS-47827 Jenkins / JENKINS-47827 Support passing a user/uid into containerTemplate Change By: Cochise Ruhulessin Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186329.1509818749000.25430.1560282241355%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47827) Support passing a user/uid into containerTemplate
Title: Message Title Cochise Ruhulessin updated an issue Jenkins / JENKINS-47827 Support passing a user/uid into containerTemplate Change By: Cochise Ruhulessin Comment: The suggested solution does not work for Pod templates that are created through Groovy init scripts. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186329.1509818749000.25408.1560282120442%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47827) Support passing a user/uid into containerTemplate
Title: Message Title Cochise Ruhulessin commented on JENKINS-47827 Re: Support passing a user/uid into containerTemplate The suggested solution does not work for Pod templates that are created through Groovy init scripts. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186329.1509818749000.25397.1560282060334%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57929) BlueOcean steps do not appear green when they were successful when using parallel stages while still running
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-57929 BlueOcean steps do not appear green when they were successful when using parallel stages while still running Change By: Devin Nusbaum Attachment: Screen Shot 2019-06-11 at 15.25.25.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199903.1560145735000.25392.1560281520300%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57929) BlueOcean steps do not appear green when they were successful when using parallel stages while still running
Title: Message Title
Devin Nusbaum commented on JENKINS-57929
Re: BlueOcean steps do not appear green when they were successful when using parallel stages while still running
Spent a bit of time trying to reproduce this in case it was related to my changes for JENKINS-39203, but was not able to do so. Here is the Pipeline I was using:
pipeline {
agent any
stages {
stage('before') {
steps {
echo 'before'
}
}
stage("parallel") {
parallel {
stage("simple") {
stages {
stage ("simple-inner?") {
steps {
echo 'simple-inner?'
sleep 1
}
}
}
}
stage("sequential") {
stages {
stage("sequential-1") {
steps {
echo 'sequential-1'
sleep 1
}
}
stage("sequential-2") {
steps {
echo 'sequential-2'
sleep 1
}
}
}
}
}
}
stage('after') {
parallel {
stage('after-1') {
steps {
sleep 60
}
}
stage('after-2') {
steps {
echo 'after-2'
}
}
}
}
}
}
And here is what it looked like: Jon B If you can figure out how to reproduce the problem with tweaks to my basic Pipeline here, that would be helpful. From what I can tell, it looks like what you are reporting might be a dupe of JENKINS-53816, see in particular this comment which notes some problems in this area in Blue Ocean 1.17.0.
Add Comment
[JIRA] (JENKINS-57973) Switch Plugin Installation Manager Tool to Java Util Logging
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57973 Switch Plugin Installation Manager Tool to Java Util Logging Issue Type: Improvement Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-11 18:24 Priority: Minor Reporter: Oleg Nenashev Currently the tool uses System out for logging. It would be great to switch to Java Util Logging so that the tool can be used as a library in Jenkins components Add Comment This message was sent by
[JIRA] (JENKINS-57972) Integrate the Plugin Manager tool into the Jenkins Docker image
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57972 Integrate the Plugin Manager tool into the Jenkins Docker image Issue Type: Improvement Assignee: Carlos Sanchez Components: docker, plugin-installation-manager-tool Created: 2019-06-11 18:22 Priority: Minor Reporter: Oleg Nenashev Once the first version is ready to be released, it would be great to add it to https://github.com/jenkinsci/docker and update install-plugins.sh to use the new tool. Acceptance criteria: Plugin Manager tool is released (as alpha?) Plugin Manager tool is added to the Docker distribution Scripts are updated to invoke the tool during execution. All features are retained so that the tool is fully compatible. Documentation is updated to reference the tool Add Comment
[JIRA] (JENKINS-57971) Add user documentation to the Plugin Installation Manager tool
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57971 Add user documentation to the Plugin Installation Manager tool Issue Type: Improvement Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-11 18:18 Priority: Minor Reporter: Oleg Nenashev Currently there is no dicumentation in the repository. It would be great to move some docs from https://github.com/jenkinsci/docker#preinstalling-plugins so that users can access these docs while looking at the repo Add Comment
[JIRA] (JENKINS-57970) Add checks for available updates and known security issues in the installation script
Title: Message Title
Oleg Nenashev created an issue
Jenkins / JENKINS-57970
Add checks for available updates and known security issues in the installation script
Issue Type:
Improvement
Assignee:
Natasha Stopa
Components:
plugin-installation-manager-tool
Created:
2019-06-11 18:14
Priority:
Minor
Reporter:
Oleg Nenashev
See https://github.com/jenkinsci/docker/pull/668 I am using the base Dockerfile to build my own Jenkins instances, and it's difficult to update {{plugins.txt}}manually. Every time you need to launch the update center and then to go through the updates list and to update the file. And then rebuild the image until the UI is fine... In order to simplify the use-case, I have added printing of available updates after the build (see availableUpdates). It will use the same update center as the installation logic, so the output will show only those updates which are actually applicable. It would be great to have this functionality supported in the plugin management tool OOTB
Add Comment
[JIRA] (JENKINS-57969) Add License to the Plugin Installation Manager tool
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57969 Add License to the Plugin Installation Manager tool Issue Type: Improvement Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-11 18:10 Priority: Minor Reporter: Oleg Nenashev Explicit License definition is important for some users. It would be great to have it in the repository. Could you please add one (e.g. MIT License)? Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-56305) Need some help with init scripts on this plugin
Title: Message Title
sigur edited a comment on JENKINS-56305
Re: Need some help with init scripts on this plugin
Is there a simple way to store the created configs in the jobs config folder? I'm only able to store then in the global config folder {code :java }configFileProvider([configFile(fileId: 'DEFAULT_JSON_CONFIG', variable: 'default_config_content')]) {def instance = Jenkins.getInstance() def provider = instance.getExtensionList('org.jenkinsci.plugins.configfiles.json.JsonConfig$JsonConfigProvider')[0] def config = new org.jenkinsci.plugins.configfiles.json.JsonConfig("${BRANCH_NAME}_config", "Config for ${BRANCH_NAME}", "Branch config ${BRANCH_NAME}", "$default_config_content") provider.save(config) }{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197885.155124611.25377.1560276611683%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57947) Managing credentials in JCasC yaml
Title: Message Title Parichay Barpanda commented on JENKINS-57947 Re: Managing credentials in JCasC yaml See https://groups.google.com/forum/#!topic/jenkinsci-dev/hWyPi2QBU4Q Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199924.1560215713000.25374.1560276540042%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56305) Need some help with init scripts on this plugin
Title: Message Title
sigur commented on JENKINS-56305
Re: Need some help with init scripts on this plugin
Is there a simple way to store the created configs in the jobs config folder? I'm only able to store then in the global config folder
configFileProvider([configFile(fileId: 'DEFAULT_JSON_CONFIG', variable: 'default_config_content')]) {
def instance = Jenkins.getInstance()
def provider = instance.getExtensionList('org.jenkinsci.plugins.configfiles.json.JsonConfig$JsonConfigProvider')[0]
def config = new org.jenkinsci.plugins.configfiles.json.JsonConfig("${BRANCH_NAME}_config", "Config for ${BRANCH_NAME}", "Branch config ${BRANCH_NAME}", "$default_config_content")
provider.save(config)
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197885.155124611.25372.1560276480365%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57968) Set the source root for Warnings-ng plugin
Title: Message Title Henry Borchers updated an issue Jenkins / JENKINS-57968 Set the source root for Warnings-ng plugin Change By: Henry Borchers Summary: set Set the source root for Warnings-ng plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199952.1560274992000.25369.1560275580283%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57968) set the source root for Warnings-ng plugin
Title: Message Title Henry Borchers updated an issue Jenkins / JENKINS-57968 set the source root for Warnings-ng plugin Change By: Henry Borchers Summary: set the source rootfor Warnings-ng plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199952.1560274992000.25367.1560275580261%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57713) Cloud agent provisioning errors due to Remoting behaviour change
Title: Message Title Jeff Thompson commented on JENKINS-57713 Re: Cloud agent provisioning errors due to Remoting behaviour change It's not clear to me how to preserve the sequencing behavior describes and also achieve the sequencing change Javier Delgado desired in #JENKINS-46515. Different scenarios or implementations rely on or are impacted by the sequence differently. There might be some way to add a flag to invoke the new behavior, while not impacting the existing but I'm not sure if that could meet the needs. Unfortunately, the sequencing isn't well-specified or clarified. I'll reference this Jira issue to remove the changes for #JENKINS-46515 / jenkinsci/remoting#193 from the Remoting master branch. Once done, I'll release a new Remoting version with the other changes. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199655.1559046575000.25361.1560275460272%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57968) set the source root
Title: Message Title Henry Borchers created an issue Jenkins / JENKINS-57968 set the source root Issue Type: New Feature Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-06-11 17:43 Priority: Minor Reporter: Henry Borchers My pipelines generate my builds out of source which has provide me with a problem with any warning messages that use relative paths for the file names. warnings-ng is able to parse the warning messages beautifully but it's unable to link it back to the scm directory or source root. For reference, my jenkins workspace looks a little like this... / /scm/ /scm/.git/ /build/ /reports/ /dist/ /logs/ What I would love is to use is something like this is my pipeline recordIssues( tools: [myPy(name: 'MyPy', pattern: 'logs/mypy.log')], sourcePath: "scm" ) I love this plugin. it's saved me from so much trouble
[JIRA] (JENKINS-46515) Launcher will retry connections forever under some irrecoverable status
Title: Message Title Jeff Thompson commented on JENKINS-46515 Re: Launcher will retry connections forever under some irrecoverable status The Remoting release (3.30) containing this change was reverted from Jenkins core because it introduced a regression in some other scenarios, particularly involving cloud agents. I'm going to revert it from the Remoting master branch and create a new release without it and containing the changes included in 3.30. See #JENKINS-57759 and #JENKINS-57713 Javier Delgado (or someone else), if you are interested you can re-open this issue or create a similar one and propose a new approach that resolves the issues described here and maintains sequence needed by the other scenarios. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184832.1503993829000.25355.1560274680274%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57967) vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher
Title: Message Title Nick Jones updated an issue Jenkins / JENKINS-57967 vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher Change By: Nick Jones Component/s: ssh-slaves-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199950.1560271877000.25334.1560271980171%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57967) vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher
Title: Message Title Nick Jones created an issue Jenkins / JENKINS-57967 vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 2019-06-11 16:51 Environment: vSphere Cloud 2.19, SSH Slaves 1.30.0 Priority: Blocker Reporter: Nick Jones Having upgraded to SSH Slaves 1.30, our vSphere Cloud plugin no longer works – agent nodes fail to provision, and a message like the following gets logged: Unexpected exception encountered while provisioning agent agent1 java.lang.NoSuchMethodError: hudson.plugins.sshslaves.SSHLauncher.(Ljava/lang/String;ILjava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/Integer;Ljava/lang/Integer;Ljava/lang/Integer;)V at org.jenkinsci.plugins.vSphereCloudSlaveTemplate.determineLauncher(vSphereCloudSlaveTemplate.java:481) at org.jenkinsci.plugins.vSphereCloudSlaveTemplate.provision(vSphereCloudSlaveTemplate.java:451) at org.jenkinsci.plugins.vSphereCloudSlaveTemplate.provision(vSphereCloudSlaveTemplate.java:396) at org.jenkinsci.plugins.vSphereCloud$VSpherePlannedNode.provisionNewNode(vSphereCloud.java:534) at org.jenkinsci.plugins.vSphereCloud$VSpherePlannedNode.access$100(vSphereCloud.java:496) at org.jenkinsci.plugins.vSphereCloud$VSpherePlannedNode$1.call(vSphereCloud.java:510) at org.jenkinsci.plugins.vSphereCloud$VSpherePlannedNode$1.call(vSphereCloud.java:506) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at
[JIRA] (JENKINS-57966) Multibranch Pipeline Indexing fails with ClassCastException in svn
Title: Message Title
Daniel Eichert updated an issue
Jenkins / JENKINS-57966
Multibranch Pipeline Indexing fails with ClassCastException in svn
Change By:
Daniel Eichert
When I was indexing my jobs today I got an ClassCastException, the result of this mistake is hat my MultiBranch Pipeline job cannot find any branches and therefore the folder stays empty. This is a critical issue for me. I would appreciate any help. Here is my error message:{code:java}ERROR: [Tue Jun 11 18:16:54 CEST 2019] Could not fetch branches from source 78aad773-0322-49fb-99da-95df2966fe5bjava.lang.ClassCastException: [[J cannot be cast to org.mapdb.BTreeMap$BNodeat org.mapdb.BTreeMap.put2(BTreeMap.java:663)at org.mapdb.BTreeMap.put(BTreeMap.java:643)at org.mapdb.DB.catPut(DB.java:105)at org.mapdb.DB.createHashMap(DB.java:443)at org.mapdb.DB$HTreeMapMaker.make(DB.java:216)at org.mapdb.DB.getHashMap(DB.java:356)at org.mapdb.DB.getHashMap(DB.java:329)at jenkins.scm.impl.subversion.SVNRepositoryView.(SVNRepositoryView.java:115)at jenkins.scm.impl.subversion.SubversionSCMSource.openSession(SubversionSCMSource.java:336)at jenkins.scm.impl.subversion.SubversionSCMSource.retrieve(SubversionSCMSource.java:240) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373)at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283)at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:634)at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277)at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164)at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1025)at hudson.model.ResourceController.execute(ResourceController.java:97)at hudson.model.Executor.run(Executor.java:429)[Tue Jun 11 18:16:54 CEST 2019] Finished branch indexing. Indexing took 74 msFATAL: Failed to recompute children of truemdmBuildReports » testjava.lang.ClassCastException: [[J cannot be cast to org.mapdb.BTreeMap$BNodeat org.mapdb.BTreeMap.put2(BTreeMap.java:663)at org.mapdb.BTreeMap.put(BTreeMap.java:643)at org.mapdb.DB.catPut(DB.java:105)at org.mapdb.DB.createHashMap(DB.java:443)at org.mapdb.DB$HTreeMapMaker.make(DB.java:216)at org.mapdb.DB.getHashMap(DB.java:356)at org.mapdb.DB.getHashMap(DB.java:329)at jenkins.scm.impl.subversion.SVNRepositoryView.(SVNRepositoryView.java:115)at jenkins.scm.impl.subversion.SubversionSCMSource.openSession(SubversionSCMSource.java:336)at jenkins.scm.impl.subversion.SubversionSCMSource.retrieve(SubversionSCMSource.java:240) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373)at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283)at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:634) at
[JIRA] (JENKINS-57966) Multibranch Pipeline Indexing fails with ClassCastException in svn
Title: Message Title Daniel Eichert created an issue Jenkins / JENKINS-57966 Multibranch Pipeline Indexing fails with ClassCastException in svn Issue Type: Bug Assignee: rsandell Components: multi-branch-project-plugin (not Pipeline), pipeline Created: 2019-06-11 16:42 Environment: Jenkins is running on a RHEL 7 Jenkins Version is 2.180 Labels: multibranch pipeline branch Priority: Critical Reporter: Daniel Eichert When I was indexing my jobs today I got an ClassCastException, the result of this mistake is hat my MultiBranch Pipeline job cannot find any branches and therefore the folder stays empty. This is a critical issue for me. I would appreciate any help. Here is my error message: ERROR: [Tue Jun 11 18:16:54 CEST 2019] Could not fetch branches from source 78aad773-0322-49fb-99da-95df2966fe5b java.lang.ClassCastException: [[J cannot be cast to org.mapdb.BTreeMap$BNode at org.mapdb.BTreeMap.put2(BTreeMap.java:663) at org.mapdb.BTreeMap.put(BTreeMap.java:643) at org.mapdb.DB.catPut(DB.java:105) at org.mapdb.DB.createHashMap(DB.java:443) at org.mapdb.DB$HTreeMapMaker.make(DB.java:216) at org.mapdb.DB.getHashMap(DB.java:356) at org.mapdb.DB.getHashMap(DB.java:329) at jenkins.scm.impl.subversion.SVNRepositoryView.(SVNRepositoryView.java:115) at
[JIRA] (JENKINS-57833) All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log
Title: Message Title Cyrille Le Clerc commented on JENKINS-57833 Re: All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log Markus Till can you please search for any xerces jar file in the plugins that you have loaded in your instance. It is typically outdated versions of xerces that cause issues with the DocumentBuilderFactory. Can you on the master run "find -iname "xerces"" under "JENKINS_HOME/plugins". It looks like $ cd /plugins # verify that we are in the right folder verifying the number of jar files we found $ find -iname "*.jar" | wc - $ find -iname "*xerces*.jar" Result typically looks like: $ find -iname "*.jar" | wc -l 1262 $ find -iname "xerces*.jar" ./analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar $ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199790.1559631863000.25312.1560269460187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38257) Feature to define non-actual user
Title: Message Title Kalle Niemitalo commented on JENKINS-38257 Re: Feature to define non-actual user Jenkins 2.176.1 LTS now includes JENKINS-24513, which warns about builds running as SYSTEM. But virtual users are difficult to define when Jenkins is using SAML Plugin against Microsoft's AD FS. I wonder if, instead of the "significant changes" in JENKINS-32596, this could be implemented: as a security realm wrapper plugin that lets the admin select an inner security realm for the real users and define some additional virtual users, or as a composite security realm plugin that lets the admin select two or more inner security realms, one of which could then be Jenkins’ own user database. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174420.1473972094000.25310.1560269040321%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57965) Clicking "Save" on node config throws java.lang.NullPointerException
Title: Message Title Adam Romano updated an issue Jenkins / JENKINS-57965 Clicking "Save" on node config throws java.lang.NullPointerException Change By: Adam Romano Labels: regression Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199948.1560268008000.25298.1560268260233%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57955) Clean and sync incorrectly follows junction/directory symlinks on Windows
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57955 Clean and sync incorrectly follows junction/directory symlinks on Windows Change By: Karl Wirth Summary: p4-plugin Clean and sync incorrectly follows junction/directory symlinks on Windows Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.25297.1560268260218%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36111) p4 plugin cleanup behavior wrong with AutoCleanImpl and linked directory
Title: Message Title Karl Wirth closed an issue as Fixed Closing in favour of JENKINS-57955. Jenkins / JENKINS-36111 p4 plugin cleanup behavior wrong with AutoCleanImpl and linked directory Change By: Karl Wirth Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172074.1466510323000.25295.1560268200522%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36111) p4 plugin cleanup behavior wrong with AutoCleanImpl and linked directory
Title: Message Title Karl Wirth commented on JENKINS-36111 Re: p4 plugin cleanup behavior wrong with AutoCleanImpl and linked directory Newer case has come in on this topic - JENKINS-57955. Am closing this one in favour of new case with repro steps. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172074.1466510323000.25292.1560268140126%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57955) p4-plugin
Title: Message Title Karl Wirth assigned an issue to Unassigned Jenkins / JENKINS-57955 p4-plugin Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.25289.1560268080206%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57955) p4-plugin
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57955 p4-plugin Change By: Karl Wirth Environment: Windows Host and Agent, Jenkins ver. 2.176.1 (Pipeline in SCM) P4-Plugin 1.10.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.25287.1560268080182%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57965) Clicking "Save" on node config throws java.lang.NullPointerException
Title: Message Title Adam Romano created an issue Jenkins / JENKINS-57965 Clicking "Save" on node config throws java.lang.NullPointerException Issue Type: Bug Assignee: Unassigned Attachments: Screenshot 2019-06-11 at 15.24.52.png, Screenshot 2019-06-11 at 15.25.03.png Components: core Created: 2019-06-11 15:46 Environment: Jenkins 2.164.1 Priority: Blocker Reporter: Adam Romano On the Build Executor Status list, select a node, open the dropdown, change something (or change nothing, same result) and click save. a j ava.lang.NullPointerException is thrown. Add Comment
[JIRA] (JENKINS-57955) p4-plugin
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57955 p4-plugin Change By: Karl Wirth Labels: windows P4_B Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.25284.1560268020238%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57955) p4-plugin
Title: Message Title
Karl Wirth commented on JENKINS-57955
Re: p4-plugin
Hi Kieron Kierzo, I have been able to reproduce this behavior. Changing it to 'mklink /D' does not solve the problem. If it works for you, using 'sync only' is one workaround. Would another be to run 'rmdir' on the junction before the end of the job then recreate it next time? Reproduction steps: 1. Create a file on the build machine called 'C:\filestore\Jenkins\temp\symlink_target1\file1'. 2. Add a file to '//depot/win_symlink/...'. 3. Create a pipeline job with the following config:
pipeline {
agent { label 'Windows10' }
stages {
stage("Repro") {
steps {
script {
checkout perforce(credential: 'JenkinsMaster', populate: forceClean(have: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: false), workspace: manualSpec(charset: 'none', cleanup: false, name: 'jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}', pinHost: false, spec: clientSpec(allwrite: false, backup: true, changeView: '', clobber: true, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, serverID: '', streamName: '', type: 'WRITABLE', view: '//depot/win_symlink/...
bat 'dir /b /s'
bat 'mklink /J "linkeddir" "C:\\filestore\\Jenkins\\temp\\symlink_target1"'
bat 'dir /b /s'
}
}
}
}
}
4. Build the job. 5. Build the job again. Result seen - 'C:\filestore\Jenkins\temp\symlink_target1\file1' is deleted. Expected result - 'C:\filestore\Jenkins\temp\symlink_target1\file1' is not deleted.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are
[JIRA] (JENKINS-48430) Provided config file is sometimes not complete
Title: Message Title Dominik Bartholdi commented on JENKINS-48430 Re: Provided config file is sometimes not complete I would very much like to fix this, but as stated previously, I'm not able to reproduce the issue in my env. I have an idea for a fix, but would need someone to try it before I ship it. Anyone willing to help/test out? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187028.1512645914000.25261.1560266880250%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45228) Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command
Title: Message Title Geoffroy Jabouley edited a comment on JENKINS-45228 Re: Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command Helloalso facing this issue in some cases where files where modified/added into source branch of PR.Any idea when/if LFS credentials support will be added to the merge portion of the git plugin? Maybe at leat least providing some implementation guidance for a future contributionBR Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183359.1498813755000.25250.1560266641018%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57964) Documentation unclear for node() in scripted pipeline
Title: Message Title leemeador created an issue Jenkins / JENKINS-57964 Documentation unclear for node() in scripted pipeline Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2019-06-11 15:23 Environment: n/a Labels: documentation scripted node Priority: Minor Reporter: leemeador On this page in the documentation, it describes node(). https://jenkins.io/doc/pipeline/steps/workflow-durable-task-step/#node-allocate-node Some examples of using the operators have no quotes. Some have quotes around the individual components (eg. 'linux' || 'osx'). None have the full correct syntax (eg. 'linux || osx'). If you use the form with the quotes around the individual components, you get an error saying that node() does not allow a boolean argument. Of course, we are used to the error messaages occasionally having no useful information. I suggest changing the documentation to NOT include the example with quotes around the components. (It says exactly this: For example, "osx (10.11)" || "Windows Server") I also suggest putting something up at the top that shows a full example with an _expression_ as well as a single agent's label.
[JIRA] (JENKINS-57922) Ability to specify output directory for translation-tool.pl
Title: Message Title Mustafa Ulu assigned an issue to Mustafa Ulu Jenkins / JENKINS-57922 Ability to specify output directory for translation-tool.pl Change By: Mustafa Ulu Assignee: Mustafa Ulu Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199895.156010731.25232.1560266520106%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57963) Failed to connect to repository
Title: Message Title louis Catarino updated an issue Jenkins / JENKINS-57963 Failed to connect to repository Change By: louis Catarino Attachment: image-2019-06-11-16-59-14-007.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199946.1560265396000.25229.1560265500135%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57963) Failed to connect to repository
Title: Message Title louis Catarino updated an issue Jenkins / JENKINS-57963 Failed to connect to repository Change By: louis Catarino hey , Could you help me please :D ? !image-2019-06-11-17-02-59-844.png!!image-2019-06-11-17- 04-52-764.png!!image-2019-06-11-17- 03-58-044.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199946.1560265396000.25231.1560265500200%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57963) Failed to connect to repository
Title: Message Title louis Catarino updated an issue Jenkins / JENKINS-57963 Failed to connect to repository Change By: louis Catarino Attachment: image-2019-06-11-17-04-52-764.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199946.1560265396000.25230.1560265500186%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57963) Failed to connect to repository
Title: Message Title louis Catarino created an issue Jenkins / JENKINS-57963 Failed to connect to repository Issue Type: Bug Assignee: Unassigned Attachments: image-2019-06-11-16-59-14-007.png, image-2019-06-11-17-02-59-844.png, image-2019-06-11-17-03-58-044.png Components: _unsorted Created: 2019-06-11 15:03 Priority: Blocker Reporter: louis Catarino hey , Could you help me please ? Add Comment
[JIRA] (JENKINS-57963) Failed to connect to repository
Title: Message Title louis Catarino updated an issue Jenkins / JENKINS-57963 Failed to connect to repository Change By: louis Catarino Attachment: image-2019-06-11-16-59-20-387.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199946.1560265396000.25225.1560265440312%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57963) Failed to connect to repository
Title: Message Title louis Catarino updated an issue Jenkins / JENKINS-57963 Failed to connect to repository Change By: louis Catarino Attachment: image-2019-06-11-17-03-58-044.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199946.1560265396000.25227.1560265440341%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57963) Failed to connect to repository
Title: Message Title louis Catarino updated an issue Jenkins / JENKINS-57963 Failed to connect to repository Change By: louis Catarino hey , Could you help me please :D ? !image-2019-06-11-17-02-59-844.png! !image-2019-06-11-17-03-58-044.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199946.1560265396000.25228.1560265440352%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57963) Failed to connect to repository
Title: Message Title louis Catarino updated an issue Jenkins / JENKINS-57963 Failed to connect to repository Change By: louis Catarino hey , Could you help me please :D ? !image-2019-06-11-16-59-20-387.png! !image-2019-06-11-17-02-59-844.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199946.1560265396000.25226.1560265440327%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-5256) Cannot save changes in node configuration
Title: Message Title Adam Romano commented on JENKINS-5256 Re: Cannot save changes in node configuration I'm still having this issue Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.135345.1263363246000.25221.1560265020373%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57962) Jenkins log is flooded with 'You must override the newer overload of annotate from org.jenkinsci.plugins.issuelink.IssueLinkChangeLogAnnotator'
Title: Message Title Christopher Crowe created an issue Jenkins / JENKINS-57962 Jenkins log is flooded with 'You must override the newer overload of annotate from org.jenkinsci.plugins.issuelink.IssueLinkChangeLogAnnotator' Issue Type: Bug Assignee: Emilio Escobar Components: changelog-history-plugin Created: 2019-06-11 14:50 Environment: linux - centos 7 Jenkins 2.164.3 Labels: changelog annotate Priority: Minor Reporter: Christopher Crowe Log output (https://jenkins/log/all) the following warning is spammed: ... Jun 11, 2019 10:39:49 AM WARNING hudson.scm.ChangeLogAnnotator annotate You must override the newer overload of annotate from org.jenkinsci.plugins.issuelink.IssueLinkChangeLogAnnotator Jun 11, 2019 10:39:49 AM WARNING hudson.scm.ChangeLogAnnotator annotate You must override the newer overload of annotate from org.jenkinsci.plugins.issuelink.IssueLinkChangeLogAnnotator Jun 11, 2019 10:39:49 AM WARNING hudson.scm.ChangeLogAnnotator annotate You must override the newer overload of annotate from org.jenkinsci.plugins.issuelink.IssueLinkChangeLogAnnotator Jun 11, 2019 10:39:49 AM WARNING hudson.scm.ChangeLogAnnotator annotate You must override the newer overload of annotate from org.jenkinsci.plugins.issuelink.IssueLinkChangeLogAnnotator Jun 11, 2019 10:39:49 AM WARNING hudson.scm.ChangeLogAnnotator annotate You must override the newer overload of annotate from org.jenkinsci.plugins.issuelink.IssueLinkChangeLogAnnotator Jun 11, 2019 10:39:49 AM WARNING hudson.scm.ChangeLogAnnotator annotate You must override the newer overload of annotate from
[JIRA] (JENKINS-57669) Write K8s spec for Zookeeper and Kafka nodes
Title: Message Title Long Nguyen updated JENKINS-57669 Jenkins / JENKINS-57669 Write K8s spec for Zookeeper and Kafka nodes Change By: Long Nguyen Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199602.1558718399000.25209.1560264420187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57667) Launching Zookeeper and Kafka in K8s UI
Title: Message Title Long Nguyen updated JENKINS-57667 Jenkins / JENKINS-57667 Launching Zookeeper and Kafka in K8s UI Change By: Long Nguyen Status: In Review Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199600.155871834.25210.1560264420346%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45318) Add dependancy on net.i2p.crypto inside sshd module
Title: Message Title Stefan Spieker closed an issue as Fixed Already merged as far as I can see: https://github.com/jenkinsci/sshd-module/pull/25 Jenkins / JENKINS-45318 Add dependancy on net.i2p.crypto inside sshd module Change By: Stefan Spieker Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183458.1499267159000.25206.1560264180474%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57956) Cancel outdated jobs not working properly with multiple jobs ont the same pull request
Title: Message Title Jakub Bochenski commented on JENKINS-57956 Re: Cancel outdated jobs not working properly with multiple jobs ont the same pull request Bartlomiej Poleszak the repository you mention is abandoned and outside of control of the jenkins project. Please feel free to re-submit the PR to the official repository at https://github.com/jenkinsci/stash-pullrequest-builder-plugin This functionality has been moved to StashRepository. We also require some basic unit test coverage for new changes Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199937.1560252872000.25204.1560263880531%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49183) Retry in Declarative options passes stage but causes false fail in pipeline
Title: Message Title Devin Nusbaum resolved as Duplicate Jenkins / JENKINS-49183 Retry in Declarative options passes stage but causes false fail in pipeline Change By: Devin Nusbaum Status: Open Resolved Resolution: Duplicate Released As: pipeline-model-definition 1.3.8 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188020.1516956301000.25180.1560263708721%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
