[JIRA] (JENKINS-56322) URL validation breaks when inside private LAN
Title: Message Title hugo fonseca created an issue Jenkins / JENKINS-56322 URL validation breaks when inside private LAN Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2019-02-28 11:15 Priority: Blocker Reporter: hugo fonseca You don't need a valid FQDN inside private Lan networks. E.g. because we have everything locally available and locked out from the outside our Jenkins address is "jenkins" and it is perfectly valid for Bitbucket server API. You are checking for the existence of a . (dot) to verify the URL and it is breaking our process since it isn't publishing the build status. The following error appears: Can not determine Jenkins root URL or Jenkins URL is not a valid URL regarding Bitbucket API. Commit status notifications are disabled until a root URL is configured in Jenkins global configuration. We traced down the error and created our own version of the plugin editing the method "checkURL" from the BitbucketBuildStatusNotifications.java file which does not make the dot check and it works perfectly. Please take a look at this as it is blocking us from future updates of this plugin.
[JIRA] (JENKINS-36421) Expose some Pull Request/Branch attributes as Environment Variables
Title: Message Title hugo fonseca commented on JENKINS-36421 Re: Expose some Pull Request/Branch attributes as Environment Variables I understand. Just to make my point clear before we close this, let me explain what I would like to have: I want to publish notifications (email for example) when a build fails. On that email I want to add information about which pull request the build refers too and its author (I'm only working with pull requests) AFAIK Jenkins is receiving a webhook containing all that information https://confluence.atlassian.com/bitbucket/event-payloads-740262817.html#EventPayloads-PullRequestEvents Technically it should be possible to get that information from my pipeline script (without having to hack). Yet, I'm not fully aware of how the pipeline script work internally neither how this plugin is built and I still haven't look into it, but in theory I'm not asking anything weird. But please, enlighten me and feel free to close 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.
[JIRA] (JENKINS-36421) Expose some Pull Request/Branch attributes as Environment Variables
Title: Message Title hugo fonseca commented on JENKINS-36421 Re: Expose some Pull Request/Branch attributes as Environment Variables I'm sorry you mean that github-branch-source-plugin wont provide such variables (and being so we can close this) or that it is just currently not providing them? 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-36421) Expose some Pull Request/Branch attributes as Environment Variables
Title: Message Title hugo fonseca created an issue Jenkins / JENKINS-36421 Expose some Pull Request/Branch attributes as Environment Variables Issue Type: New Feature Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Jul/04 5:08 PM Priority: Major Reporter: hugo fonseca It would be very nice if we could use expose some variables just like github is doing. Environment Variables such as: bbprbActualCommit bbprbActualCommitAuthor bbprbActualCommitAuthorEmail bbprbPullDescription bbprbPullId bbprbPullLink bbprbPullTitle bbprbSourceBranch bbprbTargetBranch sha1 Add Comment
[JIRA] (JENKINS-36307) "Can not read hook payload" exception whenever a hook is received
Title: Message Title hugo fonseca created an issue Jenkins / JENKINS-36307 "Can not read hook payload" exception whenever a hook is received Issue Type: Bug Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Jun/29 8:54 AM Priority: Minor Reporter: hugo fonseca Can not read hook payload org.codehaus.jackson.map.JsonMappingException: Can not construct instance of com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRepository, problem: abstract types can only be instantiated with additional type information at [Source: java.io.StringReader@7dd7306; line: 1, column: 345] (through reference chain: com.cloudbees.jenkins.plugins.bitbucket.client.events.BitbucketCloudPullRequestEvent["repository"]) at org.codehaus.jackson.map.JsonMappingException.from(JsonMappingException.java:163) at org.codehaus.jackson.map.deser.StdDeserializationContext.instantiationException(StdDeserializationContext.java:233) at org.codehaus.jackson.map.deser.AbstractDeserializer.deserialize(AbstractDeserializer.java:60) at org.codehaus.jackson.map.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:299) at org.codehaus.jackson.map.deser.SettableBeanProperty$MethodProperty.deserializeAndSet(SettableBeanProperty.java:414) at org.codehaus.jackson.map.deser.BeanDeserializer.deserializeFromObject(BeanDeserializer.java:697) at org.codehaus.jackson.map.deser.BeanDeserializer.deserialize(BeanDeserializer.java:580) at org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2732) at org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1863) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudWebhookPayload.parse(BitbucketCloudWebhookPayload.java:65) at
[JIRA] [ec2-plugin] (JENKINS-26531) Slave does not start if the temp dir is not set to anything after upgrade to 1.25
hugo fonseca commented on JENKINS-26531 Slave does not start if the temp dir is not set to anything after upgrade to 1.25 Thank you @Francis and sorry the delay. Great job BTW. 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] [ec2-plugin] (JENKINS-26531) Weird Could not find /init.sh after update
hugo fonseca commented on JENKINS-26531 Weird Could not find /init.sh after update Node dem (i-cc)(i-cc) is still pending/launching, waiting 5s Node dem (i-cc)(i-) is ready Connecting to ec2.compute-1.amazonaws.com on port 22, with timeout 1. Waiting for SSH to come up. Sleeping 5. Connected via SSH. bootstrap() Getting keypair... Using key: dom Authenticating as dam take over connection Creating tmp directory () if it does not exist mkdir: missing operand Try `mkdir --help' for more information. Executing init script bash: /init.sh: No such file or directory init script failed: exit code=127 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] [ec2-plugin] (JENKINS-26531) Weird Could not find /init.sh after update
hugo fonseca commented on JENKINS-26531 Weird Could not find /init.sh after update Jenkins 1.580.2 Amazon EC2 plugin 1.25 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] [ec2-plugin] (JENKINS-26531) Weird Could not find /init.sh after update
hugo fonseca commented on JENKINS-26531 Weird Could not find /init.sh after update Ubuntu slave No fancy configurations. Almost default. 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] [ec2-plugin] (JENKINS-26531) Weird Could not find /init.sh after update
hugo fonseca commented on JENKINS-26531 Weird Could not find /init.sh after update No stacktrace at Jenkins log. 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] [ec2-plugin] (JENKINS-26531) Weird Could not find /init.sh after update
hugo fonseca commented on JENKINS-26531 Weird Could not find /init.sh after update If I set temp dir it works. Maybe some "null - empty string" 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] [ec2-plugin] (JENKINS-26531) Weird Could not find /init.sh after update
hugo fonseca created JENKINS-26531 Weird Could not find /init.sh after update Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 21/Jan/15 2:44 PM Project: Jenkins Priority: Blocker Reporter: hugo fonseca 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] [ec2-plugin] (JENKINS-26531) Weird Could not find /init.sh after update
hugo fonseca updated JENKINS-26531 Weird Could not find /init.sh after update Change By: hugo fonseca (21/Jan/15 2:48 PM) Description: AfterupdatingthepluginIcannolongerprovisionEC2machines.ItconnectswithsuccessbutitfailswithCouldnotfind/init.shIvefixedbyrevertingtopreviousversion. 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] [build-failure-analyzer] (JENKINS-17658) Provide a token so that build failure causes can be included in build failure emails
hugo fonseca commented on JENKINS-17658 Provide a token so that build failure causes can be included in build failure emails No, I still haven't found the solution for this. I tried something like: http://jenkins-ci.361315.n4.nabble.com/Build-Failure-Analyzer-Email-Ext-td4720692.html and when I try the "Email template testing" it works fine but since in the real build the scan is triggered after the email being sent it does not work. :/ 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] [build-failure-analyzer] (JENKINS-17658) Provide a token so that build failure causes can be included in build failure emails
hugo fonseca commented on JENKINS-17658 Provide a token so that build failure causes can be included in build failure emails I've being struggling to get this token in my groovy template. Anyone knows how can I get this token from there? Sorry if this is not the right place for this question. I'm newbie at it and this is the first time I ask something here. 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] [ruby-runtime] (JENKINS-18311) Jenkins 1.518 fails to load plugin ruby-runtime
hugo fonseca commented on JENKINS-18311 Jenkins 1.518 fails to load plugin ruby-runtime +1 here is failing too: hudson.util.IOException2: Failed to dynamically deploy this plugin at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1314) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Caused by: hudson.util.IOException2: Failed to install ruby-runtime plugin at hudson.PluginManager.dynamicLoad(PluginManager.java:417) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1310) ... 7 more Caused by: hudson.util.IOException2: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:371) at hudson.PluginManager.dynamicLoad(PluginManager.java:408) ... 8 more Caused by: java.lang.NullPointerException at java.lang.Class.isAssignableFrom(Native Method) at org.jenkinsci.jruby.JavaProxyConverter.canConvert(JavaProxyConverter.java:43) at com.thoughtworks.xstream.core.DefaultConverterLookup.registerConverter(DefaultConverterLookup.java:68) at com.thoughtworks.xstream.XStream.registerConverter(XStream.java:1293) at com.thoughtworks.xstream.XStream.registerConverter(XStream.java:1288) at org.jenkinsci.jruby.JRubyXStream.register(JRubyXStream.java:26) at ruby.RubyRuntimePlugin.initRubyXStreams(RubyRuntimePlugin.java:46) at ruby.RubyRuntimePlugin.start(RubyRuntimePlugin.java:28) at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:379) at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:368) ... 9 more I was just trying to install vagrant plugin which is ruby-runtime dependent. 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/groups/opt_out.
[JIRA] [ruby-runtime] (JENKINS-18311) Jenkins 1.518 fails to load plugin ruby-runtime
hugo fonseca edited a comment on JENKINS-18311 Jenkins 1.518 fails to load plugin ruby-runtime +1 here is failing too 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/groups/opt_out.
