[JIRA] (JENKINS-41871) class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method!
Title: Message Title Denis Shvedchenko edited a comment on JENKINS-41871 Re: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method! if it implement convert, so issue would be solved with assumption in first comment :D Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41871) class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method!
Title: Message Title Denis Shvedchenko commented on JENKINS-41871 Re: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method! if it implement convert, so issue would be solved with assumption in first comment Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41871) class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method!
Title: Message Title Dominik Bartholdi commented on JENKINS-41871 Re: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method! I will provide a solution to create new configs dynamically. Beside this, your last comment is about the best hint I got about an other issue: I did not know that emailext is also using the config-file-provider plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41871) class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method!
Title: Message Title Dominik Bartholdi started work on JENKINS-41871 Change By: Dominik Bartholdi Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41872) jenkins anonymous had overall read authorize can approve pipeline project stave view process
Title: Message Title hans wang created an issue Jenkins / JENKINS-41872 jenkins anonymous had overall read authorize can approve pipeline project stave view process Issue Type: Bug Assignee: Unassigned Components: authorize-project-plugin Created: 2017/Feb/09 7:55 AM Environment: jenkins 2.19.4 Matrix Project Plugin 1.7.1 Matrix Authorization Strategy Plugin 1.4 Script Security Plugin 1 .25 Labels: jenkins Priority: Major Reporter: hans wang hi, i set anonymous had only overall read permission using Project Matrix Authorization Strategy, and setting it in pipeline project config as only read permission for anonymous. logout and open project dashboard stage view, it still can execute the pipeline approve process or abort? The anonymous just has "read" permission for this project. sorry, my english is not good enough.
[JIRA] (JENKINS-41871) class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method!
Title: Message Title Denis Shvedchenko commented on JENKINS-41871 Re: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method! hudson.plugins.emailext.GroovyTemplateConfig does not override convert, also convert is deprecated, so I need another solution Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40799) Swarm plugin changelog has not been updated for 3 releases
Title: Message Title Peter Jönsson commented on JENKINS-40799 Re: Swarm plugin changelog has not been updated for 3 releases Yes, however right now I need to resolve another problem. for some reason the uber-jar for the swarm client does not contain all the neccessary libraries, so it does not start properly. I hope to resolve this real soon. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38484) Using test stability publisher in a Pipeline build will hang
Title: Message Title Sean Flanigan commented on JENKINS-38484 Re: Using test stability publisher in a Pipeline build will hang kutzi It might take me a little while to finish JENKINS-33168, so in the meantime I'd like to go ahead and release this, unless you want to do it. Should I request to become maintainer, or to become a second maintainer? Or is it possible for me to make a release without being considered a maintainer? I see that there are no developers currently listed here (probably because you hadn't made a release for a while when they created the yml-based system): https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-test-stability.yml Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41871) class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method!
Title: Message Title Denis Shvedchenko commented on JENKINS-41871 Re: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method! I 've added my current version of scirpt, that is working with previous version. I hope adding provider.convert(Config) will solve this issue with 2.15 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41871) class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method!
Title: Message Title Denis Shvedchenko updated an issue Jenkins / JENKINS-41871 class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method! Change By: Denis Shvedchenko Attachment: 0040_managed_config.groovy Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41303) Managed Files does not list previous config file after update
Title: Message Title Dominik Bartholdi commented on JENKINS-41303 Re: Managed Files does not list previous config file after update sorry, I think I was not clear enough about the new ticket - the issue with the "class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method!" will not be solved by this (this is caused by the wrong usage of the NEW api) - but I'm working on a solution to allow you dynamic creation of a config via provider. So the important part for the new ticket would be the script you use. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41303) Managed Files does not list previous config file after update
Title: Message Title Denis Shvedchenko commented on JENKINS-41303 Re: Managed Files does not list previous config file after update and will try to use provider.convert(Config) to get correct Config implementation provider Specific Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41303) Managed Files does not list previous config file after update
Title: Message Title Denis Shvedchenko commented on JENKINS-41303 Re: Managed Files does not list previous config file after update I use ConfigProvider provider = ConfigProvider.getByIdOrNull(providerId); to construct ConfigProviders by Id String Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41303) Managed Files does not list previous config file after update
Title: Message Title Denis Shvedchenko commented on JENKINS-41303 Re: Managed Files does not list previous config file after update created JENKINS-41871 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41871) class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method!
Title: Message Title Denis Shvedchenko created an issue Jenkins / JENKINS-41871 class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method! Issue Type: Bug Assignee: Dominik Bartholdi Components: config-file-provider-plugin Created: 2017/Feb/09 7:26 AM Environment: Using all latest versions : 2.15.5. Jenkins : 2.32.2 Priority: Minor Reporter: Denis Shvedchenko Using all latest versions : 2.15.5. Every time visiting Global Config Files: log has exception: WARNING: Caught exception evaluating: it.groupedConfigs in /configfiles/index. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Caused by: java.lang.IllegalStateException: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method! at org.jenkinsci.lib.configprovider.model.Config.getDescriptor(Config.java:108) at org.jenkinsci.lib.configprovider.model.Config.getProvider(Config.java:115) at org.jenkinsci.plugins.configfiles.GlobalConfigFiles.getGroupedConfigs(GlobalConfigFiles.java:72) at org.jenkinsci.plugins.configfiles.ConfigFilesManagement.getGroupedConfigs(ConfigFilesManagement.java:112) ... 116 more Do not know why but file : org.jenkinsci.plugins.configfiles.GlobalConfigFiles.xml for newly created items has 5aa81ca6-1ed0--bded-03960d58fc46 MyCustom
[JIRA] (JENKINS-41303) Managed Files does not list previous config file after update
Title: Message Title Dominik Bartholdi commented on JENKINS-41303 Re: Managed Files does not list previous config file after update Denis Shvedchenko can you please create an other issue with your problem and assign it to me? ...I started to work on a solution for this problem Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41315) Jira Trigger not triggering jenkins build jobs
Title: Message Title Wisen Tanasa commented on JENKINS-41315 Re: Jira Trigger not triggering jenkins build jobs Apologies for the late response as I'm not getting any notification as this issue is not assigned to me. It seems like you have a reverse proxy (nginx) that requires an authentication. This might block JIRA webhook to Jenkins and it is not something that the plugin can handle, you might want to check JIRA webhook documentation. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41315) Jira Trigger not triggering jenkins build jobs
Title: Message Title Wisen Tanasa closed an issue as Not A Defect Jenkins / JENKINS-41315 Jira Trigger not triggering jenkins build jobs Change By: Wisen Tanasa Status: Open Closed Assignee: jan kryztoff calma Wisen Tanasa Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41315) Jira Trigger not triggering jenkins build jobs
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-41315 Jira Trigger not triggering jenkins build jobs Change By: Wisen Tanasa Attachment: authentication required.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41779) REGRESSION: Aborted header is not grey
Title: Message Title Josh McDonald commented on JENKINS-41779 Re: REGRESSION: Aborted header is not grey https://github.com/jenkinsci/blueocean-plugin/pull/805 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (TEST-100) How to Launch a openstack windows instance from Jenkins
Title: Message Title Shimith Menon updated an issue test / TEST-100 How to Launch a openstack windows instance from Jenkins Change By: Shimith Menon Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41303) Managed Files does not list previous config file after update
Title: Message Title
Dominik Bartholdi edited a comment on JENKINS-41303
Re: Managed Files does not list previous config file after update
[~dshvedchenko] this will not work anymoreyou need to use the specific class - {{org.jenkinsci.lib.configprovider.model.Config}} is not a valid type (actually, it should and will be be abstract in the future):{noformat} def loadConfigForProvider(provider, configs) {configs.each { spec -> def config = new org.jenkinsci.plugins.configfiles.custom.CustomConfig(spec.id, spec.name, spec.comment, getContentForSpec(spec)) config.setProviderId(provider.getProviderId()); provider.save(config);} }{noformat}you could also create an instance of the new config like this:{noformat} def config = provider.newConfig(spec.id) {noformat}...but the problem here is, that the {{config}} does not have setters for the single fields one more note to be more clear: the class {{org.jenkinsci.plugins.configfiles.custom.CustomConfig}} is a different for each provider - each provider only works with its own implementation of a config class - so the above example only works if the provider is an instance of {{org.jenkinsci.plugins.configfiles.custom.CustomConfig.CustomConfigProvider}}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41735) Investigate acceptability of overall performance
Title: Message Title Ben Walding commented on JENKINS-41735 Re: Investigate acceptability of overall performance Well my theory - it was just the volume of items on the page causing the delay - it didn't seem like favourites were exponentially worse than the normal jobs that were displayed on first load. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40877) Display links to Github PR and Branch on Pipeline Result
Title: Message Title James Dumay assigned an issue to Thorsten Scherler Jenkins / JENKINS-40877 Display links to Github PR and Branch on Pipeline Result Change By: James Dumay Assignee: Thorsten Scherler Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40860) Go to the end of the expanded log
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40860 Go to the end of the expanded log Change By: James Dumay Sprint: release candidate, pannonian , panthalassa Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40202) Action buttons are misaligned
Title: Message Title James Dumay updated JENKINS-40202 Jenkins / JENKINS-40202 Action buttons are misaligned Change By: James Dumay Status: In Review Resolved Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39860) messages column in blue ocean should display if there are more commits
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39860 messages column in blue ocean should display if there are more commits Change By: James Dumay Sprint: tasman, panthalassa post-release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41870) Update duration format
Title: Message Title James Dumay assigned an issue to Josh McDonald Jenkins / JENKINS-41870 Update duration format Change By: James Dumay Assignee: Josh McDonald Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41735) Investigate acceptability of overall performance
Title: Message Title Michael Neale commented on JENKINS-41735 Re: Investigate acceptability of overall performance Of course an Australian (who lives near me) already tried that: http://www.dansdata.com/goop.htm Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41870) Update duration format
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41870 Update duration format Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/09 5:59 AM Priority: Minor Reporter: James Dumay Scope We want to change anywhere in the UI where we display durations like "23 minutes 31 seconds" to the format below. Format: 2d 3h 2m 1s 2d 3h 2m 3hr 2m 1s 3hr 2m 2m 1s 2m 1s < 1s We want to display < 1s for any value less than 1 second Pages Duration column on Activity tab Duration on the Run page Run details duration Step duration
[JIRA] (JENKINS-41735) Investigate acceptability of overall performance
Title: Message Title Michael Neale commented on JENKINS-41735 Re: Investigate acceptability of overall performance From what Ben is saying this seems to get worse with more Favourites (which is odd, I could understand they would be slow to serve, but to render?) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41735) Investigate acceptability of overall performance
Title: Message Title Ben Walding commented on JENKINS-41735 Re: Investigate acceptability of overall performance I use vegemite as thermal paste. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35143) Delete Pipeline Multibranch sub projects
Title: Message Title Andrew Hill commented on JENKINS-35143 Re: Delete Pipeline Multibranch sub projects Thanks - in which case, I was clearly not actually excluding the branch! That was where I was looking, but there was no option to delete the branch. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41851) Downstream job URL in blueocean UI
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41851 Downstream job URL in blueocean UI Change By: James Dumay Sprint: post-release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41869) Pipeline views header and body max width of 1200px
Title: Message Title Brody Maclean created an issue Jenkins / JENKINS-41869 Pipeline views header and body max width of 1200px Issue Type: Story Assignee: Brody Maclean Components: blueocean-plugin Created: 2017/Feb/09 4:59 AM Priority: Minor Reporter: Brody Maclean Constrain the width of the Pipeline views header and body to 1200px, to align with the rest of BO. If logs need to be wider we may role back but want to keep BO tidy and consistent. Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-41779) REGRESSION: Aborted header is not grey
Title: Message Title Josh McDonald commented on JENKINS-41779 Re: REGRESSION: Aborted header is not grey JDL fix: https://github.com/jenkinsci/jenkins-design-language/pull/145 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41572) ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
Title: Message Title T. King closed an issue as Won't Fix No further comments. I'll seek support through other channels. Jenkins / JENKINS-41572 ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins Change By: T. King Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-41542) Run details changes
Title: Message Title Josh McDonald resolved as Fixed Fixed in master Jenkins / JENKINS-41542 Run details changes Change By: Josh McDonald Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41542) Run details changes
Title: Message Title Josh McDonald stopped work on JENKINS-41542 Change By: Josh McDonald Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40924) REGRESSION: Queued freestyle jobs do not show up on Activity
Title: Message Title Keith Zantow updated JENKINS-40924 Jenkins / JENKINS-40924 REGRESSION: Queued freestyle jobs do not show up on Activity Change By: Keith Zantow Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41777) REGRESSION: All indicators have grey glyphs
Title: Message Title Josh McDonald resolved as Fixed No longer an issue Jenkins / JENKINS-41777 REGRESSION: All indicators have grey glyphs Change By: Josh McDonald Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41542) Run details changes
Title: Message Title Josh McDonald commented on JENKINS-41542 Re: Run details changes https://github.com/jenkinsci/blueocean-plugin/pull/804 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41735) Investigate acceptability of overall performance
Title: Message Title Keith Zantow commented on JENKINS-41735 Re: Investigate acceptability of overall performance At first, I thought this was coming from a Raspberry PI... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41735) Investigate acceptability of overall performance
Title: Message Title Michael Neale commented on JENKINS-41735 Re: Investigate acceptability of overall performance Ben Walding have you tried a water cooling CPU? just use a hose. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41735) Investigate acceptability of overall performance
Title: Message Title Ben Walding commented on JENKINS-41735 Re: Investigate acceptability of overall performance I'll add my anecdotal data from a short investigation I did today. Using Chrome / Firefox, the web developer consoles say that BO is "ready" after 1.5s. However when I sit watching blueocean load - it's actually around 6s to a usable screen with my jobs loaded. It takes around 800ms to get the main page, and then 900ms to download the jobs. And if I sit watching the consoles, then there is an unexplained 3-4s delay after the jobs are downloaded where BO is "doing nothing", and then everything renders.In the screenshot above, the "idle" period is from 28000ms to 32000ms I also found (in a separate run - don't correlate to above) that scripting is showing up as a major consumer of time Obviously DOM manipulation has to be done - but I don't think I was expecting it to be such a heavy cost. (I have a modern MBP with 4 processors and 16GB of RAM) Enjoy this anecdote! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41735) Investigate acceptability of overall performance
Title: Message Title Ben Walding updated an issue Jenkins / JENKINS-41735 Investigate acceptability of overall performance Change By: Ben Walding Attachment: screenshot-3.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41735) Investigate acceptability of overall performance
Title: Message Title Ben Walding updated an issue Jenkins / JENKINS-41735 Investigate acceptability of overall performance Change By: Ben Walding Attachment: screenshot-2.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41833) Update table design
Title: Message Title James Dumay assigned an issue to Josh McDonald Jenkins / JENKINS-41833 Update table design Change By: James Dumay Assignee: James Dumay Josh McDonald Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41833) Update table design
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41833 Update table design Change By: James Dumay Sprint: iapetus panthalassa Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41833) Update table design
Title: Message Title Brody Maclean assigned an issue to James Dumay Jenkins / JENKINS-41833 Update table design Change By: Brody Maclean Assignee: Brody Maclean James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41735) Investigate acceptability of overall performance
Title: Message Title Ben Walding updated an issue Jenkins / JENKINS-41735 Investigate acceptability of overall performance Change By: Ben Walding Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39801) Waiting for next available executor
Title: Message Title
Lionel Orellana edited a comment on JENKINS-39801
Re: Waiting for next available executor
This becomes more apparent when you try to run pods in parallel. {code:java} podTemplate(name: 'jenkins-slave', label: 'kube-node', instanceCap: 4, containers: [ containerTemplate(name: 'maven', image: "${registry}:5000/jenkins/slave-maven",command: '/bin/bash',args: '',alwaysPullImage: true,ttyEnabled: true) ]) { parallel ( "Unit": { node('kube-node') { container('maven') { sleep(30) } } }, "Integration": { node('kube-node') { container('maven') { sleep(30) } } } )} {code} The second pod only gets created after the first on finishes effectively serialising the parallel steps.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37663) Build is not marked as UNSTABLE even though failures are found
Title: Message Title Chris Girard commented on JENKINS-37663 Re: Build is not marked as UNSTABLE even though failures are found We are also seeing this in our builds. We are using the multi-branch pipeline (i.e. Jenkinsfile) with the "junit" step. We have also seen back-to-back builds where the actual failing tests did not change, but one build was marked unstable while the other was passing. Peculiar symptom: On the build status page for such builds, note the "Test Result (no failures)" followed immediately by the "Show All Failed Tests >>>" link: Clicking the Show All link expanded to the 39 failing tests we had for that build. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39801) Waiting for next available executor
Title: Message Title
Lionel Orellana commented on JENKINS-39801
Re: Waiting for next available executor
This becomes more apparent when you try to run pods in parallel. podTemplate(name: 'jenkins-slave', label: 'kube-node', instanceCap: 4, containers: [ containerTemplate( name: 'maven', image: "$ {registry} :5000/jenkins/slave-maven", command: '/bin/bash', args: '', alwaysPullImage: true, ttyEnabled: true) ]) { parallel ( "Unit": { node('kube-node') { container('maven') { sleep(30) } } }, "Integration": { node('kube-node') { container('maven') { sleep(30) } } } ) } The second pod only gets created after the first on finishes effectively serialising the parallel steps.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37663) Build is not marked as UNSTABLE even though failures are found
Title: Message Title Chris Girard updated an issue Jenkins / JENKINS-37663 Build is not marked as UNSTABLE even though failures are found Change By: Chris Girard Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41867) Scanning MultiBranchProject fails with IllegalStateException
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-41867 Scanning MultiBranchProject fails with IllegalStateException Change By: Mark Waite Component/s: git-plugin Component/s: core Component/s: scm-api-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41867) Scanning MultiBranchProject fails with IllegalStateException
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-41867 Scanning MultiBranchProject fails with IllegalStateException Change By: Mark Waite Summary: Scanning MultiBranchProject with scm-api 2.0.3 fails : with IllegalStateException Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41867) Scanning MultiBranchProject fails with IllegalStateException
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-41867 Scanning MultiBranchProject fails with IllegalStateException Change By: Mark Waite Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41867) Scanning MultiBranchProject with scm-api 2.0.3 fails: IllegalStateException
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-41867
Scanning MultiBranchProject with scm-api 2.0.3 fails: IllegalStateException
Change By:
Mark Waite
Addendum - it appears I'm wrong about the root cause. I reverted scm-api 2.0.3, switching back to scm-api 2.0.2 and see the same behavior. Sorry for the false alarm on scm-api 2.0.3. My initial attempts to bisect the problem have failed. Please ignore this bug report until I investigate further. Initial scan of branches in a multi-branch-project fails with an IllegalStateException.Steps to duplicate the problem:# Clone, build, and run the docker instance{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41867 $ cd JENKINS-41867 $ git checkout -b lts-with-plugins dac2eebcf7afc90caf9180a9f6a6de6d98ae26b6 # -t origin/lts-with-plugins $ docker build -t jenkins:JENKINS-41867 . $ docker run -i --rm --publish 8080:8080 jenkins:JENKINS-41867{code}# Connect a web browser to that docker instance (http://localhost:8080)# Open the "Git Client Plugin Folder"# Open the "Git Client Branches - Maven" multi-branch job# Click the "Scan Project" link and then the "Run Now" link to start branch indexing# Click the "Log" link to view the log - stack trace will appear in that logThe problem seems to be new with scm-api 2.0.3. Prior versions of scm-api did not show the same behavior.Stack trace is:{noformat}Started by user Mark Waite[Wed Feb 08 16:59:22 MST 2017] Starting branch indexing...Creating git repository in /var/jenkins_home/caches/git-65641b79111589c081c788caa640559c > git init /var/jenkins_home/caches/git-65641b79111589c081c788caa640559c # timeout=11Setting origin to https://github.com/MarkEWaite/git-plugin.git > git config remote.origin.url https://github.com/MarkEWaite/git-plugin.git # timeout=11Fetching & pruning origin...Fetching upstream changes from origin > git --version # timeout=11using GIT_ASKPASS to set credentials intentionally invalid user and password for credentials NPE in multi-branch jobs > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --pruneGetting remote branches...Seen branch in repository origin/2.6.xSeen branch in repository origin/3.0.0-PR439-add-ATH-subset-to-JenkinsfileSeen branch in repository origin/masterSeen branch in repository origin/master-PR439-add-ATH-subset-to-JenkinsfileSeen branch in repository origin/master-PR463-add-git-lfsSeen branch in repository origin/master-PRxxx-move-findbugs-suppressions-into-codeSeen branch in repository origin/master-findbugs-combinedSeen branch in repository origin/master-findbugs-fixesSeen branch in repository origin/ongoing/latest-jenkins-ltsSeen branch in repository origin/ongoing/ltsSeen 10 remote branchesChecking branch master-PR463-add-git-lfsScheduled build for branch: master-PR463-add-git-lfsChecking branch ongoing/ltsChecking branch masterChecking branch master-PR439-add-ATH-subset-to-JenkinsfileERROR: [Wed Feb 08 16:59:24 MST 2017] Could not fetch branches from source
[JIRA] (JENKINS-30350) Jobs get triggered twice from polling git scm
Title: Message Title Shoo Yoo Yoon commented on JENKINS-30350 Re: Jobs get triggered twice from polling git scm Confirm with Jenkins 2.42 and most of plugin is the latest version at this moment. I agree with Klemen Ferjančič . My scenario is following: Jenkins queue is 5 items. each build takes 2 hours. GIT polling for 15 minutes. When there is a new git commit, GIT polling will queue a build because all executors is busy. After 15 minutes, this build still in queue because all executors is still busy. At this moment, GIT polling will check again then it queue a new build because "Last Built Revision" remains. Result: there are two the same build which are queued, in the the Jenkins queue. My suggestion: GIT polling should check whether a similar build is queued. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41868) Locks within parallel tasks release other locks within the pipeline
Title: Message Title Mark Nysen updated an issue Jenkins / JENKINS-41868 Locks within parallel tasks release other locks within the pipeline Change By: Mark Nysen Summary: Locks within parallel tasks release other locks within a project the pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41868) Locks within parallel tasks release other locks within a project
Title: Message Title
Mark Nysen created an issue
Jenkins / JENKINS-41868
Locks within parallel tasks release other locks within a project
Issue Type:
Bug
Assignee:
Unassigned
Components:
lockable-resources-plugin
Created:
2017/Feb/09 1:25 AM
Labels:
lockable lock
Priority:
Critical
Reporter:
Mark Nysen
When a pipeline has an outer lock of a resource and then runs multiple tasks in parallel which have inner locks. The outer lock is sometimes prematurely cleared when the parallel tasks clear their inner lock. This bug was introduced in 1.11 and does not appear in 1.10 A sample pipeline job is below. When the 1st parallel jobs completes, it releases the inner lock as expected. When the 2nd parallel job completes, it releases the inner lock but the outer lock is also cleared. This could be due to clean up code that is clearing a resource lock that it shouldn't be.
node('master'){
// outer lock here, this should persist until the end
lock('outer') {
sh "sleep 10"
def stepsForParallel = [:]
for (int i = 1; i <= 4; i++) {
def stepName = "Inner Run - ${i}"
stepsForParallel[stepName] = test()
}
parallel stepsForParallel
sh "sleep 10"
}
}
def test() {
return {
// create an inner lock which the parallel tasks will queue around
lock('inner') {
sh "sleep 10"
}
}
}
[JIRA] (JENKINS-41867) Scanning MultiBranchProject with scm-api 2.0.3 fails: IllegalStateException
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-41867
Scanning MultiBranchProject with scm-api 2.0.3 fails: IllegalStateException
Change By:
Mark Waite
Initial scan of branches in a multi-branch-project fails with an IllegalStateException.Steps to duplicate the problem:# Clone, build, and run the docker instance{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41867 $ cd JENKINS-41867 $ git checkout -b lts-with-plugins dac2eebcf7afc90caf9180a9f6a6de6d98ae26b6 # -t origin/lts-with-plugins $ docker build -t jenkins:JENKINS-41867 . $ docker run -i --rm --publish 8080:8080 jenkins:JENKINS-41867{code}# Connect a web browser to that docker instance (http://localhost:8080)# Open the "Git Client Plugin Folder"# Open the "Git Client Branches - Maven" multi-branch job# Click the "Scan Project" link and then the "Run Now" link to start branch indexing# Click the "Log" link to view the log - stack trace will appear in that logThe problem seems to be new with scm-api 2.0.3. Prior versions of scm-api did not show the same behavior.Stack trace is:{noformat}Started by user Mark Waite[Wed Feb 08 16:59:22 MST 2017] Starting branch indexing...Creating git repository in /var/jenkins_home/caches/git-65641b79111589c081c788caa640559c > git init /var/jenkins_home/caches/git-65641b79111589c081c788caa640559c # timeout=11Setting origin to https://github.com/MarkEWaite/git-plugin.git > git config remote.origin.url https://github.com/MarkEWaite/git-plugin.git # timeout=11Fetching & pruning origin...Fetching upstream changes from origin > git --version # timeout=11using GIT_ASKPASS to set credentials intentionally invalid user and password for credentials NPE in multi-branch jobs > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --pruneGetting remote branches...Seen branch in repository origin/2.6.xSeen branch in repository origin/3.0.0-PR439-add-ATH-subset-to-JenkinsfileSeen branch in repository origin/masterSeen branch in repository origin/master-PR439-add-ATH-subset-to-JenkinsfileSeen branch in repository origin/master-PR463-add-git-lfsSeen branch in repository origin/master-PRxxx-move-findbugs-suppressions-into-codeSeen branch in repository origin/master-findbugs-combinedSeen branch in repository origin/master-findbugs-fixesSeen branch in repository origin/ongoing/latest-jenkins-ltsSeen branch in repository origin/ongoing/ltsSeen 10 remote branchesChecking branch master-PR463-add-git-lfsScheduled build for branch: master-PR463-add-git-lfsChecking branch ongoing/ltsChecking branch masterChecking branch master-PR439-add-ATH-subset-to-JenkinsfileERROR: [Wed Feb 08 16:59:24 MST 2017] Could not fetch branches from source d7205f38-9ade-472c-923c-6a839d7ec90djava.lang.IllegalStateException: Did not call mayCreate, or used the wrong Item.name for hudson.model.FreeStyleProject@689690d2[Git-Folder/git-plugin-freestyle-multi-branch/master-PR4.l4tko8c5k0.enkinsfile] with name master-PR4.l4tko8c5k0.enkinsfile among [master-PR439-add-ATH-subset-to-Jenkinsfile,
[JIRA] (JENKINS-41867) Scanning MultiBranchProject with scm-api 2.0.3 fails: IllegalStateException
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-41867
Scanning MultiBranchProject with scm-api 2.0.3 fails: IllegalStateException
Change By:
Mark Waite
Initial scan of branches in a multi-branch-project fails with an IllegalStateException.Steps to duplicate the problem:# Clone, build, and run the docker instance{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41867 $ cd JENKINS-41867 $ git checkout -b lts-with-plugins dac2eebcf7afc90caf9180a9f6a6de6d98ae26b6 # -t origin/lts-with-plugins $ docker build -t jenkins:JENKINS-41867 . $ docker run -i --rm --publish 8080:8080 jenkins:JENKINS-41867{code}# Connect a web browser to that docker instance (http://localhost:8080)# Open the "Git Client Plugin Folder"# Open the "Git Client Branches - Maven" multi-branch job# Click the "Scan Project" link and then the "Run Now" link to start branch indexing# Click the "Log" link to view the log - stack trace will appear in that logThe problem seems to be new with scm-api 2.0.3. Prior versions of scm-api did not show the same behavior.Stack trace is:{noformat}Started by user Mark Waite[Wed Feb 08 16:59:22 MST 2017] Starting branch indexing...Creating git repository in /var/jenkins_home/caches/git-65641b79111589c081c788caa640559c > git init /var/jenkins_home/caches/git-65641b79111589c081c788caa640559c # timeout=11Setting origin to https://github.com/MarkEWaite/git-plugin.git > git config remote.origin.url https://github.com/MarkEWaite/git-plugin.git # timeout=11Fetching & pruning origin...Fetching upstream changes from origin > git --version # timeout=11using GIT_ASKPASS to set credentials intentionally invalid user and password for credentials NPE in multi-branch jobs > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --pruneGetting remote branches...Seen branch in repository origin/2.6.xSeen branch in repository origin/3.0.0-PR439-add-ATH-subset-to-JenkinsfileSeen branch in repository origin/masterSeen branch in repository origin/master-PR439-add-ATH-subset-to-JenkinsfileSeen branch in repository origin/master-PR463-add-git-lfsSeen branch in repository origin/master-PRxxx-move-findbugs-suppressions-into-codeSeen branch in repository origin/master-findbugs-combinedSeen branch in repository origin/master-findbugs-fixesSeen branch in repository origin/ongoing/latest-jenkins-ltsSeen branch in repository origin/ongoing/ltsSeen 10 remote branchesChecking branch master-PR463-add-git-lfsScheduled build for branch: master-PR463-add-git-lfsChecking branch ongoing/ltsChecking branch masterChecking branch master-PR439-add-ATH-subset-to-JenkinsfileERROR: [Wed Feb 08 16:59:24 MST 2017] Could not fetch branches from source d7205f38-9ade-472c-923c-6a839d7ec90djava.lang.IllegalStateException: Did not call mayCreate, or used the wrong Item.name for hudson.model.FreeStyleProject@689690d2[Git-Folder/git-plugin-freestyle-multi-branch/master-PR4.l4tko8c5k0.enkinsfile] with name master-PR4.l4tko8c5k0.enkinsfile among [master-PR439-add-ATH-subset-to-Jenkinsfile,
[JIRA] (JENKINS-41867) Scanning MultiBranchProject with scm-api 2.0.3 fails: IllegalStateException
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-41867
Scanning MultiBranchProject with scm-api 2.0.3 fails: IllegalStateException
Change By:
Mark Waite
Initial scan of branches in a multi-branch-project fails with an IllegalStateException.Steps to duplicate the problem:# Clone, build, and run the docker instance{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41867 $ cd JENKINS-41867 $ git checkout -b lts-with-plugins -t origin/lts-with-plugins $ docker build -t jenkins:JENKINS-41867 . $ docker run -i --rm --publish 8080:8080 jenkins:JENKINS-41867{code}# Connect a web browser to that docker instance (http://localhost:8080)# Open the "Git Client Plugin Folder"# Open the "Git Client Branches - Maven" multi-branch job# Click the "Scan Project" link , and then the "Run Now " link to start branch indexing# Click the "Log" link to view the log - stack trace will appear in that logThe problem seems to be new with scm-api 2.0.3. Prior versions of scm-api did not show the same behavior.Stack trace is:{noformat}Started by user Mark Waite[Wed Feb 08 16:59:22 MST 2017] Starting branch indexing...Creating git repository in /var/jenkins_home/caches/git-65641b79111589c081c788caa640559c > git init /var/jenkins_home/caches/git-65641b79111589c081c788caa640559c # timeout=11Setting origin to https://github.com/MarkEWaite/git-plugin.git > git config remote.origin.url https://github.com/MarkEWaite/git-plugin.git # timeout=11Fetching & pruning origin...Fetching upstream changes from origin > git --version # timeout=11using GIT_ASKPASS to set credentials intentionally invalid user and password for credentials NPE in multi-branch jobs > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --pruneGetting remote branches...Seen branch in repository origin/2.6.xSeen branch in repository origin/3.0.0-PR439-add-ATH-subset-to-JenkinsfileSeen branch in repository origin/masterSeen branch in repository origin/master-PR439-add-ATH-subset-to-JenkinsfileSeen branch in repository origin/master-PR463-add-git-lfsSeen branch in repository origin/master-PRxxx-move-findbugs-suppressions-into-codeSeen branch in repository origin/master-findbugs-combinedSeen branch in repository origin/master-findbugs-fixesSeen branch in repository origin/ongoing/latest-jenkins-ltsSeen branch in repository origin/ongoing/ltsSeen 10 remote branchesChecking branch master-PR463-add-git-lfsScheduled build for branch: master-PR463-add-git-lfsChecking branch ongoing/ltsChecking branch masterChecking branch master-PR439-add-ATH-subset-to-JenkinsfileERROR: [Wed Feb 08 16:59:24 MST 2017] Could not fetch branches from source d7205f38-9ade-472c-923c-6a839d7ec90djava.lang.IllegalStateException: Did not call mayCreate, or used the wrong Item.name for hudson.model.FreeStyleProject@689690d2[Git-Folder/git-plugin-freestyle-multi-branch/master-PR4.l4tko8c5k0.enkinsfile] with name master-PR4.l4tko8c5k0.enkinsfile among [master-PR439-add-ATH-subset-to-Jenkinsfile, master-PR463-add-git-lfs] at
[JIRA] (JENKINS-41867) Scanning MultiBranchProject with scm-api 2.0.3 fails: IllegalStateException
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-41867
Scanning MultiBranchProject with scm-api 2.0.3 fails: IllegalStateException
Change By:
Mark Waite
Initial scan of branches in a multi-branch-project fails with an IllegalStateException.Steps to duplicate the problem:# Clone, build, and run the docker instance{code} $ git clone https://github.com/MarkEWaite/docker JENKINS- x 41867 $ cd JENKINS- x 41867 $ git checkout -b lts-with-plugins -t origin/lts-with-plugins $ docker build -t jenkins:JENKINS- x 41867 . $ docker run -i --rm --publish 8080:8080 jenkins:JENKINS- x 41867 {code}# Connect a web browser to that docker instance (http://localhost:8080)# Open the "Git Client Plugin Folder"# Open the "Git Client Branches - Maven" multi-branch job# Click the "Scan Project" link, and the "Run" link to start branch indexing# Click the "Log" link to view the log - stack trace will appear in that logThe problem seems to be new with scm-api 2.0.3. Prior versions of scm-api did not show the same behavior.Stack trace is:{noformat}Started by user Mark Waite[Wed Feb 08 16:59:22 MST 2017] Starting branch indexing...Creating git repository in /var/jenkins_home/caches/git-65641b79111589c081c788caa640559c > git init /var/jenkins_home/caches/git-65641b79111589c081c788caa640559c # timeout=11Setting origin to https://github.com/MarkEWaite/git-plugin.git > git config remote.origin.url https://github.com/MarkEWaite/git-plugin.git # timeout=11Fetching & pruning origin...Fetching upstream changes from origin > git --version # timeout=11using GIT_ASKPASS to set credentials intentionally invalid user and password for credentials NPE in multi-branch jobs > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --pruneGetting remote branches...Seen branch in repository origin/2.6.xSeen branch in repository origin/3.0.0-PR439-add-ATH-subset-to-JenkinsfileSeen branch in repository origin/masterSeen branch in repository origin/master-PR439-add-ATH-subset-to-JenkinsfileSeen branch in repository origin/master-PR463-add-git-lfsSeen branch in repository origin/master-PRxxx-move-findbugs-suppressions-into-codeSeen branch in repository origin/master-findbugs-combinedSeen branch in repository origin/master-findbugs-fixesSeen branch in repository origin/ongoing/latest-jenkins-ltsSeen branch in repository origin/ongoing/ltsSeen 10 remote branchesChecking branch master-PR463-add-git-lfsScheduled build for branch: master-PR463-add-git-lfsChecking branch ongoing/ltsChecking branch masterChecking branch master-PR439-add-ATH-subset-to-JenkinsfileERROR: [Wed Feb 08 16:59:24 MST 2017] Could not fetch branches from source d7205f38-9ade-472c-923c-6a839d7ec90djava.lang.IllegalStateException: Did not call mayCreate, or used the wrong Item.name for hudson.model.FreeStyleProject@689690d2[Git-Folder/git-plugin-freestyle-multi-branch/master-PR4.l4tko8c5k0.enkinsfile] with name master-PR4.l4tko8c5k0.enkinsfile among [master-PR439-add-ATH-subset-to-Jenkinsfile, master-PR463-add-git-lfs] at
[JIRA] (JENKINS-41867) Scanning MultiBranchProject with scm-api 2.0.3 fails: IllegalStateException
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-41867 Scanning MultiBranchProject with scm-api 2.0.3 fails: IllegalStateException Issue Type: Bug Assignee: Unassigned Components: scm-api-plugin Created: 2017/Feb/09 12:51 AM Environment: scm-api 2.0.3 Priority: Major Reporter: Mark Waite Initial scan of branches in a multi-branch-project fails with an IllegalStateException. Steps to duplicate the problem: Clone, build, and run the docker instance $ git clone https://github.com/MarkEWaite/docker JENKINS-x $ cd JENKINS-x $ git checkout -b lts-with-plugins -t origin/lts-with-plugins $ docker build -t jenkins:JENKINS-x . $ docker run -i --rm --publish 8080:8080 jenkins:JENKINS-x Connect a web browser to that docker instance (http://localhost:8080) Open the "Git Client Plugin Folder" Open the "Git Client Branches - Maven" multi-branch job Click the "Scan Project" link, and the "Run" link to start branch indexing Click the "Log" link to view the log - stack trace will appear
[JIRA] (JENKINS-41433) Add new API for "permissions"
Title: Message Title Vivek Pandey started work on JENKINS-41433 Change By: Vivek Pandey Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Vivek Pandey updated JENKINS-41403 Jenkins / JENKINS-41403 Additions to Github APIs for Organizations and Repositories Change By: Vivek Pandey Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41861) New message templates show "is not supported in this context" in Pipeline builds
Title: Message Title aldaris resolved as Fixed Hopefully the issues raised here are now all addressed. If HIPCHAT_CHANGES_OR_CAUSE and COMMIT_MESSAGE is still acting up: pull requests welcome. Will wait for a week or so to see if any other issues get reported, and then I'll release 2.1.1. Jenkins / JENKINS-41861 New message templates show "is not supported in this context" in Pipeline builds Change By: aldaris Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-41861) New message templates show "is not supported in this context" in Pipeline builds
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41861 Re: New message templates show "is not supported in this context" in Pipeline builds Code changed in jenkins User: Peter Major Path: src/main/java/jenkins/plugins/hipchat/ext/tokens/BuildDurationMacro.java src/test/java/jenkins/plugins/hipchat/ext/tokens/BuildDurationMacroTest.java http://jenkins-ci.org/commit/hipchat-plugin/c2bb55ebc511698b6cfcf7088c3e6d468fb8b40c Log: JENKINS-41861 Fix BUILD_DURATION for pipeline builds Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41861) New message templates show "is not supported in this context" in Pipeline builds
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41861 Re: New message templates show "is not supported in this context" in Pipeline builds Code changed in jenkins User: Peter Major Path: src/main/java/jenkins/plugins/hipchat/ext/tokens/CommitMessageMacro.java src/main/java/jenkins/plugins/hipchat/ext/tokens/HipchatChangesMacro.java http://jenkins-ci.org/commit/hipchat-plugin/c2524866e24eab55d4560e04879d798bc7de64b5 Log: JENKINS-41861 Attempt to support CHANGES_OR_CAUSE and COMMIT_MESSAGE for pipeline builds Compare: https://github.com/jenkinsci/hipchat-plugin/compare/9ab63eb119e1...c2524866e24e Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41861) New message templates show "is not supported in this context" in Pipeline builds
Title: Message Title aldaris commented on JENKINS-41861 Re: New message templates show "is not supported in this context" in Pipeline builds Changeset information access with pipeline jobs is not too straightforward (not for me at least), so that is currently not supported with pipeline jobs. I now see that the CHANGES macro has some hacky reflection code to deal with this, so you may find $CHANGES to be a more suitable option for now. BUILD_DURATION should be supported with pipeline jobs as well, it is however buggy as you've found. The 0 ms issue should be resolved soon. Since you are saying that CHANGES_OR_CAUSE and COMMIT_MESSAGE has worked with pipeline builds before, I think there may be an easy solution to fix them, but it's unlikely that I'll investigate a lot more than that. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41572) ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
Title: Message Title T. King updated an issue Jenkins / JENKINS-41572 ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins Change By: T. King Comment: I see, I was about to ask you that. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41572) ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
Title: Message Title T. King updated an issue Jenkins / JENKINS-41572 ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins Change By: T. King Comment: Can you be more specific as far as your configuration question? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41572) ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
Title: Message Title T. King updated an issue Jenkins / JENKINS-41572 ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins Change By: T. King Comment: Where do I find the config.xml? Usually I work with Linux systems, this is my first time working with a Windows system. To be honest, that's one reason I am not knowledgeable of what's going on. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41572) ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
Title: Message Title T. King updated an issue Jenkins / JENKINS-41572 ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins Change By: T. King Comment: Can you please answer my last question? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41572) ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
Title: Message Title T. King updated an issue Jenkins / JENKINS-41572 ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins Change By: T. King Comment: So, I looked on the slave, I don't see that? I went to C:\jenkins. I see no folder named nodes, therefore I'm not going to see anything as far as node names. Any ideas? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41572) ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
Title: Message Title T. King updated an issue Jenkins / JENKINS-41572 ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins Change By: T. King Comment: Ok, I found the file what exactly do you need to see within it? any specific section? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41572) ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
Title: Message Title T. King updated an issue Jenkins / JENKINS-41572 ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins Change By: T. King Comment: I'm still waiting for a reply to my question. Could you please comment sooner than later? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41866) Robot Framework creates artifacts owned by root user
Title: Message Title Matthew Smith created an issue Jenkins / JENKINS-41866 Robot Framework creates artifacts owned by root user Issue Type: Bug Assignee: jpiironen Attachments: robot_root.PNG, ws_cleanup_fail.PNG Components: robot-plugin Created: 2017/Feb/08 11:50 PM Environment: Robot Framework plugin 1.6.4 Workspace Cleanup Plugin 0.32 Priority: Major Reporter: Matthew Smith Robot Framework plugin creates output files with root ownership. Because of this, the Workspace Cleanup Plugin is unable to clean up the workspace after a build is done. I think the Robot Framework plugin should only create artifacts owned by the user that Jenkins runs as, or it should allow the user to be specified in the configuration. Add Comment
[JIRA] (JENKINS-41572) ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
Title: Message Title Oleg Nenashev commented on JENKINS-41572 Re: ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins T. King It is a bugtracker, not a support site. There is no SLAs, several-day response delays are fine. It is a responsibility of reporters to provide a good issue description and to google a bit in order to find locations of config files, etc. The most of us contribute the project during their spare time, which is not something consistent. Please avoid such pinging. Just attach the file to the ticket. I have no idea what to look for since I do not know your slave configuration. Likely there is no bug in Jenkins at all, and you need to allow connection to the Jenkins JNLP port (in Global security settings). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41572) ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
Title: Message Title T. King commented on JENKINS-41572 Re: ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins Can you please answer my last question? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41843) Sandbox RejectedAccessException when running from Global Shared Pipeline Library
Title: Message Title
aldaris resolved as Cannot Reproduce
Works fine for me after following the instructions provided in the pipeline documentation:
in my global shared library's git repo I have the following file under src/com/mycompany/Hipchat.groovy:
package com.mycompany;
class Hipchat implements Serializable {
def notifyStarted(script, room) {
script.hipchatSend (color: 'YELLOW', room: room, notify: false,
message: "STARTED: Job '${script.env.JOB_NAME} [${script.env.BUILD_NUMBER}]' (${script.env.BUILD_URL})"
)
}
}
The pipeline job has been configured with this DSL:
@Library('utils')
import com.mycompany.Hipchat
node() {
stage('hipchat') {
new Hipchat().notifyStarted(this, 'Jenkins')
}
}
Jenkins / JENKINS-41843
Sandbox RejectedAccessException when running from Global Shared Pipeline Library
Change By:
aldaris
Status:
Open Resolved
Assignee:
aldaris
Resolution:
Cannot Reproduce
[JIRA] (JENKINS-41714) Docker Build and Publish Force Pull option needs to be changed
Title: Message Title Carlos Sanchez commented on JENKINS-41714 Re: Docker Build and Publish Force Pull option needs to be changed force pull just triggers a docker pull, the --force arg is only set if forceTag is set, and it is not by default Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41861) New message templates show "is not supported in this context" in Pipeline builds
Title: Message Title aldaris assigned an issue to aldaris Jenkins / JENKINS-41861 New message templates show "is not supported in this context" in Pipeline builds Change By: aldaris Assignee: aldaris Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41832) master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener()
Title: Message Title Tom FENNELLY resolved as Fixed merged upstream Jenkins / JENKINS-41832 master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener() Change By: Tom FENNELLY Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-41780) REGRESSION: Purple vomit for aborted stage
Title: Message Title James Dumay updated JENKINS-41780 Jenkins / JENKINS-41780 REGRESSION: Purple vomit for aborted stage Change By: James Dumay Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41865) buildWithParameters does not work with slashes in branch name
Title: Message Title marc young updated an issue Jenkins / JENKINS-41865 buildWithParameters does not work with slashes in branch name Change By: marc young Attachment: Screen Shot 2017-02-08 at 4.12.19 PM.png Attachment: Screen Shot 2017-02-08 at 4.12.26 PM.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41865) buildWithParameters does not work with slashes in branch name
Title: Message Title marc young updated an issue Jenkins / JENKINS-41865 buildWithParameters does not work with slashes in branch name Change By: marc young Attachment: Screen Shot 2017-02-08 at 4.12.19 PM.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41865) buildWithParameters does not work with slashes in branch name
Title: Message Title marc young updated an issue Jenkins / JENKINS-41865 buildWithParameters does not work with slashes in branch name Change By: marc young Attachment: Screen Shot 2017-02-08 at 4.12.26 PM.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41865) buildWithParameters does not work with slashes in branch name
Title: Message Title marc young created an issue Jenkins / JENKINS-41865 buildWithParameters does not work with slashes in branch name Issue Type: Bug Assignee: Kirill Merkushev Attachments: Screen Shot 2017-02-08 at 4.12.19 PM.png, Screen Shot 2017-02-08 at 4.12.26 PM.png, Screen Shot 2017-02-08 at 4.25.16 PM.png Components: github-branch-source-plugin, github-plugin Created: 2017/Feb/08 10:26 PM Priority: Critical Reporter: marc young Build is a github project on the latest everything. Jenkins v 2.45 AWS Linux (centos fork) Attempting to build github branches with slashes in them returns a 403 marc is missing the Job/Build permission Authorization is set so that Any logged in user can do anything This problem does not exist on branches without slashes in them.
[JIRA] (JENKINS-41846) artifact archiving error - concatenated absolute paths
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41846 Re: artifact archiving error - concatenated absolute paths Code changed in jenkins User: restjohn Path: src/main/java/org/jenkinsci/plugins/androidsigning/SignApksBuilder.java src/test/java/org/jenkinsci/plugins/androidsigning/SignApksBuilderTest.java src/test/resources/workspace/test-unsigned.apk http://jenkins-ci.org/commit/android-signing-plugin/b5349c8c63c33f7f2d9d3ae769613903a3c3dcd6 Log: fix JENKINS-41846: now using the correct relative paths in artifact archive map and added some real tests Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Michael Neale commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit Yes this is happening stil quite often with the SCM 2.0 suite - as discovered by Cliff Meyers Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41832) master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener()
Title: Message Title Michael Neale commented on JENKINS-41832 Re: master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener() Thanks for PR and release quickly all! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Michael Neale assigned an issue to Stephen Connolly Jenkins / JENKINS-36121 Github Branch Source plugin trips api rate limit Change By: Michael Neale Assignee: CloudBees Inc. Stephen Connolly Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36121 Github Branch Source plugin trips api rate limit Change By: Michael Neale Priority: Major Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41864) Illegal dates for cron entry cause 100% cpu
Title: Message Title stefan thomasson commented on JENKINS-41864 Re: Illegal dates for cron entry cause 100% cpu Having the next-executions plugin https://wiki.jenkins-ci.org/display/JENKINS/Next+Executions installed also spawns new threads at 100% Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41528) Use local git reference repo to speed up cloning when using large jenkins instances
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41528 Re: Use local git reference repo to speed up cloning when using large jenkins instances Code changed in jenkins User: Victor Martinez Path: CONTRIBUTING.md README.md src/main/java/org/jenkins/ci/plugins/jenkinslint/JenkinsLintAction.java src/main/java/org/jenkins/ci/plugins/jenkinslint/check/GitRefChecker.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/GitRefCheckerTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/5eaffc09d9b048d3f03fa997811eaa4425913bfe Log: JENKINS-41528 Merge pull request #2 from jenkinsci/git_ref JENKINS-41528 Git Ref cloning might help to speed up your cloning time Compare: https://github.com/jenkinsci/jenkinslint-plugin/compare/2f95712cd9f7...5eaffc09d9b0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32296) Jenkins global security configuration page should provide option to configure the new "Content Security Policy"
Title: Message Title Daniel Beck commented on JENKINS-32296 Re: Jenkins global security configuration page should provide option to configure the new "Content Security Policy" to keep the setting after system reboot Did you read https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Content+Security+Policy ? It explains how to customize this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
