[JIRA] [clearcase-plugin] (JENKINS-32551) Pipeline script from SCM: ClearCase not available
Title: Message Title Jesse Glick assigned an issue to Praqma Support There are at least three ClearCase SCM plugins; I am not sure which you are using. Whichever it is, it would need to be updated to support Pipeline. Jenkins / JENKINS-32551 Pipeline script from SCM: ClearCase not available Change By: Jesse Glick Issue Type: Bug New Feature Component/s: clearcase-plugin Component/s: workflow-plugin Priority: Minor Major Labels: clearcase workflow Assignee: Jesse Glick Praqma Support Add Comment
[JIRA] [git-plugin] (JENKINS-32552) Multibranch project git branch checkout
Title: Message Title Jesse Glick assigned an issue to Mark Waite Jenkins / JENKINS-32552 Multibranch project git branch checkout Change By: Jesse Glick Component/s: git-plugin Component/s: workflow-plugin Assignee: Jesse Glick Mark Waite 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] [git-plugin] (JENKINS-32552) Multibranch project git branch checkout
Title: Message Title Jesse Glick commented on JENKINS-32552 Re: Multibranch project git branch checkout …for which you need JENKINS-31924. 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-32552) Multibranch project git branch checkout
Title: Message Title Jesse Glick resolved as Not A Defect For whatever reason, the Git plugin checks out branch heads in detached mode. You can override this behavior with an extension. Jenkins / JENKINS-32552 Multibranch project git branch checkout Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect 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-32545) failFast has no effect when withCredentials is used
Title: Message Title Jesse Glick commented on JENKINS-32545 Re: failFast has no effect when withCredentials is used No idea offhand, would have to see if reproducible in a functional test. 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-32533) [pipeline multibranch] Job configuration more explicitly readonly?
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32533 [pipeline multibranch] Job configuration more explicitly readonly? Change By: Jesse Glick Labels: multibranch 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-32533) [pipeline multibranch] Job configuration more explicitly readonly?
Title: Message Title Jesse Glick commented on JENKINS-32533 Re: [pipeline multibranch] Job configuration more explicitly readonly? View Configuration? 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-32533) [pipeline multibranch] Job configuration more explicitly readonly?
Title: Message Title Jesse Glick commented on JENKINS-32533 Re: [pipeline multibranch] Job configuration more explicitly readonly? Really a core issue. Probably duplicate though I am unsure how to find the original issue if there is one. 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-32480) Continuous integration using Jenkins Workflow and Validated Merge
Title: Message Title Jesse Glick commented on JENKINS-32480 Re: Continuous integration using Jenkins Workflow and Validated Merge Which Validated Merge plugin? If you mean the CloudBees proprietary one, there is an internal RFE for this. 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-30744) multibranch issues if branch contains /
Title: Message Title Jesse Glick resolved as Fixed This issue is fixed. If there are problems with Windows bat steps that are related to particular characters, file them in the durable-task plugin with workflow label and link to this issue. Jenkins / JENKINS-30744 multibranch issues if branch contains / Change By: Jesse Glick Status: Reopened 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-26761) WorkflowJob.getSCMs throws NullPointerException from notifyCommit hooks after Jenkins Restart
Title: Message Title Jesse Glick commented on JENKINS-26761 Re: WorkflowJob.getSCMs throws NullPointerException from notifyCommit hooks after Jenkins Restart I suspect this is actually just one of many symptoms of JENKINS-22767 . If so, it should quietly disappear in 1.646+. 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-31769) sh steps on slaves randomly hang when complete
Title: Message Title Jesse Glick resolved as Cannot Reproduce I fixed a number of potentially related issues in 1.13. Jenkins / JENKINS-31769 sh steps on slaves randomly hang when complete Change By: Jesse Glick Status: In Progress 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] [workflow-plugin] (JENKINS-32073) Scheduling of workflow "node" allocation needs some better controls.
Title: Message Title Jesse Glick commented on JENKINS-32073 Re: Scheduling of workflow "node" allocation needs some better controls. Probably solvable with the stage step, though I would need to see a self-contained demo to really evaluate. 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-32122) A List passed to a function is received as a String
Title: Message Title Jesse Glick commented on JENKINS-32122 Re: A List passed to a function is received as a String Probably same as JENKINS-32062 , try 1.13. 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-32122) A List passed to a function is received as a String
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-32122 A List passed to a function is received as a String Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate 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-32146) Last step misleadingly marked as blue even though build status is FAILURE
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32146 Last step misleadingly marked as blue even though build status is FAILURE Change By: Jesse Glick Summary: ArtifactArchiver does not mark Last step misleadingly marked as failing blue even though build status is FAILURE 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-32146) ArtifactArchiver does not mark step as failing
Title: Message Title Jesse Glick commented on JENKINS-32146 Re: ArtifactArchiver does not mark step as failing The ball color in Pipeline Steps for the last step does not reflect overall build status. 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-32159) Errors with DescribableHelper.Schema
Title: Message Title Jesse Glick commented on JENKINS-32159 Re: Errors with DescribableHelper.Schema parallel is a lost cause, needs to be handled specially. 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-32192) Step termination link fails silently when site accessed by short name
Title: Message Title Jesse Glick commented on JENKINS-32192 Re: Step termination link fails silently when site accessed by short name A warning gets printed to the Jenkins log but it should probably be shown in the build log. 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-32192) Hyperlinks quietly fail when JenkinsLocationConfiguration incorrect
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32192 Hyperlinks quietly fail when JenkinsLocationConfiguration incorrect Change By: Jesse Glick Summary: Step termination link fails silently Hyperlinks quietly fail when site accessed by short name JenkinsLocationConfiguration incorrect 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-32343) User task list
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-32343 User task list Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate 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 Jesse Glick resolved as Duplicate Jenkins / JENKINS-32675 Pipeline Plugin: Adjusting the Visualization of Pipeline Steps Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate 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-32352) [WORKFLOW] Progress Bar when stash/unstashing files in Workflow
Title: Message Title Jesse Glick commented on JENKINS-32352 Re: [WORKFLOW] Progress Bar when stash/unstashing files in Workflow Jenkins has never had a progress bar for the basic artifact archival feature, so this is a more general issue. 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] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani commented on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus This one works fine . 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] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani commented on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus But i have one issue (in 1.29 also same issue) "with only 'root' account i could able to launch instances .if i provide other LDAP account is not able to authenticate and launch instance. Remote FS root /root Remote user root 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] [google-container-registry-auth-plugin] (JENKINS-32700) 403 Forbidden
Title: Message Title James Green created an issue Jenkins / JENKINS-32700 403 Forbidden Issue Type: Bug Assignee: Wei Z Components: google-container-registry-auth-plugin Created: 01/Feb/16 9:16 AM Environment: jenkins:1.642.1 (master only) within a Docker 1.9.1 container Google Container Registry Auth Plugin:0.3 Google OAuth Credentials plugin:0.4 Priority: Critical Reporter: James Green I tried using both JSON and p12 flavours but both result in the following failure: [workspace] $ docker tag --force=true 2815f91921d7 eu.gcr.io/project-id/reporting-server:latest [workspace] $ docker inspect 2815f91921d7 [workspace] $ docker push eu.gcr.io/project-id/reporting-server:12 The push refers to a repository [eu.gcr.io/project-id/reporting-server] (len: 1) 2815f91921d7: Preparing Post https://eu.gcr.io/v2/project-id/reporting-server/blobs/uploads/: token auth attempt for registry: https://eu.gcr.io/v2/token?account=_token&scope=repository%3Aproject-id%2Freporting-server%3Apush%2Cpull&service=eu.gcr.io request failed with status: 403 Forbidden Build step 'Docker Build and Publish' marked build as failure Sadly it is not clear precisely what has failed. The user that created the token successfully pushed the image manually using the gcloud tool so there was
[JIRA] [analysis-core-plugin] (JENKINS-31202) Trend Graphs are not shown in Job view for Workflow builds
Title: Message Title Antonio Muñiz commented on JENKINS-31202 Re: Trend Graphs are not shown in Job view for Workflow builds Might this be connected with JENKINS-31926 ? No, it's unrelated. 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-failure-analyzer-plugin] (JENKINS-32686) Limit Scan by Job Label, Job Type, Name Etc.
Title: Message Title Tomas Westling commented on JENKINS-32686 Re: Limit Scan by Job Label, Job Type, Name Etc. I assume that the main driver for this idea is to spend less time and resources on scanning? Sounds like a good idea and I agree, the obvious place to start is with the easy implementations e.g. job name. 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-21977) "java.io.IOException: Failed to clean up temp dirs" because of "secret.key"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-21977 Re: "java.io.IOException: Failed to clean up temp dirs" because of "secret.key" Code changed in jenkins User: Nicolas BACOT Path: pom.xml http://jenkins-ci.org/commit/mattermost-plugin/43909e6e1161b2964e9235e86f7ee6fdd1943480 Log: Align with Jenkins 1.579 to include fix JENKINS-21977 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] [durable-task-plugin] (JENKINS-32701) Slashes in branch names cause 'bat' workflow task to hang
Title: Message Title
Jan Arend Jansen updated an issue
Jenkins / JENKINS-32701
Slashes in branch names cause 'bat' workflow task to hang
Change By:
Jan Arend Jansen
As first reported in JENKINS-30744 windows 'bat' workflow task hangs on the encoding of git branch names when these branches contain special characters (tested with gitflow naming convention that has '/' in the branch name).The encoded path seems to create problems on windows when using 'bat'.Any branch that has a slash in it for example ('feature/myfeature') will get an encoded path on windows like /feature%2Fmyfeature@script and /feature%2Fmyfeature.When I apply the following workflow in a multibranch job in a root file 'Jenkinsfile', Jenkins hangs forever on the bat command {code} node {stage 'Checkout'checkout scmstage 'Build'bat "echo 'test'"} {code| When I add this same script on the 'master' branch everything is fine.
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] [durable-task-plugin] (JENKINS-32701) Slashes in branch names cause 'bat' workflow task to hang
Title: Message Title
Jan Arend Jansen created an issue
Jenkins / JENKINS-32701
Slashes in branch names cause 'bat' workflow task to hang
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
durable-task-plugin
Created:
01/Feb/16 9:42 AM
Environment:
Windows 8.1 Jenkins 1.643 Workflow Plugin 1.12
Labels:
workflow
Priority:
Major
Reporter:
Jan Arend Jansen
As first reported in
JENKINS-30744
windows 'bat' workflow task hangs on the encoding of git branch names when these branches contain special characters (tested with gitflow naming convention that has '/' in the branch name).
The encoded path seems to create problems on windows when using 'bat'. Any branch that has a slash in it for example ('feature/myfeature') will get an encoded path on windows like /feature%2Fmyfeature@script and /feature%2Fmyfeature. When I apply the following workflow in a multibranch job in a root file 'Je
[JIRA] [workflow-plugin] (JENKINS-30744) multibranch issues if branch contains /
Title: Message Title Jan Arend Jansen commented on JENKINS-30744 Re: multibranch issues if branch contains / Done 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] [durable-task-plugin] (JENKINS-32701) Slashes in branch names cause 'bat' workflow task to hang
Title: Message Title
Jan Arend Jansen updated an issue
Jenkins / JENKINS-32701
Slashes in branch names cause 'bat' workflow task to hang
Change By:
Jan Arend Jansen
As first reported in JENKINS-30744 windows 'bat' workflow task hangs on the encoding of git branch names when these branches contain special characters (tested with gitflow naming convention that has '/' in the branch name).The encoded path seems to create problems on windows when using 'bat'.Any branch that has a slash in it for example ('feature/myfeature') will get an encoded path on windows like /feature%2Fmyfeature@script and /feature%2Fmyfeature.When I apply the following workflow in a multibranch job in a root file 'Jenkinsfile', Jenkins hangs forever on the bat command{code}node {stage 'Checkout'checkout scmstage 'Build'bat "echo 'test'"}{code | } When I add this same script on the 'master' branch everything is fine.
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] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani edited a comment on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus This one works fine It is having still same issue . Not able to launch instance 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] [metrics-plugin] (JENKINS-32696) healthcheck API endpoint causes a new run of health checks instead of reusing previous values
Title: Message Title Carlos Sanchez commented on JENKINS-32696 Re: healthcheck API endpoint causes a new run of health checks instead of reusing previous values https://github.com/jenkinsci/metrics-plugin/pull/19 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] [metrics-plugin] (JENKINS-32695) Result from health checks are lost when more than 3 run at the same time
Title: Message Title Carlos Sanchez commented on JENKINS-32695 Re: Result from health checks are lost when more than 3 run at the same time https://github.com/jenkinsci/metrics-plugin/pull/18 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] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani edited a comment on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus It is having still same issue .Not able to launch instance .Attached log jenkins._1.32_1_30_2016.log 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] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani updated an issue Jenkins / JENKINS-32588 Unable to launch linux slaves using ec2 plugin using Eucalyptus Change By: Murali Phani Attachment: jenkins._1.32_1_30_2016.log 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] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Francis Upton commented on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus The issue that you have with 1.29 about the root should be a separate JIRA since it happens in that version. This issue is only the problem introduced since 1.29. I looked at the log and there is little in it. I don't see any tracing of exceptions or anything. Do you have more 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] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani updated an issue Jenkins / JENKINS-32588 Unable to launch linux slaves using ec2 plugin using Eucalyptus Change By: Murali Phani Attachment: jenkins._1.32_1_30_2016.log 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] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani commented on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus sorry it is working fine.But it is taking too long to create instance.At least 5-10 mins for initiating instance launch 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] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani edited a comment on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus sorry it is ,the new pluginis working fine.But it is taking too long to create instance.At least 5-10 mins for initiating instance launch About root account ,the only log appearing at console.I will attach log . 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] [ec2-plugin] (JENKINS-32690) Cannot manually provision new slave if one already exists
Title: Message Title Ohad Basan commented on JENKINS-32690 Re: Cannot manually provision new slave if one already exists I am also hitting this issue and I have a different use case for it I have a workflow job that does stress tests with several works when the job runs it starts 10 slaves concurrently and then runs a another job once on each slave. I can't use this architecture since the latest change. 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] [ec2-plugin] (JENKINS-32690) Cannot manually provision new slave if one already exists
Title: Message Title Ohad Basan edited a comment on JENKINS-32690 Re: Cannot manually provision new slave if one already exists I am also hitting this issue and I have a different use case for itI have a workflow job that does stress tests with several works workers when the job runs it starts 10 slaves concurrently and then runs a another job once on each slave.I can't use this architecture since the latest change. 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-32122) A List passed to a function is received as a String
Title: Message Title Dean Birch commented on JENKINS-32122 Re: A List passed to a function is received as a String I can confirm it's resolved with 1.13. 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] [gradle-plugin] (JENKINS-27393) Workflow step for Gradle invocation
Title: Message Title Christopher Orr commented on JENKINS-27393 Re: Workflow step for Gradle invocation Jean-Francois Bibeau: I agree this would be nice to have. But just in case you didn't see already, arbitrary shell script stuff is supported, e.g. sh './gradlew assemble' 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] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani updated an issue Jenkins / JENKINS-32588 Unable to launch linux slaves using ec2 plugin using Eucalyptus Change By: Murali Phani Comment: It is having still same issue .Not able to launch instance.Attached log jenkins._1.32_1_30_2016.log 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-31862) "Build Now" should trigger Perforce polling
Title: Message Title Paul Allen commented on JENKINS-31862 Re: "Build Now" should trigger Perforce polling Thank you for trying this out. I'll close the ticket when the change goes out in the next release. 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] [project-inheritance-plugin] (JENKINS-23993) Page load time of inheritance projects
Title: Message Title Emilio Escobar commented on JENKINS-23993 Re: Page load time of inheritance projects Hi Martin Schröder, after 1.5.3 with the add of copyAndSortParametersByName instead of sortParametersByName we are facing performance issues. Basically because every parameters inside inheritance jobs are evaluated every time a dashboard is rendered, or build history is rendered. Also there is a trigger? thats evaluate continuously thous parameters. This is really needed? It seems that there is a lack of performance here. 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-32533) [pipeline multibranch] Job configuration more explicitly readonly?
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-32533 [pipeline multibranch] Job configuration more explicitly readonly? Change By: Cyrille Le Clerc Attachment: screenshot-1.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] [workflow-plugin] (JENKINS-32533) [pipeline multibranch] Job configuration more explicitly readonly?
Title: Message Title Cyrille Le Clerc commented on JENKINS-32533 Re: [pipeline multibranch] Job configuration more explicitly readonly? Jesse Glick this screen "View Configuration" uses read/write html form elements instead of readonly elements. 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-32533) [pipeline multibranch] Job configuration more explicitly readonly?
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-32533 Re: [pipeline multibranch] Job configuration more explicitly readonly? [~jglick] this screen "View Configuration" uses read/write html form elements instead of readonly elements.!screenshot-1.png |thumbnail ! 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] [credentials-plugin] (JENKINS-32642) Parameters are considered non-default in builds triggered by timer
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32642 Re: Parameters are considered non-default in builds triggered by timer Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsParameterDefinition.java src/test/java/com/cloudbees/plugins/credentials/CredentialsParameterDefinitionTest.java http://jenkins-ci.org/commit/credentials-plugin/3b59fbb153384c05937a5fbf72e6e6b0792883ca Log: Merge pull request #40 from daniel-beck/ JENKINS-32642 [FIX JENKINS-32642] Consider default value to be the default Compare: https://github.com/jenkinsci/credentials-plugin/compare/5a528b27a262...3b59fbb15338 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] [credentials-plugin] (JENKINS-32642) Parameters are considered non-default in builds triggered by timer
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32642 Re: Parameters are considered non-default in builds triggered by timer Code changed in jenkins User: Daniel Beck Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsParameterDefinition.java src/test/java/com/cloudbees/plugins/credentials/CredentialsParameterDefinitionTest.java http://jenkins-ci.org/commit/credentials-plugin/0c811af0765f3e31619528a95a1de0ec240f6915 Log: [FIX JENKINS-32642] Consider default value to be the default 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] [credentials-plugin] (JENKINS-32642) Parameters are considered non-default in builds triggered by timer
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-32642 Parameters are considered non-default in builds triggered by timer Change By: SCM/JIRA link daemon 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] [docker] (JENKINS-32702) Using Env variable on Build/Publish docker container
Title: Message Title sébastien glon created an issue Jenkins / JENKINS-32702 Using Env variable on Build/Publish docker container Issue Type: Bug Assignee: Nicolas De Loof Components: docker, docker-plugin Created: 01/Feb/16 11:02 AM Priority: Critical Reporter: sébastien glon I have defined build param IMAGE; On "Directory for Dockerfile", i want to set ./library/$IMAGE But $Image is not resolved I have this error: Docker Build: building image at path /home/jenkins/workspace/BuildLabsService/library/$IMAGE ERROR: Build step failed with exception Jenkins 1.625.3 Docker plugin 0.16.0 Add Comment
[JIRA] [ec2-plugin] (JENKINS-32703) Unable to use LDAP accounts as remote user to connect slaves using EC2 plugin
Title: Message Title Murali Phani created an issue Jenkins / JENKINS-32703 Unable to use LDAP accounts as remote user to connect slaves using EC2 plugin Issue Type: Bug Assignee: Francis Upton Attachments: auth.log Components: ec2-plugin Created: 01/Feb/16 11:14 AM Environment: EC2 1.29 Priority: Major Reporter: Murali Phani Hi, Using EC2 plugin we are launching linux instances .While configuring we are giving remote user as "root",then instances able to connect .But if we use LDAP accounts which have access are not able to connect instances after launching ,Authentication is getting failed.Could you please help to check this issue[attached log]
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani commented on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus Reported another Jira regarding LDAP https://issues.jenkins-ci.org/browse/JENKINS-32703?filter=-2 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] [packaging] (JENKINS-32687) Packaging allows the use of other pgp keys for signing but publishing hard codes KK's sun key.
Title: Message Title James Nord resolved as Fixed Jenkins / JENKINS-32687 Packaging allows the use of other pgp keys for signing but publishing hard codes KK's sun key. Change By: James Nord 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] [audit2db-plugin] (JENKINS-21058) Close sleep connections
Title: Message Title Ricardo García Fernández commented on JENKINS-21058 Re: Close sleep connections Configuration I've configured correctly c3p0 values in hibernate.cfg.xml file: https://github.com/ricardogarfe/audit2db-plugin/commit/2dccc21102f5f7ef8ac79eb823d1844a805d406d And make a pull request to base repository https://github.com/jenkinsci/audit2db-plugin/pull/14 I've tested connections during three days and thera are only 4 connections idle instead of more than 20... 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] [multijob-plugin] (JENKINS-27025) Condition for phase job is always downcased
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27025 Re: Condition for phase job is always downcased Code changed in jenkins User: Shachar Ben-Zeev Path: src/main/java/com/tikal/jenkins/plugins/multijob/MultiJobBuilder.java http://jenkins-ci.org/commit/tikal-multijob-plugin/254cc5025aab1a2f0655db9c76af80a57132ee79 Log: Merge pull request #91 from shacharbz/master don't downcase the conditional in multijob job JENKINS-27025 + fix comment Compare: https://github.com/jenkinsci/tikal-multijob-plugin/compare/93a4453f1c25...254cc5025aab 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] [multijob-plugin] (JENKINS-27025) Condition for phase job is always downcased
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27025 Re: Condition for phase job is always downcased Code changed in jenkins User: shachar ben-zeev Path: src/main/java/com/tikal/jenkins/plugins/multijob/MultiJobBuilder.java http://jenkins-ci.org/commit/tikal-multijob-plugin/8793063d090be2b426013b69371d91324d79c39a Log: don't downcase the conditional in multijob job JENKINS-27025 + fix comment 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] [ssh-agent-plugin] (JENKINS-32704) Command line ssh-add does not work
Title: Message Title Michael Rumpf created an issue Jenkins / JENKINS-32704 Command line ssh-add does not work Issue Type: Bug Assignee: Unassigned Components: ssh-agent-plugin Created: 01/Feb/16 12:56 PM Priority: Major Reporter: Michael Rumpf I have the ssh-agent-plugin configured for one of my Jenkins jobs. The SSH connection uses a jump server to get to a target machine. | Jenkins Build Node | -A-> | Jump Server | -B-> | Target Machine | A) The key for the "deploy" user on the jump server has been added to the Jenkins configuration and is added to the SSH Agent as part of the job. B) The user on the target server is selected from a drop-down box in the parameterized job form, which is displayed when clicking on the link "Build with Paramaters". For this to work a Bash shell script is started which adds the private key for the selected environment to the SSH agent by running ssh-add seckeys/dev. The connection to the SSH agent is established by the Unix socket, as defined by SSH_AUTH_SOCK=/tmp/jenkins421145548058133.jnr. I run ssh-add -l afterwards to validate that the key has been added: 4096 e0:bd:34:99:42:26:60:0f:bf:89:c2:b9:f1:b0:83:
[JIRA] [ssh-agent-plugin] (JENKINS-32704) Command line ssh-add does not work
Title: Message Title
Michael Rumpf updated an issue
Jenkins / JENKINS-32704
Command line ssh-add does not work
Change By:
Michael Rumpf
I have the ssh-agent-plugin configured for one of my Jenkins jobs.The SSH connection uses a jump server to get to a target machine.{code}| Jenkins Build Node | -A-> | Jump Server | -B-> | Target Machine |{code}A) The key for the "deploy" user on the jump server has been added to the Jenkins configuration and is added to the SSH Agent as part of the job.B) The user on the target server is selected from a drop-down box in the parameterized job form, which is displayed when clicking on the link "Build with Paramaters Parameters ".For this to work a Bash shell script is started which adds the private key for the selected environment to the SSH agent by running {{ssh-add seckeys/dev}}. The connection to the SSH agent is established by the Unix socket, as defined by {{SSH_AUTH_SOCK=/tmp/jenkins421145548058133.jnr}}.I run {{ssh-add -l}} afterwards to validate that the key has been added:{code}4096 e0:bd:34:99:42:26:60:0f:bf:89:c2:b9:f1:b0:83:cc deploy (The jump server user) (RSA)17 8c:64:4a:c3:40:c2:50:ec:8e:ac:03:86:5f:45:24:37 seckeys/dev (RSA) {code} {code}The first key is the deploy user's (A) key on the jump server, which is the same for all targets.The second one is the private key for the environment specific user on the target server (B).As you can see that the key, added by {{ssh-add}} from the shell script seems to broken, as the key length, i.e. the first value, is only 17Bit. The consequence is that the server rejects the key and not connection is possible.When I add both keys to the Linux standard ssh-agent the key dump looks like this:{code}4096 6f:89:e7:13:00:6f:09:7c:2f:bf:5a:a5:71:ff:31:2c seckeys/dev (RSA)4096 e0:bd:34:99:42:26:60:0f:bf:89:c2:b9:f1:b0:83:cc deploy (RSA){code}The workarounds are:# Add all keys to Jenkins. The disadvantage is that the list of environments/keys cannot be extended by the maintainers of the deployment project in our Git repository. There is always a Jenkins configuration change necessary (We have a restricted environment where users cannot access the configuration page of a job).# Use the Linux default ssh-agent as part of the shell script and do not use the ssh-agent-plugin at all
Add Comment
[JIRA] [multijob-plugin] (JENKINS-25111) Ability to Copy Artifacts from a Phase Job
Title: Message Title Geoffroy Jabouley commented on JENKINS-25111 Re: Ability to Copy Artifacts from a Phase Job Hi will this feature support multijob of multijob? Lets say i have the following job organization: multiJobA --> PhaseA1 --> jobA1 --> PhaseA2 --> MultijobB --> PhaseB1 > jobB1 I need to retrieve an artefact from jobA1 in jobB1. We currently pass the JOBA1_BUILD_NUMBER variable as parameter of MultijobB. Any change to use this new functionality with our use case? Add Comment
[JIRA] [multijob-plugin] (JENKINS-25111) Ability to Copy Artifacts from a Phase Job
Title: Message Title
Geoffroy Jabouley edited a comment on JENKINS-25111
Re: Ability to Copy Artifacts from a Phase Job
Hiwill this feature support multijob of multijob?Lets say i have the following job organization: {noformat} multiJobA|--> PhaseA1|--> jobA1|--> PhaseA2 |--> MultijobB multijobB |--> PhaseB1 |> jobB1 {noformat} I need to retrieve an artefact from jobA1 in jobB1.We currently pass the JOBA1_BUILD_NUMBER variable as parameter of MultijobB.Any change to use this new functionality with our use case?
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] [description-setter-plugin] (JENKINS-11349) Project description field with a long text renders configuration page unusable
Title: Message Title Shaun Reich resolved as Duplicate other issue is more generic, though created after this – this bug doesn't apply to just the description setter plugin, or the desc field. it applies to most every field Jenkins / JENKINS-11349 Project description field with a long text renders configuration page unusable Change By: Shaun Reich Status: Open Resolved Resolution: Duplicate 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] [description-setter-plugin] (JENKINS-11349) Project description field with a long text renders configuration page unusable
Title: Message Title Shaun Reich edited a comment on JENKINS-11349 Re: Project description field with a long text renders configuration page unusable other this is a dup of JENKINS-29632that issue is more generic, though created after this -- . this bug doesn't apply to just the description setter plugin, or the desc field. it applies to most every field in job settings 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-20217) Too many PingThread's
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-20217 Too many PingThread's Change By: Jesse Glick Component/s: remoting Component/s: core 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-20217) Too many PingThread's
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-20217 Too many PingThread's Change By: Jesse Glick Labels: performance remoting 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] [cli] (JENKINS-32705) jenkins-cli.jar should not use PWD for temporary files
Title: Message Title Heikki Hokkanen created an issue Jenkins / JENKINS-32705 jenkins-cli.jar should not use PWD for temporary files Issue Type: Bug Assignee: Unassigned Components: cli Created: 01/Feb/16 1:35 PM Environment: 1.646 Priority: Major Reporter: Heikki Hokkanen Latest jenkins-cli.jar uses present working directory for temporary files when installing plugins, exploding spectacularly when a directory with the plugin name already exists. To reproduce, run: $ mkdir job-dsl $ java -jar /opt/jenkins-cli.jar -s http://localhost:8080/ install-plugin job-dsl Installing a plugin from local file: job-dsl Unexpected exception occurred while performing install-plugin command! java.io.IOException: Failed to copy job-dsl to /var/lib/jenkins/plugins/job-dsl.jpi at hudson.FilePath.copyTo(FilePath.java:1990) at hudson.cli.InstallPluginCommand.run(InstallPluginCommand.java:85) at hudson.cli.CLICommand.main(CLICommand.java:238) at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92) Caused by: java.io.FileNotFoundException: job-dsl (Is a directory)
[JIRA] [workflow-plugin] (JENKINS-32480) Continuous integration using Jenkins Workflow and Validated Merge
Title: Message Title JT Chu commented on JENKINS-32480 Re: Continuous integration using Jenkins Workflow and Validated Merge Jesse Glick Yes, Validated Merge plugin. Any estimated time for this RFE delivery? 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-27035) Request/response statistics
Title: Message Title Jesse Glick commented on JENKINS-27035 Re: Request/response statistics Wireshark plugin or other detailed diagnostics would be good too. 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] [neoload-jenkins] (JENKINS-32706) Neoload test result broken links
Title: Message Title JP Gamby created an issue Jenkins / JENKINS-32706 Neoload test result broken links Issue Type: Bug Assignee: Unassigned Components: neoload-jenkins Created: 01/Feb/16 2:04 PM Environment: Jenkins ver. 1.644 with NeoLoad Plugin 1.0.1 Labels: plugin neoload Priority: Minor Reporter: JP Gamby Most of my Neoload test report links are broken ... I get the following message when I click on Performance Result link: A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace
[JIRA] [core] (JENKINS-32328) A custom update center is not consulted for Tool installer metadata
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32328 Re: A custom update center is not consulted for Tool installer metadata Code changed in jenkins User: Valentina Armenise Path: changelog.html http://jenkins-ci.org/commit/jenkins/30712a19a15dbd3c4484065ebdd85c2b991f5d4c Log: updated changelog for JENKINS-32328 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-32328) A custom update center is not consulted for Tool installer metadata
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32328 Re: A custom update center is not consulted for Tool installer metadata Code changed in jenkins User: Oleg Nenashev Path: changelog.html http://jenkins-ci.org/commit/jenkins/aa4b30cc9297c3a2770c74b1cfea10df432ed52f Log: Merge pull request #2004 from varmenise/ JENKINS-32328 -changelog updated changelog for JENKINS-32328 Compare: https://github.com/jenkinsci/jenkins/compare/59540fa2a399...aa4b30cc9297 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-32707) Git plugin built the same commit 1300 times
Title: Message Title Patrick Rose created an issue Jenkins / JENKINS-32707 Git plugin built the same commit 1300 times Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 01/Feb/16 2:39 PM Environment: Jenkins: 1.644 git: 2.3.5 git-client: 1.16.1 Priority: Minor Reporter: Patrick Rose Our git plugin is set up to poll for commits whenever a commit is pushed, and when we left on Friday evening it seems that Jenkins build the same commit ~1300 times. It seemed to start at 18:34 on Friday and then finish at 05:00 this morning (Monday). Our builds take ~1 minute to run at the moment, and a quick look through the console log seems to suggest that the pre-build made Jenkins decide it needed to do another build Add Comment
[JIRA] [tfs-plugin] (JENKINS-30382) TFS plug-in 4.0.0 NumberFormatExceptions
Title: Message Title Olivier Dagenais assigned an issue to Olivier Dagenais Jenkins / JENKINS-30382 TFS plug-in 4.0.0 NumberFormatExceptions Change By: Olivier Dagenais Assignee: redsolo Olivier Dagenais 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] [analysis-core-plugin] (JENKINS-27548) Sporadic IOException: Failed to persist config
Title: Message Title Gianluca Chiodaroli commented on JENKINS-27548 Re: Sporadic IOException: Failed to persist config I have the same issue. I use Jenkins 1.646 version. I tried to add xerces.jar in "Additional classpath" but it doesn'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] [git-plugin] (JENKINS-32707) Git plugin built the same commit 1300 times
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-32707 Git plugin built the same commit 1300 times Change By: Mark Waite Assignee: Mark Waite 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-32707) Git plugin built the same commit 1300 times
Title: Message Title Mark Waite commented on JENKINS-32707 Re: Git plugin built the same commit 1300 times Sorry that it went into a loop building the same commit repeatedly. Unfortunately, I don't know how to duplicate the problem you're describing. Can you duplicate the problem on a freshly installed system, then share the duplication steps? If you want an easy starting point, you might consider the official Jenkins docker image, or if you'd prefer an image configured with the plugins that I often use, you could start with my master with plugins docker image. Is there a reason you're running the very latest weekly build of Jenkins but running git plugin and git client plugin versions from a year ago? You suggest that the "pre-build made Jenkins decide it needed to do another build". Can you explain further what you mean by that, and what you observed? 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] [tfs-plugin] (JENKINS-30479) TFS plugin did not support version 2005
Title: Message Title Olivier Dagenais assigned an issue to Olivier Dagenais Jenkins / JENKINS-30479 TFS plugin did not support version 2005 Change By: Olivier Dagenais Assignee: redsolo Olivier Dagenais 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] [metrics-plugin] (JENKINS-32696) healthcheck API endpoint causes a new run of health checks instead of reusing previous values
Title: Message Title Carlos Sanchez stopped work on JENKINS-32696 Change By: Carlos Sanchez Status: In Progress Open 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] [envinject-plugin] (JENKINS-32708) Envinject plugin does not integrate correctly with role strategy plugin
Title: Message Title mike bayliss created an issue Jenkins / JENKINS-32708 Envinject plugin does not integrate correctly with role strategy plugin Issue Type: Bug Assignee: Oleg Nenashev Attachments: envinject+role.png Components: envinject-plugin, role-strategy-plugin Created: 01/Feb/16 3:02 PM Environment: Jenkins 1.643, 1.646, Envinject plugin 1.92 or 1.92.1, role strategy plugin 2.2.0. 1.643 is an ubuntu 14 master with multiple windows/linux slaves, 1.646 is an ubuntu 14 master, with no slaves, assembled to isolate this bug. Problem is visible in Firefox and Chrome. Priority: Minor Reporter: mike bayliss When the envinject plugin is installed together with the role strategy plugin, the "Manage and Assign Roles" screen displays incorrectly. The column added to each role table for Env. Inject has no text in the second row of the table, and the third (and subsequent) row of the column includes the button for the "delete row" operation, not the checkbox for selecting the role. (Screenshot attached.) The probl
[JIRA] [metrics-plugin] (JENKINS-32696) healthcheck API endpoint causes a new run of health checks instead of reusing previous values
Title: Message Title Carlos Sanchez assigned an issue to Unassigned Jenkins / JENKINS-32696 healthcheck API endpoint causes a new run of health checks instead of reusing previous values Change By: Carlos Sanchez Assignee: Carlos Sanchez 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] [metrics-plugin] (JENKINS-32696) healthcheck API endpoint causes a new run of health checks instead of reusing previous values
Title: Message Title Carlos Sanchez commented on JENKINS-32696 Re: healthcheck API endpoint causes a new run of health checks instead of reusing previous values Based on PR comments this works as expected although there are some changes of a DoD if the health checks get executed too fast and take some time to run 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-32707) Git plugin built the same commit 1300 times
Title: Message Title Patrick Rose commented on JENKINS-32707 Re: Git plugin built the same commit 1300 times Can you duplicate the problem on a freshly installed system, then share the duplication steps? I have a feeling it's similar to JENKINS-31731. We've never had this happen before and since it was late on a Friday I don't know what was fully going on. I might be able to piece together what was happening in git if I have some spare time. Is there a reason you're running the very latest weekly build of Jenkins but running git plugin and git client plugin versions from a year ago? I'll have to ask the sysadmin I'm afraid! It's probably because we're doing significant updates to the project that we use Jenkins for and we began updating our Jenkins server to accommodate (but dropped it when we realised it'd make running CI for the old version of our project in parallel difficult). I'll update the git plugin tonight though. You suggest that the "pre-build made Jenkins decide it needed to do another build". Can you explain further what you mean by that, and what you observed? I had a quick scan through the console logs visible on the web page. The git plugin has output Scheduling another build to catch up with ProjectName, and seems to have done that for each of the builds. At 5:01 this morning it built a different commit which is why I'm wondering if it's a dupe of JENKINS-31731. 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 jenkinsc
[JIRA] [workflow-plugin] (JENKINS-26535) DescribableHelper does not handle wildcards well
Title: Message Title Pedro Algarvio commented on JENKINS-26535 Re: DescribableHelper does not handle wildcards well I have, as a final pipeline step, the following: step([$class: 'JUnitResultArchiver', allowEmptyResults: true, keepLongStdio: true, testDataPublishers: [[$class: 'StabilityTestDataPublisher']], testResults: 'test-results.xml']) If I comment out that last step, the build completes as it should, successfully, however, if that step is present: [Pipeline] } //withEnv [Pipeline] Set environment variables : End [Pipeline] step [Pipeline] } //timeout [Pipeline] Enforce time limit : End [Pipeline] } //parallel [Pipeline] Execute sub-workflows in parallel : End [Pipeline] } //wrap [Pipeline] General Build Wrapper : End [Pipeline] } //wrap [Pipeline] General Build Wrapper : End [Pipeline] } //node [Pipeline] Allocate node : End [Pipeline] End of Pipeline org.jenkinsci.plugins.workflow.cps.steps.ParallelStepException: Parallel step unit failed at org.jenkinsci.plugins.workflow.cps.steps.ParallelStep$ResultHandler$Callback.checkAllDone(ParallelStep.java:153) at org.jenkinsci.plugins.workflow.cps.steps.ParallelStep$ResultHandler$Callback.onFailure(ParallelStep.java:119) at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$FailureAdapter.receive(CpsBodyExecution.java:294) at com.cloudbees.groovy.cps.impl.ThrowBlock$1.receive(ThrowBlock.java:68) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:58) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:164) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:277) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:77) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:186) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:184) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:47) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.UnsupportedOperationException: JENKINS-26535: do not know how to handle ? extends hudson.tasks.junit.TestDataPublisher at org.jenkinsci.plugins.workflow.structs.DescribableHelper.coerce(DescribableHelper.java:574) at org.jenkinsci.plugins.workflow.structs.DescribableHelper.mapList(DescribableHelper.java:603) at org.jenkinsci.plugins.workflow.structs.DescribableHelper.coerce(DescribableHelper.java:588) at org.jenkinsci.plugins.workflow.structs.DescribableHelper.buildArguments(DescribableHelper.java:524) at org.jenkinsci.plugins.workflow.structs.DescribableHelper.injectSetters(DescribableHelper.java:663) at org.jenkinsci.plugins.workflow.structs.DescribableHelper.instantiate(DescribableHelper.java:98) at org.jenkinsci.plugins.workfl
[JIRA] [tfs-plugin] (JENKINS-30625) more SCM polling activities scheduled than handled
Title: Message Title Olivier Dagenais resolved as Won't Fix The Jenkins TFS plugin no longer supports unsupported versions of TFS (2005, 2008, 2010). Jenkins / JENKINS-30625 more SCM polling activities scheduled than handled Change By: Olivier Dagenais Status: Open Resolved Assignee: redsolo Ronny Borchert Resolution: Won't Fix 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/
[JIRA] [tfs-plugin] (JENKINS-13663) Allow use of credentials from Credentials Plugin
Title: Message Title Olivier Dagenais assigned an issue to Olivier Dagenais Jenkins / JENKINS-13663 Allow use of credentials from Credentials Plugin Change By: Olivier Dagenais Assignee: redsolo Olivier Dagenais 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] [tfs-plugin] (JENKINS-31110) Support credentials plugin
Title: Message Title Olivier Dagenais resolved as Duplicate Jenkins / JENKINS-31110 Support credentials plugin Change By: Olivier Dagenais Status: Open Resolved Assignee: redsolo Will Saxon Resolution: Duplicate 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-32698) Negative duration times displayed by Jenkins TestNG plugin
Title: Message Title Nathaniel Mishkin commented on JENKINS-32698 Re: Negative duration times displayed by Jenkins TestNG plugin One thing that's possible special/peculiar about my scenario is that the job runs multiple TestNG suites and a subset of the tests (actual classes and methods) are run in every suite. These are the tests in the com.vmware.cloud.systemtests.tests.common.setup and com.vmware.cloud.systemtests.tests.common.teardown packages. (Each suite also runs suite-specific tests.) What made me think to mention this is that in other jobs I'm seeing another duration-related anomalies related to these packages: The displayed duration of the package and of the test-containing classes they contain is wrong, although the displayed duration of each test method in the "Order of Execution by Test Method" table is correct. In the case of the former, the duration displayed for each class appears to be the time between the first execution of a test method in the class and the last execution of a test method in the class--across all the suites that were run in the job (instead of within each suite and then summed). 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] [docker-workflow-plugin] (JENKINS-32709) Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
Title: Message Title
Keith Zantow created an issue
Jenkins / JENKINS-32709
Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
docker-workflow-plugin
Created:
01/Feb/16 3:43 PM
Environment:
Jenkins installed: OSX 10.10 local boot2docker 1.9.1, Docker 1.9.1 on Ubuntu VM
Priority:
Major
Reporter:
Keith Zantow
Expect this to be executed on the remote Docker host with TLS configured, instead it is executed on the Jenkins-local Docker container (remote ip: 10.11.11.109, port: 2376, Docker credential ID: my-docker-creds) : docker.withServer('tcp://10.11.11.109:2376', 'my-docker-creds'){ s -> docker.image('httpd').inside { c -> sh 'uname -a' }
}
This is the console output:
[Pipeline] node { [Pipeline] Sets up Docker server endpoint : Start [Pipeline] withDockerServer { [Pipeline] sh [fds] Running shell script + docker inspect -f . httpd . [Pipeline] Run build steps inside a Docker container : Start $ docker run -t -d -u 501:20 -w /Users/kzantow/jenkins_latest_jan_2016/workspace/fds -v /Users/kzantow/jenkins_latest_jan_2016/workspace/fds:/Users/kzantow/jenkins_latest_jan_2016/workspace/fds:rw -e -e -e -e -e -e -e -e **
[JIRA] [docker-workflow-plugin] (JENKINS-32709) Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
Title: Message Title
Keith Zantow updated an issue
Jenkins / JENKINS-32709
Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
Change By:
Keith Zantow
Expect this to be executed on the remote Docker host with TLS configured, instead it is executed on the Jenkins-local Docker container (remote ip: 10.11.11.109, port: 2376, Docker credential ID: my-docker-creds) : {code} docker.withServer('tcp://10.11.11.109:2376', 'my-docker-creds'){ s -> docker.image('httpd').inside { c ->sh 'uname -a' }} {code} This is the console output: {code} [Pipeline] node {[Pipeline] Sets up Docker server endpoint : Start[Pipeline] withDockerServer {[Pipeline] sh[fds] Running shell script+ docker inspect -f . httpd.[Pipeline] Run build steps inside a Docker container : Start$ docker run -t -d -u 501:20 -w /Users/kzantow/jenkins_latest_jan_2016/workspace/fds -v /Users/kzantow/jenkins_latest_jan_2016/workspace/fds:/Users/kzantow/jenkins_latest_jan_2016/workspace/fds:rw -e -e -e -e -e -e -e -e -e -e -e -e -e httpd cat[Pipeline] withDockerContainer {[Pipeline] sh ...{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] [tfs-plugin] (JENKINS-10960) TFS plugin should consider NO_CI flag
Title: Message Title Olivier Dagenais assigned an issue to Olivier Dagenais Jenkins / JENKINS-10960 TFS plugin should consider NO_CI flag Change By: Olivier Dagenais Assignee: Olivier Dagenais 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-32692) Access to environment variables set in workflow script in other plugins
Title: Message Title Teemu Murtola commented on JENKINS-32692 Re: Access to environment variables set in workflow script in other plugins Yes, a way to directly interact with Gerrit Trigger from the workflow would provide another solution, but JENKINS-26103 by itself would not provide a perfect solution for us: we have multiple Jenkins jobs that trigger on the same Gerrit event, and Gerrit Trigger automatically combines the posts back to Gerrit such that there is only one post, once all the builds finish. For now, we would probably just want to move one of these jobs to a workflow, and still keep this reporting otherwise functional. So intermediate voting as mentioned in that issue would not be ideal. What could work is that if instead of JENKINS-26103, Gerrit Trigger provided a mechanism to influence the final post from within the workflow. That would probably be a good long-term solution for our case. EnvironmentContributor could be more general, but I'm not sure how many other plugins would actually benefit from 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] [tfs-plugin] (JENKINS-24593) Need a way to exclude commits done by the build itself from triggering another build
Title: Message Title Olivier Dagenais commented on JENKINS-24593 Re: Need a way to exclude commits done by the build itself from triggering another build Pull request #27 was submitted and will be investigated soon. 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-32630) Branches to build does not take into account which branch is most recent
Title: Message Title Dieter Blomme edited a comment on JENKINS-32630 Re: Branches to build does not take into account which branch is most recent Hi, thanks for the answer. This is very clear to me here, but on the help text it wasn't, could this be enhanced? If yes, I could try to help out by using your explanation here along with the current help text and make a proposal. And I fully understand this behaviour can't be changed so nothing breaks :) 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] [active-directory-plugin] (JENKINS-32710) Configure AD via Groovy
Title: Message Title John Mickey created an issue Jenkins / JENKINS-32710 Configure AD via Groovy Issue Type: Improvement Assignee: Unassigned Components: active-directory-plugin Created: 01/Feb/16 4:22 PM Priority: Minor Reporter: John Mickey I am working on configuring Active Directory via Groovy. I was able to authenticate via active directory via the UI. I have the following based on the LDAP plugin: import jenkins.model.* import hudson.security.* import hudson.plugins.* String domain = 'my.domain.com' String server = '192.168.1.1' String bindName = 'acco...@my.domain.com' String bindPassword = 'password' SecurityRealm ad_realm = new ActiveDirectorySecurityRealm(domain, server, bindName, bindPassword) jenkins.instance.setSecurityRealm(ad_realm) This is the error: STDERR: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: RemoteClass: 10: unable to resolve class ActiveDirectorySecurityRealm @ line 10, column 26. SecurityRealm ad_realm = new ActiveDirectorySecurityRealm(domain, server, bindName, bindPassword) ^
[JIRA] [git-plugin] (JENKINS-32630) Branches to build does not take into account which branch is most recent
Title: Message Title Dieter Blomme commented on JENKINS-32630 Re: Branches to build does not take into account which branch is most recent Hi, thanks for the answer. This is very clear to me here, but on the help text it wasn't, could this be enhanced? If yes, I could try to help out by using your explanation here along with the current help text and make a proposal. 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.
