[JIRA] [email-ext-plugin] (JENKINS-33980) Document (List) Pipeline features of email-ext-plugin
Title: Message Title Leon Leon edited a comment on JENKINS-33980 Re: Document (List) Pipeline features of email-ext-plugin Hello, this works fine for committers, do you have any idea about accessing the culprits list within a pipeline ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-33980) Document (List) Pipeline features of email-ext-plugin
Title: Message Title Leon Leon commented on JENKINS-33980 Re: Document (List) Pipeline features of email-ext-plugin Hello, this works fine for committers, do you have any idea about accessing the culprits list ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-34763) Email-ext plugin in Jenkins Pipeline
Title: Message Title Leon Leon created an issue Jenkins / JENKINS-34763 Email-ext plugin in Jenkins Pipeline Issue Type: New Feature Assignee: Alex Earl Components: email-ext-plugin, workflow-plugin Created: 2016/May/12 11:35 AM Environment: Operating System: Windows 7 64 bit Jenkins: 1.642.4 Java: 1.7.0_15 Email Extension Plugin 2.41.3 Pipeline 1.15 Priority: Blocker Reporter: Leon Leon Hello, We are trying to send use the Email Extension Plugin in the Pipeline. However, It is not possible to send the notification automatically to the culprits and/or committers (as for freestyle job). I get the followign output when using the snippet generator: emailext body: 'body', subject: 'subject', to: 'my@email' Add Comment
[JIRA] [email-ext-plugin] (JENKINS-34763) Email-ext plugin (culprits and committers) in Jenkins Pipeline
Title: Message Title Leon Leon updated an issue Jenkins / JENKINS-34763 Email-ext plugin (culprits and committers) in Jenkins Pipeline Change By: Leon Leon Summary: Email-ext plugin (culprits and committers) in Jenkins Pipeline Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32997) Pipeline job: Abort older builds which are running
Title: Message Title Leon Leon edited a comment on JENKINS-32997 Re: Pipeline job: Abort older builds which are running Thank you for the information.This issue is related to [JENKINS-27039|https://issues.jenkins-ci.org/browse/JENKINS-27039] independently of user inputs. The Use Case is to make the last build able to abort older builds in a specific stage (and by doing so , just one build will perform some operations once daily for example).In other words, a specific stage should have only the last build which passed all older stages running on it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32997) Pipeline job: Abort older builds which are running
Title: Message Title Leon Leon edited a comment on JENKINS-32997 Re: Pipeline job: Abort older builds which are running Thank you for the information.This issue is related to [JENKINS-27039|https://issues.jenkins-ci.org/browse/JENKINS-27039] independently of user inputs. The Use Case is to make the last build able to abort older builds in a specific stage (and by doing so just one build performing will perform some operations once daily for example ).In other words, a specific stage should have only the last build which passed all older stages running on it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32997) Pipeline job: Abort older builds which are running
Title: Message Title Leon Leon edited a comment on JENKINS-32997 Re: Pipeline job: Abort older builds which are running Thank you for the information. This issue is related to [JENKINS-27039|https://issues.jenkins-ci.org/browse/JENKINS-27039] independently of user inputs. The Use Case is to make the last build able to abort older builds in a specific stage (and just one build performing some operations once daily).In other words, a specific stage should have only the last build which passed all older stages running on it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32997) Pipeline job: Abort older builds which are running
Title: Message Title Leon Leon commented on JENKINS-32997 Re: Pipeline job: Abort older builds which are running This issue is related to JENKINS-27039 independently of user inputs. The Use Case is to make the last build able to abort older builds in a specific stage (and just one build performing some operations once daily). In other words, a specific stage should have only the last build which passed all older stages running on it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-27140) Workflow support for Integrity SCM Plugin
Title: Message Title Leon Leon updated an issue Jenkins / JENKINS-27140 Workflow support for Integrity SCM Plugin Change By: Leon Leon Comment: We are using the special PTC plugin 1.31-4.10.9049 because we have an old MKS version.Which change should be made to this special PTC plugin version to make it compatible with workflow ?Any help will be very appreciated. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32997) Pipeline job: Abort older builds which are running
Title: Message Title Leon Leon updated an issue Jenkins / JENKINS-32997 Pipeline job: Abort older builds which are running Change By: Leon Leon Is there a way to make the current build abort older builds (which are running) in a workflow job ?Scenario:My workflow contains:- multiple stages to be run after every SCM changes- a stage to be run once every day based on the last build which passed all stages.I thought about using *waitUntil* and *stage concurrency: 1*Build #1 passed all normal stages and waitsBuild #2 passed all stages -> it should abort Build #1 and waitsBuild #3 passed all stages -> it should abort Build #2 and wait waits ...So I want to have just one build (the last one) waiting for the last stage and if waitUntil return true, only the last build should enter the last stage.Thank you in advance.Any help would be greatly appreciate. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32997) Pipeline job: Abort older builds which are running
Title: Message Title Leon Leon updated an issue Jenkins / JENKINS-32997 Pipeline job: Abort older builds which are running Change By: Leon Leon Is there a way to make the current build abort older builds (which are running) in a workflow job ?Scenario:My workflow contains:- multiple stages to be run after every SCM changes- a stage to be run once every day based on the last build which passed all stages.I thought about using *waitUntil *and *stage concurrency: 1*Build #1 passed all normal stages and enter the waitUntil waits Build #2 passed all stages -> it should abort Build #1 and waits Build #3 passed all stages -> it should abort Build #2 and wait ... So I want to have just one build (the last one) waiting for the last stage and if waitUntil return true, only the last build should enter the last stage.Thank you in advance.Any help would be greatly appreciate. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32997) Pipeline job: Abort older builds which are running
Title: Message Title Leon Leon updated an issue Jenkins / JENKINS-32997 Pipeline job: Abort older builds which are running Change By: Leon Leon Is there a way to make the current build abort older builds (which are running) in a workflow job ?Scenario:My workflow contains :- multiple stages to be run after every SCM changes , and - a stage to be run once every day based on the last build which passed all stages.I thought about using *waitUntil *and *stage concurrency: 1*Build #1 passed all normal stages and enter the waitUntilBuild #2 passed all stages -> it should abort Build #1Build #3 passed all stages -> it should abort Build #2So I want to have just one build (the last one) waiting for the last stage and if waitUntil return true, only the last build should enter the last stage.Thank you in advance.Any help would be greatly appreciate. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32997) Pipeline job: Abort older builds which are running
Title: Message Title Leon Leon updated an issue Jenkins / JENKINS-32997 Pipeline job: Abort older builds which are running Change By: Leon Leon Is there a way to make the current build abort older builds during the (which are running) in a workflow : job ? Scenario:My workflow contains multiple stages to be run after every SCM changes, and a stage to be run once every day based on the last build which passed all stages.I thought about using *waitUntil *and *stage concurrency: 1*Build #1 passed all normal stages and enter the waitUntilBuild #2 passed all stages -> it should abort Build #1Build #3 passed all stages -> it should abort Build #2So I want to have just one build (the last one) waiting for the last stage and if waitUntil return true, only the last build should enter the last stage.Thank you in advance.Any help would be greatly appreciate. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32997) Pipeline job: Abort older builds which are running
Title: Message Title Leon Leon updated an issue Jenkins / JENKINS-32997 Pipeline job: Abort older builds which are running Change By: Leon Leon Is there a function way to make the current build abort older builds during the workflow:Scenario:My workflow contains multiple steps stages to be runned run after every SCM changes, and a step stage to be runned run once every day based on the last build which passed all stages. I thought about using *waitUntil *and *stage concurrency: 1*Build #1 passed all normal stages and enter the waitUntilBuild #2 passed all stages -> it should abort Build #1Build #3 passed all stages -> it should abort Build #2So I want to have just one build (the last one) waiting for the last stage and if waitUntil return true, only the last build should enter the last stage.Thank you in advance.Any help would be greatly appreciate. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32997) Pipeline job: Abort older builds which are running
Title: Message Title Leon Leon created an issue Jenkins / JENKINS-32997 Pipeline job: Abort older builds which are running Issue Type: Task Assignee: Jesse Glick Components: workflow-plugin Created: 17/Feb/16 1:38 PM Environment: Pipeline version 1.13 Priority: Critical Reporter: Leon Leon Is there a function to make the current build abort older builds during the workflow: Scenario: My workflow contains multiple steps to be runned after every SCM changes, and a step to be runned once every day based on the last build which passed all stages. I thought about using waitUntil *and *stage concurrency: 1 Build #1 passed all normal stages and enter the waitUntil Build #2 passed all stages -> it should abort Build #1 Build #3 passed all stages -> it should abort Build #2 So I want to have just one build (the last one) waiting and if waitUntil return true, only the last build should enter the last stage. Thank you in advance. Any help would be greatly appreciate.
[JIRA] [workflow-plugin] (JENKINS-31154) 2.0: provide better workflow visualization out of the box
Title: Message Title Leon Leon updated an issue Jenkins / JENKINS-31154 2.0: provide better workflow visualization out of the box Change By: Leon Leon Comment: Hello everyone,Do you have experience with changing the source code of the pipeline/workflow plugin by yourself ?We are trying to change the visualization of the pipeline steps to make it more understandable for Jenkins users (developers or managers) and make it only show relevant steps:.i.e: showing steps (nodes) and their status like:- stages- running batch- parallel stepsBut not showing other steps like:- Allocate node : Start- Allocate node : Body : Start- Change Directory : StartIs such an operation possible or will it affect the workflow functionality ?I tried to made the changes by starting with the class FlowGraphTable.Any help would be greatly appreciated Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31154) 2.0: provide better workflow visualization out of the box
Title: Message Title Leon Leon commented on JENKINS-31154 Re: 2.0: provide better workflow visualization out of the box Hello everyone, Do you have experience with changing the source code of the pipeline plugin by yourself ? We are trying to change the visualization of the pipeline steps to make it more understandable for Jenkins users (developers or managers) and make it only show relevant steps:. i.e: showing steps (nodes) and their status like: stages running batch parallel steps But not showing other steps like: Allocate node : Start Allocate node : Body : Start Change Directory : Start Is such an operation possible or will at affect the workflow functionality ? I tried to made the changes by starting with the class FlowGraphTable. Any help would be greatly appreciated Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-31154) 2.0: provide better workflow visualization out of the box
Title: Message Title Leon Leon edited a comment on JENKINS-31154 Re: 2.0: provide better workflow visualization out of the box Hello everyone,Do you have experience with changing the source code of the pipeline /workflow plugin by yourself ?We are trying to change the visualization of the pipeline steps to make it more understandable for Jenkins users (developers or managers) and make it only show relevant steps:.i.e: showing steps (nodes) and their status like:- stages- running batch- parallel stepsBut not showing other steps like:- Allocate node : Start- Allocate node : Body : Start- Change Directory : StartIs such an operation possible or will at affect the workflow functionality ?I tried to made the changes by starting with the class FlowGraphTable.Any help would be greatly appreciated Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31154) 2.0: provide better workflow visualization out of the box
Title: Message Title Leon Leon edited a comment on JENKINS-31154 Re: 2.0: provide better workflow visualization out of the box Hello everyone,Do you have experience with changing the source code of the pipeline/workflow plugin by yourself ?We are trying to change the visualization of the pipeline steps to make it more understandable for Jenkins users (developers or managers) and make it only show relevant steps:.i.e: showing steps (nodes) and their status like:- stages- running batch- parallel stepsBut not showing other steps like:- Allocate node : Start- Allocate node : Body : Start- Change Directory : StartIs such an operation possible or will at it affect the workflow functionality ?I tried to made the changes by starting with the class FlowGraphTable.Any help would be greatly appreciated Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32675) Pipeline Plugin: Adjusting the Visualization of Pipeline Steps
Title: Message Title Leon Leon created an issue Jenkins / JENKINS-32675 Pipeline Plugin: Adjusting the Visualization of Pipeline Steps Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 28/Jan/16 3:24 PM Environment: Workflow Plugin 1.10 Pipeline Plugin 1.13 Priority: Minor Reporter: Leon Leon Hello everyone, We are trying to change the visualization of the pipeline steps to make it more understandable for Jenkins users (developers or managers) and make it only show relevant steps:. i.e: showing nodes like: stages running batch parallel steps But not showing other steps like:
[JIRA] [workflow-plugin] (JENKINS-32675) Pipeline Plugin: Adjusting the Visualization of Pipeline Steps
Title: Message Title Leon Leon updated an issue Jenkins / JENKINS-32675 Pipeline Plugin: Adjusting the Visualization of Pipeline Steps Change By: Leon Leon Hello everyone,We are trying to change the visualization of the pipeline steps to make it more understandable for Jenkins users (developers or managers) and make it only show relevant steps:.i.e: showing nodes like: - stages- running batch- parallel stepsBut not showing other steps like:- Allocate node : StartAllocate node : Body : StartChange Directory : Start My question: Is such an operation possible or will at affect the workflow functionality ?I tried to made the changes by starting with the class FlowGraphTable.Thank you in advance.Any help would be greatly appreciated Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-27140) Workflow support for Integrity SCM Plugin
Title: Message Title Leon Leon reopened an issue Jenkins / JENKINS-27140 Workflow support for Integrity SCM Plugin Change By: Leon Leon Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-27140) Workflow support for Integrity SCM Plugin
Title: Message Title Leon Leon commented on JENKINS-27140 Re: Workflow support for Integrity SCM Plugin We are using the special PTC plugin 1.31-4.10.9049 because we have an old MKS version. Which change should be made to this special PTC plugin version to make it compatible with workflow ? Any help will be very appreciated. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-25228) Using the integrity-plugin together with concurrent builds causes SQL Exceptions
Title: Message Title Leon Leon commented on JENKINS-25228 Re: Using the integrity-plugin together with concurrent builds causes SQL Exceptions Yes, workflow jobs. We are already using the PTC Plugin special one off version 1.31-4.10.9049 with Workflow Plugin version 1.10 and 1.11 beta and we are "sometimes" facing the issue mentionaed earlier. Is it not unadvisable to use the PTC Plugin with Workflow ? Thank you for your help. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-25228) Using the integrity-plugin together with concurrent builds causes SQL Exceptions
Title: Message Title Leon Leon edited a comment on JENKINS-25228 Re: Using the integrity-plugin together with concurrent builds causes SQL Exceptions Yes, workflow jobs.We are already using the PTC Plugin special one off version 1.31-4.10.9049 with Workflow Plugin version 1.10 and 1.11 beta and we are "sometimes" facing the issue mentionaed mentioned earlier. Is it not unadvisable to use the PTC Plugin with Workflow ?Thank you for your help. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-25228) Using the integrity-plugin together with concurrent builds causes SQL Exceptions
Title: Message Title
Leon Leon edited a comment on JENKINS-25228
Re: Using the integrity-plugin together with concurrent builds causes SQL Exceptions
Can you please tell me in which PTC plugin version is the problem solved ? We are using PTC version 1.34 and this problem still persisting with workflow jobs.{color:red}A SQL Exception was caught!Table/View 'SCM_E9A7D857_553C_48D3_AF6D_FF45A06EFD90' does not exist.{color}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-25228) Using the integrity-plugin together with concurrent builds causes SQL Exceptions
Title: Message Title Leon Leon commented on JENKINS-25228 Re: Using the integrity-plugin together with concurrent builds causes SQL Exceptions Can you please tell me in which PTC plugin version is the problem solved ? We are using version 1.34 and this problem still persisting with workflow jobs. A SQL Exception was caught! Table/View 'SCM_E9A7D857_553C_48D3_AF6D_FF45A06EFD90' does not exist. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-30966) Integrity Plugin - Dropped members issue
Title: Message Title Leon Leon commented on JENKINS-30966 Re: Integrity Plugin - Dropped members issue Thank you very much for you support. I still need help with the first question: Is there a way to check which members will be really check-out in the curent build (in the class IntegritySCM or in another java class) ? We need that information because we are generating a report containing these information. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-30966) Integrity Plugin - Dropped members issue
Title: Message Title Leon Leon commented on JENKINS-30966 Re: Integrity Plugin - Dropped members issue I am using the option "clean workspace" and all other options are unchecked. Why does the projectMembersList list still contain the dropped member ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-30966) Integrity Plugin - Dropped members issue
Title: Message Title Leon Leon commented on JENKINS-30966 Re: Integrity Plugin - Dropped members issue Yes, it is needed in the change log report which contains dropped members. But is there a way to access a list containing just the members which will be checked-out ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-30966) Integrity Plugin - Dropped members issue
Title: Message Title Leon Leon created an issue Jenkins / JENKINS-30966 Integrity Plugin - Dropped members issue Issue Type: Task Assignee: Cletus D'Souza Components: integrity-plugin Created: 15/Oct/15 7:50 AM Environment: Operating System: Windows 7 64 bit Jenkins: 1.609.3 Java: 1.7.0_15 PTC Integrity Plugin version 1.34 Priority: Major Reporter: Leon Leon Hello everyone, I noticed that after dropping a member from MKS, the next build will check-out the remaining members (as expected) but in the "Successfully checked out" output the number of all members is listed. So for example if I have initially 10 members, and then drop one and then build: 9 members will be check out (that is correct) but and I got the output: "Successfully checked out 10 files!" That means that the dropped member is still in the projectMembersList List. Is there a way to correct this ? or to get access to the members which will be really check-out in the curent build (in the class IntegritySCM). I am trying to generate a report containing the checked-out members. Thank you in advance.
[JIRA] [warnings-plugin] (JENKINS-27209) Enable reporting of compiler warnings in workflow steps
Title: Message Title Leon Leon commented on JENKINS-27209 Re: Enable reporting of compiler warnings in workflow steps I am trying to use the compiler warnings in workflow. Since it is not available in the snippet generator. I am calling it this way: step([$class: 'WarningsPublisher', consoleParsers: [[parserName: 'myParser']]]) How can I add more options to it ? I need to make it always run even if the build failed (So I need this option: Run always: If this plug-in should run even for failed builds then activate this check box) Thank you. in advance Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-27209) Enable reporting of compiler warnings in workflow steps
Title: Message Title
Leon Leon edited a comment on JENKINS-27209
Re: Enable reporting of compiler warnings in workflow steps
I am trying to use the compiler warnings in workflow. However, since it is not available in the snippet generator. I am calling it this way:{color:red}step([$class: 'WarningsPublisher', consoleParsers: [[parserName: 'myParser']]]){color}How can I add more options to this ? I need to make it always run even if the build failed (So I need this option: Run always: If this plug-in should run even for failed builds then activate this check box)Thank you . in advance
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-27209) Enable reporting of compiler warnings in workflow steps
Title: Message Title Leon Leon edited a comment on JENKINS-27209 Re: Enable reporting of compiler warnings in workflow steps I am trying to use the compiler warnings in workflow. Since However, since it is not available in the snippet generator. I am calling it this way:step([$class: 'WarningsPublisher', consoleParsers: [[parserName: 'myParser']]])How can I add more options to it this ? I need to make it always run even if the build failed (So I need this option: Run always: If this plug-in should run even for failed builds then activate this check box)Thank you. in advance Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-27209) Enable reporting of compiler warnings in workflow steps
Title: Message Title
Leon Leon edited a comment on JENKINS-27209
Re: Enable reporting of compiler warnings in workflow steps
I am trying to use the compiler warnings in workflow. However, since it is not available in the snippet generator. I am calling it this way: {color:red} step([$class: 'WarningsPublisher', consoleParsers: [[parserName: 'myParser']]]) {color} How can I add more options to this ? I need to make it always run even if the build failed (So I need this option: Run always: If this plug-in should run even for failed builds then activate this check box)Thank you. in advance
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29889) Support of PTC Integrity in Wokflow version 1.9
Title: Message Title Leon Leon created an issue Jenkins / JENKINS-29889 Support of PTC Integrity in Wokflow version 1.9 Issue Type: Bug Assignee: Jesse Glick Attachments: Capture.PNG Components: workflow-plugin Created: 11/Aug/15 9:41 AM Environment: Operating System: Windows 7 64 bit Jenkins: 1.596.2 and 1.609.1 Java: 1.7.0_15 Workflow 1.9 Priority: Minor Reporter: Leon Leon Hello everyone, It seems that after updating the workflow to version 1.9, only Subversion is available as option in General SCM step with the Snippet Generator. Does that mean that other SCM are not supported correctly ? However when I tried to configure Integrity there: setting fetchChangedWorkspaceFiles to true did not overwrite and update the
[JIRA] [workflow-plugin] (JENKINS-29563) Access old builds properties in a Workflow job
Title: Message Title Leon Leon closed an issue as Not A Defect Such properties can be accessed with: def Run lastSuccessfulBuild = job.getLastSuccessfulBuild() def lastSuccessfulBuildStrTime = lastSuccessfulBuild.getStartTimeInMillis() Jenkins / JENKINS-29563 Access old builds properties in a Workflow job Change By: Leon Leon Status: Open Closed Resolution: NotADefect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29656) Workflow failed after Warning: program state save failed
Title: Message Title
Leon Leon updated an issue
Jenkins / JENKINS-29656
Workflow failed after Warning: program state save failed
Change By:
Leon Leon
Helloeveryone,Iamfacingaprogramstatesavefailederrorwhichpreventstheworkflowfromrunningthenextsteps.{code} {color:red} org.jenkinsci.plugins.workflow.cps.CpsThreadGroupsaveProgramWARNING:programstatesavefailedjava.io.IOException:renameC:\Jenkins\current\jobs\MyWorkflowJob\builds\134\atomic3893270739985964803.tmptoC:\Jenkins\current\jobs\MyWorkflowJob\builds\134\program.datfailed atorg.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:350) atorg.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:328) atorg.jenkinsci.plugins.workflow.cps.CpsStepContext$3.onSuccess(CpsStepContext.java:482) atorg.jenkinsci.plugins.workflow.cps.CpsStepContext$3.onSuccess(CpsStepContext.java:478) atorg.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:519) atorg.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:32) atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) atjava.util.concurrent.FutureTask.run(FutureTask.java:166) athudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) atjenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) atjava.util.concurrent.FutureTask.run(FutureTask.java:166) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) atjava.lang.Thread.run(Thread.java:722) {color} {code}Itseemsthatthefollowinginstructionfromtheorg.jenkinsci.plugins.workflow.cps.CpsThreadGroupclassisthereason:{ color:red code }if(!tmpFile.renameTo(f)){thrownewIOException(rename+tmpFile+to+f+failed);}LOGGER.log(FINE,programstatesaved);}catch(RuntimeExceptione){LOGGER.log(WARNING,programstatesavefailed,e);propagateErrorToWorkflow(e);thrownewIOException(Failedtopersist+f,e);}{ color code }Butwhydoesthathappenandhowcanitbesolved?Thankyouinadvance.
Add Comment
[JIRA] [workflow-plugin] (JENKINS-29656) Workflow failed after Warning: program state save failed
Title: Message Title
Leon Leon updated an issue
Jenkins / JENKINS-29656
Workflow failed after Warning: program state save failed
Change By:
Leon Leon
Helloeveryone,Iamfacingaprogramstatesavefailederrorwhichpreventstheworkflowfromrunningthenextsteps.{ code}{ color:red}org.jenkinsci.plugins.workflow.cps.CpsThreadGroupsaveProgramWARNING:programstatesavefailedjava.io.IOException:renameC:\Jenkins\current\jobs\MyWorkflowJob\builds\134\atomic3893270739985964803.tmptoC:\Jenkins\current\jobs\MyWorkflowJob\builds\134\program.datfailed atorg.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:350) atorg.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:328) atorg.jenkinsci.plugins.workflow.cps.CpsStepContext$3.onSuccess(CpsStepContext.java:482) atorg.jenkinsci.plugins.workflow.cps.CpsStepContext$3.onSuccess(CpsStepContext.java:478) atorg.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:519) atorg.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:32) atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) atjava.util.concurrent.FutureTask.run(FutureTask.java:166) athudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) atjenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) atjava.util.concurrent.FutureTask.run(FutureTask.java:166) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) atjava.lang.Thread.run(Thread.java:722){color} {code} Itseemsthatthefollowinginstructionfromtheorg.jenkinsci.plugins.workflow.cps.CpsThreadGroupclassisthereason:{color:red}if(!tmpFile.renameTo(f)){thrownewIOException(rename+tmpFile+to+f+failed);}LOGGER.log(FINE,programstatesaved);}catch(RuntimeExceptione){LOGGER.log(WARNING,programstatesavefailed,e);propagateErrorToWorkflow(e);thrownewIOException(Failedtopersist+f,e);}{color}Butwhydoesthathappenandhowcanitbesolved?Thankyouinadvance.
Add Comment
[JIRA] [workflow-plugin] (JENKINS-29656) Workflow failed after Warning: program state save failed
Title: Message Title Leon Leon created an issue Jenkins / JENKINS-29656 Workflow failed after Warning: program state save failed Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 27/Jul/15 3:04 PM Environment: Operating System: Windows 7 64 bit Jenkins: 1.596.2 and 1.609.1 Java: 1.7.0_15 Priority: Blocker Reporter: Leon Leon Hello everyone, I am facing a program state save failed error which prevents the workflow from running the next steps. org.jenkinsci.plugins.workflow.cps.CpsThreadGroup saveProgram WARNING: program state save failed java.io.IOException: rename C:\Jenkins\current\jobs\MyWorkflowJob\builds\134\atomic3893270739985964803.tmp to C:\Jenkins\current\jobs\MyWorkflowJob\builds\134\program.dat failed at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:350) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:328) at org.jenkinsci.plugins.workflow.cps.CpsStepContext$3.onSuccess(CpsStepContext.java:482) at org.jenkinsci.plugins.workflow.cps.CpsStepContext$3.onSuccess(CpsStepContext.java:478) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:519) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:32) at
[JIRA] [workflow-plugin] (JENKINS-29563) Access old builds properties in a Workflow job
Title: Message Title Leon Leon updated an issue Jenkins / JENKINS-29563 Access old builds properties in a Workflow job Change By: Leon Leon Helloeveryone,IsitpossibletoaccessthelastfailedbuildandthelastsuccessfulbuildinformationswithinaworkflowJob?TheinformationIneedisthestarttimeofthosebuilds ,inordertoknowhowlongthebuildisfailing .Thankyou. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29563) Access old builds settings in a Workflow job
Title: Message Title Leon Leon created an issue Jenkins / JENKINS-29563 Access old builds settings in a Workflow job Issue Type: Task Assignee: Jesse Glick Components: workflow-plugin Created: 22/Jul/15 9:28 AM Environment: Operating System: Windows 7 64 bit Jenkins: 1.596.2 and 1.609.1 Java: 1.7.0_15 Priority: Minor Reporter: Leon Leon Hello everyone, Is it possible to access the last failed build and the last successful build informations within a workflow Job ? The information I need is the start time of those builds, in order to know how long the build is failing. Thank you. Add Comment
[JIRA] [workflow-plugin] (JENKINS-29563) Access old builds properties in a Workflow job
Title: Message Title Leon Leon updated an issue Jenkins / JENKINS-29563 Access old builds properties in a Workflow job Change By: Leon Leon Summary: Accessoldbuilds settings properties inaWorkflowjob Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [locks-and-latches-plugin] (JENKINS-29461) Using a lock in a Wokflow Job
Title: Message Title Leon Leon updated an issue Jenkins / JENKINS-29461 Using a lock in a Wokflow Job Change By: Leon Leon Helloeveryone,Iwanttousealockinaworkflowjobinordertopreventjobsfromrunningatthesametimeonthesamenode. Iwanttousethefunctionalityofthelockandlatchesplugintocontroltheparallelexecutionofjobs:WhenaJobAstartsbuildingonaspecificnode,JobBshouldwaituntilAisdone,andthenBcanrun. HowcanIachievethat?oristhereanothersolution(incaselocksarenotsupportedinworkflowjobs)? Thankyou. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [locks-and-latches-plugin] (JENKINS-29461) Using a lock in a Wokflow Job
Title: Message Title Leon Leon created an issue Jenkins / JENKINS-29461 Using a lock in a Wokflow Job Issue Type: Improvement Assignee: stephenconnolly Components: locks-and-latches-plugin, workflow-plugin Created: 16/Jul/15 1:20 PM Environment: Operating System: Windows 7 64 bit Jenkins: 1.596.2 and 1.609.1 Java: 1.7.0_15 Priority: Major Reporter: Leon Leon Hello everyone, I want to use a lock in a workflow job in order to prevent jobs from running at the same time on the same node. How can I achieve that ? or is there another solution (in case locks are not supported in workflow jobs) ? Thank you. Add Comment
