[JIRA] (JENKINS-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Laurent DEVOS commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API I'm using version 2.5 of the plugin. The problem was resolved after upgrading to 2.107.2 and updating all of my other plugins that had a new version. 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-40839) pipeline timeout doesn't kill the job
Title: Message Title
Maxfield Stewart edited a comment on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Here's my minimal repro for this: {code:java}node ('somelabel) { timeout (30) { timetstamps timestamps { withEnv(someEnvArray) { sleep 15 } } }}{code} While the sleep is running, put Jenkins in shutdown. Then cancel shutdown. The job will trigger the timeout, eventually say it's killing with extreme prejudice and need to be hard aborted otherwise it will be stuck forever.This mainly manifests as a problem when doing maintenance/restarts where some jobs might properly resume but end up stuck for other reasons and never cleanup. When I forcibly terminate at the text prompt it's still stuck inside "withEnv" I've also tested this by removing the "withEnv" and just using "timestamps" and the same problem occurs. As well as doing it without "timestamps" at each interval the nested section it's stuck in is inner one. So this seems to be a problem with the timeout handler.
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-40839) pipeline timeout doesn't kill the job
Title: Message Title
Maxfield Stewart edited a comment on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Here's my minimal repro for this: {code:java}node ('somelabel) { timeout (30) { timetstamps { withEnv(someEnvArray) { sleep 15 } } }}{code} While the sleep is running, put Jenkins in shutdown. Then cancel shutdown. The job will trigger the timeout, eventually say it's killing with extreme prejudice and need to be hard aborted otherwise it will be stuck forever.This mainly manifests as a problem when doing maintenance/restarts where some jobs might properly resume but end up stuck for other reasons and never cleanup. When I forcibly terminate at the text prompt it's still stuck inside "withEnv"
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-40839) pipeline timeout doesn't kill the job
Title: Message Title
Maxfield Stewart edited a comment on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Here's my minimal repro for this: ``` {code:java} node ('somelabel) \ { timeout (30) \ { timetstamps \ { withEnv(someEnvArray) \ { sleep 15 } } } } {code } ``` While the sleep is running, put Jenkins in shutdown. Then cancel shutdown. The job will trigger the timeout, eventually say it's killing with extreme prejudice and need to be hard aborted otherwise it will be stuck forever.This mainly manifests as a problem when doing maintenance/restarts where some jobs might properly resume but end up stuck for other reasons and never cleanup.
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-40839) pipeline timeout doesn't kill the job
Title: Message Title
Maxfield Stewart commented on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Here's my minimal repro for this: ``` node ('somelabel) { timeout (30) { timetstamps { withEnv(someEnvArray) { sleep 15 } } } } ``` While the sleep is running, put Jenkins in shutdown. Then cancel shutdown. The job will trigger the timeout, eventually say it's killing with extreme prejudice and need to be hard aborted otherwise it will be stuck forever. This mainly manifests as a problem when doing maintenance/restarts where some jobs might properly resume but end up stuck for other reasons and never cleanup.
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-38840) log parser plugin fails on slave node
Title: Message Title Ragu Raman S commented on JENKINS-38840 Re: log parser plugin fails on slave node I also have the same issue and looks like Log parser rules are referred only from Master(this plugin doesn't support to configure parser rules in slave machines) - any workaround/solution? 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-50855) Replay action visible although Replay permission is not granted
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-50855 Replay action visible although Replay permission is not granted Issue Type: Improvement Assignee: Unassigned Components: workflow-cps-plugin Created: 2018-04-18 04:24 Environment: workflow-cps:2.48 Priority: Minor Reporter: Allan BURDAJEWICZ The Replay action is visible if a user has the Build permission but not the Replay permission. In that case, the Replay feature enables to rebuild the pipeline with the original script but does not enables the user to modify the pipeline. That improvement is not about the functionality itself but more about the fact that the action "Replay" still shows up even though the permission "Replay" is not granted. Which is misleading / counterintuitive. The link could be renamed in that particular case. Add Comment
[JIRA] (JENKINS-50854) when i start tomcat .startup.bat file in cmd getting errors
Title: Message Title ashok sk created an issue Jenkins / JENKINS-50854 when i start tomcat .startup.bat file in cmd getting errors Issue Type: Bug Assignee: Devin Nusbaum Components: apache-httpcomponents-client-4-api-plugin Created: 2018-04-18 03:44 Priority: Critical Reporter: ashok sk Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are
[JIRA] (JENKINS-50848) Define the client<->server update lifecycle
Title: Message Title R. Tyler Croy updated JENKINS-50848 Jenkins / JENKINS-50848 Define the client<->server update lifecycle Change By: R. Tyler Croy Status: In Progress Review 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-50848) Define the client<->server update lifecycle
Title: Message Title R. Tyler Croy commented on JENKINS-50848 Re: Define the client<->server update lifecycle initial sketch in https://github.com/jenkinsci/jep/pull/89 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-50780) How can I manual exit pipeline job sucess
Title: Message Title xian xjr commented on JENKINS-50780 Re: How can I manual exit pipeline job sucess i want to return turn [sucess] in any stages 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-50785) when stage and input stage both is not work
Title: Message Title xian xjr commented on JENKINS-50785 Re: when stage and input stage both is not work Operating System:centos 7 java version "1.8.0_111"** Jenkins ver. 2.117 run: nohup java -jar jenkins.war --httpPort=8090 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-45771) Disable shallow clone when we know a merge will take place
Title: Message Title
Shiqi Yang edited a comment on JENKINS-45771
Re: Disable shallow clone when we know a merge will take place
I found a case where this bug still applies in parallel stages, reopen this one since I think it is the same issue but please let me know if it is not and I can open another oneenvironment:jenkins 2.89.3github-branch-source-plugin 2.32.2I have a multibranch project setup with `discover the pull requests from origin``merge pull request with target`fetch all tagsshallow clone I also have Basic Branch Build Strategies Plugin installed to stop the build storm when we scan repo but I don't think it is relatedmy pipeline file has 2 parallel stages and one of the stages has its own node {} section to specify the builder label and workspace path.it looks like this (this is almost the same example of https://jenkins.io/blog/2017/09/25/declarative-1, only difference here is that I have customWorkspace specified on the nodes to reuse the local code repo in the hope to save some time on git clone, our git repo is huge):{code:java}pipeline { agent nonestages {stage('Run Tests') {parallel {stage('Test 1') {agent { label "windows" customWorkspace "${env.HOME}/TEST1"}steps { bat "run-tests.bat"}post { always { junit "**/TEST-*.xml" }}}stage('Test On Linux') {agent { label "linux" customWorkspace "${env.HOME}/TEST2"}steps { sh "run-tests.sh"}post { always { junit "**/TEST-*.xml" }}}}}}}{code}the error I am seeing is that when the pipeline enters the parallel stages, especially after the workspace switch, it will fail to merge if the PR is couple of commits behind master because the head of master is checked out without git history. ( I logged in to the builder after the failure and manually verified that in the workspace)it seems that removing two ways to resolve this for now:1 remove the the customWorkspace this is not going to work well for us because the lack of self clean on the branches of multibranch (without customworkspace different branch runs will help resolve not share workspace in current design of multibranch pipeline)2. add 'wipe out workspace and clone again in advanced' settings. ( this will increase our build time tremendously because our github repo is big, and unnecessary) {code:java}> /usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > /usr/local/bin/git config remote.origin.url !INFO_EXTRACTED! # timeout=10Fetching upstream changes from !INFO_EXTRACTED! > /usr/local/bin/git --version # timeout=10using GIT_ASKPASS to set credentials JENKINS_GH > /usr/local/bin/git fetch --tags --progress !INFO_EXTRACTED! +refs/pull/!INFO_EXTRACTED!/head:refs/remotes/origin/PR-!INFO_EXTRACTED! +refs/heads/master:refs/remotes/origin/master # timeout=60Merging remotes/origin/master commit !INFO_EXTRACTED! into PR head commit !INFO_EXTRACTED! > /usr/local/bin/git config core.sparsecheckout # timeout=10 > /usr/local/bin/git checkout -f !INFO_EXTRACTED! > /usr/local/bin/git merge !INFO_EXTRACTED! # timeout=10 > /usr/local/bin/git config core.sparsecheckout #
[JIRA] (JENKINS-49485) jenkin crashes with {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
Title: Message Title
Sam Gleske edited a comment on JENKINS-49485
Re: jenkin crashes with {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
For now, I recommend using project matrix authorization and generating jobs via something like Job DSL plugin with authorizations. At this time, GitHub authorization strategy leaves a lot to be desired. In general, errors resulting for the GitHub API are usually related to improperly scoped tokens. It needs repo, org:read, and user:email.
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-49485) jenkin crashes with {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
Title: Message Title
Sam Gleske edited a comment on JENKINS-49485
Re: jenkin crashes with {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
For now, I recommend using project matrix authorization and generating jobs via something like Job DSL plugin with authorizations. At this time, GitHub authorization strategy leaves a lot to be desired. In general, errors resulting for the GitHub API are usually related to improperly scoped tokens. It needs repo, org:read, and user:email. I use this plugin daily (with brand new provisions) and do not encounter these errors.
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-49485) jenkin crashes with {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
Title: Message Title
Sam Gleske commented on JENKINS-49485
Re: jenkin crashes with {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
For now, I recommend using project matrix authorization and generating jobs via something like Job DSL plugin with authorizations. At this time, GitHub authorization strategy leaves a lot to be desired.
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-45771) Disable shallow clone when we know a merge will take place
Title: Message Title
Shiqi Yang edited a comment on JENKINS-45771
Re: Disable shallow clone when we know a merge will take place
I found a case where this bug still applies in parallel stages, reopen this one since I think it is the same issue but please let me know if it is not and I can open another oneenvironment:jenkins 2.89.3github-branch-source-plugin 2.32.2I have a multibranch project setup with `discover the pull requests from origin``merge pull request with target`fetch all tagsshallow clone I also have Basic Branch Build Strategies Plugin installed to stop the build storm when we scan repo but I don't think it is relatedmy pipeline file has 2 parallel stages and one of the stages has its own node {} section to specify the builder label and workspace path.it looks like this (this is almost the same example of https://jenkins.io/blog/2017/09/25/declarative-1, only difference here is that I have customWorkspace specified on the nodes to reuse the local code repo in the hope to save some time on git clone, our git repo is huge):{code:java}pipeline { agent nonestages {stage('Run Tests') {parallel {stage('Test 1') {agent { label "windows" customWorkspace "${env.HOME}/TEST1"}steps { bat "run-tests.bat"}post { always { junit "**/TEST-*.xml" }}}stage('Test On Linux') {agent { label "linux" customWorkspace "${env.HOME}/TEST2"}steps { sh "run-tests.sh"}post { always { junit "**/TEST-*.xml" }}}}}}}{code}the error I am seeing is that when the pipeline enters the parallel stages, especially after the workspace switch, it will fail to merge if the PR is couple of commits behind master because the head of master is checked out without git history. ( I logged in to the builder after the failure and manually verified that in the workspace)it seems that removing the customWorkspace will help resolve this{code:java}> /usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > /usr/local/bin/git config remote.origin.url !INFO_EXTRACTED! # timeout=10Fetching upstream changes from !INFO_EXTRACTED! > /usr/local/bin/git --version # timeout=10using GIT_ASKPASS to set credentials JENKINS_GH > /usr/local/bin/git fetch --tags --progress !INFO_EXTRACTED! +refs/pull/!INFO_EXTRACTED!/head:refs/remotes/origin/PR-!INFO_EXTRACTED! +refs/heads/master:refs/remotes/origin/master # timeout=60Merging remotes/origin/master commit !INFO_EXTRACTED! into PR head commit !INFO_EXTRACTED! > /usr/local/bin/git config core.sparsecheckout # timeout=10 > /usr/local/bin/git checkout -f !INFO_EXTRACTED! > /usr/local/bin/git merge !INFO_EXTRACTED! # timeout=10 > /usr/local/bin/git config core.sparsecheckout # timeout=10 > /usr/local/bin/git checkout -f !INFO_EXTRACTED!Command "/usr/local/bin/git merge !INFO_EXTRACTED!" returned status code 128:stdout: stderr: fatal: refusing to merge unrelated histories{code}FYI I remove the sensitive date from the output and replaced with ` !INFO_EXTRACTED! `
[JIRA] (JENKINS-45771) Disable shallow clone when we know a merge will take place
Title: Message Title
Shiqi Yang edited a comment on JENKINS-45771
Re: Disable shallow clone when we know a merge will take place
I found a case where this bug still applies in parallel stages, reopen this one since I think it is the same issue but please let me know if it is not and I can open another oneenvironment:jenkins 2.89.3github-branch-source-plugin 2.32.2I have a multibranch project setup with `discover the pull requests from origin``merge pull request with target`fetch all tagsshallow clone I also have Basic Branch Build Strategies Plugin installed to stop the build storm when we scan repo but I don't think it is relatedmy pipeline file has 2 parallel stages and one of the stages has its own node {} section to specify the builder label and workspace path.it looks like this (this is almost the same example of https://jenkins.io/blog/2017/09/25/declarative-1, only difference here is that I have customWorkspace specified on the nodes to reuse the local code repo in the hope to save some time on git clone, our git repo is huge):{code:java}pipeline { agent nonestages {stage('Run Tests') {parallel {stage('Test 1') {agent { label "windows" customWorkspace "${env.HOME}/TEST1"}steps { bat "run-tests.bat"}post { always { junit "**/TEST-*.xml" }}}stage('Test On Linux') {agent { label "linux" customWorkspace "${env.HOME}/TEST2"}steps { sh "run-tests.sh"}post { always { junit "**/TEST-*.xml" }}}}}}}{code}the error I am seeing is that when the pipeline enters the parallel stages, especially after the workspace switch, it will fail to merge if the PR is couple of commits behind master because the head of master is checked out without git history. ( I logged in to the builder after the failure and manually verified that in the workspace)it seems that removing the customWorkspace will help resolve this{code:java}> /usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > /usr/local/bin/git config remote.origin.url !INFO_EXTRACTED! # timeout=10Fetching upstream changes from !INFO_EXTRACTED! > /usr/local/bin/git --version # timeout=10using GIT_ASKPASS to set credentials JENKINS_GH > /usr/local/bin/git fetch --tags --progress !INFO_EXTRACTED! +refs/pull/!INFO_EXTRACTED!/head:refs/remotes/origin/PR-!INFO_EXTRACTED! +refs/heads/master:refs/remotes/origin/master # timeout=60Merging remotes/origin/master commit !INFO_EXTRACTED! into PR head commit !INFO_EXTRACTED! > /usr/local/bin/git config core.sparsecheckout # timeout=10 > /usr/local/bin/git checkout -f !INFO_EXTRACTED! > /usr/local/bin/git merge !INFO_EXTRACTED! # timeout=10 > /usr/local/bin/git config core.sparsecheckout # timeout=10 > /usr/local/bin/git checkout -f !INFO_EXTRACTED!Command "/usr/local/bin/git merge !INFO_EXTRACTED!" returned status code 128:stdout: stderr: fatal: refusing to merge unrelated histories{code}FYI I remove the sensitive date from the output and replaced with ` (' !INFO_EXTRACTED !` ')
[JIRA] (JENKINS-45771) Disable shallow clone when we know a merge will take place
Title: Message Title
Shiqi Yang edited a comment on JENKINS-45771
Re: Disable shallow clone when we know a merge will take place
I found a case where this bug still applies in parallel stages, reopen this one since I think it is the same issue but please let me know if it is not and I can open another oneenvironment:jenkins 2.89.3github-branch-source-plugin 2.32.2I have a multibranch project setup with `discover the pull requests from origin``merge pull request with target`fetch all tagsshallow clone I also have Basic Branch Build Strategies Plugin installed to stop the build storm when we scan repo but I don't think it is relatedmy pipeline file has 2 parallel stages and one of the stages has its own node {} section to specify the builder label and workspace path.it looks like this (this is almost the same example of https://jenkins.io/blog/2017/09/25/declarative-1, only difference here is that I have customWorkspace specified on the nodes to reuse the local code repo in the hope to save some time on git clone, our git repo is huge):{code:java}pipeline { agent nonestages {stage('Run Tests') {parallel {stage('Test 1') {agent { label "windows" customWorkspace "${env.HOME}/TEST1"}steps { bat "run-tests.bat"}post { always { junit "**/TEST-*.xml" }}}stage('Test On Linux') {agent { label "linux" customWorkspace "${env.HOME}/TEST2"}steps { sh "run-tests.sh"}post { always { junit "**/TEST-*.xml" }}}}}}}{code}the error I am seeing is that when the pipeline enters the parallel stages, especially after the workspace switch, it will fail to merge if the PR is couple of commits behind master because the head of master is checked out without git history. ( I logged in to the builder after the failure and manually verified that in the workspace)it seems that removing the customWorkspace will help resolve this{code:java}> /usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > /usr/local/bin/git config remote.origin.url !INFO_EXTRACTED! # timeout=10Fetching upstream changes from !INFO_EXTRACTED! > /usr/local/bin/git --version # timeout=10using GIT_ASKPASS to set credentials JENKINS_GH > /usr/local/bin/git fetch --tags --progress !INFO_EXTRACTED! +refs/pull/!INFO_EXTRACTED!/head:refs/remotes/origin/PR-!INFO_EXTRACTED! +refs/heads/master:refs/remotes/origin/master # timeout=60Merging remotes/origin/master commit !INFO_EXTRACTED! into PR head commit !INFO_EXTRACTED! > /usr/local/bin/git config core.sparsecheckout # timeout=10 > /usr/local/bin/git checkout -f !INFO_EXTRACTED! > /usr/local/bin/git merge !INFO_EXTRACTED! # timeout=10 > /usr/local/bin/git config core.sparsecheckout # timeout=10 > /usr/local/bin/git checkout -f !INFO_EXTRACTED!Command "/usr/local/bin/git merge !INFO_EXTRACTED!" returned status code 128:stdout: stderr: fatal: refusing to merge unrelated histories{code} FYI I remove the sensitive date from the output and replaced with !INFO_EXTRACTED!
[JIRA] (JENKINS-45771) Disable shallow clone when we know a merge will take place
Title: Message Title
Shiqi Yang reopened an issue
I found a case where this bug still applies in parallel stages, reopen this one since I think it is the same issue but please let me know if it is not and I can open another one environment: jenkins 2.89.3 github-branch-source-plugin 2.32.2 I have a multibranch project setup with `discover the pull requests from origin` `merge pull request with target` fetch all tags shallow clone I also have Basic Branch Build Strategies Plugin installed to stop the build storm when we scan repo but I don't think it is related my pipeline file has 2 parallel stages and one of the stages has its own node {} section to specify the builder label and workspace path. it looks like this (this is almost the same example of https://jenkins.io/blog/2017/09/25/declarative-1, only difference here is that I have customWorkspace specified on the nodes to reuse the local code repo in the hope to save some time on git clone, our git repo is huge):
pipeline {
agent none
stages {
stage('Run Tests') {
parallel {
stage('Test 1') {
agent {
label "windows"
customWorkspace "${env.HOME}/TEST1"
}
steps {
bat "run-tests.bat"
}
post {
always {
junit "**/TEST-*.xml"
}
}
}
stage('Test On Linux') {
agent {
label "linux"
customWorkspace "${env.HOME}/TEST2"
}
steps {
sh "run-tests.sh"
}
post {
always {
junit "**/TEST-*.xml"
}
}
}
}
}
}
}
the error I am seeing is that when the pipeline enters the parallel stages, especially after the workspace switch, it will fail to merge if the PR is couple of commits behind master because the head of master is checked out without git history. ( I logged in to the builder after the failure and manually verified that in the workspace) it seems that removing the customWorkspace will help resolve this
> /usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> /usr/local/bin/git config remote.origin.url !INFO_EXTRACTED! # timeout=10
Fetching upstream changes from !INFO_EXTRACTED!
> /usr/local/bin/git --version # timeout=10
using GIT_ASKPASS to set credentials JENKINS_GH
> /usr/local/bin/git fetch --tags --progress !INFO_EXTRACTED! +refs/pull/!INFO_EXTRACTED!/head:refs/remotes/origin/PR-!INFO_EXTRACTED! +refs/heads/master:refs/remotes/origin/master # timeout=60
Merging remotes/origin/master commit !INFO_EXTRACTED! into PR head commit !INFO_EXTRACTED!
> /usr/local/bin/git config core.sparsecheckout # timeout=10
> /usr/local/bin/git checkout -f !INFO_EXTRACTED!
> /usr/local/bin/git merge !INFO_EXTRACTED! # timeout=10
> /usr/local/bin/git config core.sparsecheckout # timeout=10
> /usr/local/bin/git checkout -f !INFO_EXTRACTED!
Command "/usr/local/bin/git merge !INFO_EXTRACTED!" returned status code 128:
stdout:
stderr: fatal: refusing to merge unrelated histories
[JIRA] (JENKINS-36783) Artifact download links rely on mime type to determine download vs. view
Title: Message Title Michael Neale commented on JENKINS-36783 Re: Artifact download links rely on mime type to determine download vs. view Sorin Sbarnea it may be a regression, in which case do you mind opening a new ticket? I wasn't able to reproduce it myself (it maybe some browser subtlety). 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-49485) jenkin crashes with {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
Title: Message Title
Jeremy Marshall commented on JENKINS-49485
Re: jenkin crashes with {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
I'm also having problem with GHE and declarative pipelines It seems ordinary users are not able to read credentials, even ones they created
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-50853) Windows JNLP slave permissions errors, works manually via RDP cmd
Title: Message Title
Antony Gelberg updated an issue
Jenkins / JENKINS-50853
Windows JNLP slave permissions errors, works manually via RDP cmd
Change By:
Antony Gelberg
We can bring up a slave and connect successfully:{{Apr 17, 2018 11:55:18 PM null }}\{\{FINER: Node windows-server-2012 (i-09233a1df87ee74c0)(i-09233a1df87ee74c0) is ready windows-server-2012 (i-09233a1df87ee74c0) booted at 1523569187000 Connecting to ip-172-16-2-40.ec2.internal(172.16.2.40) with WinRM as Administrator Connected with WinRM. Creating tmp directory if it does not exist slave.jar sent remotely. Bootstrapping it <===[JENKINS REMOTING CAPACITY]===>Remoting version: 3.17 This is a Windows agent Agent successfully connected and online}}But there is a difference between running commands from the RDP desktop as Administrator, and from the slave connected via JNLP (which also seems to be Administrator, according to the output of `whoami`).Running commands from RDP:{{C:\Windows\system32>whoami}} {{win-4iqcddh05vj\administrator}} \ { \ {C:\Windows\system32>psexec }} {{web.sandbox.MUNGED.com iisreset /restart}} {{PsExec v2.2 - Execute processes remotely}} {{Copyright (C) 2001-2016 Mark Russinovich}} {{Sysinternals - www.sysinternals.com}} {{Attempting stop...}} {{Internet services successfully stopped}} {{Attempting start...}} {{Internet services successfully restarted}} {{iisreset exited on web.sandbox.MUNGED.com with error code 0.}} However, running the following code from the same server, via JNLP / Pipeline, results in a `handle is invalid` error: \ { \ { environment \{}} {{ SERVER = 'web.sandbox.MUNGED.com'}} \ { \ { }}} \ { \ { steps \{}} {{ bat "whoami"}} {{ bat "psexec $\{SERVER} iisreset /restart"}} \ { \ { }}} Results in:{{00:19:24 [control-pipeline] Running batch script}} \{\{00:19:28 }} {{00:19:28 c:\jenkins\workspace\control-pipeline>whoami}} {{00:19:28 win-4iqcddh05vj\administrator}} {{[Pipeline] bat}} {{00:19:34 [control-pipeline] Running batch script}} \{\{00:19:38 }} \{\{00:19:38 c:\jenkins\workspace\control-pipeline>psexec web.sandbox.MUNGED.com iisreset /restart }} \{\{00:19:38 }} {{00:19:38 PsExec v2.2 - Execute processes remotely}} {{00:19:38 Copyright (C) 2001-2016 Mark Russinovich}} {{00:19:38 Sysinternals - www.sysinternals.com}} \{\{00:19:38 }} {{00:19:38 The handle is invalid.}} {{00:19:38 Connecting to web.sandbox.MUNGED.com...}} {{Couldn't access web.sandbox.MUNGED.com:}} {{00:19:40 Connecting to web.sandbox.MUNGED.com...}} We also see different behaviour between the two when running Powershell steps, but I left those out of here due to the convoluted nature of Powershell configuration. I'm sure it's the same root cause. Please let me know what extra information I can provide to help debug this. I set to Major as I don't see a workaround.
[JIRA] (JENKINS-50853) Windows JNLP slave permissions errors, works manually via RDP cmd
Title: Message Title
Antony Gelberg updated an issue
Jenkins / JENKINS-50853
Windows JNLP slave permissions errors, works manually via RDP cmd
Change By:
Antony Gelberg
We can bring up a slave and connect successfully:{{Apr 17, 2018 11:55:18 PM null }}\{\{FINER: Node windows-server-2012 (i-09233a1df87ee74c0)(i-09233a1df87ee74c0) is ready windows-server-2012 (i-09233a1df87ee74c0) booted at 1523569187000 Connecting to ip-172-16-2-40.ec2.internal(172.16.2.40) with WinRM as Administrator Connected with WinRM. Creating tmp directory if it does not exist slave.jar sent remotely. Bootstrapping it <===[JENKINS REMOTING CAPACITY]===>Remoting version: 3.17 This is a Windows agent Agent successfully connected and online }}But there is a difference between running commands from the RDP desktop as Administrator, and from the slave connected via JNLP (which also seems to be Administrator, according to the output of `whoami`). Running commands from RDP:{{C:\Windows\system32>whoami}}{{win-4iqcddh05vj\administrator}} \ { \ {C:\Windows\system32>psexec }}{{web.sandbox.MUNGED.com iisreset /restart}} {{PsExec v2.2 - Execute processes remotely}} {{Copyright (C) 2001-2016 Mark Russinovich}} {{Sysinternals - www.sysinternals.com}} {{Attempting stop...}} {{Internet services successfully stopped}} {{Attempting start...}} {{Internet services successfully restarted}} {{iisreset exited on web.sandbox.MUNGED.com with error code 0.}} However, running the following code from the same server, via JNLP / Pipeline, results in a `handle is invalid` error:\{\{ environment \{}} {{ SERVER = 'web.sandbox.MUNGED.com'}} \{\{ }}} \{\{ steps \{}} {{ bat "whoami"}} {{ bat "psexec $\{SERVER} iisreset /restart"}} \{\{ }}} Results in:{{00:19:24 [control-pipeline] Running batch script}} \{\{00:19:28 }} {{00:19:28 c:\jenkins\workspace\control-pipeline>whoami}} {{00:19:28 win-4iqcddh05vj\administrator}} {{[Pipeline] bat}} {{00:19:34 [control-pipeline] Running batch script}} \{\{00:19:38 }} \{\{00:19:38 c:\jenkins\workspace\control-pipeline>psexec web.sandbox.MUNGED.com iisreset /restart }} \{\{00:19:38 }} {{00:19:38 PsExec v2.2 - Execute processes remotely}} {{00:19:38 Copyright (C) 2001-2016 Mark Russinovich}} {{00:19:38 Sysinternals - www.sysinternals.com}} \{\{00:19:38 }} {{00:19:38 The handle is invalid.}} {{00:19:38 Connecting to web.sandbox.MUNGED.com...}} {{Couldn't access web.sandbox.MUNGED.com:}} {{00:19:40 Connecting to web.sandbox.MUNGED.com...}} We also see different behaviour between the two when running Powershell steps, but I left those out of here due to the convoluted nature of Powershell configuration. I'm sure it's the same root cause. Please let me know what extra information I can provide to help debug this. I set to Major as I don't see a workaround.
[JIRA] (JENKINS-50853) Windows JNLP slave permissions errors, works manually via RDP cmd
Title: Message Title
Antony Gelberg updated an issue
Jenkins / JENKINS-50853
Windows JNLP slave permissions errors, works manually via RDP cmd
Change By:
Antony Gelberg
We can bring up a slave and connect successfully:{{\{\{Apr 17, 2018 11:55:18 PM null }}\{\{FINER: Node windows-server-2012 (i-09233a1df87ee74c0)(i-09233a1df87ee74c0) is ready windows-server-2012 (i-09233a1df87ee74c0) booted at 1523569187000 Connecting to ip-172-16-2-40.ec2.internal(172.16.2.40) with WinRM as Administrator Connected with WinRM. Creating tmp directory if it does not exist slave.jar sent remotely. Bootstrapping it <===[JENKINS REMOTING CAPACITY]===>Remoting version: 3.17 This is a Windows agent Agent successfully connected and online {{ !http://jenkins.sandbox.graduway.com:8080/static/e7824fc9/images/spinner.gif!}} {{ }}{{ But there is a difference between running commands from the RDP desktop as Administrator, and from the slave connected via JNLP (which also seems to be Administrator, according to the output of `whoami`). }} {{ }} {{ Running commands from RDP: }} {{C:\Windows\system32>whoami}}{{win-4iqcddh05vj\administrator}}{{C:\Windows\system32>psexec }}{{web.sandbox.MUNGED.com iisreset /restart}} {{PsExec v2.2 - Execute processes remotely}} {{Copyright (C) 2001-2016 Mark Russinovich}} {{Sysinternals - www.sysinternals.com}} {{Attempting stop...}} {{Internet services successfully stopped}} {{Attempting start...}} {{Internet services successfully restarted}} {{iisreset exited on web.sandbox.MUNGED.com with error code 0.}} However, running the following code from the same server, via JNLP / Pipeline, results in a `handle is invalid` error:\{\{ environment \{}} {{ SERVER = 'web.sandbox.MUNGED.com'}} \{\{ }}} \{\{ steps \{}} {{ bat "whoami"}} {{ bat "psexec $\{SERVER} iisreset /restart"}} \{\{ }}} Results in:{{00:19:24 [control-pipeline] Running batch script}} \{\{00:19:28 }} {{00:19:28 c:\jenkins\workspace\control-pipeline>whoami}} {{00:19:28 win-4iqcddh05vj\administrator}} {{[Pipeline] bat}} {{00:19:34 [control-pipeline] Running batch script}} \{\{00:19:38 }} \{\{00:19:38 c:\jenkins\workspace\control-pipeline>psexec web.sandbox.MUNGED.com iisreset /restart }} \{\{00:19:38 }} {{00:19:38 PsExec v2.2 - Execute processes remotely}} {{00:19:38 Copyright (C) 2001-2016 Mark Russinovich}} {{00:19:38 Sysinternals - www.sysinternals.com}} \{\{00:19:38 }} {{00:19:38 The handle is invalid.}} {{00:19:38 Connecting to web.sandbox.MUNGED.com...}} {{Couldn't access web.sandbox.MUNGED.com:}} {{00:19:40 Connecting to web.sandbox.MUNGED.com...}} We also see different behaviour between the two when running Powershell steps, but I left those out of here due to the convoluted nature of Powershell configuration. I'm sure it's the same root cause. Please let me know what extra information I can provide to help debug this. I set to Major as I don't see a workaround.
[JIRA] (JENKINS-50853) Windows JNLP slave permissions errors, works manually via RDP cmd
Title: Message Title
Antony Gelberg updated an issue
Jenkins / JENKINS-50853
Windows JNLP slave permissions errors, works manually via RDP cmd
Change By:
Antony Gelberg
We can bring up a slave and connect successfully:{{ \{\{ Apr 17, 2018 11:55:18 PM null }}\{\{FINER: Node windows-server-2012 (i-09233a1df87ee74c0)(i-09233a1df87ee74c0) is ready windows-server-2012 (i-09233a1df87ee74c0) booted at 1523569187000 Connecting to ip-172-16-2-40.ec2.internal(172.16.2.40) with WinRM as Administrator Connected with WinRM. Creating tmp directory if it does not exist slave.jar sent remotely. Bootstrapping it <===[JENKINS REMOTING CAPACITY]===>Remoting version: 3.17 This is a Windows agent Agent successfully connected and online }} }} But there is a difference between running commands from the RDP desktop as Administrator, and from the slave connected via JNLP (which also seems to be Administrator, according to the output of `whoami`).Running commands from RDP:{{C:\Windows\system32>whoami}}{{win-4iqcddh05vj\administrator}}{{C:\Windows\system32>psexec }}{{web.sandbox.MUNGED.com iisreset /restart}} {{PsExec v2.2 - Execute processes remotely}} {{Copyright (C) 2001-2016 Mark Russinovich}} {{Sysinternals - www.sysinternals.com}} {{Attempting stop...}} {{Internet services successfully stopped}} {{Attempting start...}} {{Internet services successfully restarted}} {{iisreset exited on web.sandbox.MUNGED.com with error code 0.}} However, running the following code from the same server, via JNLP / Pipeline, results in a `handle is invalid` error:\{\{ environment \{}} {{ SERVER = 'web.sandbox.MUNGED.com'}} \{\{ }}} \{\{ steps \{}} {{ bat "whoami"}} {{ bat "psexec $\{SERVER} iisreset /restart"}} \{\{ }}} Results in:{{00:19:24 [control-pipeline] Running batch script}} \{\{00:19:28 }} {{00:19:28 c:\jenkins\workspace\control-pipeline>whoami}} {{00:19:28 win-4iqcddh05vj\administrator}} {{[Pipeline] bat}} {{00:19:34 [control-pipeline] Running batch script}} \{\{00:19:38 }} \{\{00:19:38 c:\jenkins\workspace\control-pipeline>psexec web.sandbox.MUNGED.com iisreset /restart }} \{\{00:19:38 }} {{00:19:38 PsExec v2.2 - Execute processes remotely}} {{00:19:38 Copyright (C) 2001-2016 Mark Russinovich}} {{00:19:38 Sysinternals - www.sysinternals.com}} \{\{00:19:38 }} {{00:19:38 The handle is invalid.}} {{00:19:38 Connecting to web.sandbox.MUNGED.com...}} {{Couldn't access web.sandbox.MUNGED.com:}} {{00:19:40 Connecting to web.sandbox.MUNGED.com...}} We also see different behaviour between the two when running Powershell steps, but I left those out of here due to the convoluted nature of Powershell configuration. I'm sure it's the same root cause. Please let me know what extra information I can provide to help debug this. I set to Major as I don't see a workaround.
[JIRA] (JENKINS-50853) Windows JNLP slave permissions errors, works manually via RDP cmd
Title: Message Title
Antony Gelberg updated an issue
Jenkins / JENKINS-50853
Windows JNLP slave permissions errors, works manually via RDP cmd
Change By:
Antony Gelberg
We can bring up a slave and connect successfully:{{ \{\{ Apr 17, 2018 11:55:18 PM null }} \ { \ {FINER: Node windows-server-2012 (i-09233a1df87ee74c0)(i-09233a1df87ee74c0) is ready windows-server-2012 (i-09233a1df87ee74c0) booted at 1523569187000 Connecting to ip-172-16-2-40.ec2.internal(172.16.2.40) with WinRM as Administrator Connected with WinRM. Creating tmp directory if it does not exist slave.jar sent remotely. Bootstrapping it <===[JENKINS REMOTING CAPACITY]===>Remoting version: 3.17 This is a Windows agent Agent successfully connected and online }} }} {{ !http://jenkins.sandbox.graduway.com:8080/static/e7824fc9/images/spinner.gif! }} {{ }} {{ But there is a difference between running commands from the RDP desktop as Administrator, and from the slave connected via JNLP (which also seems to be Administrator, according to the output of `whoami`). }} {{ }} {{ Running commands from RDP: }} {{C:\Windows\system32>whoami}}{{win-4iqcddh05vj\administrator}}{{C:\Windows\system32>psexec \\ }}{{ web.sandbox.MUNGED.com iisreset /restart}}{{PsExec v2.2 - Execute processes remotely}}{{Copyright (C) 2001-2016 Mark Russinovich}}{{Sysinternals - www.sysinternals.com}}{{Attempting stop...}}{{Internet services successfully stopped}}{{Attempting start...}}{{Internet services successfully restarted}}{{iisreset exited on web.sandbox.MUNGED.com with error code 0.}} However, running the following code from the same server, via JNLP / Pipeline, results in a `handle is invalid` error: \ { \ { environment \{}}{{ SERVER = 'web.sandbox.MUNGED.com'}} \ { \ { }}} \ { \ { steps \{}}{{ bat "whoami"}}{{ bat "psexec $\{SERVER} iisreset /restart"}} \ { \ { }}} Results in:{{00:19:24 [control-pipeline] Running batch script}} \ { \ {00:19:28 }}{{00:19:28 c:\jenkins\workspace\control-pipeline>whoami}}{{00:19:28 win-4iqcddh05vj\administrator}}{{[Pipeline] bat}}{{00:19:34 [control-pipeline] Running batch script}} \ { \ {00:19:38 }} \ { \ {00:19:38 c:\jenkins\workspace\control-pipeline>psexec \\ web.sandbox.MUNGED.com iisreset /restart }} \ { \ {00:19:38 }}{{00:19:38 PsExec v2.2 - Execute processes remotely}}{{00:19:38 Copyright (C) 2001-2016 Mark Russinovich}}{{00:19:38 Sysinternals - www.sysinternals.com}} \ { \ {00:19:38 }}{{00:19:38 The handle is invalid.}}{{00:19:38 Connecting to web.sandbox.MUNGED.com...}}{{Couldn't access web.sandbox.MUNGED.com:}}{{00:19:40 Connecting to web.sandbox.MUNGED.com...}} We also see different behaviour between the two when running Powershell steps, but I left those out of here due to the convoluted nature of Powershell configuration. I'm sure it's the same root cause. Please let me know what extra information I can provide to help debug this. I set to Major as I don't see a workaround.
[JIRA] (JENKINS-50853) Windows JNLP slave permissions errors, works manually via RDP cmd
Title: Message Title
Antony Gelberg created an issue
Jenkins / JENKINS-50853
Windows JNLP slave permissions errors, works manually via RDP cmd
Issue Type:
Bug
Assignee:
Francis Upton
Components:
ec2-plugin
Created:
2018-04-18 00:33
Environment:
Jenkins 2.107.2 ec2-plugin 1.39
Priority:
Major
Reporter:
Antony Gelberg
We can bring up a slave and connect successfully: {{Apr 17, 2018 11:55:18 PM null }}{{FINER: Node windows-server-2012 (i-09233a1df87ee74c0)(i-09233a1df87ee74c0) is ready windows-server-2012 (i-09233a1df87ee74c0) booted at 1523569187000 Connecting to ip-172-16-2-40.ec2.internal(172.16.2.40) with WinRM as Administrator Connected with WinRM. Creating tmp directory if it does not exist slave.jar sent remotely. Bootstrapping it <===[JENKINS REMOTING CAPACITY]===>Remoting version: 3.17 This is a Windows agent Agent successfully connected and online }} But there is a difference between running commands from the RDP desktop as Administrator, and from the slave connected via JNLP (which also seems to be Administrator, according to the output of `whoami`). Running commands from RDP: C:\Windows\system32>whoami win-4iqcddh05vj\administrator C:\Windows\system32>psexec web.sandbox.MUNGED.com iisreset /restart PsExec v2.2 - Execute processes remotely Copyright (C) 2001-2016 Mark Russinovich Sysinternals - www.sysinternals.com Attempting stop... Internet services successfully stopped Attempting start... Internet services successfully restarted iisreset exited on web.sandbox.MUNGED.com with error code 0. However, running the following code from the same server, via JNLP / Pipeline, results in a `handle is invalid` error: {{ environment {}} SERVER = 'web.sandbox.MUNGED.com' {{ }}} {{ steps {}} bat "whoami" bat "psexec ${SERVER} iisreset /restart" {{ }}}
[JIRA] (JENKINS-36956) Pipeline hangs on JUnitResultArchiver step with test publishers
Title: Message Title
Nikolas Falco edited a comment on JENKINS-36956
Re: Pipeline hangs on JUnitResultArchiver step with test publishers
We have the same issue where in a pipeline we run in parallel two maven build that perform integration tests on different application server. We would like collect the tests distinguishing (because are the same) them by branch. When maven build in all branches ends the pipeline hang during the report generation I suppose. We had try both: {code:java} junit testDataPublishers: [[$class: 'JUnitFlakyTestDataPublisher']], testResults: '**/target/surefire-reports/*.xml' {code} and {code:java} junit '**/target/surefire-reports/*.xml' {code}
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-36956) Pipeline hangs on JUnitResultArchiver step with test publishers
Title: Message Title Nikolas Falco edited a comment on JENKINS-36956 Re: Pipeline hangs on JUnitResultArchiver step with test publishers We have the same issue where in a pipeline we run in parallel two maven build that perform integration tests on different application server. We would like collect the tests distinguishing (because are the same) them by branch. When maven build in all branches ends the pipeline hang during the report generation I suppose. We had try both:junit testDataPublishers: [[$class: 'JUnitFlakyTestDataPublisher']], testResults: '**/target/surefire-reports/*.xml'andjunit '**/target/surefire-reports/*.xml' 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-50769) Deploying EAR to WAS 7 Issue with JDK
Title: Message Title Greg Peters commented on JENKINS-50769 Re: Deploying EAR to WAS 7 Issue with JDK 1) Is WAS v7 using the standard IBM JRE that's installed with WAS? 2) I believe JDK 1.6 and WAS v7 .jar files the correct versions you need to deploy to WAS v7. Where JDK 1.6 is running Jenkins and the admin.jar and orb.jar files are copied directly from the WAS v7 server into the plugin classpath as outline in the Plugin documentation site. 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-36956) Pipeline hangs on JUnitResultArchiver step with test publishers
Title: Message Title Nikolas Falco commented on JENKINS-36956 Re: Pipeline hangs on JUnitResultArchiver step with test publishers We have the same issue where in a pipeline we run in parallel two maven build that perform integration tests on different application server. We would like collect the tests distinguishing (because are the same) them by branch. When maven build in all branches ends the pipeline hang during the report generation I suppose. 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-45337) EC2 plugin cant launch windows slave (Unexpected EOF)
Title: Message Title Antony Gelberg commented on JENKINS-45337 Re: EC2 plugin cant launch windows slave (Unexpected EOF) Daniel Majano Maybe close the issue if it works? 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-32066) Time axis incorrect on Test History graph
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-32066 Time axis incorrect on Test History graph Change By: Nikolas Falco Component/s: junit-plugin Component/s: xunit-plugin 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-32066) Time axis incorrect on Test History graph
Title: Message Title Nikolas Falco closed an issue as Fixed Jenkins / JENKINS-32066 Time axis incorrect on Test History graph Change By: Nikolas Falco Status: Reopened Closed 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-32066) Time axis incorrect on Test History graph
Title: Message Title Nikolas Falco edited a comment on JENKINS-32066 Re: Time axis incorrect on Test History graph The That graph is an action not part of xunit-plugin but junit-plugin. Anyway issue seems to be resolved in latest most recent version of junit plugin. !screenshot-1.png|thumbnail! 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-32066) Time axis incorrect on Test History graph
Title: Message Title Nikolas Falco reopened an issue Jenkins / JENKINS-32066 Time axis incorrect on Test History graph Change By: Nikolas Falco Resolution: Fixed Status: Closed 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-32066) Time axis incorrect on Test History graph
Title: Message Title Nikolas Falco commented on JENKINS-32066 Re: Time axis incorrect on Test History graph The issue seems to be resolved in latest version 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-32066) Time axis incorrect on Test History graph
Title: Message Title Nikolas Falco closed an issue as Fixed Jenkins / JENKINS-32066 Time axis incorrect on Test History graph Change By: Nikolas Falco Status: Open Closed 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-32066) Time axis incorrect on Test History graph
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-32066 Time axis incorrect on Test History graph Change By: Nikolas Falco Attachment: screenshot-1.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.
[JIRA] (JENKINS-32066) Time axis incorrect on Test History graph
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-32066 Time axis incorrect on Test History graph Change By: Nikolas Falco Assignee: Gregory Boissinot Nikolas Falco 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-50507) withMaven must not trigger its own project
Title: Message Title dan tran edited a comment on JENKINS-50507 Re: withMaven must not trigger its own project I am still trying to troubleshoot this issue. Is it safe for me to wipe out the H2 database at /var/jenkins_home/jenkins-jobs/jenkins-jobs, and restart Jenkins to see if this helps? 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-50852) Maven report: remove duplicate dependencies list
Title: Message Title dan tran created an issue Jenkins / JENKINS-50852 Maven report: remove duplicate dependencies list Issue Type: Improvement Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2018-04-17 23:43 Priority: Minor Reporter: dan tran The new Maven report is awesome. One minor request to remove duplicated ones here is my sample Dependencies * com.xxx.brs.commons:common-test:2.0.2-SNAPSHOT - jar - compile com.xxx.brs.commons:common-test:2.0.2-SNAPSHOT - jar - compile com.xxx.brs.commons:common-test:2.0.2-SNAPSHOT - jar - compile com.xxx.brs.commons:common-test:2.0.2-SNAPSHOT - jar - compile com.xxx.brs.commons:common-test:2.0.2-SNAPSHOT - jar - compile and I have many of those in my 300+ modules build Add Comment
[JIRA] (JENKINS-28190) New version of xUnit is NOT showing jBehave plugin.
Title: Message Title Nikolas Falco resolved as Fixed As reported by Slavomir Kundrik the issue seems to be fixed with most recent version of both plugins. If not feel free to reopen this again. Jenkins / JENKINS-28190 New version of xUnit is NOT showing jBehave plugin. Change By: Nikolas Falco Status: Open 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
[JIRA] (JENKINS-28190) New version of xUnit is NOT showing jBehave plugin.
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-28190 New version of xUnit is NOT showing jBehave plugin. Change By: Nikolas Falco Assignee: Nikolas Falco 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-50850) createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0
Title: Message Title Chenyang Liu assigned an issue to Chenyang Liu Jenkins / JENKINS-50850 createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0 Change By: Chenyang Liu Assignee: Azure DevOps Chenyang Liu 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-50850) createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0
Title: Message Title
Chenyang Liu commented on JENKINS-50850
Re: createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0
From the logs, it seems you exceed the core limit in your subscription. Please add the quota limits Deployment Failed: Microsoft.Compute/virtualMachines:jenkins-linux-8-core-build-slaveb939d10 - Conflict - {error={code=OperationNotAllowed, message=Operation results in exceeding quota limits of Core. Maximum allowed: 350, Current in use: 344, Additional requested: 8. Please read more about quota increase at http://aka.ms/corequotaincrease.}}
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-42031) xUnit Plugin Does Not Parse Some Boost 1.63 Test Reports
Title: Message Title Nikolas Falco resolved as Fixed Jenkins / JENKINS-42031 xUnit Plugin Does Not Parse Some Boost 1.63 Test Reports Change By: Nikolas Falco Status: Open 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-42031) xUnit Plugin Does Not Parse Some Boost 1.63 Test Reports
Title: Message Title Nikolas Falco stopped work on JENKINS-42031 Change By: Nikolas Falco Status: In Progress Open 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-42031) xUnit Plugin Does Not Parse Some Boost 1.63 Test Reports
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42031 Re: xUnit Plugin Does Not Parse Some Boost 1.63 Test Reports Code changed in jenkins User: Nikolas Falco Path: src/main/resources/org/jenkinsci/plugins/xunit/types/boosttest-1.5.0.xsd src/test/java/org/jenkinsci/plugins/xunit/types/BoostTestTest.java src/test/resources/org/jenkinsci/plugins/xunit/types/boosttest/testcase19/junit-result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/boosttest/testcase19/testlog.xml http://jenkins-ci.org/commit/xunit-plugin/da4a90d80b0ef8f34f593e32e71627ee1c9a538d Log: Merge branch 'feature/JENKINS-42031' 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-50803) Paranoid mode for git-changelist-maven-extension
Title: Message Title Jesse Glick started work on JENKINS-50803 Change By: Jesse Glick Status: Open In Progress 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-42031) xUnit Plugin Does Not Parse Some Boost 1.63 Test Reports
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42031 Re: xUnit Plugin Does Not Parse Some Boost 1.63 Test Reports Code changed in jenkins User: Thomas Ascher Path: src/main/resources/org/jenkinsci/plugins/xunit/types/boosttest-1.5.0.xsd src/test/java/org/jenkinsci/plugins/xunit/types/BoostTestTest.java src/test/resources/org/jenkinsci/plugins/xunit/types/boosttest/testcase19/junit-result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/boosttest/testcase19/testlog.xml http://jenkins-ci.org/commit/xunit-plugin/ce609d4fe0b508544da529b42eb9ccd031e257be Log: JENKINS-42031 xUnit Plugin Does Not Parse Some Boost 1.63 Test Reports Change the boosttest-1.5.0.xsd validation file to accept some test reports generated by the test framework of Boost 1.63 where these reports may contain a "Message" element as child of a "TestSuite" element. 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-42031) xUnit Plugin Does Not Parse Some Boost 1.63 Test Reports
Title: Message Title Nikolas Falco edited a comment on JENKINS-42031 Re: xUnit Plugin Does Not Parse Some Boost 1.63 Test Reports Thanks [~tascher] for the report and the attached report. With the pull request 52 and your output report attached file I will try fix this bug soon with propert a proper test case.Since 1.64.0 of boosttest is able to produce directly the [JUnit report|https://www.boost.org/doc/libs/1_66_0/libs/test/doc/html/boost_test/change_log.html#boost_test.change_log.boost_test_v3_5_boost_1_64] I will reduce the priority. 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-42031) xUnit Plugin Does Not Parse Some Boost 1.63 Test Reports
Title: Message Title Nikolas Falco commented on JENKINS-42031 Re: xUnit Plugin Does Not Parse Some Boost 1.63 Test Reports Thanks Thomas Ascher for the report and the attached report. With the pull request 52 and your output report I will try fix this bug soon with propert test case. Since 1.64.0 of boosttest is able to produce directly the JUnit report I will reduce the priority. 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-42031) xUnit Plugin Does Not Parse Some Boost 1.63 Test Reports
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-42031 xUnit Plugin Does Not Parse Some Boost 1.63 Test Reports Change By: Nikolas Falco Priority: Major Minor 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-42031) xUnit Plugin Does Not Parse Some Boost 1.63 Test Reports
Title: Message Title Nikolas Falco started work on JENKINS-42031 Change By: Nikolas Falco Status: Open In Progress 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-42031) xUnit Plugin Does Not Parse Some Boost 1.63 Test Reports
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-42031 xUnit Plugin Does Not Parse Some Boost 1.63 Test Reports Change By: Nikolas Falco Assignee: Gregory Boissinot Nikolas Falco 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-50700) Fix maven-hpi-plugin to use hudson.util.VersionNumber
Title: Message Title Jesse Glick updated JENKINS-50700 Jenkins / JENKINS-50700 Fix maven-hpi-plugin to use hudson.util.VersionNumber Change By: Jesse Glick Status: In Progress Review 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-50507) withMaven must not trigger its own project
Title: Message Title dan tran commented on JENKINS-50507 Re: withMaven must not trigger its own project I am still trying to troubleshoot this issue. Is it safe for me to wipe out the H2 database restart Jenkins to see if this helps? 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-50700) Fix maven-hpi-plugin to use hudson.util.VersionNumber
Title: Message Title Jesse Glick started work on JENKINS-50700 Change By: Jesse Glick Status: Open In Progress 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-50693) Script to interoperate with maven-release-plugin
Title: Message Title Jesse Glick resolved as Fixed Formally documented this script. Can promote it to a saved file somewhere later, TBD. Jenkins / JENKINS-50693 Script to interoperate with maven-release-plugin Change By: Jesse Glick Status: In Progress 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,
[JIRA] (JENKINS-50851) Skipped count percentage is affected by integer rounding
Title: Message Title Nikolas Falco resolved as Fixed Jenkins / JENKINS-50851 Skipped count percentage is affected by integer rounding Change By: Nikolas Falco Status: Open 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-49085) Request to JIRA webhook breaking pipeline
Title: Message Title Wisen Tanasa commented on JENKINS-49085 Re: Request to JIRA webhook breaking pipeline Dmitriy Kagarlickij Please watch JENKINS-49178. 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-50443) Issues with JIRA Trigger Pluggin
Title: Message Title Wisen Tanasa closed an issue as Duplicate Jenkins / JENKINS-50443 Issues with JIRA Trigger Pluggin Change By: Wisen Tanasa Status: Open Closed Resolution: Duplicate 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-50443) Issues with JIRA Trigger Pluggin
Title: Message Title Wisen Tanasa commented on JENKINS-50443 Re: Issues with JIRA Trigger Pluggin Please watch JENKINS-49178 as this is a duplicate. 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-45916) Path is not getting set correctly in pipeline when there is a variable present
Title: Message Title Andrew Bayer commented on JENKINS-45916 Re: Path is not getting set correctly in pipeline when there is a variable present Blanca Borro Escribano - please provide a Jenkinsfile that can reproduce this. 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-49947) unclear usage of input step in declarative pipeline
Title: Message Title Andrew Bayer commented on JENKINS-49947 Re: unclear usage of input step in declarative pipeline Andreas Klemp - Yeah, https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/227 (which will hopefully merge/release next month) will give you a better approach. 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-50044) Run a task on node x or node y
Title: Message Title Andrew Bayer assigned an issue to Unassigned Jenkins / JENKINS-50044 Run a task on node x or node y Change By: Andrew Bayer Assignee: Andrew Bayer 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-50044) Run a task on node x or node y
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-50044 Run a task on node x or node y Change By: Andrew Bayer Component/s: workflow-durable-task-step-plugin Component/s: pipeline-model-definition-plugin 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-50645) Post failure condition should be evaluated after other conditions
Title: Message Title Andrew Bayer updated JENKINS-50645 Jenkins / JENKINS-50645 Post failure condition should be evaluated after other conditions Change By: Andrew Bayer Status: In Progress Review 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-50645) Post failure condition should be evaluated after other conditions
Title: Message Title Andrew Bayer started work on JENKINS-50645 Change By: Andrew Bayer Status: Open In Progress 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-50645) Post failure condition should be evaluated after other conditions
Title: Message Title Andrew Bayer commented on JENKINS-50645 Re: Post failure condition should be evaluated after other conditions PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/266 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-50777) Exported API for SCMRevisionAction
Title: Message Title Jesse Glick updated JENKINS-50777 Merged but unreleased. Jenkins / JENKINS-50777 Exported API for SCMRevisionAction Change By: Jesse Glick Status: In Review 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-50815) beside GIT_BRANCH also expose it as BRANCH
Title: Message Title Andrew Bayer commented on JENKINS-50815 Re: beside GIT_BRANCH also expose it as BRANCH PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/265 adding fallback to GIT_LOCAL_BRANCH (which doesn't have the remote on it, unlike GIT_BRANCH) if BRANCH_NAME is null. 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-50815) beside GIT_BRANCH also expose it as BRANCH
Title: Message Title Andrew Bayer updated JENKINS-50815 Jenkins / JENKINS-50815 beside GIT_BRANCH also expose it as BRANCH Change By: Andrew Bayer Status: In Progress Review 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-50815) beside GIT_BRANCH also expose it as BRANCH
Title: Message Title Andrew Bayer started work on JENKINS-50815 Change By: Andrew Bayer Status: Open In Progress 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-50815) beside GIT_BRANCH also expose it as BRANCH
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-50815 beside GIT_BRANCH also expose it as BRANCH Change By: Andrew Bayer Assignee: Andrew Bayer 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-48551) Cannot select CIFS publish in project configuration
Title: Message Title Kevin Waite edited a comment on JENKINS-48551 Re: Cannot select CIFS publish in project configuration Jenkins is reporting this snapshot for this plugin "[0.10-SNAPSHOT (private-7fe5315e-win2012-8a8450$)|http://build-pc:8080/pluginManager/plugin/publish-over-cifs/thirdPartyLicenses]"...How else / more can I provide verification? The problem is that the CIFS drop down is empty, I cannot select and any name to save. !image-2018-04-17-16-22-58-431.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.
[JIRA] (JENKINS-48551) Cannot select CIFS publish in project configuration
Title: Message Title Kevin Waite commented on JENKINS-48551 Re: Cannot select CIFS publish in project configuration Jenkins is reporting this snapshot for this plugin "0.10-SNAPSHOT (private-7fe5315e-win2012-8a8450$)"... How else / more can I provide verification? The problem is that the CIFS drop down is empty, I cannot select and name to save. 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-48551) Cannot select CIFS publish in project configuration
Title: Message Title Kevin Waite updated an issue Jenkins / JENKINS-48551 Cannot select CIFS publish in project configuration Change By: Kevin Waite Attachment: image-2018-04-17-16-22-58-431.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.
[JIRA] (JENKINS-43882) Declarative parity
Title: Message Title Jenn Briden assigned an issue to Jenn Briden Jenkins / JENKINS-43882 Declarative parity Change By: Jenn Briden Assignee: James Dumay Jenn Briden 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-48551) Cannot select CIFS publish in project configuration
Title: Message Title Alex Earl commented on JENKINS-48551 Re: Cannot select CIFS publish in project configuration You open the job configuration, select the correct CIFS share and resave and it doesn't remain? Can you verify you have the snapshot version of the plugin installed? 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-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title Karl Shultz resolved as Fixed Fixed via this PR in pipeline-model-definition. Jenkins / JENKINS-50805 Jenkins Blue Ocean won't show Agent when creating a Pipeline Change By: Karl Shultz Status: Open 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
[JIRA] (JENKINS-50173) Extension point for marking generated items
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-50173 Extension point for marking generated items Change By: Jesse Glick Component/s: configuration-as-code-plugin 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-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title Karl Shultz edited a comment on JENKINS-50805 Re: Jenkins Blue Ocean won't show Agent when creating a Pipeline [~reijis2], [~theelix], and [~jkiddo],[~abayer] already had has released a fix for the issue, and I'm pretty sure that once you update the plugin versions, this problem will be resolved. Since at least one of you is new to setting up your own Jenkins, here's how to go about it:1. Launch your container and log in if necessary: !screenshot-1.png|thumbnail! 2. In the navigation bar at the left, click "Manage Jenkins." That'll take you to the below screen, where you'll want to pick "Manage Plugins." In the below screenshot, "Manage Plugins" is highlighted, but I haven't clicked it yet: !screenshot-3.png|thumbnail! 3. Once there, you should see the Manage Plugins screen, with the "Updates" tab preselected for you. If your list looks empty or nearly empty, click the "Check Now" button. That should produce a list much like what you see here: !screenshot-4.png|thumbnail! 4. Click "Select All," then click "Download now and install after restart." !screenshot-5.png|thumbnail! 5. You'll see the updates taking place. Click the checkbox at the bottom to restart Jenkins once it's ready. !screenshot-6.png|thumbnail! 6. Once it's back up, if you go back to Manage Plugins and check the "Installed" tab, you should see that your versions of the `pipeline-model-definition` and its related plugins have been updated to 1.2.9. You can spot this easily by looking for the "Downgrade to 1.2.8" buttons at the right. !screenshot-7.png|thumbnail! 7. For historical purposes, here's my install _before_ taking the updated version of pipeline-model-definition. As you can see, the Pipeline editor does not show the Agent settings, which is exactly the bug reported here: !screenshot-2.png|thumbnail! 8. And now, with the upgrades in place, the Agent dropdown is available in the Pipeline Editor: !screenshot-8.png|thumbnail! I hope that's helpful if we have newcomers to Jenkins looking at this issue. Thanks again for reporting the bug! I'm going to go ahead and mark it as Resolved, but feel free to follow up here if you run into any trouble. Add Comment
[JIRA] (JENKINS-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title Karl Shultz commented on JENKINS-50805 Re: Jenkins Blue Ocean won't show Agent when creating a Pipeline Christopher Francisco, Elia Zammuto, and Jens Villadsen, Andrew Bayer already had a fix for the issue, and I'm pretty sure that once you update the plugin versions, this problem will be resolved. Since at least one of you is new to setting up your own Jenkins, here's how to go about it: 1. Launch your container and log in if necessary: 2. In the navigation bar at the left, click "Manage Jenkins." That'll take you to the below screen, where you'll want to pick "Manage Plugins." In the below screenshot, "Manage Plugins" is highlighted, but I haven't clicked it yet: 3. Once there, you should see the Manage Plugins screen, with the "Updates" tab preselected for you. If your list looks empty or nearly empty, click the "Check Now" button. That should produce a list much like what you see here: 4. Click "Select All," then click "Download now and install after restart." 5. You'll see the updates taking place. Click the checkbox at the bottom to restart Jenkins once it's ready. 6. Once it's back up, if you go back to Manage Plugins and check the "Installed" tab, you should see that your versions of the `pipeline-model-definition` and its related plugins have been updated to 1.2.9. You can spot this easily by looking for the "Downgrade to 1.2.8" buttons at the right. 7. For historical purposes, here's my install before taking the updated version of pipeline-model-definition. As you can see, the Pipeline editor does not show the Agent settings, which is exactly the bug reported here: 8. And now, with the upgrades in place, the Agent dropdown is available in the Pipeline Editor: I hope that's helpful if we have newcomers to Jenkins looking at this issue. Thanks again for reporting the bug! I'm going to go ahead and mark it as Resolved, but feel free to follow up here if you run into any trouble. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50805 Jenkins Blue Ocean won't show Agent when creating a Pipeline Change By: Karl Shultz Attachment: screenshot-8.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.
[JIRA] (JENKINS-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50805 Jenkins Blue Ocean won't show Agent when creating a Pipeline Change By: Karl Shultz Attachment: screenshot-7.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.
[JIRA] (JENKINS-48551) Cannot select CIFS publish in project configuration
Title: Message Title Kevin Waite commented on JENKINS-48551 Re: Cannot select CIFS publish in project configuration Unfortunately, re-saving the jobs doesn't fix this problem, after several saves and Jenkins restart the this drop down for CIFS name remains empty. Promotion still is failing with the error listed above. 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-48551) Cannot select CIFS publish in project configuration
Title: Message Title Kevin Waite updated an issue Jenkins / JENKINS-48551 Cannot select CIFS publish in project configuration Change By: Kevin Waite Attachment: image-2018-04-17-15-56-40-385.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.
[JIRA] (JENKINS-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50805 Jenkins Blue Ocean won't show Agent when creating a Pipeline Change By: Karl Shultz Attachment: screenshot-6.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.
[JIRA] (JENKINS-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50805 Jenkins Blue Ocean won't show Agent when creating a Pipeline Change By: Karl Shultz Attachment: screenshot-5.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.
[JIRA] (JENKINS-48551) Cannot select CIFS publish in project configuration
Title: Message Title Alex Earl commented on JENKINS-48551 Re: Cannot select CIFS publish in project configuration Sadly, you may need to open the jobs that are affected and resave the configuration so that the name gets saved off correctly. The problem is that the field was not saved under some circumstances, so you need to reapply the name in the job, but going forward it should be saved correctly. Please let me know if that still doesn't work. 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-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50805 Jenkins Blue Ocean won't show Agent when creating a Pipeline Change By: Karl Shultz Attachment: screenshot-4.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.
[JIRA] (JENKINS-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50805 Jenkins Blue Ocean won't show Agent when creating a Pipeline Change By: Karl Shultz Attachment: screenshot-3.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.
[JIRA] (JENKINS-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50805 Jenkins Blue Ocean won't show Agent when creating a Pipeline Change By: Karl Shultz Attachment: screenshot-2.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.
[JIRA] (JENKINS-50851) Skipped count percentage is affected by integer rounding
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50851 Re: Skipped count percentage is affected by integer rounding Code changed in jenkins User: Nikolas Falco Path: src/test/java/org/jenkinsci/plugins/xunit/threshold/SkippedThresholdTest.java http://jenkins-ci.org/commit/xunit-plugin/332b96c6a0d07fdde73710189a80c945ac4ad7be Log: JENKINS-50851 Skipped count percentage is affected by integer rounding Add unit test 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-35269) Job configuration UI Layout is broken
Title: Message Title Alex Taylor commented on JENKINS-35269 Re: Job configuration UI Layout is broken Manuel Recena Soto Any ideas on the future PRs for this issue? 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-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50805 Jenkins Blue Ocean won't show Agent when creating a Pipeline Change By: Karl Shultz Attachment: screenshot-1.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.
[JIRA] (JENKINS-50825) Add editor ATH coverage for deleting steps and stages from a pipeline
Title: Message Title Karl Shultz started work on JENKINS-50825 Change By: Karl Shultz Status: Open In Progress 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.
