Urgent Requirement for Technical Test Lead (DWT ) @ Irvine, CA.

[nitin david]

Hi Folks,
Hope you are doing well !!!
This is Nitin working with Humac Inc,
We have urgent openings for  a requirement,Please share the profiles if you
have any good resources to ni...@humacinc.com  or you can reach me at
6237484363.



*Title : Technical Test Lead (DWT )*
*Duration   :  Long Term*
*Location   :   Irvine, CA.*


*JD:*


• Bachelor’s degree or foreign equivalent required. Will also consider one
year of relevant work experience in lieu of every

year of education

• At least  4 years of experience with Data warehouse testing

Preferred

• At least 4 years of experience in Data warehouse testing Skills, in
creating Test Strategy, Test scenarios and Test cases

• Experience in any data warehouse technologies is preferred

• Experience in managing testing teams in onsite offshore model

• Ability to work in team in diverse/ multiple stakeholder environment

• Ability to communicate the status and progress to stakeholders when
required

• Experience and desire to work in a Global delivery environment

Experience with Financial domain is preferred



-- 

*Nitin *

*IT Recruiter*
*Humac Inc*
*Phone: 623-748-4363*
*Email: ni...@humacinc.com *

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [zentimestamp-plugin] (JENKINS-29699) ZenTimeStamp should create the BUILD_TIMESTAMP for Jenkins pre-v1.597

[tobeych...@hotmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Tobey created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29699 
 
 
 
  ZenTimeStamp should create the BUILD_TIMESTAMP for Jenkins pre-v1.597   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Gregory Boissinot 
 
 
 

Components:
 

 zentimestamp-plugin 
 
 
 

Created:
 

 29/Jul/15 2:21 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Chris Tobey 
 
 
 
 
 
 
 
 
 
 
This should also expose the BUILD_TIMESTAMP for jenkins pre-1.597 so that this plugin can be applied, jobs can be updated to use the BUILD_TIMESTAMP variable, and then Jenkins can be updated separately and at a later time, with no changes needed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
  

[JIRA] [workflow-plugin] (JENKINS-29676) Workflow: executing bat through Groovy can loop infinitely.

[mbeda...@matrox.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Bédard commented on  JENKINS-29676 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Workflow: executing bat through Groovy can loop infinitely.  
 
 
 
 
 
 
 
 
 
 
I tried finding where is the latest hpi file I could setup in Jenkins to install it and tried it again, with no luck. Where is the latest file with this bugs solved so I can confirm and close the bug? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-29568) When NodeProvisioner processes planned nodes, it must always call spent()

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29568 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: When NodeProvisioner processes planned nodes, it must always call spent()  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Beck Path: changelog.html http://jenkins-ci.org/commit/jenkins/1598a464ff7973cbe6d3d6aa2493085a4a0646ec Log: Noting #1770 in 1.622, 

JENKINS-29568
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-keeper-plugin] (JENKINS-25293) Build Keeper Plugin functionality does not appear

[h...@couwet.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hein Couwet updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-25293 
 
 
 
  Build Keeper Plugin functionality does not appear  
 
 
 
 
 
 
 
 
 
 
Also took me a while to figure it out :  
The plugin can be seen in the Build Environment section ... (see screenshots) 
 
 
 
 
 
 
 
 
 

Change By:
 
 Hein Couwet 
 
 
 

Attachment:
 
 Screen Shot 2015-07-29 at 15.13.58.png 
 
 
 

Attachment:
 
 Screen Shot 2015-07-29 at 15.13.21.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] [checkstyle-plugin] (JENKINS-29648) Make Checkstyle Plugin compatible with Workflow

