[JIRA] [mercurial-plugin] (JENKINS-22825) Support latesttag in Mercurial
Title: Message Title Justinas Urbanavicius commented on JENKINS-22825 Re: Support latesttag in Mercurial mercurial has a built in latest tag it's called "tip", you can specify it as the tag name and it will always build the latest comitted revision. 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] [hp-application-automation-tools-plugin] (JENKINS-34553) Jenkins plugin doesn't check if ALM server address is truly belongs to ALM server.
Title: Message Title Jason Kuang commented on JENKINS-34553 Re: Jenkins plugin doesn't check if ALM server address is truly belongs to ALM server. fixed, already created a pull request:https://github.com/hpsa/hp-application-automation-tools-plugin/pull/84 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] [hp-application-automation-tools-plugin] (JENKINS-34553) Jenkins plugin doesn't check if ALM server address is truly belongs to ALM server.
Title: Message Title Jason Kuang created an issue Jenkins / JENKINS-34553 Jenkins plugin doesn't check if ALM server address is truly belongs to ALM server. Issue Type: Bug Assignee: Jason Kuang Components: hp-application-automation-tools-plugin Created: 2016/May/03 5:21 AM Priority: Minor Reporter: Jason Kuang From Center, defect Id:226292. Jenkins plugin doesn't check if ALM server address is truly belongs to ALM server. It looks like Jenkins check only host existance and: 1. Writes to log "Logged in successfully" even for non-ALM host 2. Sometimes it may lead to faux-passed builds (always leads on upload external test result) Add Comment
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-34225) globalization problem for SSE build
Title: Message Title Jason Kuang resolved as Fixed fixed, already created a pull request:https://github.com/hpsa/hp-application-automation-tools-plugin/pull/84 Jenkins / JENKINS-34225 globalization problem for SSE build Change By: Jason Kuang Status: Open Resolved Resolution: Fixed 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] [job-dsl-plugin] (JENKINS-34552) parameterFactories support for hudson.plugins.parameterizedtrigger.FileBuildParameterFactory
Title: Message Title zuo wuhui created an issue Jenkins / JENKINS-34552 parameterFactories support for hudson.plugins.parameterizedtrigger.FileBuildParameterFactory Issue Type: Bug Assignee: Daniel Spilker Attachments: Screenshot-14.png Components: job-dsl-plugin Created: 2016/May/03 3:02 AM Environment: job-dsl-plugin version:1.45 Parameterized Trigger plugin version:2.30 Priority: Major Reporter: zuo wuhui parameterFactories only support $class: hudson.plugins.parameterizedtrigger.BinaryFileParameterFactory by #forMatchingFiles[https://jenkinsci.github.io/job-dsl-plugin/#path/job-steps-downstreamParameterized-trigger-parameterFactories-forMatchingFiles] But the important function is not support:hudson.plugins.parameterizedtrigger.FileBuildParameterFactory
[JIRA] [job-dsl-plugin] (JENKINS-34551) scm#git#cleanBeforeCheckout is wrong.
Title: Message Title zuo wuhui created an issue Jenkins / JENKINS-34551 scm#git#cleanBeforeCheckout is wrong. Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2016/May/03 2:30 AM Environment: version: 1.45 Priority: Major Reporter: zuo wuhui see: https://github.com/sheehan/job-dsl-playground/issues/29 Add Comment
[JIRA] [core] (JENKINS-34550) Remote Command Execution - running a job on Windows machines, it is possible to escape parameters by adding “ before string and execute commands on target system.
Title: Message Title jmarz created an issue Jenkins / JENKINS-34550 Remote Command Execution - running a job on Windows machines, it is possible to escape parameters by adding “ before string and execute commands on target system. Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/May/02 11:55 PM Priority: Minor Reporter: jmarz When running a job on Windows machines, it is possible to escape parameters by adding “ before string and execute commands on target system. we were able to run system commands, mount shares and bring files in and out of the machine. Impact: By running commands on build machine, user will be able to see other user’s jobs, steal credentials, and install a backdoor shell. Criticality is set to high since user has to be authenticated to Jenkins. Suggested Remediation: Escape input strings for parameters, just like on Unix machines. Add Comment
[JIRA] [matrix-project-plugin] (JENKINS-33230) Jenkins creates lots of warning message for creating matrix project root directory
Title: Message Title Rick Liu commented on JENKINS-33230 Re: Jenkins creates lots of warning message for creating matrix project root directory Hi kohsuke, Do you know when my pull-request (https://github.com/jenkinsci/matrix-project-plugin/pull/34) will be merged to trunk? 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] [ws-cleanup-plugin] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Sven Schott commented on JENKINS-24824 Re: Asynchronous cleanup not removing renamed workspace directories on slaves Hi, just wanting to know if there is a timeframe on resolution of this issue. Would like to know just in case it's not in the near future so that I can set up a semi-temporary workaround for the problem (most likely a scheduled cleanup on our windows machines). 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] [powershell-plugin] (JENKINS-31069) Error after 1.3 Powershell Plugin Update
Title: Message Title Alex Earl resolved as Cannot Reproduce Need more information to reproduce this issue. I haven't been able to do so. Jenkins / JENKINS-31069 Error after 1.3 Powershell Plugin Update Change By: Alex Earl Status: Open Resolved Resolution: Cannot Reproduce 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] [gitlab-plugin] (JENKINS-34549) Pipeline script editor is squashed when gitlab plugin trigger is enabled
Title: Message Title owenmehegan updated an issue Jenkins / JENKINS-34549 Pipeline script editor is squashed when gitlab plugin trigger is enabled Change By: owenmehegan Attachment: script not squashed.png Attachment: script squashed.png 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] [gitlab-plugin] (JENKINS-34549) Pipeline script editor is squashed when gitlab plugin trigger is enabled
Title: Message Title owenmehegan created an issue Jenkins / JENKINS-34549 Pipeline script editor is squashed when gitlab plugin trigger is enabled Issue Type: Bug Assignee: Tom FENNELLY Components: gitlab-plugin, workflow-plugin Created: 2016/May/02 11:01 PM Environment: Chrome 50, MacOS Labels: user-experience Priority: Minor Reporter: owenmehegan The ACE Pipeline script editor (as of version 2.0 of the Pipeline plugin) is squashed, width-wise, when the GitLab plugin is installed and its trigger is enabled for a job. This could be an issue with the jelly files within that plugin, and as I'm a maintainer of it, if that's the case I'm ready to fix it. Just not sure how. Screen shots are attached.
[JIRA] [git-client-plugin] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title alex karpinski commented on JENKINS-30318 Re: Git plugin breaks usage of Git LFS due to lack of Git Clone use I can reproduce the same state Alex Agranov mentioned. But I really don't want to manually initialize a workspace any time I'm working with an LFS repo. I'd really prefer to have an appropriate way to work with LFS in Jenkins. 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] [core] (JENKINS-34548) InjectedTest failure: github plugin fails to start
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-34548 InjectedTest failure: github plugin fails to start Issue Type: Bug Assignee: Kirill Merkushev Components: core, github-plugin Created: 2016/May/02 10:12 PM Environment: ubuntu:15.04, run inside docker container Priority: Minor Reporter: Vivek Pandey Our plugin has maven dependency on github plugin. org.jenkins-ci.plugins git 2.4.2 InjectedTest are run during test run and it fails with the following error. Failure is random so not easy to reproduce. Running InjectedTest Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 9.611 sec <<< FAILURE! - in InjectedTest testPluginActive(org.jvnet.hudson.test.PluginAutomaticTestBuilder$OtherTests) Time elapsed: 0.086 sec <<< ERROR! java.lang.Error: Plugin github failed to start at
[JIRA] [jobconfighistory-plugin] (JENKINS-34151) Add support for Pipeline projects to display config changes in build history
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34151 Re: Add support for Pipeline projects to display config changes in build history Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/pipeline-plugin/9f9ad9cda0ab0d1fabaa87829cc677860d75dfc4 Log: JENKINS-34151 Noting. 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] [jobconfighistory-plugin] (JENKINS-34151) Add support for Pipeline projects to display config changes in build history
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-34151 Add support for Pipeline projects to display config changes in build history Change By: Jesse Glick Labels: workflow 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] [cloudbees-folder-plugin] (JENKINS-34546) Access Denied missing Job/Create Permission on New Item within Folder
Title: Message Title Benjamin Heiskell updated an issue Jenkins / JENKINS-34546 Access Denied missing Job/Create Permission on New Item within Folder Change By: Benjamin Heiskell When ACLs are enabled, users with full privileges on a folder receiving _Access Denied_ when trying to create a _New Item_ within a folder. It only occurs during the AJAX validation of _Item Name_. It does not prevent clicking OK and actually creating the new item.It appears the regression was introduced in 5.6. I think it is related to the changes to use the standard new page in this pull request: https://github.com/jenkinsci/cloudbees-folder-plugin/pull/48Reproducer:* Install Jenkins 1.651.1 (LTS)* Install folder plugin (5.9)* In "Configure Global Security" * * Enable "Jenkin's own user database with sign up" in "Configure Global Security" * * Save* Create a user account (bheiskell) and log in* In "Configure Global Security" * * Enable "Project-based Matrix Authorization Strategy" * * Add created user account (bheiskell) with full permissions * * Check Overall read permission for Anonymous* Create new folder (Folder) * * Enable project-based security * * Add user account (jsmith) to folder with full privileges* Logout and create a new account (jsmith)* Click New Item within the folder * * Type anything in the "Item Name" field 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,
[JIRA] [workflow-plugin] (JENKINS-34547) Make WorkflowJob.concurrentBuild into a JobProperty
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-34547 Make WorkflowJob.concurrentBuild into a JobProperty Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 2016/May/02 9:24 PM Priority: Major Reporter: Jesse Glick As described in JENKINS-30519 . Add Comment
[JIRA] [cloudbees-folder-plugin] (JENKINS-34546) Access Denied missing Job/Create Permission on New Item within Folder
Title: Message Title Benjamin Heiskell created an issue Jenkins / JENKINS-34546 Access Denied missing Job/Create Permission on New Item within Folder Issue Type: Bug Assignee: Jesse Glick Attachments: New Item [Jenkins] - Google Chrome_2016-05-02_17-09-30.png Components: cloudbees-folder-plugin Created: 2016/May/02 9:23 PM Environment: Vanilla installation of Jenkins 1.651.1 (LTS) on Linux with up to date plugins (folder plugin at 5.9) Priority: Minor Reporter: Benjamin Heiskell When ACLs are enabled, users with full privileges on a folder receiving Access Denied when trying to create a New Item within a folder. It only occurs during the AJAX validation of Item Name. It does not prevent clicking OK and actually creating the new item. It appears the regression was introduced in 5.6. I think it is related to the changes to use the standard new page in this pull request: https://github.com/jenkinsci/cloudbees-folder-plugin/pull/48 Reproducer:
[JIRA] [cloudbees-folder-plugin] (JENKINS-34546) Access Denied missing Job/Create Permission on New Item within Folder
Title: Message Title Benjamin Heiskell updated an issue Jenkins / JENKINS-34546 Access Denied missing Job/Create Permission on New Item within Folder Change By: Benjamin Heiskell When ACLs are enabled, users with full privileges on a folder receiving _Access Denied_ when trying to create a _New Item_ within a folder. It only occurs during the AJAX validation of _Item Name_. It does not prevent clicking OK and actually creating the new item.It appears the regression was introduced in 5.6. I think it is related to the changes to use the standard new page in this pull request: https://github.com/jenkinsci/cloudbees-folder-plugin/pull/48Reproducer:* Install Jenkins 1.651.1 (LTS)* Install folder plugin (5.9)* In "Configure Global Security" * Enable "Jenkin's own user database with sign up" in "Configure Global Security" * Save* Create a user account (bheiskell) and log in* In "Configure Global Security" * Enable "Project-based Matrix Authorization Strategy" * Add created user account (bheiskell) with full permissions * Check Overall read permission for Anonymous* Create new folder (Folder) * Enable project-based security * Add user account (jsmith) to folder with full privileges* Logout and create a new account (jsmith)* Click New Item within the folder * Type anything in the "Item Name" field 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
[JIRA] [role-strategy-plugin] (JENKINS-34545) Assigning roles is case sensitive, and it shouldn't be
Title: Message Title Christopher Shannon created an issue Jenkins / JENKINS-34545 Assigning roles is case sensitive, and it shouldn't be Issue Type: Bug Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 2016/May/02 9:07 PM Environment: Jenkins 1.646 Role-based Authorization Strategy 2.2.0 Labels: plugin plugins security Priority: Minor Reporter: Christopher Shannon Steps to reproduce: Create a user in Jenkins own user database with upper-case letters. Assign a role to this user, but use lower-case letters. Note that going back into Assign Roles shows the icon indicating that this user is valid.
[JIRA] [git-parameter-plugin] (JENKINS-34544) NPE After update to 0.5.0
Title: Message Title Boguslaw Klimas closed an issue as Fixed Jenkins / JENKINS-34544 NPE After update to 0.5.0 Change By: Boguslaw Klimas Status: Resolved Closed 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] [git-parameter-plugin] (JENKINS-34544) NPE After update to 0.5.0
Title: Message Title Boguslaw Klimas resolved as Fixed Jenkins / JENKINS-34544 NPE After update to 0.5.0 Change By: Boguslaw Klimas Status: In Progress Resolved Resolution: Fixed 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-32374) Workflow job item won't allow me to parameterize it
Title: Message Title Jesse Glick closed an issue as Cannot Reproduce Are you able to reproduce the issue from scratch? If so, how? Jenkins / JENKINS-32374 Workflow job item won't allow me to parameterize it Change By: Jesse Glick Status: Open Closed Resolution: Cannot Reproduce 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] [git-parameter-plugin] (JENKINS-34544) NPE After update to 0.5.0
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34544 Re: NPE After update to 0.5.0 Code changed in jenkins User: Boguslaw Klimas Path: src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java http://jenkins-ci.org/commit/git-parameter-plugin/b1cdf2653e4010603ff90cf02cd5f6fb54245b40 Log: Merge pull request #22 from jenkinsci/bugfix/JENKINS-34544 NPE After update to 0.5.0 Compare: https://github.com/jenkinsci/git-parameter-plugin/compare/11074b527dde...b1cdf2653e40 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] [git-parameter-plugin] (JENKINS-34544) NPE After update to 0.5.0
Title: Message Title Boguslaw Klimas started work on JENKINS-34544 Change By: Boguslaw Klimas Status: Open In Progress 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] [git-parameter-plugin] (JENKINS-34544) NPE After update to 0.5.0
Title: Message Title
Boguslaw Klimas created an issue
Jenkins / JENKINS-34544
NPE After update to 0.5.0
Issue Type:
Bug
Assignee:
Boguslaw Klimas
Components:
git-parameter-plugin
Created:
2016/May/02 8:45 PM
Priority:
Minor
Reporter:
Boguslaw Klimas
https://github.com/jenkinsci/git-parameter-plugin/pull/17#issuecomment-208865040
Jenkins LTS here (1.642.4), we get:
Caused by: java.lang.NullPointerException at java.util.regex.Pattern.(Pattern.java:1350) at java.util.regex.Pattern.compile(Pattern.java:1028) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.generateContents(GitParameterDefinition.java:313) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition$DescriptorImpl.doFillValueItems(GitParameterDefinition.java:399) definition is:
gitParam('GIT_BRANCH') { description('git branch to build') type('BRANCH') defaultValue('origin/dev/*') }
Add Comment
[JIRA] [template-project-plugin] (JENKINS-34543) Failure email generated for ClearCase UCM job when changing node name
Title: Message Title
Christopher Shannon updated an issue
Jenkins / JENKINS-34543
Failure email generated for ClearCase UCM job when changing node name
Change By:
Christopher Shannon
I believe that this issue is specific to the Template Project Plugin when the build steps result in "NOT_BUILT".I'm seeing some problems when changing node names on an existing ClearCase UCM job. Here are the steps to reproduce:# Create a job which uses the ClearCase UCM Plugin for SCM.# Set the job to Poll Self and Promotion Level INITIAL.# Set the job to poll SCM at a certain rate.# Set the job to use publishers from another job.# In this other job, configure an email notification upon failure.# Map this job to a given node.# Run the job enough to process all INITIAL baselines on the given stream (such that the job doesn't have anything to do until a new baseline is created).# Change the name of the node.What happens is that the job will execute the next time it polls: {{ Started on May 2, 2016 8:43:14 AMWorkspace is offline.Scheduling a new build to get a workspace. (nonexisting_workspace)Done. Took 1 msChanges found }} The job will then not build because there are no baselines available to process, but I get an email notification of a failed build. {{ 08:38:43 [CCUCM] * Promotion level: INITIAL08:38:43 08:38:45 ERROR: No valid baselines found08:38:45 [TemplateProject] Starting publishers from: 08:38:45 Sending e-mails to: 08:38:46 [TemplateProject] Successfully performed publishers from: 08:38:46 [CCUCM] Nothing to do!08:38:46 Build step 'ClearCase UCM' changed build result to NOT_BUILT08:38:46 Notifying upstream projects of job completion08:38:46 Finished: NOT_BUILT }} When I do a similar flow, but without using the Template Project Plugin, the email notification publisher is completely suppressed: {{ 08:43:22 [CCUCM] * Promotion level: INITIAL08:43:22 08:43:25 ERROR: No valid baselines found08:43:25 [WARNINGS] Skipping publisher since build result is FAILURE08:43:25 [CCUCM] Nothing to do!08:43:25 Build step 'ClearCase UCM' changed build result to NOT_BUILT08:43:25 Notifying upstream projects of job completion08:43:25 Finished: NOT_BUILT }} In this case, I really don't want the email notification of a failure, because it really isn't a failed build. Also, I'm sure that there is a simpler way to initiate a "NOT_BUILT" condition without using the ClearCase UCM Plugin, but i don't know what that is...
Add Comment
[JIRA] [template-project-plugin] (JENKINS-34543) Failure email generated for ClearCase UCM job when changing node name
Title: Message Title
Christopher Shannon updated an issue
Jenkins / JENKINS-34543
Failure email generated for ClearCase UCM job when changing node name
Change By:
Christopher Shannon
I believe that this issue is specific to the Template Project Plugin when the build steps result in "NOT_BUILT".I'm seeing some problems when changing node names on an existing ClearCase UCM job. Here are the steps to reproduce:# Create a job which uses the ClearCase UCM Plugin for SCM.# Set the job to Poll Self and Promotion Level INITIAL.# Set the job to poll SCM at a certain rate.# Set the job to use publishers from another job.# In this other job, configure an email notification upon failure.# Map this job to a given node.# Run the job enough to process all INITIAL baselines on the given stream (such that the job doesn't have anything to do until a new baseline is created).# Change the name of the node.What happens is that the job will execute the next time it polls:{{ Started on May 2, 2016 8:43:14 AMWorkspace is offline.Scheduling a new build to get a workspace. (nonexisting_workspace)Done. Took 1 msChanges found}}The job will then not build because there are no baselines available to process, but I get an email notification of a failed build.{{ 08:38:43 [CCUCM] * Promotion level: INITIAL08:38:43 08:38:45 ERROR: No valid baselines found08:38:45 [TemplateProject] Starting publishers from: 08:38:45 Sending e-mails to: 08:38:46 [TemplateProject] Successfully performed publishers from: 08:38:46 [CCUCM] Nothing to do!08:38:46 Build step 'ClearCase UCM' changed build result to NOT_BUILT08:38:46 Notifying upstream projects of job completion08:38:46 Finished: NOT_BUILT}}When I do a similar flow, but without using the Template Project Plugin, the email notification publisher is completely suppressed:{{ 08:43:22 [CCUCM] * Promotion level: INITIAL08:43:22 08:43:25 ERROR: No valid baselines found08:43:25 [WARNINGS] Skipping publisher since build result is FAILURE08:43:25 [CCUCM] Nothing to do!08:43:25 Build step 'ClearCase UCM' changed build result to NOT_BUILT08:43:25 Notifying upstream projects of job completion08:43:25 Finished: NOT_BUILT}}In this case, I really don't want the email notification of a failure, because it really isn't a failed build. Also, I'm sure that there is a simpler way to initiate a "NOT_BUILT" condition without using the ClearCase UCM Plugin, but i don't know what that is...
Add Comment
[JIRA] [template-project-plugin] (JENKINS-34543) Failure email generated for ClearCase UCM job when changing node name
Title: Message Title
Christopher Shannon updated an issue
Jenkins / JENKINS-34543
Failure email generated for ClearCase UCM job when changing node name
Change By:
Christopher Shannon
I believe that this issue is specific to the Template Project Plugin when the build steps result in "NOT_BUILT".I'm seeing some problems when changing node names on an existing ClearCase UCM job. Here are the steps to reproduce:# Create a job which uses the ClearCase UCM Plugin for SCM.# Set the job to Poll Self and Promotion Level INITIAL.# Set the job to poll SCM at a certain rate.# Set the job to use publishers from another job.# In this other job, configure an email notification upon failure.# Map this job to a given node.# Run the job enough to process all INITIAL baselines on the given stream (such that the job doesn't have anything to do until a new baseline is created).# Change the name of the node.What happens is that the job will execute the next time it polls:{{Started on May 2, 2016 8:43:14 AMWorkspace is offline.Scheduling a new build to get a workspace. (nonexisting_workspace)Done. Took 1 msChanges found }}The job will then not build because there are no baselines available to process, but I get an email notification of a failed build.{{08:38:43 [CCUCM] * Promotion level: INITIAL08:38:43 08:38:45 ERROR: No valid baselines found08:38:45 [TemplateProject] Starting publishers from: 08:38:45 Sending e-mails to: 08:38:46 [TemplateProject] Successfully performed publishers from: 08:38:46 [CCUCM] Nothing to do!08:38:46 Build step 'ClearCase UCM' changed build result to NOT_BUILT08:38:46 Notifying upstream projects of job completion08:38:46 Finished: NOT_BUILT }}When I do a similar flow, but without using the Template Project Plugin, the email notification publisher is completely suppressed:{{08:43:22 [CCUCM] * Promotion level: INITIAL08:43:22 08:43:25 ERROR: No valid baselines found08:43:25 [WARNINGS] Skipping publisher since build result is FAILURE08:43:25 [CCUCM] Nothing to do!08:43:25 Build step 'ClearCase UCM' changed build result to NOT_BUILT08:43:25 Notifying upstream projects of job completion08:43:25 Finished: NOT_BUILT }}In this case, I really don't want the email notification of a failure, because it really isn't a failed build. Also, I'm sure that there is a simpler way to initiate a "NOT_BUILT" condition without using the ClearCase UCM Plugin, but i don't know what that is...
Add Comment
[JIRA] [template-project-plugin] (JENKINS-34543) Failure email generated for ClearCase UCM job when changing node name
Title: Message Title Christopher Shannon created an issue Jenkins / JENKINS-34543 Failure email generated for ClearCase UCM job when changing node name Issue Type: Bug Assignee: huybrechts Components: template-project-plugin Created: 2016/May/02 8:42 PM Environment: Jenkins 1.646 ClearCase UCM Plugin 1.6.9 Template Project Plugin 1.5.2 Labels: plugin plugins Priority: Minor Reporter: Christopher Shannon I believe that this issue is specific to the Template Project Plugin when the build steps result in "NOT_BUILT". I'm seeing some problems when changing node names on an existing ClearCase UCM job. Here are the steps to reproduce: Create a job which uses the ClearCase UCM Plugin for SCM. Set the job to Poll Self and
[JIRA] [workflow-plugin] (JENKINS-34542) Hang in ExecutorStepExecution
Title: Message Title Jesse Glick started work on JENKINS-34542 Change By: Jesse Glick Status: Open In Progress 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-34542) Hang in ExecutorStepExecution
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-34542 Hang in ExecutorStepExecution Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/May/02 8:09 PM Environment: Pipeline 1.11 on 1.625.3 Labels: threads Priority: Major Reporter: Jesse Glick One CPS VM thread was hung in a remoting call: "Computer.threadPoolForRemoting [#...] / waiting for hudson.remoting.Channel@..." java.lang.Thread.State: TIMED_WAITING at java.lang.Object.wait(Native Method) - waiting on <...> (a hudson.remoting.UserRequest) at hudson.remoting.Request.call(Request.java:147) at hudson.remoting.Channel.call(Channel.java:780) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:954) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask.finish(ExecutorStepExecution.java:345) - locked <...> (a java.util.HashMap) at
[JIRA] [pipeline-stage-view-plugin] (JENKINS-34212) Visualization shows stage failed when an exception is caught
Title: Message Title
Michael Scharp edited a comment on JENKINS-34212
Re: Visualization shows stage failed when an exception is caught
Hi Sam,This issue is related to JENKINS-33840 which has an example use case that produces the failed stage, even though the error is caught. Here is that test case:{code:java}node('linux') {stage "fail"try {sh "false"}catch(err) {stage "cleanup"sh "true"}stage "done"echo "done"}{code}
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] [pipeline-stage-view-plugin] (JENKINS-34212) Visualization shows stage failed when an exception is caught
Title: Message Title
Michael Scharp edited a comment on JENKINS-34212
Re: Visualization shows stage failed when an exception is caught
Hi Sam,This issue is related to JENKINS-33840 which has an example use case that produces the failed stage, even though the error is caught.Here is that test case:{code:java}node( 'linux' ) {stage "fail"try {sh "false"}catch(err) {stage "cleanup"sh "true"}stage "done"echo "done"}{code}
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] [pipeline-stage-view-plugin] (JENKINS-34212) Visualization shows stage failed when an exception is caught
Title: Message Title Michael Scharp commented on JENKINS-34212 Re: Visualization shows stage failed when an exception is caught Hi Sam, This issue is related to JENKINS-33840 which has an example use case that produces the failed stage, even though the error is caught. 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] [remoting] (JENKINS-34213) Under high throughput the Unexporter can fail to clean up fast enough
Title: Message Title stephenconnolly commented on JENKINS-34213 Re: Under high throughput the Unexporter can fail to clean up fast enough We need Kohsuke Kawaguchi to actually cut a new release of remoting... when that has been out long enough then the fix will be eligible for the LTS release line 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] [mask-passwords-plugin] (JENKINS-34264) Support Global passwords from Mask Passwords in Pipeline
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34264 Support Global passwords from Mask Passwords in Pipeline Change By: Oleg Nenashev Component/s: workflow-plugin 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] [mask-passwords-plugin] (JENKINS-34264) Support Global passwords from Mask Passwords in Pipeline
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34264 Support Global passwords from Mask Passwords in Pipeline Change By: Oleg Nenashev Summary: Support Global passwords from Mask Passwords does not enable variables in workflow/pipeline 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] [mask-passwords-plugin] (JENKINS-34264) Support Global passwords from Mask Passwords in Pipeline
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34264 Support Global passwords from Mask Passwords in Pipeline Change By: Oleg Nenashev Labels: pipeline workflow 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] [mask-passwords-plugin] (JENKINS-34264) Mask Passwords does not enable variables in workflow/pipeline
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-34264 Mask Passwords does not enable variables in workflow/pipeline Change By: Oleg Nenashev Assignee: Oleg Nenashev 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] [mask-passwords-plugin] (JENKINS-34264) Mask Passwords does not enable variables in workflow/pipeline
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34264 Mask Passwords does not enable variables in workflow/pipeline Change By: Oleg Nenashev Priority: Critical Minor 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] [mask-passwords-plugin] (JENKINS-34264) Mask Passwords does not enable variables in workflow/pipeline
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34264 Mask Passwords does not enable variables in workflow/pipeline Change By: Oleg Nenashev Issue Type: Bug New Feature 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] [mask-passwords-plugin] (JENKINS-34264) Mask Passwords does not enable variables in workflow/pipeline
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34264 Mask Passwords does not enable variables in workflow/pipeline Change By: Oleg Nenashev Priority: Minor Major 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] [mask-passwords-plugin] (JENKINS-34264) Mask Passwords does not enable variables in workflow/pipeline
Title: Message Title Oleg Nenashev reopened an issue Jenkins / JENKINS-34264 Mask Passwords does not enable variables in workflow/pipeline Change By: Oleg Nenashev Resolution: Not A Defect 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] [mask-passwords-plugin] (JENKINS-34264) Mask Passwords does not enable variables in workflow/pipeline
Title: Message Title Oleg Nenashev commented on JENKINS-34264 Re: Mask Passwords does not enable variables in workflow/pipeline Mask Passwords plugin is in the stale state. I agree with Jesse that it's Global Password functionality is not what recommended for new Jenkins instances. I'll convert this bug to the medium-priority enhancement, but I do not plan to work on it in the short-term. 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] [mask-passwords-plugin] (JENKINS-34264) Mask Passwords does not enable variables in workflow/pipeline
Title: Message Title Jesse Glick commented on JENKINS-34264 Re: Mask Passwords does not enable variables in workflow/pipeline The “global passwords” feature in the Mask Passwords plugin should not be used. This predates the Credentials plugin. Define global credentials instead. 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] [p4-plugin] (JENKINS-34541) correct typo: Trust missmatch! Server fingerprint:
Title: Message Title Joel Brown created an issue Jenkins / JENKINS-34541 correct typo: Trust missmatch! Server fingerprint: Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/May/02 7:13 PM Priority: Trivial Reporter: Joel Brown From "missmatch" to "mismatch". two occurrences in: //guest/perforce_software/p4jenkins/main/src/main/java/org/jenkinsci/plugins/p4/client/ConnectionFactory.java Add Comment
[JIRA] [kubernetes-plugin] (JENKINS-34380) kubernetes plugin creates an unbounded number of Netty I/O threads
Title: Message Title Giuseppe Valente commented on JENKINS-34380 Re: kubernetes plugin creates an unbounded number of Netty I/O threads Hi, can someone take a look and let us know if this is fixable or we should work around it on our end? Thanks 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-34520) Can't use Jenkinsfile for build git tags
Title: Message Title Artem V. Navrotskiy updated an issue Jenkins / JENKINS-34520 Can't use Jenkinsfile for build git tags Change By: Artem V. Navrotskiy Labels: 2.0 2.1 Jenkinsfile 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] [git-plugin] (JENKINS-34540) Can't use Pipeline Parameter in Branch Specifier on Jenkins 2.0/2.1
Title: Message Title Artem V. Navrotskiy updated an issue Jenkins / JENKINS-34540 Can't use Pipeline Parameter in Branch Specifier on Jenkins 2.0/2.1 Change By: Artem V. Navrotskiy Labels: 2.0 2.1 Jenkinsfile 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] [git-plugin] (JENKINS-34540) Can't use Pipeline Parameter in Branch Specifier on Jenkins 2.0/2.1
Title: Message Title
Artem V. Navrotskiy created an issue
Jenkins / JENKINS-34540
Can't use Pipeline Parameter in Branch Specifier on Jenkins 2.0/2.1
Issue Type:
Bug
Assignee:
Mark Waite
Attachments:
octobuild-tag.xml
Components:
git-plugin
Created:
2016/May/02 6:29 PM
Environment:
Jenkins 2.1
Labels:
Jenkinsfile
Priority:
Minor
Reporter:
Artem V. Navrotskiy
I try to create a "Pipeline" with string parameter "TAG_NAME" and "Pipeline script from SCM" with "Branch Specifier" = "refs/tags/${TAG_NAME}" (I attached job file to this issue).
But this don't work (looks like TAG_NAME is not pass to environment variable) with error like:
[JIRA] [testng-plugin] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title
Andrew McElroy edited a comment on JENKINS-26971
Re: looking at failed TestNG result causes an exception
The problem appears to be caused by the fact that my "Publish TestNG Results" post-build action was sitting in another Jenkins job. I had this (and some other items) in a different jenkins job and was inserting this other job into my main job via the Flexible Publish plugin ("use publishers from another project"). As soon as I moved the "Publish TestNG Results" action back into my my main job, it suddenly worked again. I did not even need to run a new build - even my existing run results started working right away .It might be nice to know if [~nikolaymetchev] also had the same setup.
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] [testng-plugin] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title Nikolay Metchev commented on JENKINS-26971 Re: looking at failed TestNG result causes an exception I don't remember what the problem was or how I fixed it. Probably updating Jenkins/Plugin to a newer version. However my setup is not as described by Andrew. 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] [core] (JENKINS-33931) exceptions on pluginManager with no plugins
Title: Message Title Daniel Beck resolved as Cannot Reproduce Let's wait for more reports of this to come in. Jenkins / JENKINS-33931 exceptions on pluginManager with no plugins Change By: Daniel Beck Status: Open Resolved Resolution: Cannot Reproduce 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] [core] (JENKINS-34498) Jenkins 2.0 "out of the box" plugins failed to install
Title: Message Title Daniel Beck commented on JENKINS-34498 Re: Jenkins 2.0 "out of the box" plugins failed to install Igor Koyfman This is the data file that controls the wizard: https://github.com/jenkinsci/jenkins/blob/master/war/src/main/js/api/plugins.js#L10...L29 Plugin names are only provided as their internal IDs, but you could download from http://updates.jenkins-ci.org/download/plugins/ and just upload through plugin manager. 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] [core] (JENKINS-33281) Release Jenkins 2.0
Title: Message Title R. Tyler Croy commented on JENKINS-33281 Re: Release Jenkins 2.0 Daniel Beck only if you close or unlike the issues it depends on 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-34520) Can't use Jenkinsfile for build git tags
Title: Message Title
Artem V. Navrotskiy commented on JENKINS-34520
Re: Can't use Jenkinsfile for build git tags
I found workarong to get optional "TAG_NAME" parameter value in Jenkinsfile:
def TAG_NAME = binding.variables.get("TAG_NAME")
if (TAG_NAME != null) {
sh "echo $TAG_NAME"
} else {
sh "echo Non-tag build"
}
But "Branch Specifier" like "refs/tags/${TAG_NAME}" don't work.
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] [core] (JENKINS-34498) Jenkins 2.0 "out of the box" plugins failed to install
Title: Message Title Igor Koyfman commented on JENKINS-34498 Re: Jenkins 2.0 "out of the box" plugins failed to install Can I somehow get those plugins now anyway? Is there a list somewhere? 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] [build-flow-plugin] (JENKINS-18484) Add Grape @Grab support to flow-dsl plugin
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-18484 Add Grape @Grab support to flow-dsl plugin Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-18200) Build flow job: UI blocks for each job disappear from past jobs if configuration has changed.
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-18200 Build flow job: UI blocks for each job disappear from past jobs if configuration has changed. Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-23607) BuildGraph page doesn't load if some builds are queued
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-23607 BuildGraph page doesn't load if some builds are queued Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-30102) The wrong build is cancelled if it is still in queue
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-30102 The wrong build is cancelled if it is still in queue Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-21438) Build jobs turn suddenly into "grey" and loses the label
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-21438 Build jobs turn suddenly into "grey" and loses the label Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-19606) would be nice if ignore(){} returned the result of the given block
Title: Message Title
Damien Nozay assigned an issue to Unassigned
Jenkins / JENKINS-19606
would be nice if ignore(){} returned the result of the given block
Change By:
Damien Nozay
Assignee:
Damien Nozay
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] [build-flow-plugin] (JENKINS-23024) getDownStream function returns only the the children from the start job
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-23024 getDownStream function returns only the the children from the start job Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-17155) Allow users to run a specific combination axis in matrix builds
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-17155 Allow users to run a specific combination axis in matrix builds Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-22950) Bring back workspace and make it optional
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-22950 Bring back workspace and make it optional Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-13433) War file output naming should have an option to ignore the 'version' in the pom file
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-13433 War file output naming should have an option to ignore the 'version' in the pom file Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-17235) No error message displayed even on failure if I try to run the same job with same params in parallel
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-17235 No error message displayed even on failure if I try to run the same job with same params in parallel Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-32629) Deadlock between h.m.queue.FutureImpl#cancel and h.m.Queue#cancel
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-32629 Deadlock between h.m.queue.FutureImpl#cancel and h.m.Queue#cancel Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-18645) Exception in parameter evaluation for 'build' is hidden
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-18645 Exception in parameter evaluation for 'build' is hidden Change By: Damien Nozay Assignee: Damien Nozay 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] [testng-plugin] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title
Andrew McElroy commented on JENKINS-26971
Re: looking at failed TestNG result causes an exception
The problem appears to be caused by the fact that my "Publish TestNG Results" post-build action was sitting in another Jenkins job. I had this (and some other items) in a different jenkins job and was inserting this other job into my main job via the Flexible Publish plugin ("use publishers from another project"). As soon as I moved the "Publish TestNG Results" action back into my my job, it suddenly worked again. I did not even need to run a new build - even my existing run results started working.
It might be nice to know if Nikolay Metchev also had the same setup.
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] [core] (JENKINS-33281) Release Jenkins 2.0
Title: Message Title Daniel Beck commented on JENKINS-33281 Re: Release Jenkins 2.0 R. Tyler Croy Can this be resolved? 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] [build-flow-plugin] (JENKINS-18088) Build flow execute on slave but write file on master
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-18088 Build flow execute on slave but write file on master Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-14482) com.cloudbees.plugins.flow.JobExecutionFailureException
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-14482 com.cloudbees.plugins.flow.JobExecutionFailureException Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-14449) Editing the build flow job (even trivially) removes it as a post build action from other jobs
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-14449 Editing the build flow job (even trivially) removes it as a post build action from other jobs Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-28613) Unable to access the flow result at rescue closure
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-28613 Unable to access the flow result at rescue closure Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-22779) Build-Flow plugin problems in latest version (0.11.1)
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-22779 Build-Flow plugin problems in latest version (0.11.1) Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-16980) build flow need sandboxing
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-16980 build flow need sandboxing Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-28812) NullPointerException when running Maven job parallel
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-28812 NullPointerException when running Maven job parallel Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-33365) Support Multi-Parent jobs
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-33365 Support Multi-Parent jobs Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-17981) When ignoring failure in job run in parallel with others, jobs after parallel block will not run
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-17981 When ignoring failure in job run in parallel with others, jobs after parallel block will not run Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-18409) How do I get downstream projects to only trigger when there are scm changes
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-18409 How do I get downstream projects to only trigger when there are scm changes Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-30944) In progress build flows have result "SUCCESS" in json api
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-30944 In progress build flows have result "SUCCESS" in json api Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-20934) Build-Flow graph disappeared after restart jenkins
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-20934 Build-Flow graph disappeared after restart jenkins Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-30942) retry still trying after build has been aborted
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-30942 retry still trying after build has been aborted Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-18037) Support for general Parameter Value types (not only string and boolean)
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-18037 Support for general Parameter Value types (not only string and boolean) Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-14485) Continue job after previous job has failed
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-14485 Continue job after previous job has failed Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-29761) sleep command cannot be killed
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-29761 sleep command cannot be killed Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-25420) Stack trace thrown even with simply failure fail in parallel block
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-25420 Stack trace thrown even with simply failure fail in parallel block Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-19094) HOME Env variable is NOT SET in Build Shell Command
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-19094 HOME Env variable is NOT SET in Build Shell Command Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-16455) "Build Environment" section mission from build-flow job configuration page
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-16455 "Build Environment" section mission from build-flow job configuration page Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-15922) Parallel block is executed ignoring a failed previous job
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-15922 Parallel block is executed ignoring a failed previous job Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-17815) Build Flow Plugin does not restrict node
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-17815 Build Flow Plugin does not restrict node Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-34278) Build-flow-plugin: Incorrect z-index value in CodeMirror-gutter class
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-34278 Build-flow-plugin: Incorrect z-index value in CodeMirror-gutter class Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-17635) Javascript execution broken on build page
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-17635 _javascript_ execution broken on build page Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-19965) Plan Build from within a build for a Parametrized MultiJob is not working
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-19965 Plan Build from within a build for a Parametrized MultiJob is not working Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-15999) Flow Jobs Do Not Run Properly When Configured to Run on a Node Other Than Master
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-15999 Flow Jobs Do Not Run Properly When Configured to Run on a Node Other Than Master Change By: Damien Nozay Assignee: Damien Nozay 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] [build-flow-plugin] (JENKINS-18177) Allow to cancel both the flow and all running builds
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-18177 Allow to cancel both the flow and all running builds Change By: Damien Nozay Assignee: Damien Nozay 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.
