[JIRA] (JENKINS-60994) When using top level agents and timeouts, provisioning time is not accounted for
Title: Message Title Jose Blas Camacho Taboada stopped work on JENKINS-60994 Change By: Jose Blas Camacho Taboada Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204462.1580984833000.8243.1581529440201%40Atlassian.JIRA.
[JIRA] (JENKINS-60994) When using top level agents and timeouts, provisioning time is not accounted for
Title: Message Title Jose Blas Camacho Taboada updated an issue Jenkins / JENKINS-60994 When using top level agents and timeouts, provisioning time is not accounted for Change By: Jose Blas Camacho Taboada Issue Type: New Feature Bug Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204462.1580984833000.2725.1581007320813%40Atlassian.JIRA.
[JIRA] (JENKINS-60994) When using top level agents and timeouts, provisioning time is not accounted for
Title: Message Title
Jose Blas Camacho Taboada updated an issue
Jenkins / JENKINS-60994
When using top level agents and timeouts, provisioning time is not accounted for
Change By:
Jose Blas Camacho Taboada
When using the following pipeline, {code:groovy}pipeline {agent anyoptions {timeout(time: 10, unit: "MINUTES")}stages {stage("foo") {steps {echo "hello"}}stage("boo") {steps {echo "hello buddy"}}}}{code}Provisioning time is not accounted for in the timeout, this is the script generated: {code:groovy}3 node [{label=null}]4 { []5 timeout [{unit=MINUTES, time=10}]6{ []7stage [{name=foo}]8 { (foo) []9 echo [{message=hello}]10} []11// stage []12stage [{name=boo}]13 { (boo) []14 echo [{message=hello buddy}]15} []16// stage []17 } []18 // timeout []19 } []20 // node []{code}h1. *Proposal:*Only should work iff top level agent (agent not none) and timeout in top level option . , as stage level timeout {code:groovy}pipeline {agent anyoptions {timeout(time: 10, unit: "MINUTES")}stages {stage("foo") {steps {echo "hello"}}stage("boo") {steps {echo "hello buddy"}}}}{code} would produce a top level timeout script{code:groovy}3 timeout {unit=MINUTES, time=10}4 { 5 node {label=null}6{ 7stage {name=foo}8 { (foo) 9 echo {message=hello}10} 11// stage 12stage {name=boo}13 { (boo) 14 echo {message=hello buddy}15} 16// stage 17 } 18 // node 19 } 20 // timeout {code}
Add Comment
[JIRA] (JENKINS-60994) When using top level agents and timeouts, provisioning time is not accounted for
Title: Message Title
Jose Blas Camacho Taboada updated an issue
Jenkins / JENKINS-60994
When using top level agents and timeouts, provisioning time is not accounted for
Change By:
Jose Blas Camacho Taboada
When using the following pipeline, {code:groovy}pipeline {agent anyoptions {timeout(time: 10, unit: "MINUTES")}stages {stage("foo") {steps {echo "hello"}}stage("boo") {steps {echo "hello buddy"}}}}{code}Provisioning time is not accounted for in the timeout, this is the script generated: {code:groovy}3 node [{label=null}]4 { []5 timeout [{unit=MINUTES, time=10}]6{ []7stage [{name=foo}]8 { (foo) []9 echo [{message=hello}]10} []11// stage []12stage [{name=boo}]13 { (boo) []14 echo [{message=hello buddy}]15} []16// stage []17 } []18 // timeout []19 } []20 // node []{code}h1. *Proposal:*Only should work iff top level agent (agent not none) and timeout in top level option.{code:groovy}pipeline {agent anyoptions { provisioningTimeout() timeout(time: 10, unit: "MINUTES")}stages {stage("foo") {steps {echo "hello"}}stage("boo") {steps {echo "hello buddy"}}}}{code} would produce a top level timeout script{code:groovy}3 timeout {unit=MINUTES, time=10}4 { 5 node {label=null}6{ 7stage {name=foo}8 { (foo) 9 echo {message=hello}10} 11// stage 12stage {name=boo}13 { (boo) 14 echo {message=hello buddy}15} 16// stage 17 } 18 // node 19 } 20 // timeout {code}
Add Comment
[JIRA] (JENKINS-60994) When using top level agents and timeouts, provisioning time is not accounted for
Title: Message Title
Jose Blas Camacho Taboada updated an issue
Jenkins / JENKINS-60994
When using top level agents and timeouts, provisioning time is not accounted for
Change By:
Jose Blas Camacho Taboada
When using the following pipeline, {code:groovy}pipeline {agent anyoptions {timeout(time: 10, unit: "MINUTES")}stages {stage("foo") {steps {echo "hello"}} stage("boo") {steps {echo "hello buddy" }} }} {code}Provisioning time is not accounted for in the timeout, this is the script generated: {code:groovy}3 node [{label=null}]4 { []5 timeout [{unit=MINUTES, time=10}]6{ []7stage [{name=foo}]8 { (foo) []9 echo [{message=hello}]10} []11// stage []12stage [{name=boo}]13 { (boo) []14 echo [{message=hello buddy}]15} []16// stage []17 } []18 // timeout []19 } []20 // node []{code}h1. *Proposal:*Only should work iff top level agent (agent not none) and timeout in top level option.{code:groovy}pipeline {agent anyoptions {provisioningTimeout()timeout(time: 10, unit: "MINUTES")}stages {stage("foo") {steps {echo "hello"}}stage("boo") {steps {echo "hello buddy "}}}}{code} would produce a top level timeout script{code:groovy}3 timeout {unit=MINUTES, time=10}4 { 5 node {label=null}6{ 7stage {name=foo}8 { (foo) 9 echo {message=hello}10} 11// stage 12stage {name=boo}13 { (boo) 14 echo {message=hello buddy}15} 16// stage 17 } 18 // node 19 } 20 // timeout {code}
Add Comment
[JIRA] (JENKINS-60994) When using top level agents and timeouts, provisioning time is not accounted for
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-60994 Change By: Jose Blas Camacho Taboada Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204462.1580984833000.2248.1580984940088%40Atlassian.JIRA.
[JIRA] (JENKINS-60994) When using top level agents and timeouts, provisioning time is not accounted for
Title: Message Title
Jose Blas Camacho Taboada created an issue
Jenkins / JENKINS-60994
When using top level agents and timeouts, provisioning time is not accounted for
Issue Type:
New Feature
Assignee:
Jose Blas Camacho Taboada
Components:
pipeline-model-definition-plugin
Created:
2020-02-06 10:27
Priority:
Minor
Reporter:
Jose Blas Camacho Taboada
When using the following pipeline,
pipeline {
agent any
options {
timeout(time: 10, unit: "MINUTES")
}
stages {
stage("foo") {
steps {
echo "hello"
}
}
}
}
Provisioning time is not accounted for in the timeout, this is the script generated:
3 node [{label=null}]
4 { []
5 timeout [{unit=MINUTES, time=10}]
6{ []
7stage [{name=foo}]
8 { (foo) []
9 echo [{message=hello}]
10} []
11// stage []
12stage [{name=boo}]
13 { (boo) []
14 echo [{message=hello buddy}]
15} []
16// stage []
17 } []
18 // timeout []
19 } []
20 // node []
Proposal: Only should work iff top level agent (agent not none) and timeout in top level option.
pipeline {
agent any
options {
provisioningTimeout()
timeout(time:
[JIRA] (JENKINS-50999) Repository Branch DropDown timesout
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-50999 Jenkins / JENKINS-50999 Repository Branch DropDown timesout Change By: Jose Blas Camacho Taboada Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190225.1524666248000.2347.1564315620401%40Atlassian.JIRA.
[JIRA] (JENKINS-46068) Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected)
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-46068 Jenkins / JENKINS-46068 Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected) Change By: Jose Blas Camacho Taboada Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184301.1502219385000.6541.1562753341179%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46068) Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected)
Title: Message Title Jose Blas Camacho Taboada edited a comment on JENKINS-46068 Re: Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected) This issue is already fixed in version 2.5. 4 snapshot; 3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184301.1502219385000.6515.1562753280342%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46068) Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected)
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-46068 Jenkins / JENKINS-46068 Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected) Change By: Jose Blas Camacho Taboada Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184301.1502219385000.6511.1562752804530%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46068) Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected)
Title: Message Title Jose Blas Camacho Taboada commented on JENKINS-46068 Re: Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected) This issue is already fixed in version 2.5.4 snapshot; Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184301.1502219385000.6497.1562752803872%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46068) Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected)
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-46068 Change By: Jose Blas Camacho Taboada Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184301.1502219385000.6471.1562752740856%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46068) Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected)
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-46068 Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected) Change By: Jose Blas Camacho Taboada Assignee: Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184301.1502219385000.6440.1562750881358%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30515) scm (git) command does not fail correctly when it cannot look up credentials
Title: Message Title Jose Blas Camacho Taboada closed an issue as Fixed merged at stable-3.9 Jenkins / JENKINS-30515 scm (git) command does not fail correctly when it cannot look up credentials Change By: Jose Blas Camacho Taboada Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30515) scm (git) command does not fail correctly when it cannot look up credentials
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-30515 Jenkins / JENKINS-30515 scm (git) command does not fail correctly when it cannot look up credentials Change By: Jose Blas Camacho Taboada Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49142) Be able to customize checkout as "options" in declarative pipeline
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-49142 Jenkins / JENKINS-49142 Be able to customize checkout as "options" in declarative pipeline Change By: Jose Blas Camacho Taboada Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49142) Be able to customize checkout as "options" in declarative pipeline
Title: Message Title Jose Blas Camacho Taboada stopped work on JENKINS-49142 Change By: Jose Blas Camacho Taboada Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44376) Ability to set variables shared between stages
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Andrew Bayer Jenkins / JENKINS-44376 Ability to set variables shared between stages Change By: Jose Blas Camacho Taboada Assignee: Jose Blas Camacho Taboada Andrew Bayer Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30515) scm (git) command does not fail correctly when it cannot look up credentials
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-30515 Jenkins / JENKINS-30515 scm (git) command does not fail correctly when it cannot look up credentials Change By: Jose Blas Camacho Taboada Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30515) scm (git) command does not fail correctly when it cannot look up credentials
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-30515 Change By: Jose Blas Camacho Taboada Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44376) Ability to set variables shared between stages
Title: Message Title Jose Blas Camacho Taboada commented on JENKINS-44376 Re: Ability to set variables shared between stages The fact that a value can be set in an environment and be accessed by child stages lgtm, but setting values for siblings is unclear to be as it breaks the var scope. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30515) scm (git) command does not fail correctly when it cannot look up credentials
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-30515 scm (git) command does not fail correctly when it cannot look up credentials Change By: Jose Blas Camacho Taboada Assignee: Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52391) Restarting Parallel Stages
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Andrew Bayer Jenkins / JENKINS-52391 Restarting Parallel Stages Change By: Jose Blas Camacho Taboada Assignee: Jose Blas Camacho Taboada Andrew Bayer Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52391) Restarting Parallel Stages
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-52391 Restarting Parallel Stages Change By: Jose Blas Camacho Taboada Assignee: Andrew Bayer Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52744) Using not existing environment variables in environment GString expression causes strange error message
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-52744 Jenkins / JENKINS-52744 Using not existing environment variables in environment GString _expression_ causes strange error message Change By: Jose Blas Camacho Taboada Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49142) Be able to customize checkout as "options" in declarative pipeline
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-49142 Jenkins / JENKINS-49142 Be able to customize checkout as "options" in declarative pipeline Change By: Jose Blas Camacho Taboada Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44376) Ability to set variables shared between stages
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-44376 Jenkins / JENKINS-44376 Ability to set variables shared between stages Change By: Jose Blas Camacho Taboada Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44376) Ability to set variables shared between stages
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-44376 Change By: Jose Blas Camacho Taboada Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49950) Specifying Docker registry credentials should not silently fail if using default URL
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-49950 Jenkins / JENKINS-49950 Specifying Docker registry credentials should not silently fail if using default URL Change By: Jose Blas Camacho Taboada Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49950) Specifying Docker registry credentials should not silently fail if using default URL
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-49950 Jenkins / JENKINS-49950 Specifying Docker registry credentials should not silently fail if using default URL Change By: Jose Blas Camacho Taboada Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49142) Be able to customize checkout as "options" in declarative pipeline
Title: Message Title Jose Blas Camacho Taboada commented on JENKINS-49142 Re: Be able to customize checkout as "options" in declarative pipeline Hi Leandro Lucarella, I'm working in this ticket, would you mind to take a look into it? Github PR: https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/307 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49142) Be able to customize checkout as "options" in declarative pipeline
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-49142 Jenkins / JENKINS-49142 Be able to customize checkout as "options" in declarative pipeline Change By: Jose Blas Camacho Taboada Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52744) Using not existing environment variables in environment GString expression causes strange error message
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-52744 Using not existing environment variables in environment GString _expression_ causes strange error message Change By: Jose Blas Camacho Taboada Assignee: Andrew Bayer Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52744) Using not existing environment variables in environment GString expression causes strange error message
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-52744 Change By: Jose Blas Camacho Taboada Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48661) Execute stage only after initial pipeline execution
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-48661 Execute stage only after initial pipeline execution Change By: Jose Blas Camacho Taboada Assignee: Andrew Bayer Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44376) Ability to set variables shared between stages
Title: Message Title Jose Blas Camacho Taboada stopped work on JENKINS-44376 Change By: Jose Blas Camacho Taboada Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48661) Execute stage only after initial pipeline execution
Title: Message Title
Jose Blas Camacho Taboada commented on JENKINS-48661
Re: Execute stage only after initial pipeline execution
Hi Steven Foster there is a new feature that could be used for this triggeredBy, please see the following example where a build triggered by an user (vlinde in the example) executes the Stage Two
pipeline {
agent any
stages {
stage("One") {
steps {
echo "Hello"
}
}
stage("Two") {
when {
triggeredBy cause: "UserIdCause", detail: "vlinde"
}
steps {
script {
echo "World"
echo "Heal it"
}
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44376) Ability to set variables shared between stages
Title: Message Title
Jose Blas Camacho Taboada edited a comment on JENKINS-44376
Re: Ability to set variables shared between stages
Hi [~laurentperez], have you tried to set the environment variables in the top level? {noformat}pipeline {environment {FOO = "FOO"}agent anystages {stage("foo") {steps {echo " FOO-1 is ${env.FOO}"}}stage("group") {steps {echo " FOO-2 is ${env.FOO}"}} stage("Override"){environment {FOO = "BOO" } steps{echo " FOO-3 is ${env.FOO } "}}}} {noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44376) Ability to set variables shared between stages
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-44376 Change By: Jose Blas Camacho Taboada Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44376) Ability to set variables shared between stages
Title: Message Title
Jose Blas Camacho Taboada commented on JENKINS-44376
Re: Ability to set variables shared between stages
Hi laurent perez, have you tried to set the environment variables in the top level?
pipeline {
environment {
FOO = "FOO"
}
agent any
stages {
stage("foo") {
steps {
echo " FOO-1 is ${env.FOO}"
}
}
stage("group") {
steps {
echo " FOO-2 is ${env.FOO}"
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44376) Ability to set variables shared between stages
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-44376 Ability to set variables shared between stages Change By: Jose Blas Camacho Taboada Assignee: Andrew Bayer Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49950) Specifying Docker registry credentials should not silently fail if using default URL
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-49950 Change By: Jose Blas Camacho Taboada Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52735) checkoutToSubdirectory() ignored on first commit of new branch
Title: Message Title Jose Blas Camacho Taboada closed an issue as Not A Defect Should be fixed following the instructions provided Jenkins / JENKINS-52735 checkoutToSubdirectory() ignored on first commit of new branch Change By: Jose Blas Camacho Taboada Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46894) Provide means of detecting cause of build from declarative pipeline
Title: Message Title
Jose Blas Camacho Taboada commented on JENKINS-46894
Re: Provide means of detecting cause of build from declarative pipeline
Costin Caraivan, you can check the documentation here: https://jenkins.io/doc/book/pipeline/syntax/#declarative-pipeline And an example is: when { triggeredBy 'SCMTrigger' } or TimerTrigger
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49950) Specifying Docker registry credentials should not silently fail if using default URL
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-49950 Specifying Docker registry credentials should not silently fail if using default URL Change By: Jose Blas Camacho Taboada Assignee: Andrew Bayer Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49142) Be able to customize checkout as "options" in declarative pipeline
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-49142 Jenkins / JENKINS-49142 Be able to customize checkout as "options" in declarative pipeline Change By: Jose Blas Camacho Taboada Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52735) checkoutToSubdirectory() ignored on first commit of new branch
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-52735 Jenkins / JENKINS-52735 checkoutToSubdirectory() ignored on first commit of new branch Change By: Jose Blas Camacho Taboada Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52735) checkoutToSubdirectory() ignored on first commit of new branch
Title: Message Title Jose Blas Camacho Taboada stopped work on JENKINS-52735 Change By: Jose Blas Camacho Taboada Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49280) pipeline docker agent configuration is inconsistent
Title: Message Title Jose Blas Camacho Taboada stopped work on JENKINS-49280 Change By: Jose Blas Camacho Taboada Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49142) Be able to customize checkout as "options" in declarative pipeline
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-49142 Change By: Jose Blas Camacho Taboada Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49142) Be able to customize checkout as "options" in declarative pipeline
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-49142 Be able to customize checkout as "options" in declarative pipeline Change By: Jose Blas Camacho Taboada Assignee: Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49280) pipeline docker agent configuration is inconsistent
Title: Message Title
Jose Blas Camacho Taboada commented on JENKINS-49280
Re: pipeline docker agent configuration is inconsistent
Hi Jason Kohles, could you post more logs about this issue and more information about your pipeline? In my tests all the executions are in order. Also, could you test it with (and without it) this config option:
docker {
alwaysPull true
registryUrl ""
registryCredentialsId ""
image "*"
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46894) Provide means of detecting cause of build from declarative pipeline
Title: Message Title Jose Blas Camacho Taboada commented on JENKINS-46894 Re: Provide means of detecting cause of build from declarative pipeline This feature was implemented using run.getCauses() within a script in Utils.groovy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46894) Provide means of detecting cause of build from declarative pipeline
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-46894 Jenkins / JENKINS-46894 Provide means of detecting cause of build from declarative pipeline Change By: Jose Blas Camacho Taboada Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29977) Git Plugin truncates changelog
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-29977 Not released yet Jenkins / JENKINS-29977 Git Plugin truncates changelog Change By: Jose Blas Camacho Taboada Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29977) Git Plugin truncates changelog
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-29977 Jenkins / JENKINS-29977 Git Plugin truncates changelog Change By: Jose Blas Camacho Taboada Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29977) Git Plugin truncates changelog
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-29977 Change By: Jose Blas Camacho Taboada Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49280) pipeline docker agent configuration is inconsistent
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-49280 pipeline docker agent configuration is inconsistent Change By: Jose Blas Camacho Taboada Assignee: Andrew Bayer Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49280) pipeline docker agent configuration is inconsistent
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-49280 Change By: Jose Blas Camacho Taboada Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46894) Provide means of detecting cause of build from declarative pipeline
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-46894 Provide means of detecting cause of build from declarative pipeline Change By: Jose Blas Camacho Taboada Assignee: rsandell Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46894) Provide means of detecting cause of build from declarative pipeline
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-46894 Change By: Jose Blas Camacho Taboada Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49997) Pipeline Declarative post unsuccessful block
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-49997 Jenkins / JENKINS-49997 Pipeline Declarative post unsuccessful block Change By: Jose Blas Camacho Taboada Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49997) Pipeline Declarative post unsuccessful block
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-49997 Change By: Jose Blas Camacho Taboada Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52735) checkoutToSubdirectory() ignored on first commit of new branch
Title: Message Title
Jose Blas Camacho Taboada edited a comment on JENKINS-52735
Re: checkoutToSubdirectory() ignored on first commit of new branch
[~jenkinsedupuis], apparently is a configuration error. When using *checkoutToSuddirectory* it applies to the default checkout, hence you can see the checkout to /MyApplication. Then, when *checkout scm* a new checkout is done to the workspace root directory, that's the the second checkout to the root dir. Probably, in order to achieve that you want you would need to _skipDefaultCheckout(true)_ and wrap the *checkout scm* with *dir('MyApplication') \{ ... }*. With this configuration you avoid the default checkout and the a your checkout happens in that particular folder. ** Please, let us know if you can fix this problem. **
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52735) checkoutToSubdirectory() ignored on first commit of new branch
Title: Message Title
Jose Blas Camacho Taboada commented on JENKINS-52735
Re: checkoutToSubdirectory() ignored on first commit of new branch
Étienne Dupuis, apparently is a configuration error. When using checkoutToSuddirectory it applies to the default checkout, hence you can see the checkout to /MyApplication. Then, when checkout scm a new checkout is done to the workspace root directory, that's the the second checkout to the root dir. Probably, in order to achieve that you want you would need to skipDefaultCheckout(true) and wrap the checkout scm with dir('MyApplication') { ... }. With this configuration you avoid the default checkout and the a your checkout happens in that particular folder. ** Please, let us know if you can fix this problem. **
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52735) checkoutToSubdirectory() ignored on first commit of new branch
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-52735 Change By: Jose Blas Camacho Taboada Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52735) checkoutToSubdirectory() ignored on first commit of new branch
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-52735 checkoutToSubdirectory() ignored on first commit of new branch Change By: Jose Blas Camacho Taboada Assignee: Andrew Bayer Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52735) checkoutToSubdirectory() ignored on first commit of new branch
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-52735 Jenkins / JENKINS-52735 checkoutToSubdirectory() ignored on first commit of new branch Change By: Jose Blas Camacho Taboada Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50880) Create a new option for running when condition before stage input
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-50880 Jenkins / JENKINS-50880 Create a new option for running when condition before stage input Change By: Jose Blas Camacho Taboada Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53558) Apply top level failFast option to all parallel stages inside Jenkinsfile.
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-53558 Jenkins / JENKINS-53558 Apply top level failFast option to all parallel stages inside Jenkinsfile. Change By: Jose Blas Camacho Taboada Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53558) Apply top level failFast option to all parallel stages inside Jenkinsfile.
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-53558 Change By: Jose Blas Camacho Taboada Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53558) Apply top level failFast option to all parallel stages inside Jenkinsfile.
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-53558 Apply top level failFast option to all parallel stages inside Jenkinsfile. Change By: Jose Blas Camacho Taboada Assignee: Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46067) Pipeline task scheduled on uninitialized node
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Jeff Thompson Jenkins / JENKINS-46067 Pipeline task scheduled on uninitialized node Change By: Jose Blas Camacho Taboada Assignee: Jose Blas Camacho Taboada Jeff Thompson Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40839) pipeline timeout doesn't kill the job
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Unassigned Jenkins / JENKINS-40839 pipeline timeout doesn't kill the job Change By: Jose Blas Camacho Taboada Assignee: Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Daniel Spilker Jenkins / JENKINS-53775 FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin Change By: Jose Blas Camacho Taboada Assignee: Jose Blas Camacho Taboada Daniel Spilker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Unassigned Jenkins / JENKINS-34256 Preparing Jenkins For Shutdown Hangs Running Pipelines Change By: Jose Blas Camacho Taboada Assignee: Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50880) Create a new option for running when condition before stage input
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-50880 Change By: Jose Blas Camacho Taboada Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50880) Create a new option for running when condition before stage input
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-50880 Create a new option for running when condition before stage input Change By: Jose Blas Camacho Taboada Assignee: Andrew Bayer Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29977) Git Plugin truncates changelog
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-29977 Git Plugin truncates changelog Change By: Jose Blas Camacho Taboada Assignee: Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53246) Regression in pipeline job features.
Title: Message Title Jose Blas Camacho Taboada commented on JENKINS-53246 Re: Regression in pipeline job features. Hi Markus Baur, I think you reported this issue, could you please take a look into the comment above regarding configuration and versions? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53246) Regression in pipeline job features.
Title: Message Title Jose Blas Camacho Taboada commented on JENKINS-53246 Re: Regression in pipeline job features. Hi Markus Baur, I am working in this issue, and I'm able to use the curl call to trigger the job nicely. Could you confirm the following: the Jenkins version if your instance has security active (Jenkins / Manage Jenkins / Configure Global Security -> enable security checkbox) The Jobs has the Trigger builds remotely active with the same token you are using (Jenkins -> your_job -> Configure -> Build Triggers) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
