[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Tim Huang edited a comment on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
I have more information on the matter - I was triggering downstream jobs within a `parallel` step (not sure if this has anything to do with it ) . In an earlier sequential stage, if I trigger another build job, it causes the ones in the parallel steps (that didn't show up before) to show up in the "Triggered Jobs" section. Below is my groovy script. In the first sequential stage there is a downstream no-op job I made that, when triggered, seems to make the "Triggered Jobs" section show up for the other two downstream jobs that are triggered in the parallel stages further down. Without the no-op job, the "Triggered Jobs" section won't show up for the other two. The formatting of this code won't paste right (missing newlines here and there), so apologies.{noformat}pipeline { agent none options { // Ideally, PRs build in less than 5 timeout(time: 15, unit: 'MINUTES') } environment { CI = 'true' AWS_ACCESS_KEY_ID = credentials('aws-access-key-id-test') AWS_SECRET_ACCESS_KEY = credentials('aws-secret-access-key-test') } stages { stage('Abort previous builds on PR') { steps {// Not sure how this works, but… https://stackoverflow.com/a/52811034milestone label: '', ordinal: Integer.parseInt(env.BUILD_ID) - 1milestone label: '', ordinal: Integer.parseInt(env.BUILD_ID)// NOTE: Triggering this no-op job makes all Triggered Builds show up!!!build 'Utilities/TriggeringThisInStepsMakesTriggeredBuildsShowUp' } } stage('PR tests') { failFast false parallel {stage('Linting & formatting') { agent { node { label 'Node' } } steps { script { pullRequest.createStatus(status: 'pending',context: 'Format & Syntax (backend)',description: 'Checking code quality…',targetUrl: env.RUN_DISPLAY_URL) try {sh '! git diff --name-only ^HEAD origin/trunk | grep "^backend"'echo "No changes found, skipping tests."pullRequest.createStatus(status: 'success', context: 'Format & Syntax (backend)', description: 'Skipped (no changes).') } catch (e) {echo "Changes found, running tests."ansiColor('xterm') { // Check for it-block .only() calls which skip all other // tests in a suite. These should NEVER be version-checked. sh "! git grep '\\'" sh 'rm -rf ./frontend' sh 'yarn' sh 'yarn eslint ./backend' sh 'yarn prettier -c "./backend/**/*.js"' pullRequest.createStatus(status: 'success', context: 'Format & Syntax (backend)', description: 'Squeaky clean! You win today.')} } } } post { failure { script {pullRequest.createStatus(status: 'failure', context: 'Format & Syntax (backend)', description: 'Wow, did you even look at how malformed your code is?', targetUrl: env.RUN_DISPLAY_URL) } } }}stage('Frontend tests') { agent { node { label 'Node' } } steps { script { pullRequest.createStatus(status: 'pending',context: 'Unit tests (frontend)',description: 'Making sure you didn\'t break anything…',targetUrl: env.RUN_DISPLAY_URL) try {sh '! git diff --name-only ^HEAD origin/trunk | grep "^frontend"'sh '! git diff --name-only ^HEAD origin/trunk | grep "^shared-utilities"'echo "No changes found, skipping tests."pullRequest.createStatus(status: 'success', context: 'Unit tests (frontend)', description: 'Skipped (n
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Tim Huang edited a comment on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
I have more information on the matter - I was triggering downstream jobs within a `parallel` step (not sure if this has anything to do with it). In an earlier sequential stage, if I trigger another downstream build job, it causes itself and the ones in the parallel steps (that didn't show up before) to show up in the their respective "Triggered Jobs" section sections . Below is my groovy script. In the first sequential stage there is a downstream no-op job I made that, when triggered, seems to make the "Triggered Jobs" section show up for the other two downstream jobs that are triggered in the parallel stages further down. Without the no-op job, the "Triggered Jobs" section won't show up for the other two. The formatting of this code won't paste right (missing newlines here and there), so apologies.{noformat}pipeline { agent none options { // Ideally, PRs build in less than 5 timeout(time: 15, unit: 'MINUTES') } environment { CI = 'true' AWS_ACCESS_KEY_ID = credentials('aws-access-key-id-test') AWS_SECRET_ACCESS_KEY = credentials('aws-secret-access-key-test') } stages { stage('Abort previous builds on PR') { steps {// Not sure how this works, but… https://stackoverflow.com/a/52811034milestone label: '', ordinal: Integer.parseInt(env.BUILD_ID) - 1milestone label: '', ordinal: Integer.parseInt(env.BUILD_ID)// NOTE: Triggering this no-op job makes all Triggered Builds show up!!!build 'Utilities/TriggeringThisInStepsMakesTriggeredBuildsShowUp' } } stage('PR tests') { failFast false parallel {stage('Linting & formatting') { agent { node { label 'Node' } } steps { script { pullRequest.createStatus(status: 'pending',context: 'Format & Syntax (backend)',description: 'Checking code quality…',targetUrl: env.RUN_DISPLAY_URL) try {sh '! git diff --name-only ^HEAD origin/trunk | grep "^backend"'echo "No changes found, skipping tests."pullRequest.createStatus(status: 'success', context: 'Format & Syntax (backend)', description: 'Skipped (no changes).') } catch (e) {echo "Changes found, running tests."ansiColor('xterm') { // Check for it-block .only() calls which skip all other // tests in a suite. These should NEVER be version-checked. sh "! git grep '\\'" sh 'rm -rf ./frontend' sh 'yarn' sh 'yarn eslint ./backend' sh 'yarn prettier -c "./backend/**/*.js"' pullRequest.createStatus(status: 'success', context: 'Format & Syntax (backend)', description: 'Squeaky clean! You win today.')} } } } post { failure { script {pullRequest.createStatus(status: 'failure', context: 'Format & Syntax (backend)', description: 'Wow, did you even look at how malformed your code is?', targetUrl: env.RUN_DISPLAY_URL) } } }}stage('Frontend tests') { agent { node { label 'Node' } } steps { script { pullRequest.createStatus(status: 'pending',context: 'Unit tests (frontend)',description: 'Making sure you didn\'t break anything…',targetUrl: env.RUN_DISPLAY_URL) try {sh '! git diff --name-only ^HEAD origin/trunk | grep "^frontend"'sh '! git diff --name-only ^HEAD origin/trunk | grep "^shared-utilities"'echo "No changes found, skipping tests."pullRequest.createStatus(status: 'success', context: '
[JIRA] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-20941 Stored git credentials not used when submodule is updated Change By: Mark Waite Assignee: John Smith 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152463.1386683795000.9775.1563074702961%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50394) Branch Indexing fails with MissingObjectException
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-50394 Branch Indexing fails with MissingObjectException Change By: Mark Waite Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189448.1522043167000.9764.1563073140326%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-20941 Stored git credentials not used when submodule is updated Change By: Mark Waite Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152463.1386683795000.9630.1563067868551%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41488) Pipeline view automatically scrolls down
Title: Message Title Tim Huang commented on JENKINS-41488 Re: Pipeline view automatically scrolls down Do we just have to kill this line? https://github.com/jenkinsci/blueocean-plugin/blob/b02273dc2a6aee295ac8bd7dbab8eb3a8516a60e/blueocean-dashboard/src/main/js/components/karaoke/components/LogConsole.jsx#L156 This scroll bottom thing hurts more than it helps. It's easy enough for a user to hit fn + right arrow, or the end key... 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178288.1485459565000.9627.1563067868516%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Tim Huang updated JENKINS-38339 Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Tim Huang Resolution: Fixed Status: Resolved In Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174511.1474269026000.9555.1563067023475%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Tim Huang commented on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
I have more information on the matter - I was triggering downstream jobs within a `parallel` step (not sure if this has anything to do with it. In an earlier sequential stage, if I trigger another build job, it causes the ones in the parallel steps (that didn't show up before) to show up in the "Triggered Jobs" section. Below is my groovy script. In the first sequential stage there is a downstream no-op job I made that, when triggered, seems to make the "Triggered Jobs" section show up for the other two downstream jobs that are triggered in the parallel stages further down. Without the no-op job, the "Triggered Jobs" section won't show up for the other two. The formatting of this code won't paste right (missing newlines here and there), so apologies.
pipeline {
agent none options {
// Ideally, PRs build in less than 5
timeout(time: 15, unit: 'MINUTES')
} environment {
CI = 'true'
AWS_ACCESS_KEY_ID = credentials('aws-access-key-id-test')
AWS_SECRET_ACCESS_KEY = credentials('aws-secret-access-key-test')
} stages {
stage('Abort previous builds on PR') {
steps {
// Not sure how this works, but… https://stackoverflow.com/a/52811034
milestone label: '', ordinal: Integer.parseInt(env.BUILD_ID) - 1
milestone label: '', ordinal: Integer.parseInt(env.BUILD_ID)
// NOTE: Triggering this no-op job makes all Triggered Builds show up!!!
build 'Utilities/TriggeringThisInStepsMakesTriggeredBuildsShowUp'
}
} stage('PR tests') {
failFast false
parallel {
stage('Linting & formatting') {
agent {
node {
label 'Node'
}
} steps {
script {
pullRequest.createStatus(status: 'pending',
context: 'Format & Syntax (backend)',
description: 'Checking code quality…',
targetUrl: env.RUN_DISPLAY_URL) try {
sh '! git diff --name-only ^HEAD origin/trunk | grep "^backend"'
echo "No changes found, skipping tests."pullRequest.createStatus(status: 'success',
context: 'Format & Syntax (backend)',
description: 'Skipped (no changes).')
} catch (e) {
echo "Changes found, running tests."ansiColor('xterm') {
// Check for it-block .only() calls which skip all other
// tests in a suite. These should NEVER be version-checked.
sh "! git grep '\\'" sh 'rm -rf ./frontend'
sh 'yarn'
sh 'yarn eslint ./backend'
sh 'yarn prettier -c "./backend/**/*.js"' pullRequest.createStatus(status: 'success',
context: 'Format & Syntax (backend)',
description: 'Squeaky clean! You win today.')
}
}
}
}
post {
failure {
script {
pullRequest.createStatus(status: 'failure',
context: 'Format & Syntax (backend)',
description: 'Wow, did you even look at how malformed your code is?',
targetUrl: env.RUN_DISPLAY_URL)
}
}
}
}stage('Frontend tests') {
agent {
node {
label 'Node'
}
} steps {
script {
pullRequest.createStatus(status: 'pending',
context: 'Unit tests (frontend)',
description: 'Making sure you didn\'t break anything…',
targetUrl: env.RUN_DISPLAY_URL) try {
sh '! git diff --name-only ^HEAD origin/trunk | grep "^frontend"'
sh '! gi
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Tim Huang commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Hello, I am on Blue Ocean 1.17.0, and I do not see a link to my downstream jobs. Was there a regression? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174511.1474269026000.9437.1563059401118%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Tim Huang updated an issue Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Tim Huang Attachment: Captura de Pantalla 2019-07-13 a la(s) 4.08.07 p. m..png Attachment: Captura de Pantalla 2019-07-13 a la(s) 4.08.18 p. m..png 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174511.1474269026000.9378.1563059341660%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58056) Add option to fail the step if no files are found for pattern
Title: Message Title Ulli Hafner commented on JENKINS-58056 Re: Add option to fail the step if no files are found for pattern See https://github.com/jenkinsci/warnings-ng-plugin/pull/113. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200077.1560795254000.9372.1563055320297%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58056) Add option to fail the step if no files are found for pattern
Title: Message Title Ulli Hafner updated JENKINS-58056 Jenkins / JENKINS-58056 Add option to fail the step if no files are found for pattern Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200077.1560795254000.9375.1563055320346%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58056) Add option to fail the step if no files are found for pattern
Title: Message Title Ulli Hafner started work on JENKINS-58056 Change By: Ulli Hafner Status: Open In Progress 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200077.1560795254000.9369.1563055080283%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52781) tar function is breaking symlinks
Title: Message Title Pierre Beitz updated JENKINS-52781 Jenkins / JENKINS-52781 tar function is breaking symlinks Change By: Pierre Beitz Status: In Review Fixed but Unreleased Resolution: Fixed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192677.1532710807000.9366.1563040020538%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58411) make connection timeout configurable
Title: Message Title Thomas Reinicke commented on JENKINS-58411 Re: make connection timeout configurable The default value of the connection timeout is 300 seconds. It can be changed with an additional java option "-Dtimeout" 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200538.1562701112000.9362.1563038580046%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58411) make connection timeout configurable
Title: Message Title Thomas Reinicke started work on JENKINS-58411 Change By: Thomas Reinicke Status: Open In Progress 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200538.1562701112000.9361.1563037260159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57709) warnings-ng-plugin with incorrect dependency to git plugin
Title: Message Title Ulli Hafner updated JENKINS-57709 Fixed with https://github.com/jenkinsci/warnings-ng-plugin/commit/37b65c8089c5897c427a63492684a8641ddeb3be Jenkins / JENKINS-57709 warnings-ng-plugin with incorrect dependency to git plugin Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199650.1559035161000.9359.1563034260417%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55382) Shelve Project plugin does not correctly handle shelvedProjects symbolic link
Title: Message Title Pierre Beitz commented on JENKINS-55382 Re: Shelve Project plugin does not correctly handle shelvedProjects symbolic link Ross Oliver I made a fix for this issue. Here is the link to the hpi containing the fix in case you wish to test: https://ci.jenkins.io/job/Plugins/job/shelve-project-plugin/view/change-requests/job/PR-20/1/artifact/target/shelve-project-plugin.hpi 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196487.154646867.9326.1563026580357%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58091) HTTP proxy configuration connection refused
Title: Message Title Pierre Beitz closed an issue as Duplicate Jenkins / JENKINS-58091 HTTP proxy configuration connection refused Change By: Pierre Beitz Status: Open Closed Resolution: Duplicate 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200132.1560937993000.9295.1563024120199%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58091) HTTP proxy configuration connection refused
Title: Message Title Pierre Beitz commented on JENKINS-58091 Re: HTTP proxy configuration connection refused Suhas Ghadge looks like a duplicate of JENKINS-57383. According to this comment: https://issues.jenkins-ci.org/browse/JENKINS-57383?focusedCommentId=370814&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-370814 it should only impact the test button, the rest should work. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200132.1560937993000.9293.1563024060121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55382) Shelve Project plugin does not correctly handle shelvedProjects symbolic link
Title: Message Title Pierre Beitz updated JENKINS-55382 Jenkins / JENKINS-55382 Shelve Project plugin does not correctly handle shelvedProjects symbolic link Change By: Pierre Beitz Status: In Progress Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196487.154646867.9282.1563022560274%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57760) Add support for webhooks management
Title: Message Title Parichay Barpanda commented on JENKINS-57760 Re: Add support for webhooks management Creation of webhooks has been added. However cannot make post requests to Jenkins instance from GitLabServer. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199706.1559207961000.9270.1563021780131%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41056) Build Pipeline plugin : Wrong message : This view has no jobs associated with it
Title: Message Title Seetharaman Ramakrishnan started work on JENKINS-41056 Change By: Seetharaman Ramakrishnan Status: Open In Progress 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177793.1484284644000.9268.1563021180173%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55382) Shelve Project plugin does not correctly handle shelvedProjects symbolic link
Title: Message Title Pierre Beitz started work on JENKINS-55382 Change By: Pierre Beitz Status: Open In Progress 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196487.154646867.9264.1563020880267%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58482) req
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-58482 req Change By: Joseph Petersen Component/s: _unsorted Component/s: accurev-plugin 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200618.1563011989000.9262.1563020460136%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58482) req
Title: Message Title Joseph Petersen assigned an issue to Unassigned Jenkins / JENKINS-58482 req Change By: Joseph Petersen Assignee: Joseph Petersen 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200618.1563011989000.9260.1563020400116%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54683) Pods entering error state due to ConnectionRefusalException: Unknown client name
Title: Message Title Tobias Herrmann Hinz commented on JENKINS-54683 Re: Pods entering error state due to ConnectionRefusalException: Unknown client name will provide the requested debugging logs by the end of the weekend. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195475.1542484359000.9254.1563020340194%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58482) req
Title: Message Title manoj reddy created an issue Jenkins / JENKINS-58482 req Issue Type: Improvement Assignee: Joseph Petersen Components: accurev-plugin Created: 2019-07-13 09:59 Priority: Critical Reporter: manoj reddy 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200618.1563011989000.9224.1563012000403%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
