[JIRA] (JENKINS-33452) Workspace cleanup fails when trying to delete files with ? in name.
Title: Message Title vjuranek assigned an issue to Oliver Gondža Jenkins / JENKINS-33452 Workspace cleanup fails when trying to delete files with ? in name. Change By: vjuranek Assignee: vjuranek Oliver Gondža 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-36277) Process lauchner should check if working directory exists
Title: Message Title vjuranek created an issue Jenkins / JENKINS-36277 Process lauchner should check if working directory exists Issue Type: Improvement Assignee: vjuranek Components: core Created: 2016/Jun/28 2:31 PM Priority: Minor Reporter: vjuranek When external process is started and working directory doesn't exists, it fails with exception bellow and it's easy to overlook that process runs in non-existing directory (as the same exception is thrown when external program file doesn't exists, has wrong rights and many other reasons). It would be nice if process launcher checks that working directory exists before starting the process. java.io.IOException: Cannot run program "/my/external/program" (in directory "/tmp/aaa"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:803) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at org.jenkinsci.plugins.radargun.NodeRunner.call(NodeRunner.java:35) at org.jenkinsci.plugins.radargun.NodeRunner.call(NodeRunner.java:11) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:248) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at
[JIRA] [docker-build-step-plugin] (JENKINS-24071) Docker build step tries to build on master and not slave
Title: Message Title vjuranek commented on JENKINS-24071 Re: Docker build step tries to build on master and not slave Hi, I looked on this issue quite a long time ago - IIRC there is an issue with serialization which is not very easy to solve. If I find some time, I'd like to look on it again soon, but not promises Thanks for understanding Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [proc-cleaner-plugin] (JENKINS-31478) Attach ps output to the LOG and job console when error occurs, verify return code
Title: Message Title vjuranek resolved as Fixed Implemented in https://github.com/jenkinsci/proc-cleaner-plugin/pull/12 Jenkins / JENKINS-31478 Attach ps output to the LOG and job console when error occurs, verify return code Change By: vjuranek Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-30255) Publicly disclosed security issue on Jenkins suggested to affect latest version
Title: Message Title vjuranek closed an issue as Duplicate Thanks for reporting the issue. It duplicates SECURITY-199 which was triaged and closed as not a bug. This exploit works only when Jenkins CSRF protection is turned off, turning it on should mitigate this issue. Next time please open any security related issue under "Security issues" project, which is not publicly available. Thanks! Jenkins / JENKINS-30255 Publicly disclosed security issue on Jenkins suggested to affect latest version Change By: vjuranek Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [beaker-builder-plugin] (JENKINS-30258) Allow to specify Beaker job file via URL
Title: Message Title vjuranek created an issue Jenkins / JENKINS-30258 Allow to specify Beaker job file via URL Issue Type: New Feature Assignee: vjuranek Components: beaker-builder-plugin Created: 02/Sep/15 7:44 AM Priority: Major Reporter: vjuranek at least plain URL, later probably also should support HTTPS Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [openstack-cloud-plugin] (JENKINS-28789) NoSuchElementException: apiType network not found in catalog []
Title: Message Title vjuranek commented on JENKINS-28789 Re: NoSuchElementException: apiType network not found in catalog [] Hi, in my case it was wrong format of credential, login has to be in format tenantName:userName, now also covered in help for this field. Thanks Oliver Gondža for pointing me out on this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [docker-build-step-plugin] (JENKINS-29775) client is too old, minimum supported API version is 1.12
Title: Message Title vjuranek closed an issue as Not A Defect thanks for info, closing then Jenkins / JENKINS-29775 client is too old, minimum supported API version is 1.12 Change By: vjuranek Status: Open Closed Resolution: NotADefect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [ws-cleanup-plugin] (JENKINS-30077) Expand build parameters
Title: Message Title vjuranek commented on JENKINS-30077 Re: Expand build parameters Hi, what exactly you like to expand? Most of the options are check boxes... is it external delete command? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [monitoring-plugin] (JENKINS-29971) Failed to load index from org.kohsuke.stapler.jelly.groovy.GroovyFacet@2cc7b16d
Title: Message Title vjuranek assigned an issue to Unassigned Jenkins / JENKINS-29971 Failed to load index from org.kohsuke.stapler.jelly.groovy.GroovyFacet@2cc7b16d Change By: vjuranek Assignee: vjuranek Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [monitoring-plugin] (JENKINS-29971) Failed to load index from org.kohsuke.stapler.jelly.groovy.GroovyFacet@2cc7b16d
Title: Message Title vjuranek commented on JENKINS-29971 Re: Failed to load index from org.kohsuke.stapler.jelly.groovy.GroovyFacet@2cc7b16d changing component, this seems to be related to monitoring plugin, not groovy plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [monitoring-plugin] (JENKINS-29971) Failed to load index from org.kohsuke.stapler.jelly.groovy.GroovyFacet@2cc7b16d
Title: Message Title vjuranek updated an issue Jenkins / JENKINS-29971 Failed to load index from org.kohsuke.stapler.jelly.groovy.GroovyFacet@2cc7b16d Change By: vjuranek Component/s: monitoring-plugin Component/s: groovy-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [docker-build-step-plugin] (JENKINS-29775) client is too old, minimum supported API version is 1.12
Title: Message Title vjuranek commented on JENKINS-29775 Re: client is too old, minimum supported API version is 1.12 Milan Simonovic, yes, setting up client version in global Jenkins configuration should solve the issue. Could you confirm it works for you? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-29422) Cannot run program groovy
Title: Message Title vjuranek commented on JENKINS-29422 Re: Cannot run program groovy Wouldnt it make sense to call 'groovy' without any prefix-path specification? yes, this is exactly how it works. If you setup groovy installation, it uses full path to the installation, but (Default) call simply groovy without any prefix path, so e.g. on Linux is used the first groovy binary found on paths set in PATH environment variable - but doesn't do any auto installation and if groovy is not the PATH, it fails with an error. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-29422) Cannot run program groovy
Title: Message Title vjuranek commented on JENKINS-29422 Re: Cannot run program groovy Hi Simon, yes, I'd like to fix it, but I cannot reproduce it and haven't enough information to figure out where the problem could be. Jenkins for some reason doesn't download JSON with download URLs. Are there any other files in updates directory, i.e. is it Groovy plugin specific issue? Also is the firewall and network configured properly on your machines? Could you also be more specific what happens what Jenkins doesn't recognize that Groovy installation is not present on the slave? As for groovy not working - this is a fallback option when you haven't configured any Groovy installation, it simply calls groovy cmd and assumes you have some groovy binary on the default path. This is not a bug but intentional behavior, however, documentation can be improved in this regard and at least mention it - I already added a short note into Groovy plugin wiki page Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-29422) Cannot run program groovy
Title: Message Title vjuranek commented on JENKINS-29422 Re: Cannot run program groovy as for groovy_default_and_PATH_variable_not_working.png - it seems to be some Windows specific issue, I need to look on it (i.e. find some windows machine), on Linux works fine as for some_workaround.png - in case you have already a groovy installation on local machine, you can un-check Install automatically field in global Jenkins configuration and set a path to the installation. It can be arbitrary directory and adding it to the PATH shouldn't be needed. What is quite common is that you have e.g. NFS drive with various tools and mount the disk when you create the slave machine or start the slave ... maybe there can be again some windows specific issues, but AFAIK should work (at least my colleagues who run some groovy scripts on windows have never complained ) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-29577) Plugin creates groovy command line with classpath in wrong position
Title: Message Title vjuranek commented on JENKINS-29577 Re: Plugin creates groovy command line with classpath in wrong position thanks, obviously I was wrong and Groovy requires for some reason classpath to be the first argument... will look on it Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-28502) Install from http://groovy.codehaus.org installer method failing
Title: Message Title vjuranek resolved as Fixed Downloads from Bintray seem to work fine now. Please re-open if there are any other issues. Jenkins / JENKINS-28502 Install from http://groovy.codehaus.org installer method failing Change By: vjuranek Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-29577) Plugin creates groovy command line with classpath in wrong position
Title: Message Title vjuranek commented on JENKINS-29577 Re: Plugin creates groovy command line with classpath in wrong position Hi, what kind of issues is caused by providing properties before classpath? AFAIK the order of parameters shouldn't matter. Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-29422) Cannot run program groovy
Title: Message Title vjuranek commented on JENKINS-29422 Re: Cannot run program groovy could you please check $JENKINS_HOME/updates if hudson.plugins.groovy.GroovyInstaller file is present there a has some content (JSON file with links to bintray)? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-29422) Cannot run program groovy
Title: Message Title vjuranek commented on JENKINS-29422 Re: Cannot run program groovy Hi, which version of plugin and Jenkins core do you use? I just tried with recent jenkins/plugin version and everything seems to work fine... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-29422) Cannot run program groovy
Title: Message Title vjuranek commented on JENKINS-29422 Re: Cannot run program groovy as a workaround, you can download the json manually from https://updates.jenkins-ci.org/updates/hudson.plugins.groovy.GroovyInstaller.json and place it into $JENKINS_HOME/updates/hudson.plugins.groovy.GroovyInstaller Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-29422) Cannot run program groovy
Title: Message Title vjuranek commented on JENKINS-29422 Re: Cannot run program groovy Another way is to navigate to $JENKINS_URL/pluginManager/advanced and click on Check now on the bottom of the page. It should download json files into your updates directory automatically. If not, please check Jenkins log or your network settings. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-29422) Cannot run program groovy
Title: Message Title vjuranek updated an issue Jenkins / JENKINS-29422 Cannot run program groovy Change By: vjuranek Component/s: core Component/s: groovy-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-29422) Cannot run program groovy
Title: Message Title vjuranek updated an issue Jenkins / JENKINS-29422 Cannot run program groovy Change By: vjuranek Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-29422) Cannot run program groovy
Title: Message Title vjuranek commented on JENKINS-29422 Re: Cannot run program groovy Changing component, as if it's not some network issue (which seems to me the most likely), it's an issue with DailyCheck class which is not downloading updates from Jenkins update center. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [openstack-cloud-plugin] (JENKINS-28789) NoSuchElementException: apiType network not found in catalog []
Title: Message Title vjuranek commented on JENKINS-28789 Re: NoSuchElementException: apiType network not found in catalog [] Stack trace us bellow, but the root cause is the same as in original stack trace: Jun 24, 2015 7:30:14 AM hudson.triggers.SafeTimerTask run SEVERE: Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@4366295c failed java.util.NoSuchElementException: apiType compute not found in catalog [] at org.jclouds.openstack.keystone.v2_0.suppliers.LocationIdToURIFromAccessForTypeAndVersion.get(LocationIdToURIFromAccessForTypeAndVersion.java:97) at org.jclouds.openstack.keystone.v2_0.suppliers.LocationIdToURIFromAccessForTypeAndVersion.get(LocationIdToURIFromAccessForTypeAndVersion.java:54) at org.jclouds.rest.suppliers.MemoizedRetryOnTimeOutButNotOnAuthorizationExceptionSupplier$SetAndThrowAuthorizationExceptionSupplierBackedLoader.load(MemoizedRetryOnTimeOutButNotOnAuthorizationExceptionSupplier.java:73) at org.jclouds.rest.suppliers.MemoizedRetryOnTimeOutButNotOnAuthorizationExceptionSupplier$SetAndThrowAuthorizationExceptionSupplierBackedLoader.load(MemoizedRetryOnTimeOutButNotOnAuthorizationExceptionSupplier.java:57) at shaded.com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3524) at shaded.com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2317) at shaded.com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2280) at shaded.com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2195) at shaded.com.google.common.cache.LocalCache.get(LocalCache.java:3934) at shaded.com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3938) at shaded.com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4821) at org.jclouds.rest.suppliers.MemoizedRetryOnTimeOutButNotOnAuthorizationExceptionSupplier.get(MemoizedRetryOnTimeOutButNotOnAuthorizationExceptionSupplier.java:119) at org.jclouds.location.suppliers.derived.ZoneIdsFromZoneIdToURIKeySet.get(ZoneIdsFromZoneIdToURIKeySet.java:46) at org.jclouds.location.suppliers.derived.ZoneIdsFromZoneIdToURIKeySet.get(ZoneIdsFromZoneIdToURIKeySet.java:34) at shaded.com.google.common.base.Suppliers$SupplierComposition.get(Suppliers.java:67) at org.jclouds.rest.suppliers.MemoizedRetryOnTimeOutButNotOnAuthorizationExceptionSupplier$SetAndThrowAuthorizationExceptionSupplierBackedLoader.load(MemoizedRetryOnTimeOutButNotOnAuthorizationExceptionSupplier.java:73) at org.jclouds.rest.suppliers.MemoizedRetryOnTimeOutButNotOnAuthorizationExceptionSupplier$SetAndThrowAuthorizationExceptionSupplierBackedLoader.load(MemoizedRetryOnTimeOutButNotOnAuthorizationExceptionSupplier.java:57) at shaded.com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3524) at shaded.com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2317) at shaded.com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2280) at shaded.com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2195) at shaded.com.google.common.cache.LocalCache.get(LocalCache.java:3934) at shaded.com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3938) at shaded.com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4821) at org.jclouds.rest.suppliers.MemoizedRetryOnTimeOutButNotOnAuthorizationExceptionSupplier.get(MemoizedRetryOnTimeOutButNotOnAuthorizationExceptionSupplier.java:119) at
[JIRA] [openstack-cloud-plugin] (JENKINS-28789) NoSuchElementException: apiType network not found in catalog []
Title: Message Title vjuranek updated an issue Jenkins / JENKINS-28789 NoSuchElementException: apiType network not found in catalog [] Change By: vjuranek Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [openstack-cloud-plugin] (JENKINS-28789) NoSuchElementException: apiType network not found in catalog []
Title: Message Title vjuranek commented on JENKINS-28789 Re: NoSuchElementException: apiType network not found in catalog [] I'm hitting this exception even during provisioning so increasing the priority at least little bit (I'm hitting it also when visiting the config page, this can be work-around by direct editing config.xml, but hit it again during provisining) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [docker-build-step-plugin] (JENKINS-28920) Support multiple Docker servers
Title: Message Title vjuranek created an issue Jenkins / JENKINS-28920 Support multiple Docker servers Issue Type: New Feature Assignee: vjuranek Components: docker-build-step-plugin Created: 16/Jun/15 11:04 AM Priority: Major Reporter: vjuranek Allow to define multiple docker servers where containers can run and allow to select docker server in job configuration Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-28635) Show URL used by autoinstaller
Title: Message Title vjuranek created an issue Jenkins / JENKINS-28635 Show URL used by autoinstaller Issue Type: Improvement Assignee: vjuranek Components: core Created: 28/May/15 8:58 PM Priority: Minor Reporter: vjuranek It seems for some users is important to know exact URL from where the bits used by autoinstaller will be downloaded, see e.g. this PR discussion. Provide a way how interested users can check the URL when configuring autoinstaller. Add Comment
[JIRA] [docker-build-step-plugin] (JENKINS-28371) Not able to access Docker build step plugin
Title: Message Title vjuranek commented on JENKINS-28371 Re: Not able to access Docker build step plugin Hi, so you see any error in Jenkins log? Also, could you try without Docker plugin (i.e. with just docker-buil-step plugin). In the past there were some compatibility issues and these two plugin don't play well when installed together. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-28287) Setting Groovy installations not thread-safe
Title: Message Title vjuranek resolved as Fixed Fixed in https://github.com/jenkinsci/groovy-plugin/pull/15 Jenkins / JENKINS-28287 Setting Groovy installations not thread-safe Change By: vjuranek Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-27833) Groovy-All Bundle not deployed for BSIM Test Cases in CDB
vjuranek commented on JENKINS-27833 Groovy-All Bundle not deployed for BSIM Test Cases in CDB Skimming through the exception, it looks like it has nothing to do with Jenkins groovy plugin. Basically your custom framework fails to load groovy jar via OSGi - so probably some misconfiguration of your OSGi bundles or something like this. I'm afraid I cannot help here, it seems to be some issue in your internal framework. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-27833) Groovy-All Bundle not deployed for BSIM Test Cases in CDB
vjuranek resolved JENKINS-27833 as Not A Defect Groovy-All Bundle not deployed for BSIM Test Cases in CDB Change By: vjuranek (08/Apr/15 9:37 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-27833) Groovy-All Bundle not deployed for BSIM Test Cases in CDB
vjuranek commented on JENKINS-27833 Groovy-All Bundle not deployed for BSIM Test Cases in CDB Hi, are you sure this is intended to be filed as an upstream issue? Besides the fact I'm not sure what BSIM and CDS stands for, the server you are referring to is not publicly available. Seems to me like some internal Ericsson issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step-plugin] (JENKINS-27821) Docker Build Step Plugin: Unable to correctly install
vjuranek resolved JENKINS-27821 as Fixed Docker Build Step Plugin: Unable to correctly install yes, docker-java library is built for JDK7. I released 1.22 with docker-java rebuilt with JDK6, but as it's a 3rd party dependency, I'm not going to fix and rebuilt it every time (and hardly to push it into docker-java upstream as JDK6 is 2 year EOL), so this is probably the only release with JDK6 support. Change By: vjuranek (07/Apr/15 8:21 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-27614) Can't execute Jenkins' self-installed Groovy on Windows 2012 slave
vjuranek closed JENKINS-27614 as Not A Defect Cant execute Jenkins self-installed Groovy on Windows 2012 slave thanks for info - closing. Please reopen if you find out that's actually a problem Groovy plugin. Thanks. Change By: vjuranek (27/Mar/15 9:44 AM) Status: Open Closed Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step-plugin] (JENKINS-27296) Jenkins stopped displaying build progress after docker update
vjuranek commented on JENKINS-27296 Jenkins stopped displaying build progress after docker update Hi, this is probably wrong component - Docker build step plugin uses REST API to communicate with Docker, so according to docker login -u john I would guess this is some other plugin. Also, it would be useful to provide Docker version which you use to track down the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step-plugin] (JENKINS-26754) Stop all the started containers automatically at the end of the build
vjuranek created JENKINS-26754 Stop all the started containers automatically at the end of the build Issue Type: New Feature Assignee: vjuranek Components: docker-build-step-plugin Created: 03/Feb/15 12:11 PM Description: Cache container IDs started by the plugin withing the build and add an option to stop all of them at the end of the build. Probably as part of the start action, so the no other build step has to be added in the end of the job config. Project: Jenkins Priority: Minor Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step-plugin] (JENKINS-26512) Add support for SSL config
vjuranek created JENKINS-26512 Add support for SSL config Issue Type: New Feature Assignee: vjuranek Components: docker-build-step-plugin Created: 20/Jan/15 8:10 PM Description: SSL support was added in recent docker client. Add options to configure SSL also into the plugin and use dummy config only when no SSL certificate is set up. Project: Jenkins Priority: Minor Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [openjdk-native-plugin] (JENKINS-26434) Update for latest OpenJDK 8
vjuranek created JENKINS-26434 Update for latest OpenJDK 8 Issue Type: New Feature Assignee: vjuranek Components: openjdk-native-plugin Created: 14/Jan/15 10:32 PM Description: See https://github.com/vjuranek/openJDK-native-plugin/issues/1 Project: Jenkins Priority: Minor Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-26070) Unable to add multiple jars to classpath with wildcard
vjuranek resolved JENKINS-26070 as Fixed Unable to add multiple jars to classpath with wildcard Hi, I tested that class paths with wild cards are expanded and added automated test for it (see previous comment). If doesn't work for you, please make sure you have recent java and groovy version (IIRC wildcard support was added in java 6 and in groovy since 1.7.1). If you have recent java and groovy and still doesn't work, please reopen with more details about your environment. Change By: vjuranek (09/Jan/15 1:03 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-publish-plugin] (JENKINS-26167) none default registry in PullImageCommand not working as expected
vjuranek resolved JENKINS-26167 as Fixed none default registry in PullImageCommand not working as expected Should be fixed by https://github.com/jenkinsci/docker-build-step-plugin/pull/22 Change By: vjuranek (07/Jan/15 10:08 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step-plugin] (JENKINS-24388) Add registry authentication
vjuranek resolved JENKINS-24388 as Fixed Add registry authentication Should be fixed by https://github.com/jenkinsci/docker-build-step-plugin/pull/22 Change By: vjuranek (07/Jan/15 10:07 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-25992) Groovy script lucks permissions on slave
vjuranek resolved JENKINS-25992 as Not A Defect Groovy script lucks permissions on slave I'm closing it as this is IMHO not a bug. If I missed something or ordinary Groovy build step doesn't work for you, please re-open. Change By: vjuranek (10/Dec/14 9:40 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-25992) Groovy script lucks permissions on slave
vjuranek commented on JENKINS-25992 Groovy script lucks permissions on slave Hi, system groovy script runs in master JVM and therefore cannot see files located on slaves. System groovy script is intended to be used for various operation with master, like an automation of scripts which are executed by admin in $JENKINS_URL/script. You should use ordinary Groovy build step. This is executed on slave and should work fine for scenario you've described. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step-plugin] (JENKINS-25929) Pull image cmd broken in rel. 1.15
vjuranek created JENKINS-25929 Pull image cmd broken in rel. 1.15 Issue Type: Bug Assignee: vjuranek Components: docker-build-step-plugin Created: 05/Dec/14 9:04 AM Description: Pull image cmd is broken since 1.15, fails with ERROR: command 'Pull image' failed: invalid character 'e' in literal false (expecting 'a') See this GH comment for more details. Project: Jenkins Priority: Critical Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step-plugin] (JENKINS-25929) Pull image cmd broken in rel. 1.15
vjuranek resolved JENKINS-25929 as Fixed Pull image cmd broken in rel. 1.15 Should be fixed by https://github.com/jenkinsci/docker-build-step-plugin/commit/2b6797a7e8ce7780f959807a720eb7277bc8b6f5 Change By: vjuranek (05/Dec/14 9:52 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [beaker-builder-plugin] (JENKINS-25839) $BEAKER_JOB_ID expanded to wrong value
vjuranek created JENKINS-25839 $BEAKER_JOB_ID expanded to wrong value Issue Type: Bug Assignee: vjuranek Components: beaker-builder-plugin Created: 01/Dec/14 9:01 AM Description: see https://github.com/vjuranek/beaker-builder-plugin/issues/2 Project: Jenkins Priority: Minor Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [beaker-builder-plugin] (JENKINS-25839) $BEAKER_JOB_ID expanded to wrong value
vjuranek updated JENKINS-25839 $BEAKER_JOB_ID expanded to wrong value Change By: vjuranek (01/Dec/14 9:04 AM) Priority: Minor Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [beaker-builder-plugin] (JENKINS-25839) $BEAKER_JOB_ID expanded to wrong value
vjuranek resolved JENKINS-25839 as Not A Defect $BEAKER_JOB_ID expanded to wrong value Caused by same env. variable defined on the slave and slave env. var is preferred. Not a bug in plugin itself, maybe Jenkins core can be reviewed and prefer contributed env. variable over local env. ones. Change By: vjuranek (01/Dec/14 9:45 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step-plugin] (JENKINS-25796) Cannot pass --link parameter to Start docker container step
vjuranek resolved JENKINS-25796 as Fixed Cannot pass --link parameter to Start docker container step Added in https://github.com/jenkinsci/docker-build-step-plugin/commit/7064f157cce7c79fcb91751b01d362f9b9eb828b Change By: vjuranek (30/Nov/14 7:39 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step-plugin] (JENKINS-25692) Incompatibility with docker-plugin?
vjuranek commented on JENKINS-25692 Incompatibility with docker-plugin? IMHO docker-java PR #102 won't help as the problem with ClientBuilder is caused by different version of jersey-client (2.11 in docker-java, 2.5.1 in jDocker). As both plugins use very similar docker library (forked from same project), we can expect similar issue in the future even if this one is fixed. Both plugins needs to use non-conflicting dependencies or Jenkins core has to implement proper class loader isolation of the plugins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step-plugin] (JENKINS-25745) Ensure DOCKER_CONTAINER_IDS contains unique IDs
vjuranek resolved JENKINS-25745 as Fixed Ensure DOCKER_CONTAINER_IDS contains unique IDs Should be fixed by PR #19 Change By: vjuranek (25/Nov/14 2:21 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-25392) Post Build Steps still running regardless of Pre Step Groovy Script failure
vjuranek commented on JENKINS-25392 Post Build Steps still running regardless of Pre Step Groovy Script failure Sorry, not yet. Hopefully with get to it today evening or tomorrow. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-25392) Post Build Steps still running regardless of Pre Step Groovy Script failure
vjuranek commented on JENKINS-25392 Post Build Steps still running regardless of Pre Step Groovy Script failure Hi, I wrote a test which verifies that build fails when exception is thrown from groovy script. Test is passing, so IMHO this is really not an issue in groovy plugin itself, but in a component which wraps groovy script (and probably ignores error status of groovy step). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-25392) Post Build Steps still running regardless of Pre Step Groovy Script failure
vjuranek commented on JENKINS-25392 Post Build Steps still running regardless of Pre Step Groovy Script failure Hi, what I can do (I actually already did so, but will double check) is to verify that when exception is thrown (and is not caught) in the groovy script, groovy build step will return non-zero value from perform method. How this exit code is handled by other Jenkins parts (like maven plugin), cannot be effected by groovy plugin. However, I'll double check and confirm here, that groovy plugin return non-zero value from perform method when exception is thrown. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-9130) Add a dynamic parser to colorize and indent groovy textareas
vjuranek resolved JENKINS-9130 as Fixed Add a dynamic parser to colorize and indent groovy textareas Closing as syntax highlighting is already present in groovy plugin (actually for pretty long time, since rel. 1.15) Change By: vjuranek (10/Nov/14 7:23 PM) Status: Open Resolved Assignee: LucieVotypkova vjuranek Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-25392) Post Build Steps still running regardless of Pre Step Groovy Script failure
vjuranek commented on JENKINS-25392 Post Build Steps still running regardless of Pre Step Groovy Script failure Hi, groovy plugin preserves the contract of BuildStep#perform method, see groovy.java L117. I'm afraind there won't be any update unless you provide more details why you think this is a bug in groovy plugin or move it to the right component. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-25500) Cannot save the job after removing Groovy build step
vjuranek resolved JENKINS-25500 as Cannot Reproduce Cannot save the job after removing Groovy build step obviously some issue in my dev environment (when plugin run via mvn hpi:run). Cannot reproduce on regular Jenkins as well. Daniel Beck thanks for looking. Change By: vjuranek (08/Nov/14 6:47 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-25455) Code input field is too small
vjuranek commented on JENKINS-25455 Code input field is too small radiobox makes this element invisible and when CodeMirror computes height of the element it's zero (as element is not visible). Also gutter gets somehow broken during making it invisible and visible process. IMHO proper fix is PR #1460, however, to fix it soon (and for older Jenkins core version), I decided to pre-select StringScriptSource by default when adding new step and thus make it visible at the beginning. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-25500) Cannot save the job after removing Groovy build step
vjuranek created JENKINS-25500 Cannot save the job after removing Groovy build step Issue Type: Bug Assignee: vjuranek Components: groovy-plugin Created: 07/Nov/14 10:22 PM Description: After removing the Groovy build step, job configuration cannot be saved. There's no exception in server log in in the UI. Project: Jenkins Priority: Critical Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-25392) Post Build Steps still running regardless of Pre Step Groovy Script failure
vjuranek commented on JENKINS-25392 Post Build Steps still running regardless of Pre Step Groovy Script failure Hi, groovy plugin itself doesn't provide any pre-build actions. I guess that you use M2 Extra Steps Plugin (Jenkins core 1.433) or Jenkins core functionality. Please move this bug to appropriate component (m2-extra-steps-plugin or maven-plugin) according to the version you use. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step] (JENKINS-24551) Docker URL contains invalid version information
vjuranek resolved JENKINS-24551 as Fixed Docker URL contains invalid version information Should be fixed by PR #15, thanks to Harald Albers. Change By: vjuranek (01/Oct/14 7:42 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [ws-cleanup] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
vjuranek commented on JENKINS-24824 Asynchronous cleanup not removing renamed workspace directories on slaves Hi, any idea how to reproduce it? Everything works fine on my machine. Do you use any "Advanced" options? If so, which one? What is the OS of the slave where ws is not deleted? Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [radargun] (JENKINS-24795) Kill previous instances of RG
vjuranek created JENKINS-24795 Kill previous instances of RG Issue Type: New Feature Assignee: vjuranek Components: radargun Created: 22/Sep/14 10:34 AM Description: see https://github.com/vjuranek/radargun-plugin/issues/4 Project: Jenkins Priority: Major Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [radargun] (JENKINS-24797) Automatically add log4j configuration
vjuranek created JENKINS-24797 Automatically add log4j configuration Issue Type: New Feature Assignee: vjuranek Components: radargun Created: 22/Sep/14 10:36 AM Description: see https://github.com/vjuranek/radargun-plugin/issues/7 Project: Jenkins Priority: Major Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [radargun] (JENKINS-24796) Run RG in workspace as working directory
vjuranek created JENKINS-24796 Run RG in workspace as working directory Issue Type: New Feature Assignee: vjuranek Components: radargun Created: 22/Sep/14 10:35 AM Description: see https://github.com/vjuranek/radargun-plugin/issues/5 Project: Jenkins Priority: Major Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [radargun] (JENKINS-24801) JVM args are not expanded
vjuranek created JENKINS-24801 JVM args are not expanded Issue Type: Bug Assignee: vjuranek Components: radargun Created: 22/Sep/14 12:28 PM Description: Default and node specific JVM args are not expanded. Project: Jenkins Priority: Major Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [radargun] (JENKINS-24784) Build doesn't terminate properly when interrupted
vjuranek created JENKINS-24784 Build doesnt terminate properly when interrupted Issue Type: Bug Assignee: vjuranek Components: radargun Created: 20/Sep/14 7:50 PM Description: When the build is interrupted, in console it show ERROR: null, all actions (master and slaves) show to be in progress and probably most important it that master as well as slaves keep running. Project: Jenkins Priority: Major Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy] (JENKINS-24757) Allow spaces in script parameters
vjuranek created JENKINS-24757 Allow spaces in script parameters Issue Type: New Feature Assignee: vjuranek Components: groovy Created: 18/Sep/14 9:25 AM Description: Similar to JENKINS-23617, allow parameters also in Script parameters option Project: Jenkins Priority: Major Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy] (JENKINS-23617) Cannot use spaces in groovy script parameters
vjuranek commented on JENKINS-23617 Cannot use spaces in groovy script parameters @nigel_charman: there are two parameters options, Groovy parameters - parameter for groovy executable and Script parameters - parameters for script. It was implemented only for the first one, Groovy parameters. I've created JENKINS-24757 for allowing spaces also in Script parameters. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step] (JENKINS-24071) Docker build step tries to build on master and not slave
vjuranek reopened JENKINS-24071 Docker build step tries to build on master and not slave Sorry, it wasn't intended to resolve this issue (I just reverted previous commit which makes it potentially even worse) Change By: vjuranek (11/Sep/14 8:02 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [radargun] (JENKINS-24588) Pass -slaveIndex to slaves
vjuranek created JENKINS-24588 Pass -slaveIndex to slaves Issue Type: Bug Assignee: vjuranek Components: radargun Created: 04/Sep/14 7:44 PM Description: https://github.com/vjuranek/radargun-plugin/issues/3 Project: Jenkins Priority: Major Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [radargun] (JENKINS-24588) Pass -slaveIndex to slaves
vjuranek resolved JENKINS-24588 as Fixed Pass -slaveIndex to slaves Done in https://github.com/jenkinsci/radargun-plugin/commit/665aabb34bdfd11fd40dd6427f5333404a5444ce Change By: vjuranek (04/Sep/14 8:33 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [radargun] (JENKINS-24545) Node list from file
vjuranek created JENKINS-24545 Node list from file Issue Type: New Feature Assignee: vjuranek Components: radargun Created: 02/Sep/14 8:23 PM Description: See https://github.com/vjuranek/radargun-plugin/issues/6 Project: Jenkins Priority: Major Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [radargun] (JENKINS-24496) Build-in start up scripts doesn't work on some instances
vjuranek commented on JENKINS-24496 Build-in start up scripts doesnt work on some instances @danielback thanks for a pointer! I wasn't aware about change This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [radargun] (JENKINS-24495) JVM args are not passed correctly
vjuranek created JENKINS-24495 JVM args are not passed correctly Issue Type: Bug Assignee: vjuranek Components: radargun Created: 28/Aug/14 10:08 PM Description: JVM args are appended to the executed script, however default RG script doesn't support it in this way. Project: Jenkins Priority: Major Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [radargun] (JENKINS-24496) Build-in start up scripts doesn't work on some instances
vjuranek created JENKINS-24496 Build-in start up scripts doesnt work on some instances Issue Type: Bug Assignee: vjuranek Components: radargun Created: 28/Aug/14 10:13 PM Description: Jar file with classes and resources is not unpacked on some deployments and thus build-in scripts are not available Project: Jenkins Priority: Major Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
vjuranek resolved JENKINS-23693 as Fixed Cannot delete workspace Hopefully fixed by PR #18, fixed is contained in 0.23 released right now. If the issue is still present, please reopen. Change By: vjuranek (26/Aug/14 1:05 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step] (JENKINS-23704) Control over ports with docker build steps
vjuranek resolved JENKINS-23704 as Fixed Control over ports with docker build steps thanks. OK, closing then Change By: vjuranek (20/Aug/14 2:44 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step] (JENKINS-23704) Control over ports with docker build steps
vjuranek commented on JENKINS-23704 Control over ports with docker build steps Hi, I added two evn. variables: DOCKER_HOST_BIND_PORTS - containes comma separated list of ports to which are bound docker container ports DOCKER_HOST_PORT_$SCHEMA_$PORT - which docker conatiner port is bound to this port (e.g. DOCKER_HOST_PORT_TCP_80 would conatin value 8080 in case that conatiner port 8080 is bound to port 80 on host) Is this what you need? Any suggestion before I release it what to better, to be more user friendly? Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step] (JENKINS-24154) Cannot ping REST endpoint (after upgrade)
vjuranek resolved JENKINS-24154 as Fixed Cannot ping REST endpoint (after upgrade) JENKINS-24156 is implemented and will be in the next release, closing. Change By: vjuranek (15/Aug/14 8:47 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step] (JENKINS-22985) Fork of docker-java under jenkins namespace?
vjuranek resolved JENKINS-22985 as Fixed Fork of docker-java under jenkins namespace? Plugin has already switched to docker-java, closing. Change By: vjuranek (15/Aug/14 8:49 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step] (JENKINS-24156) Option for Docker client version
vjuranek
created JENKINS-24156
Option for Docker client version
Issue Type:
New Feature
Assignee:
vjuranek
Components:
docker-build-step
Created:
07/Aug/14 5:30 PM
Description:
Add option for configuration docker client version in global Jenkins configuration, which would overwrite default docker client version. It should use {.docker.io.properties} only as a fall back.
Project:
Jenkins
Priority:
Major
Reporter:
vjuranek
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google 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] [docker-build-step] (JENKINS-24156) Option for Docker client version
vjuranek
updated JENKINS-24156
Option for Docker client version
Change By:
vjuranek
(07/Aug/14 5:32 PM)
Description:
AddoptionforconfigurationdockerclientversioninglobalJenkinsconfiguration,whichwouldoverwritedefaultdockerclientversion.Itshoulduse{
{
.docker.io.properties}
}
onlyasafallback.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google 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] [docker-build-step] (JENKINS-24154) Cannot ping REST endpoint (after upgrade)
vjuranek
commented on JENKINS-24154
Cannot ping REST endpoint (after upgrade)
Hi,
do you see any exception like this in log?
client and server don't have same version (client : 1.13, server: 1.12)
By default version 1.13 is used. I create JENKINS-24156 to allow configure Docker client version from Jenkins.
If this is the root cause of this issue, until JENKINS-24156 is implemented, you can use ${user.home}/.docker.io.properties with following content as a workaround
docker.io.version=1.12
docker.io.readTimeout=1000
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google 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] [docker-build-step] (JENKINS-24043) envvars not resolved for 'wait for ports' field
vjuranek commented on JENKINS-24043 envvars not resolved for wait for ports field Hi, should be fixed now. However, it seems to me, that you use $DOCKER_CONTAINER_IDS in little different way than it was intended. It can be expanded in Container ID(s) field, however, it was intended rather to provide real container ID in this field and once the container is started, it will create $DOCKER_CONTAINER_IDS env. variable which is intended to be used in other build steps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step] (JENKINS-23704) Control over ports with docker build steps
vjuranek reopened JENKINS-23704 Control over ports with docker build steps Reopening - I forgot to implement exporting ports as evn. vars. Change By: vjuranek (03/Aug/14 8:03 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
vjuranek commented on JENKINS-23693 Cannot delete workspace I've just released ws-clenaup 0.22 which contains small fix for expanding env. var. on nodes and may be related to this issue. Could you please try it and let me know if it fixes the issue? If not, could anyone provide a reproducer for this issue? Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy] (JENKINS-23997) Unable to specify multiple jars on classpath for a system groovy script
vjuranek
commented on JENKINS-23997
Unable to specify multiple jars on classpath for a system groovy script
Hi Ben,
yes, this is a standard way how to let plugin developer know that there is a bug/missing feature.
And yes, this is a bug, at least text in the help is misleading as the input doesn't allow enter multiple lines. What should work is to specify all jars on one like, separated by class path separator (":" on linux, ";" on windows), e.g.
/path/to/jar1:/path/to/jar2
I'll fix either help test or add a field which allow multiple lines (probably the later to be compatible with groovy setup)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google 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] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
vjuranek commented on JENKINS-23693 Cannot delete workspace There's one small fix related to how env. variables are expanded. Could someone how is able to reproduce this issue try to check, if this change fixes the problem? Any further details how to reproduce the issue will be more than welcome. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-build-step] (JENKINS-23733) Error in saving Jenkins system configuration due to empty Docker REST URL
vjuranek commented on JENKINS-23733 Error in saving Jenkins system configuration due to empty Docker REST URL I agree plugin shouldn't disallow you to make and save any changes, I'll remove this check. But still curious what is the use case for empty Docker URL - as the plugin uses only REST API, IMHO you should either setup Docker URL to be able to use it or you don't need this plugin, as it won't work anyway This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
vjuranek commented on JENKINS-23693 Cannot delete workspace thanks for double check. I'll go through the code once again and try to figure out the reason how this can happen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
vjuranek commented on JENKINS-23693 Cannot delete workspace quickly looking into the code, it would probably result into behavior described in this issue, but IMHO this should never happen, as env. var. expansion should return null for null param: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/Util.java#L143 Anyway, will check it more carefully in the eventing. Thanks for good pointer! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
vjuranek commented on JENKINS-23693 Cannot delete workspace Hi,could you please share your configuration of the plugin? Do you use external program for cleanup? Looks like it's trying to use external program for cleanup and for some reason it wants to use workspace/SD-2893/APPLICATION/artifacts which obviously has to fail. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy] (JENKINS-23617) Cannot use spaces in groovy script parameters
vjuranek resolved JENKINS-23617 as Fixed Cannot use spaces in groovy script parameters Merged into master branch and released in 1.19. Change By: vjuranek (07/Jul/14 6:46 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
vjuranek commented on JENKINS-23693 Cannot delete workspace Thanks for details. Unfortunately, I'm not able to reproduce it: I used your config with ws-cleanup 0.20, it worked, then upgraded to 0.21 and it still works. Anyway, from log record Using command: ... is obvious, that method handling externalDelete is called. Could you please check once again, that you job configs don't contain any externalDelete (e.g. there is only externalDelete/ element without any content)? Right now I have no idea how externalDelete/ can be interpreted as not to be null Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy] (JENKINS-23617) Cannot use spaces in groovy script parameters
vjuranek reopened JENKINS-23617 Cannot use spaces in groovy script parameters ups, not intended to close it... Due to lack of time I didn't tested any other libraries and use proposed commons-exec, however this lib is IMHO far from perfect as it e.g. doesn't handle backslashed spaces (e.g. -cp /path/to/my\ groovy/libs splits into 3 args), but this is not subject of this issue and PR should be sent against used library. @enterit - please test JENKINS-23617 branch if it fixes your usecase, if yes I'll marge it to main branch and release Change By: vjuranek (06/Jul/14 8:42 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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.