[rec...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-29648 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make Checkstyle Plugin compatible with Workflow  
 
 
 
 
 
 
 
 
 
 
A PR has been sent. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [workflow-plugin] (JENKINS-29656) Workflow failed after "Warning: program state save failed"

[chahine.a...@invensity.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Leon Leon updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29656 
 
 
 
  Workflow failed after "Warning: program state save failed"   
 
 
 
 
 
 
 
 
 

Change By:
 
 Leon Leon 
 
 
 
 
 
 
 
 
 
 Hello everyone,I am facing a "program state save failed" error which prevents the workflow from running the next steps.{ code}{ color:red}org.jenkinsci.plugins.workflow.cps.CpsThreadGroup saveProgramWARNING: program state save failedjava.io.IOException: rename C:\Jenkins\current\jobs\MyWorkflowJob\builds\134\atomic3893270739985964803.tmp to C:\Jenkins\current\jobs\MyWorkflowJob\builds\134\program.dat failed at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:350) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:328) at org.jenkinsci.plugins.workflow.cps.CpsStepContext$3.onSuccess(CpsStepContext.java:482) at org.jenkinsci.plugins.workflow.cps.CpsStepContext$3.onSuccess(CpsStepContext.java:478) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:519) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:32) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) 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$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) 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:722){color} {code}   It seems that the following instruction from the org.jenkinsci.plugins.workflow.cps.CpsThreadGroup class is the reason:{color:red}  if (!tmpFile.renameTo(f)) {throw new IOException("rename " + tmpFile + " to " + f + " failed");}LOGGER.log(FINE, "program state saved");} catch (RuntimeException e) {LOGGER.log(WARNING, "program state save failed",e);propagateErrorToWorkflow(e);throw new IOException("Failed to persist "+f,e);} {color}But why does that happen and how can it be solved ?Thank you in advance. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
   

[JIRA] [workflow-plugin] (JENKINS-29656) Workflow failed after "Warning: program state save failed"

[chahine.a...@invensity.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Leon Leon updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29656 
 
 
 
  Workflow failed after "Warning: program state save failed"   
 
 
 
 
 
 
 
 
 

Change By:
 
 Leon Leon 
 
 
 
 
 
 
 
 
 
 Hello everyone,I am facing a "program state save failed" error which prevents the workflow from running the next steps.{code} {color:red} org.jenkinsci.plugins.workflow.cps.CpsThreadGroup saveProgramWARNING: program state save failedjava.io.IOException: rename C:\Jenkins\current\jobs\MyWorkflowJob\builds\134\atomic3893270739985964803.tmp to C:\Jenkins\current\jobs\MyWorkflowJob\builds\134\program.dat failed at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:350) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:328) at org.jenkinsci.plugins.workflow.cps.CpsStepContext$3.onSuccess(CpsStepContext.java:482) at org.jenkinsci.plugins.workflow.cps.CpsStepContext$3.onSuccess(CpsStepContext.java:478) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:519) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:32) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) 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$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) 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:722) {color} {code}It seems that the following instruction from the org.jenkinsci.plugins.workflow.cps.CpsThreadGroup class is the reason:{ color:red code }  if (!tmpFile.renameTo(f)) {throw new IOException("rename " + tmpFile + " to " + f + " failed");}LOGGER.log(FINE, "program state saved");} catch (RuntimeException e) {LOGGER.log(WARNING, "program state save failed",e);propagateErrorToWorkflow(e);throw new IOException("Failed to persist "+f,e);} { color code }But why does that happen and how can it be solved ?Thank you in advance. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
   

*Traduction de vos documents en toutes langues

[Aurelien SUPOT - A.Text Work]

Si vous ne visualisez pas correctement l’e-mail, cliquez ici


Bonjour,

Je me permets de vous écrire afin de vous proposer nos services de traduction.

Disposez-vous déjà d'une agence partenaire?

Notre agence, créée en 2001, peut intégralement prendre en charge vos projets
multilingues ou bien ceux de vos clients et dispose désormais d'un pôle
interprétation.

Quelques références dans le domaine juridique et financier: OCDE,Bierman
Advocaten (Hollande), Pricewaterhouse Coopers, Falcon Investissements, DG
Consulting, AXA, Milieu LTD (Belgique) : législation environnementale,
NewBridge Partners ( management opérationnel), AG Partners, Hottinger and
Partners S.A (Suisse), CBR Team Building : leader européen du Team Building,
Randstat Vedior...

Je suis à votre disposition pour toutes vos demandes d'informations et de
devis,

Bien cordialement

Aurélien SUPOT - Développement A.Text Work

A titre informatif, au cas ou vous auriez également des besoins en
interprétation, je vous transmets  6 liens vers les vidéos des derniers
évènements interprétés par notre agence.

 
PriceMinister

Conseil Général du Loiret

Université du Mans et de Sheffield

interpretation simultanée Naos group

Price Minister 2 - Pierre Kosciusko-Morizet

Interprétation simultanée pour le point presse ITER


Si vous ne désirez plus recevoir notre lettre d'information, cliquez ici


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Issues" group.
To unsubscribe from this group and stop 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-27658) Add Disable feature for Build Step

[db...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27658 
 
 
 
  Add Disable feature for Build Step  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

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] [core] (JENKINS-29590) Disable build steps temporarily

