[JIRA] (JENKINS-56221) github-sqs-plugin fails with blueocean > 1.10.1
Title: Message Title Idikoro Eradiri updated an issue Jenkins / JENKINS-56221 github-sqs-plugin fails with blueocean > 1.10.1 Change By: Idikoro Eradiri after upgrading to blueocean to 1.10.2, the github-sqs-plugin:2.1 stopped pulling github messages off of the SQS queue. We use the github-sqs-plugin to receive github webhooks from behind our firewall. We also use an IAM role, so we don't hard code the AWS creds. When I roll back to the previous docker image with blueocean:1.10.1, The github-sqs-plugin:2.1 receives messages from the SQS queue successfully. Unfortunately I'm not seeing any exceptions in the Jenkins logs related to the sqs plugin, this issue seems to happen silently.Right now we are stuck on blueocean 1.10.1 & I cannot upgrade our jenkins instance or plugins until this issue is resolved. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56221) github-sqs-plugin fails with blueocean > 1.10.1
Title: Message Title Idikoro Eradiri created an issue Jenkins / JENKINS-56221 github-sqs-plugin fails with blueocean > 1.10.1 Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin, github-sqs-plugin Created: 2019-02-20 18:55 Environment: jenkins:2.150.2-alpine docker image blueocean:1.10.2 swarm:3.15 matrix-auth:2.3 job-dsl:1.71 github:1.29.2 prometheus:2.0.0 htmlpublisher:1.18 workflow-aggregator:2.5 junit:1.26.1 slack:2.4 timestamper:1.8.10 github-sqs-plugin:2.1 lockable-resources:2.4 saml:1.1.2 github-oauth:0.31 github-pr-coverage-status:2.0.0 Priority: Minor Reporter: Idikoro Eradiri after upgrading to blueocean to 1.10.2, the github-sqs-plugin:2.1 stopped pulling github messages off of the SQS queue. We use the github-sqs-plugin to receive github webhooks from behind our firewall. When I roll back to the previous docker image with blueocean:1.10.1, The github-sqs-plugin:2.1 receives messages from the SQS queue successfully. Unfortunately I'm not seeing any exceptions in the Jenkins logs related to the sqs plugin, this issue seems to happen silently. Right now we are stuck on blueocean 1.10.1 & I cannot upgrade our jenkins instance or plugins until this issue is resolved.
[JIRA] (JENKINS-47783) parallel stages are displayed as passed even when they are not executed
Title: Message Title Idikoro Eradiri commented on JENKINS-47783 Re: parallel stages are displayed as passed even when they are not executed confirmed it's fixed in 1.5.0 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-47783) parallel stages are displayed as passed even when they are not executed
Title: Message Title Idikoro Eradiri resolved as Fixed Jenkins / JENKINS-47783 parallel stages are displayed as passed even when they are not executed Change By: Idikoro Eradiri Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-47783) parallel stages are displayed as passed even when they are not executed
Title: Message Title Idikoro Eradiri reopened an issue Jenkins / JENKINS-47783 parallel stages are displayed as passed even when they are not executed Change By: Idikoro Eradiri Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-47783) parallel stages are displayed as passed even when they are not executed
Title: Message Title Idikoro Eradiri commented on JENKINS-47783 Re: parallel stages are displayed as passed even when they are not executed Vivek Pandey James Dumay Is this fixed? I'm currenlty on Jenkins 2.89.4 and running blueocean 1.4.2 and I am still seeing the same issue. The sample pipeline script I posted above still shows parallel stages as passed even though they did not execute. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-35185) Trigger github multi-branch build via SQS
Title: Message Title
Idikoro Eradiri commented on JENKINS-35185
Re: Trigger github multi-branch build via SQS
the flow looks like this: github -> SNS -> SQS -> jenkins and this is the Jenkinsfile I used in my repo for the multibranch pipeline
pipeline {
agent any
triggers {
githubPush()
}
stages {
stage(do something') {
steps {
echo 'hello'
}
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google 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-35185) Trigger github multi-branch build via SQS
Title: Message Title Idikoro Eradiri commented on JENKINS-35185 Re: Trigger github multi-branch build via SQS Jesse Glick Stephen Connolly I can confirm that this branch of the plugin https://github.com/jenkinsci/github-sqs-plugin/pull/9 does indeed kick off Multibranch pipleline builds from messages received on SQS! I was able to get jenkins to read from SQS and trigger builds on a multi-branch pipeline that was created with the latest version of the BlueOcean UI. dThe Jenkins instances were both behind our corporate firewall. One was deployed on AWS and the other was on my local machine. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-35185) Trigger github multi-branch build via SQS
Title: Message Title Idikoro Eradiri edited a comment on JENKINS-35185 Re: Trigger github multi-branch build via SQS [~jglick] [~stephenconnolly] I can confirm that this branch of the plugin [https://github.com/jenkinsci/github-sqs-plugin/pull/9|http://example.com / ] does indeed kick off Multibranch pipleline builds from messages received on SQS! I was able to get jenkins to read from SQS and trigger builds on a multi-branch pipeline that was created with the latest version of the BlueOcean UI.!image-2017-03-23-17-44-21-564.png! dThe The Jenkins instances were both behind our corporate firewall. One was deployed on AWS and the other was on my local machine. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-35185) Trigger github multi-branch build via SQS
Title: Message Title Idikoro Eradiri updated an issue Jenkins / JENKINS-35185 Trigger github multi-branch build via SQS Change By: Idikoro Eradiri Attachment: image-2017-03-23-17-44-21-564.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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.
