[JIRA] (JENKINS-15001) Repository cache is wrong on slave nodes
Title: Message Title Johannes W commented on JENKINS-15001 Re: Repository cache is wrong on slave nodes I now have a workaround for this: It works when no absolute path is used for hg in the master and all slaves, so just "hg" instead of "/usr/local/bin/hg" or "C:\Program Files\TortoiseHg\hg.exe". Of course that means every slave needs to have "hg" in the PATH. This of course does not mean that this bug is fixed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-33205) Post-send script setting disappears when saving job configuration
Title: Message Title Johannes Weißl assigned an issue to Alex Earl Jenkins / JENKINS-33205 Post-send script setting disappears when saving job configuration Change By: Johannes Weißl Assignee: Johannes Weißl Alex Earl 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] [email-ext-plugin] (JENKINS-33205) Post-send script setting disappears when saving job configuration
Title: Message Title Johannes Weißl commented on JENKINS-33205 Re: Post-send script setting disappears when saving job configuration See https://github.com/jenkinsci/email-ext-plugin/pull/132 for a patch. 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] [email-ext-plugin] (JENKINS-30854) Support AWS SES Message IDs for In-Reply-To header
Title: Message Title Johannes Weißl commented on JENKINS-30854 Re: Support AWS SES Message IDs for In-Reply-To header Bug with the post-send script feature in JENKINS-33205. 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] [email-ext-plugin] (JENKINS-33205) Post-send script setting disappears when saving job configuration
Title: Message Title Johannes Weißl created an issue Jenkins / JENKINS-33205 Post-send script setting disappears when saving job configuration Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 28/Feb/16 9:02 PM Environment: Jenkins 1.642.2 and email-ext 2.41.3 Priority: Minor Reporter: Johannes Weißl As reported by kramarz in pull request jenkinsci/email-ext-plugin#109: The post-send script setting, introduced in JENKINS-30854 , disappears when saving job configuration. A workaround is to directly edit the config.xml job configuration file and include the following line after the line: $DEFAULT_POSTSEND_SCRIPT Afterwards select "Reload Configuration from Disk" from "Manage Jenkins".
[JIRA] [email-ext-plugin] (JENKINS-30854) Support AWS SES Message IDs for In-Reply-To header
Title: Message Title Johannes Weißl commented on JENKINS-30854 Re: Support AWS SES Message IDs for In-Reply-To header I added a paragraph to https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+Recipes#Email-extRecipes-PostsendScripts 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] [email-ext-plugin] (JENKINS-30854) Support AWS SES Message IDs for In-Reply-To header
Title: Message Title Johannes Weißl commented on JENKINS-30854 Re: Support AWS SES Message IDs for In-Reply-To header Thanks a lot! 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] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title Johannes Weißl commented on JENKINS-26493 Re: Use new EC2 API endpoint hostnames @Manuel Stadelmann: I had the same problem with aws-java-sdk and with the 401 error. But I discovered that in my case it was not the fault of the ec2-plugin: While the IAM credentials worked with aws-cli from my laptop, I got the same 401 error when using the aws-cli from the EC2 instance where Jenkins was running. Can you confirm if you experience the same behavior? 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] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title Johannes Weißl commented on JENKINS-26493 Re: Use new EC2 API endpoint hostnames Any updates? I tested my pull request #167 now and it works for me. 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] [build-blocker-plugin] (JENKINS-31002) Add ability to block build if other jobs are not in successful state
Title: Message Title Johannes Weißl created an issue Jenkins / JENKINS-31002 Add ability to block build if other jobs are not in successful state Issue Type: Improvement Assignee: Unassigned Components: build-blocker-plugin Created: 17/Oct/15 7:17 PM Priority: Minor Reporter: Johannes Weißl Would you accept a patch to add the option of blocking new builds if other jobs are not in an successful state (additionally to the block when they are currently running)? Add Comment
[JIRA] [email-ext-plugin] (JENKINS-30854) Support AWS SES Message IDs for In-Reply-To header
Title: Message Title
Johannes Weißl updated an issue
Jenkins / JENKINS-30854
Support AWS SES Message IDs for In-Reply-To header
Change By:
Johannes Weißl
The Amazon Simple Email Service ([AWS SES|https://aws.amazon.com/ses/]) rewrites the Message-ID header of outgoing emails. That means subsequent failure/success notifications will not be in the same thread, because they reference a non-existing message id in the In-Reply-To header.The rewritten message id is returned as last message of the SMTP transaction, e.g.{noformat}250 Ok <0123456abcde-1234abcd-abcd-1234-1234-1234abcd1234-000...@eu-west-1.amazonses.com>{noformat}http://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-response-codes.htmlI have written a [proof-of-concept patch|https://github.com/weisslj/email-ext-plugin/commit/ea00c77afa8c151e2ee8931ccf99cad5f0286b73] that updates the rewritten message id in case AWS SES is used for sending mails.Would you be willing to accept such a patch? It is kind of ugly to include provider-specific code like this, but it has no downside for people not using AWS SES and can probably be encapsulated to so that it doesn't get in the way.
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] [email-ext-plugin] (JENKINS-30854) Support AWS SES Message IDs for Reply-To header
Title: Message Title Johannes Weißl created an issue Jenkins / JENKINS-30854 Support AWS SES Message IDs for Reply-To header Issue Type: Improvement Assignee: Alex Earl Components: email-ext-plugin Created: 08/Oct/15 10:57 PM Priority: Minor Reporter: Johannes Weißl The Amazon Simple Email Service (AWS SES) rewrites the Message-ID header of outgoing emails. That means subsequent failure/success notifications will not be in the same thread, because they reference a non-existing message id in the In-Reply-To header. The rewritten message id is returned as last message of the SMTP transaction, e.g. 250 Ok <0123456abcde-1234abcd-abcd-1234-1234-1234abcd1234-000...@eu-west-1.amazonses.com> http://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-response-codes.html I have written a proof-of-concept patch that updates the rewritten message id in case AWS SES is used for sending mails. Would you be willing to accept such a patch? It is kind of ugly to include provider-specific code like this, but it has no downside for people not using AWS SES and can probably be encapsulated to that it doesn't get in the way.
[JIRA] [email-ext-plugin] (JENKINS-30854) Support AWS SES Message IDs for In-Reply-To header
Title: Message Title Johannes Weißl updated an issue Jenkins / JENKINS-30854 Support AWS SES Message IDs for In-Reply-To header Change By: Johannes Weißl Summary: Support AWS SES Message IDs for In- Reply-To header 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] [email-ext-plugin] (JENKINS-30854) Support AWS SES Message IDs for In-Reply-To header
Title: Message Title Johannes Weißl commented on JENKINS-30854 Re: Support AWS SES Message IDs for In-Reply-To header Thanks for your answer, I created the pull request. However, I don't see how this can be done via a pre-send script: The Message-ID is only known after the email is sent, and can only be obtained by the SMTPTransport object. 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] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title Johannes Weißl assigned an issue to Johannes Weißl Jenkins / JENKINS-26493 Use new EC2 API endpoint hostnames Change By: Johannes Weißl Assignee: Francis Upton Johannes Weißl 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] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title Johannes Weißl assigned an issue to Francis Upton Jenkins / JENKINS-26493 Use new EC2 API endpoint hostnames Change By: Johannes Weißl Assignee: Johannes Weißl Francis Upton 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] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title Johannes Weißl commented on JENKINS-26493 Re: Use new EC2 API endpoint hostnames Sorry for changing the assignee by mistake. I too have this problem with 1.29. Here is my take on a pull request: https://github.com/jenkinsci/ec2-plugin/pull/167 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] [mercurial-plugin] (JENKINS-25523) Multiple SCMs Plugin doesn't work with Mercurial plugin 1.51
Johannes Weißl commented on JENKINS-25523 Multiple SCMs Plugin doesnt work with Mercurial plugin 1.51 I can confirm this, the bug disappeared after an upgrade to Mercurial plugin 1.52 (from 1.51) and Multiple SCMs plugin 0.4 (from 0.3). Jenkins version: 1.580.3 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] [claim-plugin] (JENKINS-27194) Claim report should optionally list all unclaimed failed builds
Johannes Weißl created JENKINS-27194 Claim report should optionally list all unclaimed failed builds Issue Type: New Feature Assignee: Christian Bremer Components: claim-plugin Created: 02/Mar/15 3:15 PM Description: It would be very helpful if there would be a report (in http://host/claims/ or another page) to view all unclaimed failed builds, even the ones which have successfully built in the meantime. Reasons would be: Randomized test cases, which bring up important corner case bugs, but do not fail very often (and not reproducible). Non-reproducible errors in test cases (due to network timeouts, race conditions, etc.), which should be fixed by making the test case more stable. Of course failed builds before the claim-plugin was installed and activated should be excluded from this report. Project: Jenkins Priority: Major Reporter: Johannes Weißl 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] (JENKINS-15001) Repository cache is wrong on slave nodes
Johannes Weißl commented on JENKINS-15001 Repository cache is wrong on slave nodes I can confirm this bug the other way round (Debian GNU/Linux 7.0 Master, Windows 7 Slave). 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