[db...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29590 
 
 
 
  Disable build steps temporarily  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

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] [core] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.

[cleydso...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cleydson José de Figueiredo Júnior commented on  JENKINS-10160 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.  
 
 
 
 
 
 
 
 
 
 
Nikolai Grigoriev that workaround worked for me. 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] [build-flow-plugin] (JENKINS-29595) Build-flow project not sending mail notification

[manojo...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manoj Kumar commented on  JENKINS-29595 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build-flow project not sending mail notification  
 
 
 
 
 
 
 
 
 
 
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] [gitlab-merge-request-jenkins] (JENKINS-29698) NullPointerException and threads blocked in the JVM with the Gitlab Merge Requests Builder plugin

[ludovic.vercruy...@atos.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ludovic Vercruysse created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29698 
 
 
 
  NullPointerException and threads blocked in the JVM with the Gitlab Merge Requests Builder plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 gitlab-merge-request-jenkins 
 
 
 

Created:
 

 29/Jul/15 12:16 PM 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Ludovic Vercruysse 
 
 
 
 
 
 
 
 
 
 
Dear, 
We are currently using Jenkins 1.596.3 with the Gitlab Merge Requests Builder plugin version 1.2.2. 
If we create a jenkins job which uses this plugin, and if we try to save the configuration of the job, we see a NPE: 

 

WARNING: org.jenkinsci.plugins.gitlab.GitlabBuildTrigger.run() failed for hudson.model.FreeStyleProject@37d513a0[MY_JOB]
java.lang.NullPointerException
at org.jenkinsci.plugins.gitlab.GitlabBuildTrigger.run(GitlabBuildTrigger.java:100)
at hudson.triggers.Trigger.checkTriggers(Trigger.java:266)
at hudson.triggers.Trigger$Cron.doRun(Trigger.java:214)
at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExec

[JIRA] [durable-task-plugin] (JENKINS-27152) Store bourneshell control files outside of workspace

[jgl...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-27152 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Store bourneshell control files outside of workspace  
 
 
 
 
 
 
 
 
 
 
Agreed. A subfolder of the slave root would probably be safest. 
A little trickier than merely changing the directory location, though, since the volumes parameter here must be adjusted to include that location, meaning some kind of API from durable-task by which docker-workflow could find that temporary directory. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [nodejs-plugin] (JENKINS-29697) Support io.js installation

[adam.bi...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adam Biro created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29697 
 
 
 
  Support io.js installation  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 nodejs_config.png 
 
 
 

Components:
 

 nodejs-plugin 
 
 
 

Created:
 

 29/Jul/15 12:01 PM 
 
 
 

Labels:
 

 io.js configuration build 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Adam Biro 
 
 
 
 
 
 
 
 
 
 
On the configuration page in nodejs plugin section (screenshot attached), when I click Add Installer button, and I select "Install from nodejs.org", I can choose which version of node.js I want to install during my builds.  
It would be very handy to add a new item in the list of possible sources: "Install from iojs.org", which would list all the io.js versions retrieved from https://iojs.org/dist/ (the same way it is done for node.js).  
I have checked around and it seems nobody is working on this or has requested io.js support. 
Right now what I see as a workaround is to pre-install io.js 

[JIRA] [docker-workflow-plugin] (JENKINS-28611) withContainer DecoratedLauncher not executing using withEndpoints env variables

[jgl...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick started work on  JENKINS-28611 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

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] [docker-workflow-plugin] (JENKINS-28611) withContainer DecoratedLauncher not executing using withEndpoints env variables

[jgl...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick assigned an issue to Vincent Latombe 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28611 
 
 
 
  withContainer DecoratedLauncher not executing using withEndpoints env variables  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Assignee:
 
 Jesse Glick Vincent Latombe 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [matrix-auth-plugin] (JENKINS-29527) AuthorizationMatrixProperty converter: Inheritance blocking may be passed incorrectly

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29527 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: AuthorizationMatrixProperty converter: Inheritance blocking may be passed incorrectly  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/main/java/hudson/security/AuthorizationMatrixProperty.java http://jenkins-ci.org/commit/matrix-auth-plugin/74cbb6e79caacb9b3c3adeea2aeee9641aa8ec51 Log: Merge pull request #3 from jenkinsci/findbugs-enable 
[FIXED JENKINS-29527] - AuthorizationMatrixProperty converter: Inheritance blocking may be passed incorrectly 
Compare: https://github.com/jenkinsci/matrix-auth-plugin/compare/a30a95b2f249...74cbb6e79caa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28611) withContainer DecoratedLauncher not executing using withEndpoints env variables

[jgl...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-28611 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: withContainer DecoratedLauncher not executing using withEndpoints env variables  
 
 
 
 
 
 
 
 
 
 
Testing confirms that environment variables exposed to docker exec are not transferred to the process created in the container. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-client-plugin] (JENKINS-26757) "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Failed check. I had run that test interactively and thought it worked. An automated test is definitely working in my test harness. Unfortunately, when I just attempted the same thing from a fresh docker instance of Jenkins using https://username:passw...@bitbucket.org/username/private-repo.git, it failed. I then used the same repository URL from command line git and confirmed it works correctly. 
The automated test must not be matching the real world closely enough. I'll explore further as time allows. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-26757 
 
 
 
  "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this gro

[JIRA] [git-plugin] (JENKINS-28460) Failed to connect to private bitbucket repository with username/password

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Thanks for checking. I had run that test interactively and thought it worked. An automated test is definitely working in my test harness. Unfortunately, when I just attempted the same thing from a fresh docker instance of Jenkins using https://username:passw...@bitbucket.org/username/private-repo.git, it failed. I then used the same repository URL from command line git and confirmed it works correctly. 
The automated test must not be matching the real world closely enough. I'll explore further as time allows. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-28460 
 
 
 
  Failed to connect to private bitbucket repository with username/password  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this gr

[JIRA] [git-client-plugin] (JENKINS-24368) Authentication failed for https://usern...@bitbucket.org/project/repository.git

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Thanks for checking. I had run that test interactively and thought it worked. An automated test is definitely working in my test harness. Unfortunately, when I just attempted the same thing from a fresh docker instance of Jenkins using https://username:passw...@bitbucket.org/username/private-repo.git, it failed. I then used the same repository URL from command line git and confirmed it works correctly. 
The automated test must not be matching the real world closely enough. I'll explore further as time allows. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-24368 
 
 
 
  Authentication failed for https://usern...@bitbucket.org/project/repository.git  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from 

[JIRA] [scm-sync-configuration-plugin] (JENKINS-26727) SCM Sync not triggering when saving jobs with spaces in the name

[stefan.schaefer...@web.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Schäfer commented on  JENKINS-26727 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SCM Sync not triggering when saving jobs with spaces in the name  
 
 
 
 
 
 
 
 
 
 
We see it on a daily bas if the job name has a space. The plugin did not commit the changes. We perform a manual commit on the repository and delete the fail.log file. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [scm-sync-configuration-plugin] (JENKINS-26727) SCM Sync not triggering when saving jobs with spaces in the name

[stefan.schaefer...@web.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Schäfer edited a comment on  JENKINS-26727 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SCM Sync not triggering when saving jobs with spaces in the name  
 
 
 
 
 
 
 
 
 
 We see it on a daily  bas  base  if the job name has a space. The plugin did not commit the changes. We perform a manual commit on the repository and delete the fail.log file. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [workflow-plugin] (JENKINS-29563) Access old builds properties in a Workflow job

[chahine.a...@invensity.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Leon Leon closed an issue as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Such properties can be accessed with: 
def Run lastSuccessfulBuild = job.getLastSuccessfulBuild() 
def lastSuccessfulBuildStrTime = lastSuccessfulBuild.getStartTimeInMillis() 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-29563 
 
 
 
  Access old builds properties in a Workflow job  
 
 
 
 
 
 
 
 
 

Change By:
 
 Leon Leon 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 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] [slack-plugin] (JENKINS-29696) Slack notifications are serialized

[giulio.euli...@cern.ch (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Giulio Eulisse created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29696 
 
 
 
  Slack notifications are serialized  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Sam Gleske 
 
 
 

Components:
 

 slack-plugin 
 
 
 

Created:
 

 29/Jul/15 10:21 AM 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Giulio Eulisse 
 
 
 
 
 
 
 
 
 
 
Looks like the slack notifications are serialised in the same job. If I have jenkins running two jobs in parallel and the second to start finishes early, in its log I get: 
Slack Notifications is waiting for a checkpoint on build-any-ib #1  
and the task does not finish. Obviously this is not particularly desirable. Is there any way around this or is this an actual bug? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

[JIRA] [klockwork] (JENKINS-29673) Klocwork plugin does not work in a master/slave configuration.

[avri.schnei...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Avri Schneider commented on  JENKINS-29673 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Klocwork plugin does not work in a master/slave configuration.  
 
 
 
 
 
 
 
 
 
 
https://github.com/cittools/klocwork-plugin/pull/14 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [teamconcert-plugin] (JENKINS-29076) Auto create job parameters on trigger from RTC

[rafaelrez...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rafael Rezende commented on  JENKINS-29076 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Auto create job parameters on trigger from RTC  
 
 
 
 
 
 
 
 
 
 
Hello Nigel, I tried it myself with both String and Repository Workspace properties on the RTC Build Definition. I'm able to see the respective String value and the RW ID as environment variables on the Jenkins build without adding any Job parameters. 
They won't appear in the Parameters list of the Jenkins build (menu on the left) though. But you should still be able to use them as $ {VAR} 
. 
Let me know the outcome. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28475) Job queued "Waiting for next available executor on master" - workers idle

[wguoliang1...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Leung Wong commented on  JENKINS-28475 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Job queued "Waiting for next available executor on master" - workers idle  
 
 
 
 
 
 
 
 
 
 
I have the same issue. And it seems to be related with the Gearman plugin and newer Jenkins I'm using latest LTS version 1.609.1 which also have the problem. It works however if you use a slave node instead of master to execute jobs from Zuul. Use it as a temporary fix until this issue is 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] [delivery-pipeline-plugin] (JENKINS-29324) `columns` property does not work

[pat...@diabol.se (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrik Boström closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Released in 0.9.5 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-29324 
 
 
 
  `columns` property does not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrik Boström 
 
 
 

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] [delivery-pipeline-plugin] (JENKINS-29133) 'Enable start of new pipeline build' does not work with parameterized trigger

[pat...@diabol.se (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrik Boström closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Released in 0.9.5 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-29133 
 
 
 
  'Enable start of new pipeline build' does not work with parameterized trigger  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrik Boström 
 
 
 

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] [delivery-pipeline-plugin] (JENKINS-28837) After Successful build task stays covered by dark green progress bar color

[pat...@diabol.se (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrik Boström closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Released in 0.9.5 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-28837 
 
 
 
  After Successful build task stays covered by dark green progress bar color  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrik Boström 
 
 
 

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] [delivery-pipeline-plugin] (JENKINS-28937) Manual trigger for the downstream job is shown even if the build failed

[pat...@diabol.se (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrik Boström closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Released in 0.9.5  
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-28937 
 
 
 
  Manual trigger for the downstream job is shown even if the build failed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrik Boström 
 
 
 

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] [delivery-pipeline-plugin] (JENKINS-28845) Rebuild not respecting permissions like manualTrigger does

[pat...@diabol.se (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrik Boström closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Released in 0.9.5 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-28845 
 
 
 
  Rebuild not respecting permissions like manualTrigger does  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrik Boström 
 
 
 

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] [analysis-core-plugin] (JENKINS-25977) Make publishers of analysis-core a SimpleBuildStep

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-25977 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make publishers of analysis-core a SimpleBuildStep  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Antonio Muñiz Path: pom.xml http://jenkins-ci.org/commit/analysis-pom-plugin/2515a4f062f38802d25424fdd346a962bd438571 Log: JENKINS-25977 Update core version for workflow compatibility 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-25977) Make publishers of analysis-core a SimpleBuildStep

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-25977 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make publishers of analysis-core a SimpleBuildStep  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Antonio Muñiz Path: pom.xml http://jenkins-ci.org/commit/analysis-pom-plugin/bfa146a789d6ba5268f8fc274bae5a3f860b243d Log: Merge pull request #2 from amuniz/JENKINS-25977-workflow-compat 
JENKINS-25977 Update core version for workflow compatibility 
Compare: https://github.com/jenkinsci/analysis-pom-plugin/compare/26b9605bb16c...bfa146a789d6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [websphere-deployer-plugin] (JENKINS-29695) Wrong context root extracted from ibm-web-ext.xml file

[valerio.po...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Valerio Ponte created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29695 
 
 
 
  Wrong context root extracted from ibm-web-ext.xml file  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 websphere-deployer-plugin 
 
 
 

Created:
 

 29/Jul/15 8:32 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Valerio Ponte 
 
 
 
 
 
 
 
 
 
 
When using the recently added functionality of honoring context-root in ibm-web-ext (https://github.com/jenkinsci/websphere-deployer-plugin/pull/6) the plugin attempts to extract context-root from said file. 
Since in the file the user can write the context root both with a leading slash and without, the plugin attempts to add a leading slash if missing. Such addition is currently performed wrong, since the slash is added at the end of the specified context-root. 
The proposed PR (https://github.com/jenkinsci/websphere-deployer-plugin/pull/7) fixes this behavior by correctly adding the slash at the begin of the context-root. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
   

[JIRA] [docker-build-publish-plugin] (JENKINS-29627) JSONException: null object when interacting with Docker Hub Registry

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29627 
 
 
 
  JSONException: null object when interacting with Docker Hub Registry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Nenashev 
 
 
 

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] [docker-build-publish-plugin] (JENKINS-29627) JSONException: null object when interacting with Docker Hub Registry

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-29627 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JSONException: null object when interacting with Docker Hub Registry  
 
 
 
 
 
 
 
 
 
 
The fix has been released in docker-commons-1.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] [docker-build-publish-plugin] (JENKINS-29627) JSONException: null object when interacting with Docker Hub Registry

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-29627 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JSONException: null object when interacting with Docker Hub Registry  
 
 
 
 
 
 
 
 
 
 
It has been caused by https://github.com/jenkinsci/docker-commons-plugin/commit/97815b0654d91646602b608e4c0b05d3947d434b. https://github.com/jenkinsci/docker-commons-plugin/pull/45 addresses the 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] [openstack-cloud-plugin] (JENKINS-29694) AssertionError: Unknown credential type configured: null

[ogon...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29694 
 
 
 
  AssertionError: Unknown credential type configured: null  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oliver Gondža 
 
 
 
 
 
 
 
 
 
 There is no form validation for the credential field and the error message is quite cryptic :{noformat}WARNING: Provisioned slave template-a failed to launchjava . lang.AssertionError: Unknown credential type configured: null  at jenkins.plugins.openstack.compute.JCloudsSlaveTemplate.get(JCloudsSlaveTemplate.java:230)  at jenkins.plugins.openstack.compute.JCloudsSlaveTemplate.provisionSlave(JCloudsSlaveTemplate.java:164)  at jenkins.plugins.openstack.compute.JCloudsCloud$2.call(JCloudsCloud.java:221)  at jenkins.plugins.openstack.compute.JCloudsCloud$2.call(JCloudsCloud.java:218)  at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)  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){noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [openstack-cloud-plugin] (JENKINS-29694) AssertionError: Unknown credential type configured: null

[ogon...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29694 
 
 
 
  AssertionError: Unknown credential type configured: null  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Marat Mavlyutov 
 
 
 

Components:
 

 openstack-cloud-plugin 
 
 
 

Created:
 

 29/Jul/15 7:59 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Oliver Gondža 
 
 
 
 
 
 
 
 
 
 
There is no form validation for the credential field and the error message is quite cryptic. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[JIRA] [docker-build-publish-plugin] (JENKINS-29627) JSONException: null object when interacting with Docker Hub Registry

[jenkins...@carlossanchez.eu (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Carlos Sanchez commented on  JENKINS-29627 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JSONException: null object when interacting with Docker Hub Registry  
 
 
 
 
 
 
 
 
 
 
Seems it is this issue https://github.com/jenkinsci/docker-commons-plugin/pull/45 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-build-publish-plugin] (JENKINS-29627) JSONException: null object when interacting with Docker Hub Registry

[jenkins...@carlossanchez.eu (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Carlos Sanchez updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29627 
 
 
 
  JSONException: null object when interacting with Docker Hub Registry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Carlos Sanchez 
 
 
 

Component/s:
 
 docker-commons-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] [digitalocean-plugin] (JENKINS-29404) Unable to add/save droplet with custom image

[p...@xpg.dk (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Fleischer commented on  JENKINS-29404 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to add/save droplet with custom image  
 
 
 
 
 
 
 
 
 
 
I think this is fairly simple to fix by storing the imageId rather than the slug. However, I fear that it has a negative impact when official images are updated – it will either use an outdated image, or a non-existing one. I'm not quite sure how Digital Ocean updates its official images. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-import-plugin] (JENKINS-22942) Job Import Plugin: Password field is cleartext

[aubert...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexandre Aubert commented on  JENKINS-22942 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Job Import Plugin: Password field is cleartext  
 
 
 
 
 
 
 
 
 
 
it's indeed really sad to display password as cleartext on 'import settings' page 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-import-plugin] (JENKINS-23807) Support jobs in folders

[aubert...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexandre Aubert commented on  JENKINS-23807 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support jobs in folders  
 
 
 
 
 
 
 
 
 
 
it would be nice indeed to be able to import jobs from subfolders 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.